Bug 159372

Summary: spin_lock panic in IDE autotuning
Product: [Fedora] Fedora Reporter: Bryce <root>
Component: kernelAssignee: Alan Cox <alan>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: 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: ---
Attachments:
Description Flags
Spin_lock crash
none
Section of code involved
none
Possible fix none

Description Bryce 2005-06-02 00:38:02 UTC
Description of problem:

spinlock panic

Version-Release number of selected component (if applicable):
2.6.11-1.27_FC3

How reproducible:

on reboot every now and then

I can tell you exactly whats happening
Observe the two attached images
one shows the panic and the other is a screenshot of the code involved

notice the two spin_lock_irqsave()'s
Whats happening is simple, when there is a reset of the drive it invokes a
restore of timings. This is part of auto tuning, so it is obvious you get a
double lock down, hence the spinlock crash.

Phil
=--=

Comment 1 Bryce 2005-06-02 00:38:59 UTC
Created attachment 115072 [details]
Spin_lock crash

Crash on reboot

Comment 2 Bryce 2005-06-02 00:40:09 UTC
Created attachment 115073 [details]
Section of code involved

The red cursors identify the code lines involved

Comment 3 Bryce 2005-06-02 01:27:07 UTC
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
=--=

Comment 4 Alan Cox 2005-07-11 09:28:27 UTC
Umm yes. Does the attachment I'll add fix it ?


Comment 5 Alan Cox 2005-07-11 09:30:14 UTC
Created attachment 116592 [details]
Possible fix

Comment 6 Dave Jones 2005-07-15 19:14:51 UTC
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.

Comment 7 Bryce 2005-09-08 13:29:49 UTC
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
=--=