OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: [suse-security] Kernel Panic after Security Update

From: Radu Voicu (suseploiesti.rdsnet.ro)
Date: Mon Mar 31 2003 - 04:27:17 CST


Hi there!

Like I was saying last week, there's a human error in the compilation of the
modules, because the kernel is 2.4.18-GB, but the modules reference inside
are to 2.4.19-4GB... but you can use the updated 2.4.19-4GB (the last -
patched - version) in order to have a running machine with a secure kernel -
that's what I do (and do not forget about modutils).

Radu

----- Original Message -----
From: "Stefan Proels" <stefan.proelsgmx.de>
To: <suse-securitysuse.com>
Sent: Monday, March 31, 2003 1:18 PM
Subject: [suse-security] Kernel Panic after Security Update

Hello,

after installing the latest kernel update for the ptrace security issue on
a SuSE 8.0 system, the new kernels panics while booting with the message
"VFS: unable to mount root fs". My possibilities to analyze this problem
are very limited since the system in question is an important 24x7
production system to which I only have remote access and when the system
fails to boot this can only be fixed with the help of a local engineer.
This is why I'm asking this list if anyone has experienced this problem
before and possibly even has a solution for it. As a note, the new kernel
works fine on two SuSE 7.1 systems.

Some information on the system:

SuSE 8.0,
SuSE SMP Kernel 2.4.18-64GB-SMP for 2 P-III CPUs,
1 GB RAM,
2 SCSI drives with Adaptec SCSI controller.

Root-Filesystem is ext3
INITRD_MODULES="aic7xxx usbcore jbd ext3"
Bootloader lilo

mk_initrd und lilo after installation of the new kernel ran without any
error messages.

After re-installing the old SuSE 2.4.18 Kernel with the security leak the
systems boots up fine again.

Thanks in advance
Stefan

--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-helpsuse.com
Security-related bug reports go to securitysuse.de, not here

--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-helpsuse.com
Security-related bug reports go to securitysuse.de, not here