Bug 5642 - ohci_hcd temporary freeze on nForce4 Ultra board
Summary: ohci_hcd temporary freeze on nForce4 Ultra board
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: David Brownell
URL:
Keywords:
Depends on:
Blocks: USB
  Show dependency tree
 
Reported: 2005-11-23 05:48 UTC by Vitezslav Kotrla
Modified: 2006-02-17 11:12 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.14
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Vitezslav Kotrla 2005-11-23 05:48:21 UTC
I've noticed temporary ohci freezes during boot on my new nForce4 Ultra based
computer. First I noticed it with 2.6.13, but it is still there with 2.6.14.1.

I'm using vanilla from kernel.org.

Kernel says:

...
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt Link [LUBA] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUBA] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller

...
(here all activity stops, something waits for about 5 minutes)
...

ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:02.0: irq 10, io mem 0xfebff000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected

This behaviour is pretty random, 90 % the boot attempts is fluent, but
I've already experienced four subsequent occurences. I'd say it's much
less frequent with 2.6.14, but it is still there.

I'd be more than happy to help to debug this mystery.
Comment 1 Greg Kroah-Hartman 2006-02-14 17:46:39 UTC
Is this still present with 2.6.16-rc3?
Comment 2 Vitezslav Kotrla 2006-02-16 23:55:34 UTC
I'm currently running 2.6.15.2 and haven't seen this freeze for some time, so it
is hopefully gone. As it is hardly reproducible, consider this issue closed.
Should it reappear, I'll just reopen.
Comment 3 Greg Kroah-Hartman 2006-02-17 11:12:30 UTC
Ok, closing, thanks.

Note You need to log in before you can comment on or make changes to this bug.