FC2 > FC3 bad kernel woes

[Shannon Scott]

I was able to get the system up again by installing the most recent FC2
kernel rpm, and booting into it.  Everything actually seems to work
fine.
I'm not sure why I got the XFree86 errors with the new kernel, this
system always runs in run level 3.  When I am feeling brave again, I
will try to run yum.
Thank you to all who responded.  Your input was instrumental to getting
the system back up.
Take Care.
Shannon



-----Original Message-----
From: linux-users-bounces at linux-sxs.org
[mailto:linux-users-bounces at linux-sxs.org] On Behalf Of Net Llama!
Sent: Friday, December 03, 2004 6:42 AM
To: Linux tips and tricks
Subject: RE: FC2 > FC3 bad kernel woes

Shannon, FYI, your mail client's quoting is really fubar.

On Fri, 3 Dec 2004, Shannon Scott wrote:
> > 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."

That error (and its more of a warning than an error), is 100% harmless,
and has nothing at all to do with the probelm you're reporting.  I've
seen
that same warning on every box running a 2.6 kernel, Fedora and
otherwise.

> > 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.

2.6 kernels require *only* the following 4 commands to be built:
make mrproper
make [menuconfig|oldconfig|xconfig] #plus other variants on
configuration
tools
make
make modules_install

make runs 'make bzImage' amongst other things, so you did do that part,
but you left off a bunch of other steps (like building and installing
modules).

> 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.

do you have sshd running on the box?  If you boot into runlevel 3, then
you'll not get the atdb.c errors.

>
> Is it possible to downgrade back to the FC2 kernel?

In theory, sure.  But i doubt it will improve your situation any, since
FC3 requires udev support, and FC2 kernels didn't include that (AFAIK).

Go ahead and (re)install a FC2 kernel RPM (with rpm -ivh) and then
you'll
have that one as a boot option.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman                                netllama at linux-sxs.org
Linux Step-by-step & TyGeMo                  http://netllama.ipfox.com
_______________________________________________
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 !