Bug 146620 - Kernel panic on shutdown - ieee1394 spinlock
Summary: Kernel panic on shutdown - ieee1394 spinlock
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-30 20:49 UTC by Michael A. Peters
Modified: 2015-01-04 22:16 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2005-09-28 08:17:46 UTC

Attachments (Terms of Use)

Description Michael A. Peters 2005-01-30 20:49:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
Only device that had been connected to FireWire was iPod, and it has
been unmounted AND ejected for hours (ejected as in /dev nodes been
removed, no "do not disconnect" message.

I needed to do something in windows, so I rebooted from gnome.
I think I physically disconnected iPod before choosing reboot, but it
is possible I chose reboot and then physically disconnected.

Here's the panic that resulted:

ieee 1394: sbp2: aborting sbp2 command
Test Unit Ready 00 00 00 00 00
Kernel panic - not syncing : drivers/ieee1394/sb2.c:505:
spin_is_locked on uninitialized spinlock c3237ac8

Hardware: A7N8X Deluxe w/ built in FireWire
Additional Belkin FireWire card in PCI slot

Fom lspci:

00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire
(IEEE 1394) Controller (rev a3)

01:09.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394
Controller (Link)

If it matters, the iPod connects to the onboard IEEE 1394 (the TI card
is only there for times when I need to connect a second 6-pin firewire
device, rare)

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

How reproducible:
Couldn't Reproduce

Steps to Reproduce:
This has only happened to me once - I've been connecting the iPod for
about a month (Christmas gift) 

Additional info:

Comment 1 Michael A. Peters 2005-03-17 04:29:44 UTC
It has never happened to me again since - I don't know that it still an issue or

Comment 2 Dave Jones 2005-07-15 20:45:21 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.

Note You need to log in before you can comment on or make changes to this bug.