xen-devel
RE: [Xen-devel] RE: blue screen in windows balloon driver
To: |
<james.harper@xxxxxxxxxxxxxxxx> |
Subject: |
RE: [Xen-devel] RE: blue screen in windows balloon driver |
From: |
MaoXiaoyun <tinnycloud@xxxxxxxxxxx> |
Date: |
Mon, 14 Mar 2011 10:57:17 +0800 |
Cc: |
tinnycloud@xxxxxxxxxxx, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
Delivery-date: |
Sun, 13 Mar 2011 19:58:26 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
Importance: |
Normal |
In-reply-to: |
<BLU157-w2726FD166F4A1231D33002DACC0@xxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<BLU157-w6407B20CA375D42DAB1348DADC0@xxxxxxx><AEC6C66638C05B468B556EA548C1A77D01C559AC@trantor><BLU157-w56096891695C107FBB1243DADE0@xxxxxxx><BLU157-w3689F78415A43CC5997DD7DADE0@xxxxxxx><BLU157-w7B83FF68CB4CEE8B140C6DADE0@xxxxxxx><AEC6C66638C05B468B556EA548C1A77D01C55A4E@trantor><BLU157-w38E9B522F8710956C4992ADAC10@xxxxxxx>, <BE58E0A1-AE23-4274-9644-24DB8456512D@xxxxxxxxxxxxxxxx><BLU157-w9D31FCDD666C6D7BD73CEDAC10@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55AC7@trantor><BLU157-w655070D9CFE092D78C011DDAC10@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55ACA@trantor><BLU157-w172C0AC95FCE2C2B836BDBDAC10@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55ACC@trantor>, <AEC6C66638C05B468B556EA548C1A77D01C55ACD@trantor>, <BLU157-w35E669BF00DC04327E4E93DAC00@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55B39@trantor>, <BLU157-w3311FE380E5D57DD810827DAC00@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55B44@trantor>, <BLU157-w564C179CAAF26EC5D7559DAC00@xxxxxxx>, <AEC6C66638C05B468B556EA548C, , , ,,,1A77D 01, C, 5, 5, B, 4, 6@trantor>, <BLU157-w446CEE35E592FE12EF0180DAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55B88@trantor>, <BLU157-w5382FC5FCC26C6EE8EC18BDAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BB3@trantor>, <BLU157-w62FFC7240FD65345A0B3A8DAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BB7@trantor>, <BLU157-w30368B861A4BFFF8A8DB9DDAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BBA@trantor>, <BLU157-w28F0FE7DA9D129E9003136DAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BBD@trantor>, <BLU157-w826F2EDB9C1A7077BA524DAC30@xxxxxxx>, <019001cbdd41$1ccfbc20$566f3460$@harper@bendigoit.com.au>, <BLU157-w2726FD166F4A1231D33002DACC0@xxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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 >
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|