Forget to address the serial output:
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 156kB init memory.
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=000100f0
(XEN) ioapic_guest_write: old_entry=00010000 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=000100f0
(XEN) ioapic_guest_write: old_entry=000000f0 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1445: dom0: pirq 0 or irq 3 already mapped
(XEN) ioapic_guest_write: apic=0, pin=4, irq=4
(XEN) ioapic_guest_write: new_entry=000100f1
(XEN) ioapic_guest_write: old_entry=000000f1 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1445: dom0: pirq 0 or irq 5 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 6 already mapped
(XEN) irq.
c:1445: dom0: pirq 0 or irq 7 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 8 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 9 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 10 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 11 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 12 already mapped
(XEN) irq.c:1445: dom0: pirq 0 or irq 13 already mapped
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=000000f0
(XEN) ioapic_guest_write: old_entry=00010000 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=23, irq=23
(XEN) ioapic_guest_write: new_entry=0001a0d0
(XEN) ioapic_guest_write: old_entry=0000a0d0 pirq=23
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=18, irq=18
(XEN) ioapic_guest_write: new_entry=0001a0a8
(XEN) ioapic_guest_write: old_e
ntry=0000a0a8 pirq=18
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=18, irq=18
(XEN) ioapic_guest_write: new_entry=0001a0a8
(XEN) ioapic_guest_write: old_entry=0000a0a8 pirq=18
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
From: tinnycloud@xxxxxxxxxxx
To: james.harper@xxxxxxxxxxxxxxxx
CC: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] RE: blue screen in windows balloon driver
Date: Mon, 14 Mar 2011 10:24:14 +0800
Hi James:
I am still working on the blue screen issue.
This time I found 6 more machines to test. Two machines confronts a new blue screen in
2 days long test.
KERNEL_STACK_INPAGE_ERROR
stop:0x00000077(0xc0000185,0xc0000185,0x00000000,0x009d9000)
Attached is the log, cp1, 9, 15, 16, 17, 20, are broken, and has the log like:
-----------------------------
12944494073046: XenVbd --> XenVbd_HwScsiResetBus
12944494073046: XenVbd IRQL = 31
12944494073046: XenVbd Completing in-flight srb 892C7058 with status SRB_STATUS_BUS_RESET
12944494073046: XenVbd <-- XenVbd_HwScsiResetBus
12944494073046: XenPCI Grant Entry 16382 for ISCS still in use by ISCS
12944494073046:
*** Assertion failed: !xpdd->gnttb
l_table[ref].flags
*** Source File: e:\download\win-pvdrivers.hg\xenpci\gnttbl.c, line 120
---------------------------
Thanks.
> From: james.harper@xxxxxxxxxxxxxxxx
> To: tinnycloud@xxxxxxxxxxx
> Subject: RE: [Xen-devel] RE: blue screen in windows balloon driver
> Date: Thu, 3 Mar 2011 20:21:40 +0800
>
> I've just pushed a fix that would cause a loop then a crash in the event
> of a concurrent write.
>
> James
>
> > -----Original Message-----
> > From: MaoXiaoyun [mailto:tinnycloud@xxxxxxxxxxx]
> > Sent: Thursday, 3 March 2011 23:18
> > To: James Harper
> > Subject: RE: [Xen-devel] RE: blue screen in windows balloon driver
> >
> > Well, quite strange is no blue screen show up now.
> > Should have some VMS got crash according to previous test result.
> >
> > I will restart the t
est again.
> >
> > > Subject: RE: [Xen-devel] RE: blue screen in windows balloon driver
> > > Date: Thu, 3 Mar 2011 22:44:12 +1100
> > > From: james.harper@xxxxxxxxxxxxxxxx
> > > To: tinnycloud@xxxxxxxxxxx
> > >
> > > >
> > > > Two VM restart during the test.
> > > > From the log, I guess it is your fix, right?
> > > >
> > > > Log attatched.
> > > >
> > >
> > > It looks like at least one device failed to start up, probably due
> to
> > > delays in the backend. I don't know why it would shut down itself
> > > though.
> > >
> > > James
>
|
