l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 Dec 24 12:32

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Kernel Panic
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Kernel Panic

From the suse security announcements mail list

could this shed any light on the problem

Bill Wells

On Thursday 23 December 2004 09:19 pm, Robert G. Scofield wrote:
Subject: [suse-security] Re: SUSE Security Announcement: various kernel 
problems (SUSE-SA:2004:044)
Status: RO
X-Status: R
X-KMail-EncryptionState: N
X-KMail-SignatureState: F

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Dec 24, 2004 at 11:28:58AM +0100, Marcus Meissner wrote:
> On Wed, Dec 22, 2004 at 03:21:07PM +0100, Marcus Meissner wrote:
> > Hi folks,
> >=20
> > Like some of you noted the 9.2 kernels RPMs are not there anymore, even
> > though they are listed in the advisory.
> >=20
> > This is due us receiving reports where the Yast Online Update updating
> > this kernel made the machine fail to boot.
> >=20
> > The reason is that a script is no longer creating the vmlinuz and initrd
> > symlinks as is required for successful booting.
> >=20
> > We are preparing updated fixed packages for this problem and will be re=
> > them hopefully within the next day(s).
> We have released fixed 9.2 kernel packages, available either from Yast On=
line Update
> or via the URLs below.

The following only affects SUSE Linux 9.2.

We received additional reports of breakage if you have additionaly the User=
Mode Linux
Kernel package "kernel-um" installed.

In this case the system initrd will be created from "kernel-um" and not from
"kernel-default" or "kernel-smp"=20

As workaround:=20

- If you do not need the kernel-um package, deinstall it using:
 rpm -e kernel-um

   and recreate the system initird by running:

   before rebooting.

- if you need the kernel-um package, restore the symlink using:

        ln -sf /boot/initrd-2.6.8-24.10-default /boot/initrd

    (replace -default by the kerneltyp you use, detectable by:
     rpm -qa|grep kernel-

     which will be either "default", "smp" or "bigsmp".)

  after installing the updated packages and before booting the new kernel.

Ciao, Marcus

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.4 (GNU/Linux)



> Jonathan Stickel wrote:
> > Yep, "ls -l" would be helpful, but for seeing which files are
> > symlinks.   Hopefully you have 2 separate kernels available,
> > "2.6.8-24.10-um" and "2.6.8-24.10-default", and that one is not a
> > symlink to the other.  From your first post, the errors seemed to be
> > about the "um" kernel.  Maybe we can try to boot the "default"
> > kernel.  This will require some manual editing of grub.conf (or maybe
> > menu.1st; on my system, menu.1st is a symlink to grub.conf).  Can you
> > share a "ls -l" of /boot and /boot/grub?
> >
> > Jonathan
> Here is what ls -l of /boot shows as far as symbolic links; it looks
> like there are 4:
> "System.map-2.6.8-24.10-default
> System.map-2.6.8-24.10-um
> backup_mbr
> boot (pale blue) -> .
> config-2.6.8-24.10-default
> config-2.6.8-24.10-um
> grug (blue)
> initrd (green) -> initrd-2.6.8-24.10-um
> initrd-2.6.8-24.10-default
> initrd-2.6.8-24.10-um
> linux (pale blue)  -> linux-2.6.8-24.10-um
> linux-2.6.8-24.10-um (green)
> memtest.bin
> message
> symvers-2.6.8-24.10-i386-default.gz (red)
> symvers-2.6.8-24.10-um-um.gz (red)
> vmlinux-2.6.8-24.10-default.gz (red)
> vmlinux (pale blue)  -> vmlinuz-2.6.8-24.10-default
> vmlinuz-2.6.8-24.10-default"
> As for ls -l for /boot/grub, there are a lot of files there.  Two of the
> files are menu.lst and menu.lst.old.  There were no arrows at all.  So I
> assume that there are no symbolic links in /boot/grub.
> I did a "less command" for menu.lst, and this looks like the file that
> would have to be edited.  There's a lot of complicated stuff in there.
> Bob
> > _______________________________________________
> > vox-tech mailing list
> > vox-tech@lists.lugod.org
> > http://lists.lugod.org/mailman/listinfo/vox-tech
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.