FC2 > FC3 bad kernel woes

[Shannon Scott]

-----Original Message-----
From: linux-users-bounces at linux-sxs.org
[mailto:linux-users-bounces at linux-sxs.org] On Behalf Of Tim Wunder
Sent: Friday, December 03, 2004 9:38 AM
To: Linux tips and tricks
Subject: Re: FC2 > FC3 bad kernel woes

On 12/3/2004 8:30 AM, I believe that Shannon Scott wrote:

> 
> 
> Happy Holidays.
> 
> I recently tried to upgrade Fedora Core 2 to Fedora Core 3. 
> 
> It turns out the FC3 cd's I burned had kernel-2.6.9-1.678_FC3 with
these 
> related bugs:
> 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139786
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139691
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139674
> 

-I'm confused. These bugs should only affect FC3 users who do an update
of 
-their kernel after they've installed FC3. FC3's kernel as provided on
the 
-downloaded installation ISO's should work, and should not be (AFAIK) 
-kernel-2.6.9-1.678_FC3. At least that's how I'm reading these bug
-reports...

-Are you sure you're experiencing this same problem?
I guess I'm not exactly sure, but the issue does manifest in the same
way
That is described here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139786
After my upgrade reboot I received the following error:
"Kernel panic - not syncing: Attempted to kill init!"
I use a DELL PowerEdge 1750, could it be that I have uncovered a new
bug?

Also, the error I get with the newer kernel ( source and rpm ) does not
halt everything like it did after the first upgrade reboot.  With these
newer kernels, I get the same error, but then it is followed by an
infinite number of this error:
"atbdb.c: Spurious ACK on isa 0060/Serio0.  Some program, like XFree86,
might be trying to access hardware directly."

>  
> 
> If you go here:
> 
> http://www.fedoraforum.org/forum/showthread.php?t=27264
> 
> You will see that the suggested fix is to reboot, and use the grub
menu 
> to select an older kernel.  I don't think this is an option for me 
> because I was upgrading from FC2.  I only found the single FC3 kernel
in 
> the /boot directory after booting with the rescue disk.
> 
> So I downloaded the newest kernel rpm (kernel-2.6.9-1.681_FC3),
booted 
> to the rescue disk, performed the 'chroot /mnt/sysimage', and
installed 
> the kernel rpm.  The system still wouldn't boot.
> 
> So I downloaded the newest kernel source, booted to the rescue disk, 
> performed the 'chroot /mnt/sysimage', and compiled it using these 
> instructions:
> 
> http://www.fedoraforum.org/forum/archive/index.php/t-26572.html  ( 
> second post - using 'make oldconfig').
> 
> That won't boot either.
> 

-This may be a stupid question, but...
-What steps did you take for the "You can then proceed as usual" part of
the 
-instructions?

I almost included the info in my first post.  It was only my second time
compiling a kernel ( the first was 4 years ago ).
I used:
 make dep  - which gave a message saying it was no longer relevant.
 make bzImage
Then copied the file created in arch/i386/boot to /boot with a new name 
( kernel-test ), and modified my /etc/grub.conf to use that kernel.
I was a little confused at this step because the grub configuration from
the old kernel had a line for the initrd img, but I didn't have one for
the kernel I had created so I removed that line.

I was following the instructions from:
http://www.fedoraforum.org/forum/showthread.php?t=27135

-It seems to me that if you're compiling the kernel source from the
original 
-configuration, you'll have the same problems as you'd get from
installing 
-the pre-compiled RPM for the kernel. I'd think you'd need to change 
-something about your kernel configuration in order to avoid the
problem.

OK.  I'll look into using 'make config'.

> What can I try next? 

-Can you provide some information about your system and any specific
error 
-message you might be getting when the boot fails?

Dell Poweredge 1750 1 CPU
FC3 i686
Kernel panic - not syncing: Attempted to kill init!
atbdb.c: Spurious ACK on isa 0060/Serio0.  Some program, like XFree86,
might be trying to access hardware directly.

This last one repeats.  I'm not sure what happens before as it goes by
so fast, and is not logged.  Is there any way to stop the screen output
or the boot process at that stage?  Please let me know if I have not
provided the details you are interested in.

Is it possible to downgrade back to the FC2 kernel?

Thank you much
Shannon


_______________________________________________
Linux-users mailing list
Linux-users at linux-sxs.org
http://mail.linux-sxs.org/cgi-bin/mailman/listinfo/linux-users

Need to chat further on this subject? Check out #linux-users on
irc.linux-sxs.org !