[Xen-devel] [xen-unstable 4.1][2.6.31.13-pvops] xend[6678] general protection ip:7fb1fee83010 sp:433528d8 error:0 in libc-2.7.so[7fb1fee08000+14a000]

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Hi All,

Tried xen-unstable 4.1 today on a machine runnning fine on 4.0-rc6.


Previous working setup:
- Xen-4.0.0-rc6.gz
- Dom0 Kernel 2.6.31.12-pvops
- Debian GNU/Linux Lenny

- PCI passthrough of 3 USB controllers and one sound card


Tried:
- Xen-4.1-unstable
- Dom0 Kernel 2.6.31.13-pvops
- Debian GNU/Linux Lenny


Symptoms:
- Guests can't be started

output in dmesg:
[   47.254604] xend[6678] general protection ip:7fb1fee83010 sp:433528d8 
error:0 in libc-2.7.so[7fb1fee08000+14a000]
[   48.655418] xend[6743] general protection ip:7fb1fee83010 sp:43e788d8 
error:0 in libc-2.7.so[7fb1fee08000+14a000]
[   50.072068] xend[6808] general protection ip:7fb1fee83010 sp:444f18d8 
error:0 in libc-2.7.so[7fb1fee08000+14a000]
[   51.490593] xend[6873] general protection ip:7fb1fee83010 sp:43fb28d8 
error:0 in libc-2.7.so[7fb1fee08000+14a000]
[   52.864337] xend[6938] general protection ip:7fb1fee83010 sp:43fa48d8 
error:0 in libc-2.7.so[7fb1fee08000+14a000]



also in dmesg, but of less importance i guess:
[    0.000999] ------------[ cut here ]------------
[    0.000999] WARNING: at 
/usr/src/xen-unstable.hg/linux-2.6-pvops.git/arch/x86/xen/enlighten.c:722 
xen_apic_write+0x15/0x17()
[    0.000999] Hardware name: System Product Name
[    0.000999] Modules linked in:
[    0.000999] Pid: 0, comm: swapper Not tainted 2.6.31.13 #3
[    0.000999] Call Trace:
[    0.000999]  [<ffffffff81020ff9>] ? mce_init_timer+0x8f/0x98
[    0.000999]  [<ffffffff8100b3a6>] ? xen_apic_write+0x15/0x17
[    0.000999]  [<ffffffff8104bd20>] warn_slowpath_common+0x77/0xa4
[    0.000999]  [<ffffffff8104bd5c>] warn_slowpath_null+0xf/0x11
[    0.000999]  [<ffffffff8100b3a6>] xen_apic_write+0x15/0x17
[    0.000999]  [<ffffffff8101f4e3>] perf_counters_lapic_init+0x2e/0x30
[    0.000999]  [<ffffffff8199b02d>] init_hw_perf_counters+0x305/0x3a2
[    0.000999]  [<ffffffff8100f3ff>] ? xen_restore_fl_direct_end+0x0/0x1
[    0.000999]  [<ffffffff810da73c>] ? kmem_cache_alloc+0xcb/0x12d
[    0.000999]  [<ffffffff8199acf9>] identify_boot_cpu+0x3c/0x3e
[    0.000999]  [<ffffffff8199ad04>] check_bugs+0x9/0x2d
[    0.000999]  [<ffffffff819925ea>] start_kernel+0x41d/0x432
[    0.000999]  [<ffffffff81991adf>] x86_64_start_reservations+0xaa/0xae
[    0.000999]  [<ffffffff81995965>] xen_start_kernel+0x63a/0x641
[    0.000999] ---[ end trace 4eaa2a86a8e2da22 ]---



Don't know if it's important, but xm dmesg also ends with:
(XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others.
(XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others.
(XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others.
(XEN) irq.c:1182:d0 Cannot bind IRQ 0 to guest. Will not share with others.

Attached:
- xm info
- xm dmesg
- dmesg
- lspci -vvvknn

--
Sander

Attachment: dmesg.txt
Description: Text document

Attachment: lspci.txt
Description: Text document

Attachment: xm-dmesg.txt
Description: Text document

Attachment: xm-info.txt
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel