Bug 119916
Summary: | [firewire] kudzu service hangs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Clyde E. Kunkel <clydekunkel7734> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | markf78 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:02:22 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
Clyde E. Kunkel
2004-04-03 03:58:33 UTC
Try removing the firewire modules? I removed the firewire modules and then used interactive boot to bypass new hardware detection. I have resolved the problem, at least for now. I started kudzu from a terminal and discovered that it was finding that my hardware had changed and was asking me if I wanted to update. After replying appropriately, I then went back to the gui and starting the service by clicking the start button resulted in a message that kudzu had run. I then added kudzu back into the startup routine and booting was normal. The problem seems to be that if you have disabled kudzu and then try to start it from the gui and it wants to talk to you, it is not doing so and so it waits forever for your response which you don't see. Starting it from a terminal allows you to see its query and respond. I don't know if this is a bug or not. BTW, now running kernel 305smp with firewire added back in and no problems as far as I can see. *** This bug has been marked as a duplicate of 119262 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |