Bug 144753 - Kernel panic on shutdown
Summary: Kernel panic on shutdown
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-11 07:40 UTC by Bradley
Modified: 2015-01-04 22:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-16 13:36:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bradley 2005-01-11 07:40:29 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:
Kernel paniced on shutdown. Error message copied by hand:

kernel panic - not syncing: fs/proc/generic.c:521: spin_lock
(fs/file_table.c:c034aa10) already locked by fs/file_table.c/204

Caps lock and scroll lock lights were flashing.

magic sysreq didn't do anything (it was enabled via sysctl). There was
nothing in the logs about the panic, but the sysklogd shutdown message
was present so the oops happened at some point after that.

Version-Release number of selected component (if applicable):
kernel-2.6.9-1.724_FC3

How reproducible:
Hasn't happened before, and this is a desktop which gets shut down daily.

Steps to Reproduce:
1. Selected logout => shut down from gnome menu
2. Waited

Actual Results:  Kernel panic

Expected Results:  System should have powered off

Comment 1 Mike 2005-04-08 21:45:18 UTC
Under 2.6.10-1.770_FC3 the same message:

| kernel panic - not syncing: fs/proc/generic.c:521: spin_lock
| (fs/file_table.c:c034aa10) already locked by fs/file_table.c/204

As I remember its hapen during execution of '/etc/rc6.d/K90network' when downing
lo interface.

Mainboard is Gigabyte GA-7NF-RZ (bios up2dated, nforce2, using integrated
network and audio).

Comment 2 Dave Jones 2005-07-15 18:33:43 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 3 Bradley 2005-07-16 13:36:20 UTC
Havne't seen this for a while


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