Bug 159372
Summary: | spin_lock panic in IDE autotuning | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bryce <root> | ||||||||
Component: | kernel | Assignee: | Alan Cox <alan> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 3 | CC: | davej, packetgeek, wtogami | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | 2.6.11-1.14_FC3 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2005-09-08 13:29:49 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: | |||||||||||
Attachments: |
|
Description
Bryce
2005-06-02 00:38:02 UTC
Created attachment 115072 [details]
Spin_lock crash
Crash on reboot
Created attachment 115073 [details]
Section of code involved
The red cursors identify the code lines involved
Incidentally this arises from the mainline 2.6.11 kernel source and isn't the result of any patchs that are added to the kernel by RHAT Phil =--= Umm yes. Does the attachment I'll add fix it ? Created attachment 116592 [details]
Possible fix
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. Seems to be fixed (it was a every now and then bug in the first place) I've not seen it for quite some time so I think this is fixed. Cheers Phil =--= |