http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1706
Summary: [VT-d] sometimes xen panic when run guest with NIC
assigned
Product: Xen
Version: unstable
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P1
Component: Hardware Support
AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
ReportedBy: yang.z.zhang@xxxxxxxxx
Environment:
------------
Service Arch (ia32/ia32e/IA64):ia32/ia32e
Guest Arch (ia32/ia32e/IA64):
Guest OS Type (Linux/Windows):Linux
Change Set: 22653
Hardware: Westmere-ep and Sandybridge
Other:
xen-changeset: 22653:7b4c82f07281
xen-date: Wed Jan 05 23:54:15 2011 +0000
xen-summary: QEMU_TAG update
pvops git:
commit 862ef97190f6b54d35c76c93fb2b8fadd7ab7d68
Merge: 7835387... 5823a82...
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
Date: Mon Dec 6 14:56:48 2010 -0800
ioemu git:
commit 99d53fbb69d3e03be61ae10506a304a3d08d792f
Author: Chun Yan Liu <cyliu@xxxxxxxxxx>
Date: Wed Jan 5 23:48:36 2011 +0000
tboot changeset:
changeset: 244:2532ddd46f57
tag: tip
user: Joseph Cihula <joseph.cihula@xxxxxxxxx>
date: Tue Nov 02 12:32:20 2010 -0700
summary: Fixed bug with PCONF elements not displaying correctly
Bug detailed description:
--------------------------
For the latest xen-unstable(c/s22653).when we run the guest with NIC
assigned,causing the xen panic sometimes. The error log from serial port as
following:
(XEN) >>> Domain 32 <<<
(XEN) VCPU 0
(XEN) *** Guest State ***
(XEN) CR0: actual=0x0000000000000038, shadow=0x0000000000000010,
gh_mask=ffffffffffffffff
(XEN) CR4: actual=0x0000000000002050, shadow=0x0000000000000000,
gh_mask=ffffffffffffffff
(XEN) CR3: actual=0x00000000feffe000, target_count=0
(XEN) target0=0000000000000000, target1=0000000000000000
(XEN) target2=0000000000000000, target3=0000000000000000
(XEN) RSP = 0x0000000000001f58 (0x0000000000001f58) RIP = 0x0000000000000545
(0x0000000000000546)
(XEN) RFLAGS=0x0000000000000202 (0x0000000000000202) DR7 = 0x0000000000000400
(XEN) Sysenter RSP=0000000000000000 CS:RIP=0000:0000000000000000
(XEN) CS: sel=0xf000, attr=0x0009f, limit=0x0000ffff, base=0x00000000000f0000
(XEN) DS: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000
(XEN) SS: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000
(XEN) ES: sel=0x7000, attr=0x00093, limit=0x0000ffff, base=0x0000000000070000
(XEN) FS: sel=0x0000, attr=0x00093, limit=0x0000ffff, base=0x0000000000000000
(XEN) GS: sel=0x0000, attr=0x00093, limit=0x0000ffff, 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 = ffffe63638d9a6a0
(XEN) DebugCtl=0000000000000000 DebugExceptions=0000000000000000
(XEN) Interruptibility=0000 ActivityState=0000
(XEN) *** Host State ***
(XEN) RSP = 0xffff83013e98ff90 RIP = 0xffff82c4801bff90
(XEN) CS=e008 DS=0000 ES=0000 FS=0000 GS=0000 SS=0000 TR=e040
(XEN) FSBase=0000000000000000 GSBase=0000000000000000 TRBase=ffff83013e997b00
(XEN) GDTBase=ffff83033e91f000 IDTBase=ffff83013e994010
(XEN) CR0=000000008005003b CR3=0000000311212000 CR4=00000000000026f0
(XEN) Sysenter RSP=ffff83013e98ffc0 CS:RIP=e008:ffff82c480205f80
(XEN) Host PAT = 0x0000050100070406
(XEN) *** Control State ***
(XEN) PinBased=0000003f CPUBased=b6a1e5fa SecondaryExec=000004eb
(XEN) EntryControls=000051ff ExitControls=000fefff
(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=01f70008
(XEN) IDTVectoring: info=00000000 errcode=00000000
(XEN) TPR Threshold = 0x00
(XEN) EPT pointer = 0x000000031121601e
(XEN) Virtual processor ID = 0x0001
(XEN) **************************************
(XEN) HVM32: *** int 15h function AX=ec00, BX=0002 not yet supported!
(XEN) HVM32: KBD: unsupported int 16h function 03
(XEN) HVM32: int13_harddisk: function 02, unmapped device for ELDL=82
(XEN) HVM32: int13_harddisk: function 41, unmapped device for ELDL=82
(XEN) domctl.c:1062:d0 ioport_map:remove f_gport=c100 f_mport=c000 np=40
(XEN) domctl.c:1038:d0 ioport_map:add f_gport=c100 f_mport=c000 np=40
(XEN) domctl.c:1062:d0 ioport_map:remove f_gport=c140 f_mport=d000 np=20
(XEN) domctl.c:1038:d0 ioport_map:add f_gport=c140 f_mport=d000 np=20
(XEN) irq.c:258: Dom32 PCI link 0 changed 5 -> 0
(XEN) irq.c:258: Dom32 PCI link 1 changed 10 -> 0
(XEN) irq.c:258: Dom32 PCI link 2 changed 11 -> 0
(XEN) irq.c:258: Dom32 PCI link 3 changed 5 -> 0
(XEN) ----[ Xen-4.1-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 23
(XEN) RIP: e008:[<ffff82c4801624c9>] do_IRQ+0x3b0/0x611
(XEN) RFLAGS: 0000000000010002 CONTEXT: hypervisor
(XEN) rax: 0000000000000070 rbx: ffff83013e90fd98 rcx: ffff82c4802d41c0
(XEN) rdx: 0000003cbe647180 rsi: 0000000000000084 rdi: ffff83013e90fce0
(XEN) rbp: ffff83013e90fd88 rsp: ffff83013e90fd18 r8: 0000000000000003
(XEN) r9: 0000000000000002 r10: ffff8300beee0060 r11: 00ff00ff00ff00ff
(XEN) r12: ffff83033ee70000 r13: ffff830101e24f50 r14: 0000000000000000
(XEN) r15: 0000000000000070 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 000000010367a000 cr2: 0000000000000070
(XEN) ds: 002b es: 002b fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff83013e90fd18:
(XEN) 000000000000001c 000000000000001c ffff83013fe00e80 0000000000000000
(XEN) 00000000802d3f80 ffff83013fe00e80 ffff82c48012088b ffff83033e9265b8
(XEN) ffff83013e91b240 ffff83013e90ff18 ffff83033e817d00 ffff83033e817d90
(XEN) 0000000000000002 ffff83013e91b040 00007cfec16f0247 ffff82c48015ad76
(XEN) ffff83013e91b040 0000000000000002 ffff83033e817d90 ffff83033e817d00
(XEN) ffff83013e90fef0 ffff83013e90ff18 00ff00ff00ff00ff ffff8300beee0060
(XEN) 0000000000000002 0000000000000003 0000000000000002 0000000000000001
(XEN) 0000000000000000 ffff83013e91bb98 00000936ce8b0401 0000008400000000
(XEN) ffff82c480197d20 000000000000e008 0000000000000297 ffff83013e90fe48
(XEN) 000000000000e010 ffff83013e90fef0 ffff82c48019940e 00000936d6e09316
(XEN) 00000936d6f68339 ffff83033e9265b8 ffff8300beef6000 ffffffffffffffff
(XEN) ffff83013e90fe00 ffff82c4801207c4 aaaaaaaaaaaaaaaa 0000000000000017
(XEN) 0000000000000017 0000000000000000 0000000000000000 ffff82c4802b4880
(XEN) 0000084f0000019d ffff82c480122e7a ffff83013e90ff18 ffff8300beef6000
(XEN) ffff8300beee0000 0000000000000002 ffff83013e91b040 ffff83013e90ff10
(XEN) ffff82c480153896 ffff82c480122fee 0000000000000017 ffff83013e90fd28
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) ffff88003fcf3f10 ffffffff818720d0 0000000000000246 00000000010ed976
(XEN) ffff88003fcf3df0 0000000000000000 0000000000000000 ffffffff810093aa
(XEN) ffff88003fcf3f20 00000000deadbeef 00000000deadbeef 0000010000000000
(XEN) Xen call trace:
(XEN) [<ffff82c4801624c9>] do_IRQ+0x3b0/0x611
(XEN) [<ffff82c48015ad76>] common_interrupt+0x26/0x30
(XEN) [<ffff82c480197d20>] lapic_timer_nop+0x0/0x6
(XEN) [<ffff82c480153896>] idle_loop+0x4d/0x5e
(XEN)
(XEN) Pagetable walk from 0000000000000070:
(XEN) L4[0x000] = 000000032b8e1067 000000000001471e
(XEN) L3[0x000] = 0000000103a12067 000000000003c5ed
(XEN) L2[0x000] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 23:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: 0000000000000070
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
Reproduce steps:
----------------
1.Prepare the guest and assign the NIC for it .
2.We seen xen panic sometimes.
Current result:
----------------
Xen panic
Expected result:
----------------
Successful
Basic root-causing log:
----------------------
--
Configure bugmail:
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
Home