Bug 149759 - kernel panic with 2.6.10-1.1153
Summary: kernel panic with 2.6.10-1.1153
Status: CLOSED DUPLICATE of bug 149758
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-25 22:50 UTC by Clyde E. Kunkel
Modified: 2015-01-04 22:17 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2006-02-21 19:08:13 UTC

Attachments (Terms of Use)

Description Clyde E. Kunkel 2005-02-25 22:50:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20050109 Fedora/1.7.5-3

Description of problem:
After updating from today's rawhide, kernel panic with
2.6.10-1.1153_FC4smp and non-smp. 1149smp works fine. 

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

How reproducible:

Steps to Reproduce:
1. boot using standard grub config file

Actual Results:  kernel panic

Expected Results:  normal boot

Additional info:

here are the only msgs I could get, nothing in logs.
(during boot, detects raid devices, etc, then:)

Creating root device
mounting root filesystem
mount: error 19 mounting ext3
mount: error 2 mounting none
Switching to new root
Switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not ysncing: Attempted to kill init!

kernel 1149 boots ok, and did a mkinitrd, but didn't help

diff of configs:
# diff /boot/config-2.6.10-1.1149_FC4smp /boot/config-2.6.10-1.1153_FC4smp
< # Linux kernel version: 2.6.10-1.1149_FC4smp
< # Mon Feb 21 15:22:07 2005
> # Linux kernel version: 2.6.10-1.1153_FC4smp
> # Thu Feb 24 15:52:08 2005

root partition is a raid0 partition.

Comment 1 raxet 2005-02-26 07:27:46 UTC
Ditto here, only module ata_piix failed to load

Comment 2 Alexandre Oliva 2005-02-26 08:03:27 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:08:13 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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