Bug 208141
Summary: | 8390 lockdep/BUG | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Philip Ashmore <contact> | ||||
Component: | kernel | Assignee: | Andy Gospodarek <agospoda> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | CC: | davej, linville, peterm, triage, wtogami | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | bzcl34nup | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2008-05-06 16:25:10 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 202141 | ||||||
Attachments: |
|
Description
Philip Ashmore
2006-09-26 16:42:46 UTC
This is a kernel oops -- can you switch to tty2 afterwards and grab /tmp/syslog? Created attachment 137324 [details]
/var/log/messages
I had to swap hard disks between my two laptops to install this via PXE on a spare partition, I then swapped them back again - I can't do that again. I've attached my current /var/log/messages above in the hope that you can determine the problem from that - I know I saw one kernel problem there. Feel free to query/post bug reports based on any other problems you spot in this log. Two separate problems here, both a BUG(), and a lockdep trace. The lockdep issue should be cured in 2.6.18. The BUG looks to be a mdelay in irg context.... and in irq context The warning printed as a result of the mdelay in an irq context isn't critical. Are you still seeing both of these problems with the latest fc6 kernel or just the BUG warning? This was an installation problem with FC6 test 3 (see above) via PXE. On a seperate install I attempted to use an update repository but the graphical messages seemed to indicate that the FC6 core RPMS were the ones being installed. The installation didn't complete so I had to go back to 1. Install base system - FC6 release 2. yum -y update with a locally mirrored updates repository Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |