Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 231973 - A lot of unkown symbol in ata_piix.ko module when using kernel-2.6.20-1.2982.fc7
Summary: A lot of unkown symbol in ata_piix.ko module when using kernel-2.6.20-1.2982.fc7
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-13 12:25 UTC by MENGIS Michel
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-10-16 16:19:08 UTC

Attachments (Terms of Use)

Description MENGIS Michel 2007-03-13 12:25:02 UTC
Description of problem:
kernel-2.6.20-1.2982.fc7: a lot of unknown symbol in ata_piix.ko module
not booting.

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

How reproducible:
install test2 and do a yum update

Steps to Reproduce:
1. install fc7 test2
2. update the packages 
3. try to boot...
Actual results:
not booting. kernel panic. coz unable to load the ata_piix.ko.
A lot of unkown symbols...

Expected results:
 boot :)

Additional info:

Comment 1 Rask Ingemann Lambertsen 2007-04-07 08:00:28 UTC
I have the same problem with a freshly installed FC7 test3: It fails to boot
because the ata_piix module won't load.

Steps to Reproduce:
1. Install FC7 test3.
2. Try to boot.

There are 34 messages about unknown symbols (presumably many more scrolled off
the screen), starting with:
ata_piix: Unknown symbol ata_bmdma_start

In the end, insmod gives up:
insmod: error inserting '/lib/ata_piix.ko': -1 Unknown symbol in module

Other unknown symbols reported are: ata_bmdma_stop, ata_bmdma_setup,
ata_bmdma_thaw, pci_test_config_bits.

Comment 2 Rask Ingemann Lambertsen 2007-04-08 16:50:03 UTC
The problem is a broken initrd, which doesn't contain and doesn't load the scsi
and libata modules. Here is how to repair the system to a bootable state:

1. Boot the rescue CD.
2. Mount your system on /mnt/sysimage.
2a. If necessary, mount your boot partition on /mnt/sysimage/boot.
3. mkdir /mnt/sysimage/tmp/initrd
4. cd /mnt/sysimage/tmp/initrd
5. gzip -cd </mnt/sysimage/boot/initrd-*.img | cpio --extract
6. Find the modules libata.ko, scsi_mod.ko and sd_mod.ko in
/mnt/sysimage/lib/modules and copy them to the lib directory.
7. Edit (joe, pico, nano, emacs, ...) the file init to include these six lines
right before it tries to load ata_piix.ko:

echo "Loading scsi_mod.ko module"
insmod /lib/scsi_mod.ko
echo "Loading sd_mod.ko module"
insmod /lib/sd_mod.ko
echo "Loading libata.ko module"
insmod /lib/libata.ko

8. Generate a new initrd image:
find . -print | cpio --create --format newc | gzip -c9
9. cd /
10. Unmount, reboot and at the GRUB prompt, edit the boot commands to use your
new initrd. It should work, then.

Given the above, I think the right component to blame is mkinitrd or the
installer, rather than the kernel.

Comment 3 Will Woods 2007-04-19 18:16:09 UTC
IIRC this was due to a selinux policy error which prevented a proper module
deplist from being created. It's fixed for me now. Does it work for you?

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