[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [suse-security] Kernel Panic after Security Update
may be of interest to you as since yesterday there is a new aaa_base online
for updates of 8.0
File-Description: Fixes mk_initrd which created a broken initrd if ext3 is
as root filesystem together with newer kernels.
> -----Ursprungliche Nachricht-----
> Von: Mark O. Stitson [mailto:mark@xxxxxxxxxxx]
> Gesendet: Montag, 31. Marz 2003 16:46
> An: Stefan Proels
> Cc: suse-security@xxxxxxxx
> Betreff: Re: [suse-security] Kernel Panic after Security Update
> We have a SuSE 8.0 running on an Athlon system with a Symbios SCSI
> controller and the root filesystem on an ext3 partition and received the
> same error.
> I have now compiled the patched kernel from scratch and it seems the
> kernel tries to mount the root file system before kjournald and ext3 is
> available, so it defaults to mounting it as ext2 instead. SCSI and ext3
> are statically compiled into the kernel, so I am at a loss what is going
> wrong. Now I avoid the kernel panic, but my root filesystem is ext2.
> On Mon, 31 Mar 2003, Stefan Proels wrote:
> > 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-help@xxxxxxxx
> > Security-related bug reports go to security@xxxxxxx, not here
> Dr Mark O. Stitson, Senior Systems Programmer
> Yospace: Creating Value for Wireless
> 7 The Courtyard, High Street, Staines, UK, TW18 4DR
> Tel: +44 1784 466388
> Fax: +44 1784 466387
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> Any unauthorised dissemination or copying of this email or its
> and any use or disclosure of any information contained in them,
> is strictly
> prohibited and may be illegal. If you have received the email in error
> please notify contracts@xxxxxxxxxxx and delete it from your system.
> Check the headers for your unsubscription address
> For additional commands, e-mail: suse-security-help@xxxxxxxx
> Security-related bug reports go to security@xxxxxxx, not here
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here