Just downloaded kernel 2.6.7-1.517 and upon reboot got messages:
Mount error 6 mounting ext3 switchroot failed z2 kernel panic attempt to kill init!
My system: vanilla P-4 1.5GHz, MSI mobo no sata, no USB devs attached first ever panic
Scott
On Thu, 2004-12-08 at 10:45 -0700, Scott Talbot wrote:
Just downloaded kernel 2.6.7-1.517 and upon reboot got messages:
Mount error 6 mounting ext3 switchroot failed z2 kernel panic attempt to kill init!
My system: vanilla P-4 1.5GHz, MSI mobo no sata, no USB devs attached first ever panic
Scott
This has been Bugzilla'd already:
On Thu, Aug 12, 2004 at 10:45:18AM -0700, Scott Talbot wrote:
Just downloaded kernel 2.6.7-1.517 and upon reboot got messages:
Mount error 6 mounting ext3 switchroot failed z2 kernel panic attempt to kill init!
This is a mkinitrd problem. Either downgrade to mkinitrd-4.0.3-1 or wait until mkinitrd-4.0.5-1 will show up. In any case you will have to rebuild your initrd images which got affected.
first ever panic
A failure to mount / file system results in this outcome. :-)
Michal
On Thu, 2004-12-08 at 12:58 -0600, Michal Jaegermann wrote:
On Thu, Aug 12, 2004 at 10:45:18AM -0700, Scott Talbot wrote:
Just downloaded kernel 2.6.7-1.517 and upon reboot got messages:
Mount error 6 mounting ext3 switchroot failed z2 kernel panic attempt to kill init!
This is a mkinitrd problem. Either downgrade to mkinitrd-4.0.3-1 or wait until mkinitrd-4.0.5-1 will show up. In any case you will have to rebuild your initrd images which got affected.
From rom the comments in Bugzilla (#129773):
mkinitrd 4.0.5 at http://people.redhat.com/~katzj/mkinitrd/ should fix this (you'll need to rebuild your initrd)
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
That solved the problem for me.
On Thu, 2004-08-12 at 13:09 -0700, Christian Thibodeau wrote:
From rom the comments in Bugzilla (#129773):
mkinitrd 4.0.5 at http://people.redhat.com/~katzj/mkinitrd/ should fix this (you'll need to rebuild your initrd)
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
Didn't seem to work on this end. Updated the mkinitrd package and rebuilt initrd (using command above) and still same nfs problem
Well, my first post about this problem was ignored so I've decided to repost it + add some more problems to it.
First of all after clean install of FC3 test 1 I've updated the system via yum, at this time the sound in gnome was working just fine.
dropped down from kernel -517 to -515, mkinitrd doesn't work ..comes up with command not found"
installed newest Nvidia drivers and rebooted to KDE ... no sound!
re-logging as root or as user in Gnome or KDE makes no difference still no sound. I can make the speakers make a sound when I'm muting sound via Kmix, all I hear is the crackling "on-off" sound
apart form this in KDE the conqueror window keeps crashing every 2-5 sec after opening.
Another thing, where in new KDE can I stop my monitor form switching off? all there is in power management is laptop power ..I'm not on laptop I want my monitor and my HD's to work!..and I do now want to hard reset my FC box when I come back after more than an hour.
On Fri, 13 Aug 2004 20:26:23 +0100, Bart Kalita bartk@clara.co.uk wrote:
Well, my first post about this problem was ignored so I've decided to repost it + add some more problems to it.
This post is not very useful because it doesn't convey enough information for any other testers to compare with you and your hardware. And your methodology for troubleshooting isn't exceptionally linear which is a problem if you want people to trace your steps and compare with what you see. What you want to do is make it as easy as possible for people in the list to compare notes with you. So that means detail specifics about hardware that you think is important (in the case of sound at a minimum that means the sound card) It also means doing as much as you can to isolate each problem before you ask people for help with them. Reporting a whole list of problems that might or might not have shown up after you tried to fix other things, doesn't help other people help you confirm a specific problem. Help me, help you.
dropped down from kernel -517 to -515, mkinitrd doesn't work ..comes up with command not found"
So... you dropped back. Now thats a potential problem right there. You have not told us that sound was workingin in -515 ever. If sound worked in -517 but doesnt work in -515.. this is a non-issue. Going back to older versions of development packages to troubleshoot a new problem, like the mkinitrd issues right now, is a valid methodoloty. But you have to expect other things to break unexpectedly if you use an older development package. If -517 introduced fixes for sound, you lost them when moving back to -515.
And its very important to isolate issues when communicating them to others for troubleshooting or comparison. If something you did to work around the mkinitrd problem caused the sound problem to appear, that confuses things greatly, and its not necessarily worth anyone's time to troubleshoot, if the sound problem appears only when you use an older development kernel. Well, unless they are bug historians.
installed newest Nvidia drivers and rebooted to KDE ... no sound!
the nvidia video drivers? Thats also a problem. While you might get people to compare notes with you about your experience with the nvidia video drivers... ANY problems that only appear when the nvidia drivers are installed are beyond the scope of what any fedora developers can fix.
-jef
-----Original Message----- From: fedora-test-list-bounces@redhat.com [mailto:fedora-test-list- bounces@redhat.com] On Behalf Of Michal Jaegermann Sent: Thursday, August 12, 2004 2:59 PM To: For testers of Fedora Core development releases Subject: Re: kernel panic (517)
On Thu, Aug 12, 2004 at 10:45:18AM -0700, Scott Talbot wrote:
Just downloaded kernel 2.6.7-1.517 and upon reboot got messages:
Mount error 6 mounting ext3 switchroot failed z2 kernel panic attempt to kill init!
This is a mkinitrd problem. Either downgrade to mkinitrd-4.0.3-1 or wait until mkinitrd-4.0.5-1 will show up. In any case you will have to rebuild your initrd images which got affected.
first ever panic
A failure to mount / file system results in this outcome. :-)
Michal
Mkinitrd-4.0.5-1 works great....thanks for the fix.
On Thu, Aug 12, 2004 at 12:58:53PM -0600, Michal Jaegermann wrote:
This is a mkinitrd problem. Either downgrade to mkinitrd-4.0.3-1 or wait until mkinitrd-4.0.5-1 will show up. In any case you will have to rebuild your initrd images which got affected.
Is there a risk of this problem occuring with the kernel-2.6.8-1.521 update and mkinitrd-3.5.22 on FC2?
Is there a risk of this problem occuring with the kernel-2.6.8-1.521 update and mkinitrd-3.5.22 on FC2?
Not that I could tell. The bug was fixed in 4.0.6, but I used the 3.5 series while troubleshooting the 4.0.x bugs. I'm still recompiling my system, so I don't know if the current (4.1.1) has any new issues.
-Steve Grubb
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
-
Bart Kalita -
Christian Thibodeau -
Clyde Kunkel -
Jef Spaleta -
Matthew Miller -
Michal Jaegermann -
Mike Chambers -
Oldman -
Steve G