This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1747] New: Sometimes Xen panic on ia32pae Sandybridge wh

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1747] New: Sometimes Xen panic on ia32pae Sandybridge when restore guest
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 27 Feb 2011 18:35:36 -0800
Delivery-date: Sun, 27 Feb 2011 18:35:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Sometimes Xen panic on ia32pae Sandybridge when restore
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: yang.z.zhang@xxxxxxxxx

Service Arch (ia32/ia32e/IA64): ia32
Guest Arch (ia32/ia32e/IA64): 
Guest OS Type (Linux/Windows):Linux
Change Set: 22940
xen-changeset:   22940:5a4710640f81
xen-date:        Thu Feb 17 19:52:20 2011 +0000

pvops git:
commit 75cc13f5aa29b4f3227d269ca165dfa8937c94fe
Merge: 2607c07... a386bf7...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>

ioemu git:
commit e073e69457b4d99b6da0b6536296e3498f7f6599
Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date:   Fri Feb 11 17:54:51 2011 +0000

Bug detailed description:
For the latest xen unstable(cs 22940).We found xen panic when we restore guest
under ia32pae Sandybridge.There are some xen call
trace as following . Pls check it.

(XEN) >>> Domain 4 <<<
(XEN)   VCPU 0
(XEN) *** Guest State ***
(XEN) CR0: actual=0x0000000000000039, shadow=0x0000000000000011,
(XEN) CR4: actual=0x0000000000002050, shadow=0x0000000000000000,
(XEN) CR3: actual=0x00000000feffe000, target_count=0
(XEN)      target0=0000000000000000, target1=0000000000000000
(XEN)      target2=0000000000000000, target3=0000000000000000
(XEN) RSP = 0x0000000000067e3c (0x0000000000067e3c)  RIP = 0x000000000001b20c
(XEN) RFLAGS=0x0000000000000046 (0x0000000000000046)  DR7 = 0x0000000000000400
(XEN) Sysenter RSP=0000000000000000 CS:RIP=0000:0000000000000000
(XEN) CS: sel=0x0008, attr=0x0c09b, limit=0xffffffff, base=0x0000000000000000
(XEN) DS: sel=0x0010, attr=0x0c093, limit=0xffffffff, base=0x0000000000000000
(XEN) SS: sel=0x0010, attr=0x0c093, limit=0xffffffff, base=0x0000000000000000
(XEN) ES: sel=0x0010, attr=0x0c093, limit=0xffffffff, base=0x0000000000000000
(XEN) FS: sel=0x0010, attr=0x0c093, limit=0xffffffff, base=0x0000000000000000
(XEN) GS: sel=0x0010, attr=0x0c093, limit=0xffffffff, base=0x0000000000000000
(XEN) GDTR:                           limit=0x00000027, base=0x0000000000009040
(XEN) LDTR: sel=0x0000, attr=0x00082, limit=0x00000000, base=0x0000000000000000
(XEN) IDTR:                           limit=0x000003ff, base=0x0000000000000000
(XEN) TR: sel=0x0000, attr=0x0008b, limit=0x000000ff, base=0x0000000000000000
(XEN) Guest PAT = 0x0007040600070406
(XEN) TSC Offset = fffffeb172316197
(XEN) DebugCtl=0000000000000000 DebugExceptions=0000000000000000
(XEN) Interruptibility=0000 ActivityState=0000
(XEN) *** Host State ***
(XEN) RSP = 0x00000000ffbdffcc  RIP = 0x00000000ff1ac0e0
(XEN) CS=e008 DS=e010 ES=e010 FS=0000 GS=0000 SS=e010 TR=e040
(XEN) FSBase=0000000000000000 GSBase=0000000000000000 TRBase=00000000ffbe3980
(XEN) GDTBase=00000000ffbcd000 IDTBase=00000000ffbda008
(XEN) CR0=000000008005003b CR3=0000000076e2c000 CR4=00000000000426f0
(XEN) Sysenter RSP=00000000ffbdffe4 CS:RIP=0000:0000000000000000
(XEN) Host PAT = 0x0000050100070406
(XEN) *** Control State ***
(XEN) PinBased=0000003f CPUBased=b6a1e5fe SecondaryExec=000000eb
(XEN) EntryControls=000051ff ExitControls=000fedff
(XEN) ExceptionBitmap=000400c0
(XEN) VMEntry: intr_info=00000008 errcode=00000000 ilen=00000000
(XEN) VMExit: intr_info=00000000 errcode=00000000 ilen=00000000
(XEN)         reason=0000001e qualification=03c40000
(XEN) IDTVectoring: info=00000000 errcode=00000000
(XEN) TPR Threshold = 0x00
(XEN) EPT pointer = 0x00000000773c901e
(XEN) Virtual processor ID = 0x2fee
(XEN) **************************************
(XEN) HVM4: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) HVM4: KBD: unsupported int 16h function 03
(XEN) HVM4: int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) HVM4: *** int 15h function AX=e980, BX=e6f5 not yet supported!
(XEN) HVM4: int13_harddisk: function 02, unmapped device for ELDL=81
(XEN) HVM4: int13_harddisk: function 41, unmapped device for ELDL=81
[  446.317105] vif4.0: no IPv6 routers present
(XEN) irq.c:258: Dom4 PCI link 0 changed 5 -> 0
(XEN) irq.c:258: Dom4 PCI link 1 changed 10 -> 0
(XEN) irq.c:258: Dom4 PCI link 2 changed 11 -> 0
(XEN) irq.c:258: Dom4 PCI link 3 changed 5 -> 0
[  446.741321] tap4.0: no IPv6 routers present
[  451.202524] xenbr0: port 2(vif4.0) entering forwarding state
[  451.376746] xenbr0: port 3(tap4.0) entering forwarding state
(XEN) irq.c:324: Dom4 callback via changed to PCI INTx Dev 0x03 IntA
[  493.066772] device xenbr0 left promiscuous mode
(XEN) save.c:162:d0 HVM save: CPU
(XEN) save.c:162:d0 HVM save: PIC
(XEN) save.c:162:d0 HVM save: IOAPIC
(XEN) save.c:162:d0 HVM save: LAPIC
(XEN) save.c:162:d0 HVM save: LAPIC_REGS
(XEN) save.c:162:d0 HVM save: PCI_IRQ
(XEN) save.c:162:d0 HVM save: ISA_IRQ
(XEN) save.c:162:d0 HVM save: PCI_LINK
(XEN) save.c:162:d0 HVM save: PIT
(XEN) save.c:162:d0 HVM save: RTC
(XEN) save.c:162:d0 HVM save: HPET
(XEN) save.c:162:d0 HVM save: PMTIMER
(XEN) save.c:162:d0 HVM save: MTRR
(XEN) save.c:162:d0 HVM save: VIRIDIAN
(XEN) save.c:162:d0 HVM save: CPU_XSAVE
[  598.526048] vif vif-4-0: 2 reading script
[  598.537178] xenbr0: port 3(tap4.0) entering disabled state
[  598.591223] device tap4.0 left promiscuous mode
[  598.596225] xenbr0: port 3(tap4.0) entering disabled state
[  598.619657] xenbr0: port 2(vif4.0) entering disabled state
[  598.638034] device vif4.0 left promiscuous mode
[  598.643008] xenbr0: port 2(vif4.0) entering disabled state
(XEN) [VT-D]iommu.c:1785: VT-d page table not sharing with EPT table
(XEN) save.c:234:d0 HVM restore: CPU 0
(XEN) save.c:234:d0 HVM restore: PIC 0
(XEN) save.c:234:d0 HVM restore: PIC 1
(XEN) save.c:234:d0 HVM restore: IOAPIC 0
(XEN) save.c:234:d0 HVM restore: LAPIC 0
(XEN) save.c:234:d0 HVM restore: LAPIC_REGS 0
(XEN) save.c:234:d0 HVM restore: PCI_IRQ 0
(XEN) save.c:234:d0 HVM restore: ISA_IRQ 0
(XEN) save.c:234:d0 HVM restore: PCI_LINK 0
(XEN) save.c:234:d0 HVM restore: PIT 0
(XEN) save.c:234:d0 HVM restore: RTC 0
(XEN) save.c:234:d0 HVM restore: HPET 0
(XEN) save.c:234:d0 HVM restore: PMTIMER 0
(XEN) save.c:234:d0 HVM restore: MTRR 0
(XEN) save.c:234:d0 HVM restore: CPU_XSAVE 0
(XEN) irq.c:324: Dom5 callback via changed to PCI INTx Dev 0x03 IntA
[  664.576702] ------------[ cut here ]------------
[  664.581762] kernel BUG at
[  664.596986] invalid opcode: 0000 [#1] SMP
[  664.601638] last sysfs file: /sys/class/net/tap5.0/address
[  664.607843] Modules linked in: nfs nfs_acl auth_rpcgss lockd sunrpc sg igbvf
sr_mod cdrom igb tpm_tis tpm tpm_bios pata_acpi ata_generic ata_piix ide_gd_mod
ide_core ahci libata sd_mod scsi_mod uhci_hcd ohci_hcd ehci_hcd
[  664.629754]
[  664.631499] Pid: 40, comm: xenwatch Not tainted ( #1) SandyBridge
[  664.640131] EIP: 0061:[<c104b6ed>] EFLAGS: 00010082 CPU: 5
[  664.646336] EIP is at vmalloc_sync_one+0xbd/0xcd
[  664.651569] EAX: 0055b300 EBX: ffffffff ECX: ffffffe0 EDX: 00000000
[  664.658649] ESI: 00000fff EDI: c1821b68 EBP: ec9a7eb4 ESP: ec9a7e90
[  664.665726]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
[  664.671832] Process xenwatch (pid: 40, ti=ec9a6000 task=ec903cc0
[  664.680365] Stack:
[  664.682692]  bbdb9545 0000009a eb2474c4 ec9a7eb4 76c76067 00000000 eb2474c4
[  664.691127] <0> c22cfc20 ec9a7ed4 c104bc63 ed6d8000 c1821b60 c1780204
ec978660 e936cb40
[  664.700145] <0> 00000301 ec9a7ee0 c10d48bd fffffff4 ec9a7f30 c11ff353
00000300 00000000
[  664.709453] Call Trace:
[  664.712269]  [<c104bc63>] ? vmalloc_sync_all+0x5e/0xc0
[  664.718084]  [<c10d48bd>] ? alloc_vm_area+0x44/0x4b
[  664.723611]  [<c11ff353>] ? netif_map+0x40/0x1d5
[  664.728846]  [<c11f55ed>] ? xenbus_read+0x36/0x41
[  664.734177]  [<c11f5690>] ? xenbus_scanf+0x18/0x4e
[  664.739607]  [<c11feb14>] ? frontend_changed+0x2a5/0x510
[  664.745620]  [<c11f64b7>] ? xenbus_otherend_changed+0x5c/0x61
[  664.752114]  [<c11f6587>] ? frontend_changed+0xa/0xd
[  664.757738]  [<c11f5b4a>] ? xenwatch_thread+0xd4/0x10a
[  664.763555]  [<c1076e19>] ? autoremove_wake_function+0x0/0x33
[  664.770075]  [<c1076c9e>] ? kthread+0x58/0x5d
[  664.775019]  [<c11f5a76>] ? xenwatch_thread+0x0/0x10a
[  664.780741]  [<c1076c46>] ? kthread+0x0/0x5d
[  664.785586]  [<c102fc77>] ? kernel_thread_helper+0x7/0x10
[  664.791692] Code: 06 8b 56 04 e8 c3 fe ff ff 89 c3 89 d6 8b 07 8b 57 04 0f
ac f3 0c e8 b1 fe ff ff 89 d9 c1 e1 05 0f ac d0 0c c1 e0 05 39 c1 74 06 <0f> 0b
eb fe 31 ff 83 c4 18 89 f8 5b 5e 5f 5d c3 55 83 3d 0c 44
[  664.812830] EIP: [<c104b6ed>] vmalloc_sync_one+0xbd/0xcd SS:ESP
[  664.820880] ---[ end trace db56f78f6f5ad721 ]---
GRUB Loading stage2..                                                          
Press any key to continue.
Press any key to continue.                                                      

Reproduce steps:
1.Create a guest by "xl create config"
2.Using xl save to  save guest.
3.Using xl restore to restore guest

Current result:
Will see Xen panic sometimes

Expected result:
Successful to do restore

Basic root-causing log:

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>