Bug 129773
| Summary: | kernel 2.6.7-1.517smp panic during boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Clyde E. Kunkel <clydekunkel7734> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | bmillett, djr, hannes.kuehnemund, nphilipp, pfrields, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-11-28 08:28:52 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: | 130887 | ||
mkinitrd 4.0.5 at http://people.redhat.com/~katzj/mkinitrd/ should fix this (you'll need to rebuild your initrd) *** Bug 129750 has been marked as a duplicate of this bug. *** *** Bug 129790 has been marked as a duplicate of this bug. *** Works for me, thanks. rpm -Uvh mkinitrd-4.0.5-1.i386.rpm mkinitrd -f /boot/initrd-2.6.7-1.517.img 2.6.7-1.517 reboot Works for me also. Many thanks. This solution works for me with the non-smp kernel also. Much appreciated. Thanks also for the steps plainly laid out in comment 4 ... saved me some man-ning to get the command format right. had the same problem when updating FC1 to FC3-test3 yesterday. reissuing mkinitrd resolved the problem, probably problem in the installer? I'm reopening this one, as it seems that somehow the old mkinitrd got run instead of the new one. I guess it may have went this way: - Update from FC1 with rather ancient mkinitrd - anaconda installs the kernel(s) before mkinitrd, because it can't know it any better (kernel requires 3.5.5, FC1 has 3.5.14) - initrds are bust because they can't work in the new environment To fix this, I would have the kernel require current mkinitrd. Or re-run mkinitrd after installing pkgs in anaconda, but this is kind of lame. kernel-2.6.9-1.639 prereqs a fairly recent mkinitrd. mass update for old bugs: Is this still a problem in the 2.6.9 based kernel update ? Not for me. Thanks. |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Description of problem: during boot of new kernel 2.6.7-1.517smp kernel panic occurs. Partial msgs follow: Creating block devices Creating root devices Mounting root file system Mount: error 6 mounting exts Switching to new root Switchroot: mount failed: 22 Kernel panic: Attempted to kill init! Same problem when trying with non-smp version. Booting with .515smp is fine. No entries that I can find in logs. Grub.conf entry: root (hd0,0) kernel /vmlinuz-2.6.7-1.517smp ro root=LABEL=/1 psmouse.proto=imps initrd /initrd-2.6.7-1.517smp.img Version-Release number of selected component (if applicable): 2.6.7-1.517smp How reproducible: Always Steps to Reproduce: 1.boot computer using kernel 2.6.7-1.517smp 2. 3. Actual Results: kernel panic after problem mounting root file system Expected Results: normal boot Additional info: