Bug 179588
| Summary: | kernel panic when mounting new root fs | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ronald Warsow <rwarsow> | ||||||||||||||||||||
| Component: | mkinitrd | Assignee: | Peter Jones <pjones> | ||||||||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> | ||||||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||||||
| Priority: | medium | ||||||||||||||||||||||
| Version: | rawhide | CC: | wtogami | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2006-02-27 16:37:06 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: | |||||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||||
| Bug Blocks: | 150221 | ||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
Ronald Warsow
2006-02-01 15:54:34 UTC
Created attachment 123967 [details]
dig. photo
So, what were the steps leading up to this? Is it a new install, an upgrade, or did you upgrade the package itself? Is there an older kernel that works? If so, can you do: mkdir /tmp/initrd cd /tmp/initrd zcat /boot/initrd-2.6.15-1.1884_FC5.img | cpio -di and then attach /tmp/initrd/init to this bug? Created attachment 123998 [details]
init from the last running kernel
Created attachment 123999 [details]
init from the kernel panic
Created attachment 124001 [details]
the difference of them: diff init-2.6.15-1.1826.2.10_FC5 init-2.6.15-1.1884_FC5
this box was fresh installed at 28.01.2006 to exclude problems with/on my box after getting problems with each kernel since Version 2.6.15-1.1826.2.10_FC5. see BUG 179075 this is not testable with that kernel panic now. Comment on attachment 124001 [details]
the difference of them: diff init-2.6.15-1.1826.2.10_FC5 init-2.6.15-1.1884_FC5
LABEL=/12 == /dev/sda6
Where's it getting "/12" from? What version of mkinitrd are you using? Can you try rebuilding your initrd with mkinitrd 5.0.20-1 ? /12 came from 2cd installation, anaconda labels the 2cd root partition as /1 or /12. /dev/sda1 / => my FC4 installation /dev/sda6 /12 => my FC5-devel installation BUT is seems, that it is fixed with kernel 2.6.15-1.1898_FC5... thx ! kernel panic back AGAIN ! realizing that kerenel panic comes and goes, my questition: could it be, that the different kernels are build on different machines from different developers ? each time, when kernel panic comes up again, there seems that a module sd_mod.ko is involved. realizing that over the last 6-8 kernels. s. attachements Created attachment 124310 [details]
diff init's
Created attachment 124311 [details]
contents of init directory lib kernel 1909
Created attachment 124312 [details]
contents of init directory lib kernel 1914
Created attachment 124313 [details]
rpm -qpi kernel 1909
Created attachment 124314 [details]
rpm -qpi kernel 1914
after getting the input to build a new initrd with mkinitrd and realizing that a new kernel installation depends on the contense of (?) modprobe.conf or doing modprobe sd_mod and then building a new initrd-xxx.img, I was able to help myself. now I am on kernel-2.6.15-1.1948_FC5 and not excluded from new kernels. works 4 me ! sorry 4 bad english... I ran into something similar, doing an upgade to FC5t3 from FC4 via the installer; the initrd created by the kernel installation did not include sd_mod (on my ata_piix x86 system), so the necessary root/swap devices didn't exist. Recreating the initrd image with mkinitrd, expeclitily including a --with option for sd_mod fixed things. I'm not sure why it didn't get picked up the first time around -- my previous kernels were hand-built with ata_piix and the various sd* bits compiled in, because I was trying to get suspend/hibernate/etc working (with no luck) -- but I wouldn't have thought that mattered, since sd_mod was clearly loaded by anaconda and the like. *** This bug has been marked as a duplicate of 182008 *** |