On Tue, Jan 26, 2010 at 11:49:32AM -0500, David P. Quigley wrote:
> > > > >
> > > > > I've been trying for the better part of today to get this working and
> > > > > I
> > > > > seem to keep hitting a wall. I finally managed to get the kernel
> > > > > booted
> > > > > but only with a serial console. I found out that some modules were
> > > > > missing so that might have caused the lack of console support but now
> > > > > the kernel won't boot to a prompt at all. I keep running into a null
> > > > > dereference in the uhci driver. I can try to rebase Jeremy's patches
> > > > > onto a newer kernel.org version but I'd first like to check to make
> > > > > sure
> > > > > this isn't already a known problem with a solution.
> > > > >
> > > >
> > > > You can try my .config files for pv_ops dom0 kernel, available from
> > > > here:
> > > > http://wiki.xensource.com/xenwiki/XenParavirtOps
> > > >
> > > > in the "Troubleshooting" section.. just use "make oldconfig" with them.
> > > >
> > > > -- Pasi
> > >
> > > Thanks for the suggestion. I am already using your config though so its
> > > not clear to me if its a config issue. Once I got that working and
> > > booting I keep getting null pointer dereferences in some other code
> > > thats not xen related. The only reason it might be affected by xen is
> > > because its complaining about something with the PCI space. The error
> > > text is below.
> > >
> > > uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> > > uhci_hcd 0000:00:1a.1: UHCI Host Controller
> > > uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 3
> > > uhci_hcd 0000:00:1a.1: irq 17, io base 0x0000ff00
> > > uhci_hcd 0000:00:1a.1: host system error, PCI problems?
> > > uhci_hcd 0000:00:1a.1: host controller halted, very bad!
> > > uhci_hcd 0000:00:1a.1: HC died; cleaning up
> > >
> >
> > Uh oh :) That looks bad.. I haven't seen that on my testboxes..
> > so dunno really what would help.
> >
> > Is Xen complaining something when that happens? Check "xm dmesg".
> >
> > Do you have "loglvl=all guest_loglvl=all" options for xen.gz in grub.conf?
> >
> > -- Pasi
>
>
> I don't see anything that immediately jumps out at me but I'm new to
> this so I may be missing something. My grub config entry is below and I
> have attached the entire output from boot to the oops that I get on my
> serial console.
>
> title Fedora (2.6.31.6-pvops-dom0-dontedit)
> kernel /xen-4.0.gz console=com1,hvc0 com1=115200,8n1 loglvl=all
> guest_loglvl=all sync_console console_to_ring
> module /vmlinuz-2.6.31.6-pvops-dom0 ro
> root=/dev/mapper/VolGroup-lv_root console=com1,hvc0 com1=115200,8n1
> earlyprintk=xen
> module /initrd-2.6.31.6-pvops-dom0.img
> module /xenpolicy.24
>
There are some extra options, but those shouldn't be the problem.
Cleaned up grub.conf:
title Fedora (2.6.31.6-pvops-dom0-dontedit)
kernel /xen-4.0.gz console=com1 com1=115200,8n1 loglvl=all
guest_loglvl=all sync_console console_to_ring
module /vmlinuz-2.6.31.6-pvops-dom0 ro
root=/dev/mapper/VolGroup-lv_root console=hvc0 earlyprintk=xen
module /initrd-2.6.31.6-pvops-dom0.img
module /xenpolicy.24
Maybe try adding dom0_mem=1024M to the xen-4.0.gz line.. that might have some
effect.
> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> xen_set_ioapic_routing: irq 22 gsi 22 vector 22 ioapic 0 pin 22 triggering 1
> polarity 1
> ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 22 (level, low) -> IRQ 22
> ehci_hcd 0000:00:1a.7: EHCI Host Controller
> ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
> ehci_hcd 0000:00:1a.7: debug port 1
> ehci_hcd 0000:00:1a.7: irq 22, io mem 0xfebda000
> ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
> usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb1: Product: EHCI Host Controller
> usb usb1: Manufacturer: Linux 2.6.31.6-pvops-dom0 ehci_hcd
> usb usb1: SerialNumber: 0000:00:1a.7
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 6 ports detected
> work_for_cpu used greatest stack depth: 3888 bytes left
> xen_set_ioapic_routing: irq 23 gsi 23 vector 23 ioapic 0 pin 23 triggering 1
> polarity 1
> ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
> ehci_hcd 0000:00:1d.7: EHCI Host Controller
> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
> ehci_hcd 0000:00:1d.7: debug port 1
> ehci_hcd 0000:00:1d.7: irq 23, io mem 0xff980000
> ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
> usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
> usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb2: Product: EHCI Host Controller
> usb usb2: Manufacturer: Linux 2.6.31.6-pvops-dom0 ehci_hcd
> usb usb2: SerialNumber: 0000:00:1d.7
> usb usb2: configuration #1 chosen from 1 choice
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 6 ports detected
> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> uhci_hcd: USB Universal Host Controller Interface driver
> xen_allocate_pirq: returning irq 16 for gsi 16
> xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic 0 pin 16 triggering 1
> polarity 1
> uhci_hcd 0000:00:1a.0: PCI INT 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 3
> uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff20
> 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
> uhci_hcd 0000:00:1a.0: USB bus 3 deregistered
> uhci_hcd 0000:00:1a.0: PCI INT A disabled
> uhci_hcd 0000:00:1a.0: init 0000:00:1a.0 fail, -108
> uhci_hcd: probe of 0000:00:1a.0 failed with error -108
> xen_allocate_pirq: returning irq 17 for gsi 17
> xen_set_ioapic_routing: irq 17 gsi 17 vector 17 ioapic 0 pin 17 triggering 1
> polarity 1
> uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> uhci_hcd 0000:00:1a.1: UHCI Host Controller
> uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 3
> uhci_hcd 0000:00:1a.1: irq 17, io base 0x0000ff00
> uhci_hcd 0000:00:1a.1: host system error, PCI problems?
> uhci_hcd 0000:00:1a.1: host controller halted, very bad!
> uhci_hcd 0000:00:1a.1: HC died; cleaning up
> usb usb3: unable to read config index 0 descriptor/start: -108
> usb usb3: chopping to 0 config(s)
> usb usb3: string descriptor 0 read error: -108
> ata3: SATA link down (SStatus 4 SControl 300)
> ata6: SATA link down (SStatus 0 SControl 300)
> usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
> usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> usb usb3: no configuration chosen from 0 choices
> uhci_hcd 0000:00:1a.1: HC died; cleaning up
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000098
> IP: [<ffffffff813be3d2>] usb_kick_khubd+0x23/0x4c
> PGD 0
> Oops: 0000 [#1] SMP
> last sysfs file:
> CPU 0
> Modules linked in:
> Pid: 112, comm: work_for_cpu Not tainted 2.6.31.6-pvops-dom0 #6 OptiPlex 960
>
> RIP: e030:[<ffffffff813be3d2>] [<ffffffff813be3d2>] usb_kick_khubd+0x23/0x4c
> RSP: e02b:ffff8801dd071d40 EFLAGS: 00010046
> RAX: 0000000000000000 RBX: ffff8801dd1a0000 RCX: 00000000000001af
> RDX: ffff8801dd7d4880 RSI: ffff8801dd1a0848 RDI: ffff8801dd1a0848
> RBP: ffff8801dd071d50 R08: 000000000000000c R09: ffff8801dd071bf0
> R10: 00000002c6caa903 R11: 0000000000000144 R12: 0000000000000200
> R13: ffff8801dd1a0848 R14: ffff8801dd1a0848 R15: 0000000000000011
> FS: 0000000000000000(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
> CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000000098 CR3: 0000000001001000 CR4: 0000000000002660
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process work_for_cpu (pid: 112, threadinfo ffff8801dd070000, task
> ffff8801dd7d4880)
> Stack:
> 0000000000000200 00000000035b2d49 ffff8801dd071d80 ffffffff813c422b
> <0> ffff8801dd071d80 00000000035b2d49 ffff8801dd1a0000 0000000000000000
> <0> ffff8801dd071df0 ffffffff813c55f6 40ff8801dd071df0 000000000000ff00
> Call Trace:
> [<ffffffff813c422b>] usb_hc_died+0x78/0xa3
> [<ffffffff813c55f6>] usb_add_hcd+0x544/0x6a8
> [<ffffffff813d5206>] usb_hcd_pci_probe+0x263/0x3bd
> [<ffffffff8107e91c>] ? do_work_for_cpu+0x0/0x50
> [<ffffffff8129658f>] local_pci_probe+0x2a/0x42
> [<ffffffff8107e943>] do_work_for_cpu+0x27/0x50
> [<ffffffff81083c80>] kthread+0xac/0xb4
> [<ffffffff810161aa>] child_rip+0xa/0x20
> [<ffffffff81015b10>] ? restore_args+0x0/0x30
> [<ffffffff810161a0>] ? child_rip+0x0/0x20
> Code: 18 5b 41 5c 41 5d c9 c3 55 48 89 e5 48 83 ec 10 0f 1f 44 00 00 65 48 8b
> 04 25 28 00 00 00 48 89 45 f8 31 c0 48 8b 87 88 02 00 00 <48> 8b 80 98 00 00
> 00 48 8b b8 f8 00 00 00 e8 6d fe ff ff 48 8b
> RIP [<ffffffff813be3d2>] usb_kick_khubd+0x23/0x4c
> RSP <ffff8801dd071d40>
> CR2: 0000000000000098
> ---[ end trace cf0e97f02af8794f ]---
> BUG: spinlock lockup on CPU#1, khubd/42, ffffffff817fa050
> Pid: 42, comm: khubd Tainted: G D 2.6.31.6-pvops-dom0 #6
> Call Trace:
> [<ffffffff812852f4>] _raw_spin_lock+0x118/0x156
> [<ffffffff81518854>] _spin_lock_irq+0x71/0x9a
> [<ffffffff813c5dc9>] ? usb_hcd_submit_urb+0x304/0xa07
> [<ffffffff813c6c60>] ? usb_get_urb+0x2a/0x48
> [<ffffffff813c5dc9>] usb_hcd_submit_urb+0x304/0xa07
> [<ffffffff8100eb68>] ? xen_force_evtchn_callback+0x20/0x36
> [<ffffffff81074a4e>] ? lock_timer_base+0x3f/0x7d
> [<ffffffff81074a4e>] ? lock_timer_base+0x3f/0x7d
> [<ffffffff8100eb68>] ? xen_force_evtchn_callback+0x20/0x36
> [<ffffffff81097b93>] ? lockdep_init_map+0xad/0x138
> [<ffffffff813c6ba3>] usb_submit_urb+0x25a/0x2ed
> [<ffffffff81084577>] ? __init_waitqueue_head+0x4d/0x76
> [<ffffffff813c8509>] usb_start_wait_urb+0x71/0x1d4
> [<ffffffff813c8907>] usb_control_msg+0x10c/0x144
> [<ffffffff813bd9c4>] hub_port_status+0x99/0x137
> [<ffffffff813bdd21>] hub_port_reset+0xa9/0x2f9
> [<ffffffff813bf346>] hub_port_init+0x100/0x7ee
> [<ffffffff8100f61f>] ? xen_restore_fl_direct_end+0x0/0x1
> [<ffffffff81518489>] ? _spin_unlock_irqrestore+0x64/0x7f
> [<ffffffff813c2bae>] hub_events+0x94d/0x11e6
> [<ffffffff8100f632>] ? check_events+0x12/0x20
> [<ffffffff8100eb68>] ? xen_force_evtchn_callback+0x20/0x36
> [<ffffffff813c348d>] hub_thread+0x46/0x1d1
> [<ffffffff810840d3>] ? autoremove_wake_function+0x0/0x5f
> [<ffffffff813c3447>] ? hub_thread+0x0/0x1d1
> [<ffffffff81083c80>] kthread+0xac/0xb4
> [<ffffffff810161aa>] child_rip+0xa/0x20
> [<ffffffff81015b10>] ? restore_args+0x0/0x30
> [<ffffffff810161a0>] ? child_rip+0x0/0x20
>
Uh oh.. hopefully someone else has more ideas.
I can only suggest trying to limit dom0 memory (dom0_mem=1024M)
and see if that helps.
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home