On Sun, 8 Jun 2008, Chris Clayton wrote:

quoted text
> > The odd thing is that it occurs in the middle of USB initialisation from
> >
> 
> Because of this oddity, I've also built 2.6.26-rc5-git2 with verbose USB 
> debugging on. A boot log from that kernel is attached. You will see lots of 
> ETIME errors from usb. A log from a similarly verbose 2.6.25.5 kernel does not 
> show these errors. usb-devel added to cc list.

In fact the log shows that the 30-second delay occurs in the middle of
ohci1394 (Firewire) initialization, not USB initialization:

Jun  8 05:26:35 upstairs kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[22]  MMIO=[fbfff000-fbfff7ff]  Max Packet=[2048]  IR/IT contexts=[4/8] 
Jun  8 05:26:35 upstairs kernel: ohci_hcd 0000:02:0a.0: urb f71cb680 path 2 ep1in 5e160000 cc 5 --> status -62 
Jun  8 05:26:35 upstairs kernel: hub 1-2:1.0: transfer --> -62 
Jun  8 05:27:08 upstairs kernel: driver: '0000:02:0b.0': driver_bound: bound to device 'ohci1394' 
Jun  8 05:27:08 upstairs kernel: bus: 'pci': really_probe: bound device 0000:02:0b.0 to driver ohci1394 

Those -62 errors from ohci_hcd are red herrings.  To test this, try 
booting with "nousb".

Alan Stern

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/