Bug 127795

Summary: shutdown causes kernel oops when trying to sync disks
Product: [Fedora] Fedora Reporter: Jeff Nessen <jeff>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED NEXTRELEASE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 2CC: pfrields, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-16 05:45:54 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 Flags
syslog entries from sync problem
none
Ouput from lspci none

Description Jeff Nessen 2004-07-13 23:08:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
The system gets into some(???) state where attmeping to issue the sync
command from the shell prompt, or shutting the ssytem down (which
issues the sync command) cases a kernel oops.  After issueing either
init 0 or 6 at the shel pormpt the system will hang when attempting to
unmount disks.  Since the disks can not be unmounted, the system can
not be cleanly shutdown.  I will attach the output from syslog as well
as some information about my running system.

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


How reproducible:
Sometimes

Steps to Reproduce:
1. wait for system to get into this funky state
2. issue the sync command
3. try to shutdown
    

Actual Results:  kernel oops

Expected Results:  a nice clean sync of the disks and system shutdown

Additional info:

Comment 1 Jeff Nessen 2004-07-13 23:11:59 UTC
Created attachment 101873 [details]
syslog entries from sync problem

Comment 2 Jeff Nessen 2004-07-13 23:15:24 UTC
Created attachment 101874 [details]
Ouput from lspci

lspci listing showing shipset information (if this is usefull).

Comment 3 Dave Jones 2004-11-27 04:48:33 UTC
can you try and repeat this with the 2.6.9 update kernel please ?


Comment 4 Jeff Nessen 2004-11-29 19:26:27 UTC
At first glance it appears the problem is resolved.  I am remote to the system
right now, and have issued the sync command about a dozen times.  When I get in
front of the machine I will try a shutdown.  So far so good.

Comment 5 Dave Jones 2005-04-16 05:45:54 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.