|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Bug: Windows 2003 fails to install on xen-unstable tip
On 22/04/13 12:05, Jan Beulich wrote: On 19.04.13 at 15:51, George Dunlap <george.dunlap@xxxxxxxxxxxxx> wrote:(XEN) HVM1: Booting from DVD/CD... (XEN) HVM1: Booting from 0000:7c00 (XEN) HVM1: pnp call arg1=0 [ 75.071460] xenbr0: port 3(vif1.0-emu) entering forwarding state (XEN) pt on: 10 (XEN) B=42 [A:2a B:02 C:50 pt:10/0] (XEN) C=50 pt=10/0 (XEN) C=c0 pt=10/0 (XEN) C=00 pt=10/0 (XEN) C=c0 pt=10/0 (XEN) C=00 pt=10/0 (XEN) pt off @87Odd - both the fact that apparently two to four interrupt instances arrive, and the fact that REG_C gets read two times when supposedly there was no interrupt. The latter may be indicative of a re-read near the end of the interrupt handler (i.e. checking whether more work is to do), which is why I added time stamps in the new version of the patch. The time stamps should also help understanding whether turning off the periodic timer really happens with due distance to the last interrupt instance (also increasing the gap from 10 to 250). Plus the patch now adds tracking of when the last RTC interrupt got triggered. I also retained the NetBSD fixes in here, as I don't think they would harm Windows, and ultimately we want them committed unless we need to do some sort of revert. Jan --- a/xen/arch/x86/hvm/rtc.c +++ b/xen/arch/x86/hvm/rtc.c @@ -50,6 +50,23 @@ static void rtc_set_time(RTCState *s); static inline int from_bcd(RTCState *s, int a); static inline int convert_hour(RTCState *s, int hour);+#include <xen/symbols.h>//temp (XEN) pt on: 10 @14fd4b61ef^M (XEN) B=42 [A:2a B:02 C:50 pt:10/0] @14fd6f73d9^M (XEN) C=50 pt=10/0 @14fdb032f8^M (XEN) C=c0 pt=10/6 @14fddabc31^M (XEN) C=00 pt=10/0 @14fe04d583^M (XEN) C=c0 pt=10/0 @14feaa9978^M (XEN) C=00 pt=10/0 @14fed2ae4b^M (XEN) C=c0 pt=10/0 @14ff98fe90^M (XEN) C=00 pt=10/0 @14ffc0fbc1^M (XEN) irq.c:270: Dom1 PCI link 0 changed 5 -> 0^M (XEN) irq.c:270: Dom1 PCI link 1 changed 10 -> 0^M (XEN) irq.c:270: Dom1 PCI link 2 changed 11 -> 0^M (XEN) irq.c:270: Dom1 PCI link 3 changed 5 -> 0^M (XEN) pt off #105 @15e95c8ff8^M (XEN) pt irq @15da75fb9c (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15db644b09 (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15dc53074a (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15dd41309b (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15de2f93db (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15df1e6232 (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e00c3c2f (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e0faca4c (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e1e94f41 (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e2d7b303 (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e3c61780 (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e4b4cd99 (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e5a33c65 (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e690a53a (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e77f1d0f (rtc_periodic_interrupt+0x81/0x93)^M (XEN) pt irq @15e86d876a (rtc_periodic_interrupt+0x81/0x93)^M Full log attached... -George Attachment:
kodo2.log _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |