[Bug 490770] New: crash @ pci passthrough of pci/sata device to DomU
https://bugzilla.novell.com/show_bug.cgi?id=490770 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490770#c1 Summary: crash @ pci passthrough of pci/sata device to DomU Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: pgnet.trash@gmail.com QAContact: qa@suse.de Found By: --- Created an attachment (id=283232) --> (https://bugzilla.novell.com/attachment.cgi?id=283232) xen console output for failed domu boot User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 this is referenced split from: "Bug 489846 - pci passthrough error non-page-aligned MMIO BAR found" https://bugzilla.novell.com/show_bug.cgi?id=489846 any help debuggung/fixing this is, of course, appreciated! i'm running openSUSE 11.1, uname -ri 2.6.27.21-7-xen x86_64 booting to Xen, @grub title Xen root (hd0,0) kernel /xen.gz dom0_mem=768M vga=gfx-1280x1024x32 console=vga,com1 com1=57600,8n1 module /vmlinuz-xen root=/dev/VG_Dom0/LV_ROOT resume=/dev/VG_Swap/LV_SWAP vga=0x31a console=tty0 console=xvc0,57600 elevator=cfq max_loop=64 pci_devs_to_hide=(04:07.0)(00:14.0)(04:08.0) reassigndev=0004:07.0 module /initrd-xen passing through two devices to the DomU, cat nas.cfg ... pci = [ '04:07.0', '04:08.0' ] ... where, lspci | egrep "04:07.0|04:08.0" 04:07.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02) 04:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0) NOTE: really only want/need "04:08.0", but "04:07.0" needs to come along for the ride (cref: "Bug 489735 - pci passthrough of sata_sil24 device requires that firewire must be co-assigned to the same guest" https://bugzilla.novell.com/show_bug.cgi?id=48973 ) crashes @, xm create -c nas.cfg @console shown below; full output @ Dom0 & DomU is attached ... .. sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA vol_id[790]: segfault at 0 ip 0000000000000000 sp 00007ffffdb25220 error 14 in vol_id[400000+5000] ------------[ cut here ]------------ kernel BUG at mm/mmap.c:2145! invalid opcode: 0000 [1] SMP last sysfs file: /sys/devices/xen/pci-0/pci0000:00/0000:00:01.0/host1/target1:0:0/1:0:0:0/type CPU 0 Modules linked in: sg sd_mod crc_t10dif sata_sil24 libata ohci1394 scsi_mod forcedeth ieee1394 dock rtc_core rtc_lib joydev linear dm_snapshot dm_mod ext3 jbd mbcache xennet xenblk cdrom Supported: Yes Pid: 790, comm: vol_id Not tainted 2.6.27.21-4-xen #1 RIP: e030:[<ffffffff8028a96b>] [<ffffffff8028a96b>] exit_mmap+0xe6/0xf2 RSP: e02b:ffff8800172ddd78 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff8800013a0140 RCX: 0000000000000045 RDX: ffffffffff5fc000 RSI: ffff880016e9d820 RDI: ffff88001780f680 RBP: 0000000000000000 R08: 0000000000000000 R09: ffff880001d92200 R10: 0000000000000010 R11: ffffffff80320c8f R12: ffff880016e9d7c0 R13: ffff880016e9d820 R14: ffff8800172ddf58 R15: ffff8800172ddf08 FS: 00007fe1f5b12780(0000) GS:ffffffff80761080(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process vol_id (pid: 790, threadinfo ffff8800172dc000, task ffff8800168642c0) Stack: 000000000000007d ffff8800013a0140 ffff880016e9d7c0 ffff8800168642c0 ffff880016e9d7c0 ffffffff80230eaa ffff8800168648ac ffffffff80234adf 0000000001241000 ffff8800168642c0 0000000000000001 ffff8800168642c0 Call Trace: [<ffffffff80230eaa>] mmput+0x20/0xbc [<ffffffff80234adf>] exit_mm+0x101/0x10c [<ffffffff80236907>] do_exit+0x208/0x304 [<ffffffff80236aa2>] do_group_exit+0x9f/0xcb [<ffffffff8024028f>] get_signal_to_deliver+0x3b0/0x405 [<ffffffff8020ad3e>] do_signal+0x64/0x191 [<ffffffff8020ae78>] do_notify_resume+0xd/0x2c [<ffffffff8020ba3e>] retint_signal+0x57/0xa9 Code: 7b 18 e8 b5 76 00 00 c7 43 08 00 00 00 00 eb 0b 48 89 ef e8 d4 fe ff ff 48 89 c5 48 85 ed 75 f0 49 83 bc 24 e8 00 00 00 00 74 04 <0f> 0b eb fe 5f 41 58 5b 5d 41 5c c3 41 56 41 be f4 ff ff ff 41 RIP [<ffffffff8028a96b>] exit_mmap+0xe6/0xf2 RSP <ffff8800172ddd78> ---[ end trace de6d924e597e88a3 ]--- Fixing recursive fault but reboot is needed! ---------> xm destroy nas Adding 524280k swap on /dev/mapper/vg0-lv_swap. Priority:-1 extents:1 across:524280k general protection fault: 0000 [2] SMP last sysfs file: /sys/kernel/uevent_seqnum CPU 0 Modules linked in: sg sd_mod crc_t10dif sata_sil24 libata ohci1394 scsi_mod forcedeth ieee1394 dock rtc_core rtc_lib joydev linear dm_snapshot dm_mod ext3 jbd mbcache xennet xenblk cdrom Supported: Yes Pid: 829, comm: vgscan Tainted: G D 2.6.27.21-4-xen #1 RIP: e030:[<ffffffff802ee780>] [<ffffffff802ee780>] sysfs_readdir+0xd9/0x13e RSP: e02b:ffff8800172dfeb8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff8800178fcd20 RCX: ffffffffffffffff RDX: 0000000000000000 RSI: 14ed7f01c5e864b0 RDI: 14ed7f01c5e864b0 RBP: ffff880016e953c0 R08: 0000000000000aaa R09: 000000000000000a R10: 0000000013a97e56 R11: ffffffff803211c1 R12: ffffffff802aabbc R13: ffff8800172dff38 R14: 0000000000000000 R15: ffffffffffffffff FS: 00007fbcf58e0780(0000) GS:ffffffff80761080(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process vgscan (pid: 829, threadinfo ffff8800172de000, task ffff880016420300) Stack: 0000000013a97e56 00000000fffffffe ffff880016e953c0 ffff88001749d6e0 ffff88001749d798 ffffffff802aabbc ffff8800172dff38 ffffffff802aae3f 00000000000000ff 00000000fffffff7 ffff880016e953c0 0000000000000000 Call Trace: [<ffffffff802aae3f>] vfs_readdir+0x75/0xa7 [<ffffffff802aaeeb>] sys_getdents64+0x7a/0xbf [<ffffffff8020b3b8>] system_call_fastpath+0x16/0x1b [<00007fbcf40f4f3a>] 0x7fbcf40f4f3a Code: 61 17 00 48 8b 5b 28 eb 04 48 8b 5b 10 48 85 db 74 74 48 8b 43 38 48 39 45 38 77 ed eb 40 48 8b 73 18 44 88 f0 4c 89 f9 48 89 f7 <f2> ae 4c 89 ef 48 f7 d1 48 8d 41 ff 48 8b 4b 38 89 c2 48 89 4d RIP [<ffffffff802ee780>] sysfs_readdir+0xd9/0x13e RSP <ffff8800172dfeb8> ---[ end trace de6d924e597e88a3 ]--- Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490770 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490770#c1 --- Comment #1 from pgnet _ <pgnet.trash@gmail.com> 2009-03-31 10:27:06 MDT --- Created an attachment (id=283233) --> (https://bugzilla.novell.com/attachment.cgi?id=283233) Dom0 syslog output for failed DomU boot -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490770 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |ASSIGNED Found By|--- |Community User AssignedTo|cgriffin@novell.com |jbeulich@novell.com QAContact|qa@suse.de |jdouglas@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=490770 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=490770#c2 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |pgnet.trash@gmail.com --- Comment #2 from Jan Beulich <jbeulich@novell.com> 2009-04-01 02:25:58 MDT --- The crashes in the description have nothing in common with the crash in the DomU log - please clarify what the deal is here. Also, we will need the *full* hypervisor/dom0 log (with loglvl=all guest_loglvl=all added to the Xen command line), not just a fragment from /var/log/messages. In case you force pciback to load early, I'd also like to ask to provide us with a native kernel's boot messages in order to identify where in the loading of the drivers for the passed through devices the problems begin. Further, reducing the complexity would certainly help isolating the real issue here (which seems to start with the drive identification itself having issues, and perhaps even with the loading of the forcedeth driver), so for debugging purposes - passing through any other devices (namely the NIC) should be avoided - passing through the SATA controller should intially be done without any complex disk configurations attached, ideally even without any disk that is needed during boot of the guest (in particular, its root and swap volumes). Finally, without knowing how much memory the system has (due to the lack of complete logs), it might be that your setup is simply missing a swiotlb= option on the DomU kernel command line. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com