WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Dom0 crash in UHCI driver when using serial

To: Alexia Benington <alexbenington@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Dom0 crash in UHCI driver when using serial
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Fri, 23 Jan 2009 15:45:47 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Thu, 22 Jan 2009 23:46:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7969168f0901222254n37604786nce328055e607af1d@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acl9J3lKp1Qs5IMLSZOmOHrqkvR88gABwE6Q
Thread-topic: [Xen-devel] Dom0 crash in UHCI driver when using serial
Hi Alexia,

It should not related serial. Please try to remove "iommu=1". We have reported 
this issue serveral days ago with the title "[Xen-devel] Critical bug: VT-d 
fault causes disk corruption or Dom0 kernel panic."
 
BTW, Allen Kay is trying to fix it. You can at least pick up Xen changeset 
"19027:95d8788bf4be" for normal booting. 

Best Regards,
Yongkang You

On Friday, January 23, 2009 2:54 PM, "Alexia Benington" wrote:
> Hi all,
> 
> Apologies, I realized I missed out the subject in my previous
> submission, thus this resend. 
> 
> My Dom0 crashed if I use the first grub configuration, but is ok if I
> use the following one. 
> 
> kernel          /boot/xen-3.4-unstable.gz
> module          /boot/vmlinuz-2.6.18.8-xen root=/dev/sda2 ro
> 
> kernel          /boot/xen-3.4-unstable.gz com1=9600,8n1 console=com1
> iommu=1 
> module          /boot/vmlinuz-2.6.18.8-xen root=/dev/sda2 ro
> xencons=ttyS console=tty0 console=ttyS0 
> 
> I've attached the full boot trace. Below is a snippet of the crash
> region. Does anyone have any idea what's going on? 
> 
> Thanks and have a nice day.
> 
> 
> - Alexia
> 
> ==============================
> ==================
> USB Universal Host Controller Interface driver v3.0
> ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 16 (level, low) -> IRQ 16
> uhci_hcd 0000:00:1a.0: UHCI Host Controller
> uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
> uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000e0e0
> (XEN) [VT-D]iommu.c:721: iommu_page_fault: iommu->reg =
> ffff828bfff55000 (XEN) [VT-D]iommu.c:693: iommu_fault_status: Primary
> Pending Fault (XEN) [VT-D]iommu.c:675: iommu_fault:DMA Read: 0:1a.0
> addr bf7ed000 REASON 6 iommu->reg = ffff828bfff55000 (XEN)
> print_vtd_entries: iommu = ffff8300bfef10f0 bdf = 0:1a:0 gmfn = bf7ed
> (XEN)     root_entry = ffff83013bdea000 (XEN)     root_entry[0] =
> 1374a0001 (XEN)     context = ffff8301374a0000
> (XEN)     context[d0] = 101_13bde6001
> (XEN)     l3 = ffff83013bde6000
> (XEN)     l3_index = 2
> (XEN)     l3[2] = 137a83003
> (XEN)     l2 = ffff830137a83000
> (XEN)     l2_index = 1fb
> (XEN)     l2[1fb] = 137887003
> (XEN)     l1 = ffff830137887000
> (XEN)     l1_index = 1ed
> (XEN)     l1[1ed] = 0
> (XEN)     l1[1ed] not present
> uhci_hcd 0000:00:1a.0: host system error, PCI problems?
> uhci_hcd 0000:00:1a.0: host controller halted, very bad!
> uhci_hcd 0000:00:1a.0: HC died; cleaning up
> usb usb1: configuration #1 chosen from 1 choice
> usb usb1: can't set config #1, error -108
> uhci_hcd 0000:00:1a.0: HC died; cleaning up
> Unable to handle kernel NULL pointer dereference at 0000000000000018
>  RIP: [<ffffffff88019be9>] :usbcore:usb_kick_khubd+0x7/0x17
> PGD ef053067 PUD ef051067 PMD 0
> Oops: 0000 [1] SMP
> CPU 3
> Modules linked in: uhci_hcd usbcore thermal processor fan
> Pid: 496, comm: insmod Not tainted 2.6.18.8-xen #1
> RIP: e030:[<ffffffff88019be9>]  [<ffffffff88019be9>]
> :usbcore:usb_kick_khubd+0x7/0x17 
> RSP: e02b:ffff8800eeb6fc50  EFLAGS: 00010002
> RAX: 0000000000000000 RBX: ffff8800eed03c00 RCX: ffffffffff578000
> RDX: ffffffffff578000 RSI: 0000000000000001 RDI: ffff8800ef03e000
> RBP: 0000000000000000 R08: 000000000000000e R09: 0000000000000001
> R10: ffff8800ef052570 R11: ffffffff80300885 R12: ffff8800eecb01c8
> R13: 0000000000000000 R14: ffff8800ef03e000 R15: ffff8800eecb0070
> FS:  00002ad0ef6c66d0(0000) GS:ffffffff804d9180(0000)
> knlGS:0000000000000000 
> CS:  e033 DS: 0000 ES: 0000
> Process insmod (pid: 496, threadinfo ffff8800eeb6e000, task
> ffff8800eec867a0) 
> Stack:  ffffffff8801a39b 0000000000000012 ffff8800ef03e000
>  ffff8800eed03c00 ffffffff8801ad3c 0000001000000004 ffff8800eecb00e0
>  ffff8800eed03c00 ffff8800eecb0000 0000000000000004 ffffffff8803d4a0
> 0000000000000000 
> Call Trace:
>  [<ffffffff8801a39b>] :usbcore:usb_hc_died+0x5f/0x72
>  [<ffffffff8801ad3c>] :usbcore:usb_add_hcd+0x4eb/0x562
>  [<ffffffff880230cf>] :usbcore:usb_hcd_pci_probe+0x1e6/0x28f
>  [<ffffffff802f4f5e>] pci_device_probe+0x4c/0x75
>  [<ffffffff8034f250>] pci_bus_probe_wrapper+0x86/0x92
>  [<ffffffff802f4e48>] pci_match_device+0x13/0xbd
>  [<ffffffff8803d000>] :uhci_hcd:uhci_start+0x21e/0x3c0
>  [<ffffffff802f4f06>] pci_bus_match+0x14/0x20
>  [<ffffffff80346048>] driver_probe_device+0x52/0xa8
>  [<ffffffff80346177>] __driver_attach+0x6d/0xaa
>  [<ffffffff8034610a>] __driver_attach+0x0/0xaa
>  [<ffffffff80345a49>] bus_for_each_dev+0x43/0x6e
>  [<ffffffff803456a7>] bus_add_driver+0x7e/0x130
>  [<ffffffff802f50f9>] __pci_register_driver+0x57/0x7d
>  [<ffffffff8804305c>] :uhci_hcd:uhci_hcd_init+0x5c/0x97
>  [<ffffffff8024b1f5>] sys_init_module+0x16cc/0x1883
>  [<ffffffff8020a518>] system_call+0x68/0x6d
>  [<ffffffff8020a4b0>] system_call+0x0/0x6d
> 
> 
> Code: 48 8b 40 18 48 8b b8 f0 01 00 00 e9 52 db ff ff 41 56 41 55
> RIP  [<ffffffff88019be9>] :usbcore:usb_kick_khubd+0x7/0x17
>  RSP <ffff8800eeb6fc50>
> CR2: 0000000000000018
>  Killed

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

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