Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 207035 - unbootable kernel (sata_sil "unknown symbol in module")
Summary: unbootable kernel (sata_sil "unknown symbol in module")
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: rawhide
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks: FCMETA_SATA
TreeView+ depends on / blocked
 
Reported: 2006-09-18 21:01 UTC by Zack Cerza
Modified: 2008-08-02 23:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-04 14:59:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Zack Cerza 2006-09-18 21:01:28 UTC 
Description of problem:
The kernel hangs on boot because the SATA module fails to load, leaving it with
no root partition.

Version-Release number of selected component (if applicable):
kernel-2.6.17-1.2647.fc6.x86_64

How reproducible:
Always

Actual results:
Lots of "sata_sil: Unknown symbol foo" messages
Then "insmod: error insterting '/lib/sata_sil.ko': -1 Uknown symbol in module
And later: "Kernel panic - not syncing: Attempted to kill init!"
Comment 1 Dave Jones 2006-09-19 20:58:19 UTC 
sounds like a busted initrd.
can you paste your /etc/modprobe.conf ?
Comment 2 Zack Cerza 2006-09-20 16:50:54 UTC 
alias scsi_hostadapter sata_sil
alias eth0 tg3
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
options snd-intel8x0 index=0
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-intel8x0
Comment 3 Dave Jones 2006-09-28 22:36:20 UTC 
looks sensible.

Can you break open the initrd like so..

cp /boot/initrd-2.6.17-1.2647.fc6.img initrd.cpio.gz
gzip -d initrd.cpio.gz
cpio -t < initrd.cpio | grep \.ko

Also, you have the current mkinitrd package installed right ?
Comment 4 Zack Cerza 2006-09-29 17:19:52 UTC 
I used initrd-2.6.18-1.2693.fc6.img, since older kernels got removed. The
problem's still there.

lib/uhci-hcd.ko
lib/ohci-hcd.ko
lib/ehci-hcd.ko
lib/ext3.ko
lib/sata_sil.ko

I have mkinitrd-5.1.17-1.x86_64 installed.
Comment 5 Dave Jones 2006-10-05 22:57:49 UTC 
hmm, for some reason scsi_mod.ko didn't end up in your initrd.

Peter?
Comment 6 Peter Jones 2007-09-14 15:56:29 UTC 
Is this still broken?
Comment 7 Zack Cerza 2007-09-14 16:12:03 UTC 
I think I remember which box this happened on, and I think I may even still have
it in the office. I should be able to retest it on 9/24 at the earliest.
Comment 8 Bug Zapper 2008-04-03 18:15:14 UTC 
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 9 Zack Cerza 2008-04-04 14:59:29 UTC 
Can't find the box; If I do and this is still a problem, I'll reopen.
Note You need to log in before you can comment on or make changes to this bug.