Bug 467161

Summary: kerneloops on boot (ext4 related)
Product: [Fedora] Fedora Reporter: James Cassell <fedoraproject>
Component: kernelAssignee: Eric Sandeen <esandeen>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: rawhideCC: esandeen, gabriello.ramirez, kernel-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-16 16:12:09 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
kernel oops message
none
kernel oops message none

Description James Cassell 2008-10-16 06:11:40 UTC
Created attachment 320517 [details]
kernel oops message

Description of problem:
system won't boot.  Kernel panic after logical volumes are active (my guess is when it reads filesystem).  I'm guessing that my filesystem is corrupt, because it happens with all the kernels I have (back to the one right before .27-3)

Version-Release number of selected component (if applicable):
2.6.27-13.fc10.x86_64

How reproducible:
unknown/always

Steps to Reproduce:
1.turn on system
I really have no idea how to reproduce this
  
Actual results:
system should boot normally

Expected results:
kernel panic

Additional info:

Comment 1 James Cassell 2008-10-16 06:13:31 UTC
the oops message I attached is only the first part/halfish.  I will type the rest of it if someone says it's necessary, but I don't have time right now (perhaps tomorrow)

Comment 2 James Cassell 2008-10-16 15:21:05 UTC
Created attachment 320565 [details]
kernel oops message

I got the remainder from a separate boot (same kernel, of course), but the call trace is exactly the same.  A couple of registers were different

Comment 3 Dave Jones 2008-10-16 15:40:55 UTC
*** Bug 466843 has been marked as a duplicate of this bug. ***

Comment 4 Eric Sandeen 2008-10-16 16:12:09 UTC
Needed to update the ext4 patch queue again; the "do_mballoc_init_before_doing_filesystem_recovery" patch should take care of this failure.

Should be in the next build.

Thanks,
-Eric