|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 1409] New: VT-d fault causes disk corrupted or Dom0 kernel panic.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1409 Summary: VT-d fault causes disk corrupted or Dom0 kernel panic. Product: Xen Version: unstable Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: Hypervisor AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx ReportedBy: haicheng.li@xxxxxxxxx We met different system failures on different hardware platforms, which are all caused by VT-d fault. ========================= err 1: disk is corrupted by VT-d fault on SATA. We can duplicate disk corruption with latest xen-unstable tree, caused by VT-d faults on the SATA controller. The last working changeset is 15053 from 1/16/2009. The culprit is changeset 19054 "x86_64: Remove statically-partitioned Xen heap.". ========================= err 2: Dom0 kernel panics at booting, which is caused VT-d fault on UHCI. If disble vt-d by passing "iommu=0" to xen, this panic disappears. here is the boot log: Loading usbcore.ko module usbcore: no version for "struct_module" found: kernel tainted. usbcore: registered new driver usbfs usbcore: registered new driver hub Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 (XEN) PCI add device 00:1d.0 GSI 22 sharing vector 0x29 and IRQ 22 ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 22 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:1d.0: irq 22, io base 0x00001800 (XEN) [VT-D]iommu.c:721: iommu_page_fault: iommu->reg = ffff828bfff53000 (XEN) [VT-D]iommu.c:693: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:675: iommu_fault:DMA Read: 0:1d.0 addr cfbef000 REASON 6 io0 (XEN) print_vtd_entries: iommu = ffff8300cfada850 bdf = 0:1d:0 gmfn = cfbef (XEN) root_entry = ffff83022fde0000 (XEN) root_entry[0] = 227ad2001 (XEN) context = ffff830227ad2000 (XEN) context[e8] = 102_22fddd001 (XEN) l4 = ffff83022fddd000 (XEN) l4_index = 0 (XEN) l4[0] = 22fddc003 (XEN) l3 = ffff83022fddc000 (XEN) l3_index = 3 (XEN) l3[3] = 228658003 (XEN) l2 = ffff830228658000 (XEN) l2_index = 7d (XEN) l2[7d] = 2285da003 (XEN) l1 = ffff8302285da000 (XEN) l1_index = 1ef (XEN) l1[1ef] = 0 (XEN) l1[1ef] not present uhci_hcd 0000:00:1d.0: host system error, PCI problems? uhci_hcd 0000:00:1d.0: host controller halted, very bad! usb usb1: configuration #1 chosen from 1 choice uhci_hcd 0000:00:1d.0: HC died; cleaning up hub 1-0:1.0: USB hub found hub 1-0:1.0: config failed, can't read hub descriptor (err -22) uhci_hcd 0000:00:1d.0: HC died; cleaning up Unable to handle kernel NULL pointer dereference at 0000000000000038 RIP: [<ffffffff8800174a>] :usbcore:kick_khubd+0x19/0x69 PGD 803bf067 PUD 803aa067 PMD 0 Oops: 0000 [1] SMP CPU 1 Modules linked in: uhci_hcd usbcore Pid: 798, comm: insmod Tainted: GF 2.6.18.8-xen #1 RIP: e030:[<ffffffff8800174a>] [<ffffffff8800174a>] :usbcore:kick_khubd+0x19/09 RSP: e02b:ffff88007f31bc38 EFLAGS: 00010046 RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffffff578000 RDX: 0000000000000038 RSI: 0000000000000001 RDI: ffffffff8801c2e8 RBP: 0000000000000000 R08: 000000000000002c R09: ffff88008031a318 R10: ffff88007f512000 R11: ffffffff802d570c R12: ffff88007f8da1c8 R13: 0000000000000000 R14: ffff88007f512000 R15: ffff88007f8da070 FS: 0000000000000000(0063) GS:ffffffff804dc080(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 Process insmod (pid: 798, threadinfo ffff88007f31a000, task ffff88007f83a820) Stack: ffff8800803a8c00 ffff8800803a8c00 0000000000000000 ffffffff88004367 0000000000000012 ffff88007f512000 ffff8800803a8c00 ffffffff88004d03 0000001600000004 ffff88007f8da0e0 ffff8800803a8c00 ffff88007f8da000 Call Trace: [<ffffffff88004367>] :usbcore:usb_hc_died+0x5f/0x72 [<ffffffff88004d03>] :usbcore:usb_add_hcd+0x4eb/0x562 [<ffffffff8800d031>] :usbcore:usb_hcd_pci_probe+0x1e4/0x28b [<ffffffff802f4dca>] pci_device_probe+0x4c/0x75 [<ffffffff8034e99e>] pci_bus_probe_wrapper+0x80/0x8a [<ffffffff802f4cb4>] pci_match_device+0x13/0xbd [<ffffffff802f4d72>] pci_bus_match+0x14/0x20 [<ffffffff803457c4>] driver_probe_device+0x52/0xa2 [<ffffffff803458ed>] __driver_attach+0x6d/0xaa [<ffffffff80345880>] __driver_attach+0x0/0xaa [<ffffffff803451c5>] bus_for_each_dev+0x43/0x6e [<ffffffff80344e25>] bus_add_driver+0x7e/0x130 [<ffffffff802f4f65>] __pci_register_driver+0x57/0x7d [<ffffffff8802905c>] :uhci_hcd:uhci_hcd_init+0x5c/0x97 [<ffffffff8024af6a>] sys_init_module+0x16a1/0x1857 [<ffffffff8020a5a4>] system_call+0x68/0x6d [<ffffffff8020a53c>] system_call+0x0/0x6d Code: 48 39 53 38 48 89 c5 75 35 48 8b 05 9e ab 01 00 48 c7 43 38 RIP [<ffffffff8800174a>] :usbcore:kick_khubd+0x19/0x69 RSP <ffff88007f31bc38> CR2: 0000000000000038 Loading ohci-hcd.ko module <7>ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) -- 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
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |