Bug 69739
Summary: | extraneous messages on pegasus usb ethernet insertion | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mike McLean <mikem> |
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-04-19 18:47:03 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: |
Description
Mike McLean
2002-07-24 21:32:58 UTC
Sure, I can take that. But I do not see how this can be helped, honestly. The first message appears when the device is connected, and before the hotplug had a chance to work and load pegasus driver. If we block khubd until the hotplug finishes, it's going to give us a lot of grief with hanging. Second one is annoying, because it seems like a pegasus's fault. Surely it should be capable of waiting a little before complaining about the missing link beat. It can be changed, but I'd rather not. Too easy to fix the requestor's issue, but blow up it for someone else (like with USB serial last time). fwiw, this seems to be fixed in FC1 |