Bug 179157
Summary: | LTC21039-FC5T2 oopses on 1 out of 3 boots on 64-way Squadrons H | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | IBM Bug Proxy <bugproxy> |
Component: | kernel | Assignee: | David Woodhouse <dwmw2> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | davej, jonstanley, sundaram, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | powerpc | ||
OS: | Linux | ||
Whiteboard: | MassClosed | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-20 04:40:26 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
IBM Bug Proxy
2006-01-27 20:29:00 UTC
These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks Manoj, can you investigate this? ----- Additional Comments From gcwilson.com 2006-06-23 12:01 EDT ------- I installed the H with FC5 GA this time. I have seen it drop into xmon once. I failed get a backtrace from it. Will the next time it happens. I don't know if this happens with the same frequency, or if it is actually the same problem. Now the machine is hanging on boot starting udev. I am going to let it sit an hour or so--sometimes udev takes a _long_ time to start (which may be a problem in itself). If I can't get it to drop into xmon, I'll open separate bug on the udev problem. Neither of these issues is helping me get SELinux/MLS performance tests run. changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |REJECTED Resolution| |DUPLICATE ------- Additional Comments From gcwilson.com 2006-06-25 18:06 EDT ------- Once I worked around the start_udev variant of LTC23422/RH178229, the H boots FC5 GA and lspp.38 test kernels reliably. I don't have enough evidence to say with complete certainty that this bug is really a manifestation of bug 23422. But I strongly suspect it is. Closing as a duplicate of LTC23422/RH178229. *** This bug has been marked as a duplicate of 23422 *** A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. (this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug. |