http://bugzilla.novell.com/show_bug.cgi?id=623680 http://bugzilla.novell.com/show_bug.cgi?id=623680#c0 Summary: xen kernel freezes during boot ("usbcore: registering new driver usb") Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: martin.wilck@ts.fujitsu.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 The xen kernel freezes during boot. The last message is "usbcore: registering new driver usb". After that, the system doesn't react to any keystroke including NumLock. In particular, no AltSysrq is possible. Reproducible: Always Steps to Reproduce: 1. Install on Samsung XS50 laptop 2. Boot xen + xen kernel 3. Actual Results: see description Expected Results: No hang I am 90% positive that I was able to boot XEN with beta1 snap7. But I don't have that installation any more, so I can't check any more. The default kernel shows no problems at the stage where the xen kernel halts. The dmesg of the default kernel around this point are: [ 2.473025] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x18e0 irq 14 [ 2.473028] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18e8 irq 15 [ 2.475625] rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0 [ 2.475661] rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs [ 2.476179] usbcore: registered new device driver usb [ 2.493139] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.493178] alloc irq_desc for 23 on node -1 [ 2.493181] alloc kstat_irqs on node -1 [ 2.493189] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 2.493206] ehci_hcd 0000:00:1d.7: setting latency timer to 64 [ 2.493210] ehci_hcd 0000:00:1d.7: EHCI Host Controller So ehci, ata or rtc are potential suspects. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.