Bug 186660
Summary: | Kernel oops in usb_new_device (khubd) on bootup | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert Hancock <hancockrwd> | ||||||||
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 5 | CC: | davej, wtogami | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | 2.6.17-1.2145_FC5 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2006-07-15 01:03:51 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Robert Hancock
2006-03-25 04:04:21 UTC
Created attachment 126692 [details]
kernel output from failed bootup with oops
Created attachment 126693 [details]
kernel output from subsequent normal bootup
Oddly enough, Alan Stern posted a patch to remove assumptions about having an interface just last week. I can try to dig it out. Created attachment 127425 [details]
/var/log/messages of boot with oops
Comment on attachment 127425 [details]
/var/log/messages of boot with oops
I get this one quite often as well...
Robert, please test one of update kernels from here: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/5/i386/ It's at 2.6.17-1.2145_FC5 currently. I think the zero-interface device issue was fixed in 2.6.17. If that fails, I look closer. I have not seen this in recent kernel versions (though I can't say for certain that it is fixed as it was never very reproducible). Unless anyone has seen this in recent kernels it can likely be marked as resolved. OK, I'll close at "currentrelease"+2.6.17-1.2145_FC5. |