Bug 440583

Summary: nit[1]: segfault at 00000006 eip 00000006 esp bf81c558 error 4 with kernel 2.6.24 on Dell Inspiron E1505
Product: [Fedora] Fedora Reporter: Jeff Cook <cookiecaper>
Component: mkinitrdAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: low    
Version: 8Keywords: Reopened
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-09 07:46:02 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:

Description Jeff Cook 2008-04-04 06:33:57 UTC
Description of problem:

Machine reports init[1]: segfault at 00000006 eip 00000006 esp bf81c558 error 4
repeatedly in an endless loop while trying to boot. 

With quiet removed from the GRUB command, printk notifies that 314xxx messages
were suppressed on each error and this loop begins after "Write protecting the
kernel read-only data: 844k".

The address following esp changes on each boot. This time it was bf81c558 ... on
reboot, it is bfe38b78, after another reboot it is bfd7e2b8, and so on. This
problem has existed with every 2.6.24 kernel which yum has detected so far, most
recently 2.6.24.4-64.fc8. Kernels <= 2.6.23.15-137 work as expected.

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

2.6.24

How reproducible:

Attempt to boot a Dell Inspiron E1505 with Fedora 8 and Kernel 2.6.24. (Dell
Service Tag 4RJSBB1). Experience failure.

Steps to Reproduce:
1. Acquire Dell Inspiron E1505 with Fedora 8 and kernel 2.6.24 installed
2. Attempt to boot system with kernel 2.6.24
3. Experience failure
  
Actual results:

System repeats esoteric error in endless loop

Expected results:

System boots and allows user to operate

Comment 1 Dave Jones 2008-04-04 17:07:50 UTC

*** This bug has been marked as a duplicate of 440091 ***

Comment 2 Dave Jones 2008-04-04 17:10:10 UTC
On second thoughts, this is different, as you weren't updating to rawhide.
Still likely to be a mkinitrd bug though.


Comment 3 Bug Zapper 2008-11-26 10:23:58 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-01-09 07:46:02 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.