Bug 253463
Summary: | initng-ifiles hang after udev/filldev | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rudolf Kastl <che666> |
Component: | initng-ifiles | Assignee: | Daniel Malmgren <dm> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-11-02 12:44:04 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
Rudolf Kastl
2007-08-19 23:57:21 UTC
Ok, for a starters, what do you mean with "hangs"? Does it just stop or is there any other information? Another question that may seem somewhat irrelevant: Does the computer have any bluetooth interface? Is it activated? (My laptop sometimes stops after the filldev step and just waits until I activate the bluetooth interface. I've never found out what the connection is...) maybe what you describe is a kinda "race" condition. with hangs i want to say that it just hangs there and shows that as last step completed. actually there is no additional information i can give. maybe it is a kinda dependency loop. if you e.g. google for initng filldev hang you will see that i am not the only one having that problem. One idea: Try to start initng with "interactive" argument (as kernel argument) and see what happens. That way you'll be able to confirm every started service, might give some more information... Any new input on this one, Che? i fixed it with the modified svn diff in the new src rpm. removed an & and also removed the race condition that came with it. Ok. Since I now have built that in devel, I guess I can close this bug. |