RE: [suse-security] SuSE Security Announcement: kernel (SuSE-SA:2 003:021)
on a SuSE 8.0 installation with an ext3 root filesystem, the new kernel panics on boot, saying that can't access device 03:05 (the root filesystem is on /dev/hda5). The previous kernel did not exhibit this problem. The
I have experienced the same problem with SuSE 7.3 - just in my case it was the disk 80:03 (sda3) . The computer boots only after I have changed the fstab entry to mount the root system as ext2 - now I have a warning that I am mounting an ext3 system as ext2, but at least the kernel is not in panic. I have exactly followed the update procedure, namely I have run mk_initrd and lilo (and both initrd files are now rebuilt). I had no problem when mounting the filesystem in Tiny floppy linux Tomsrtbt. I know that oficially ext3 was supported only in SuSE 8.0, but with the previous kernel (2.4.16) I had absolutely no problem. sincerely Vaclav Brunnhofer ___________________________________ NOCC, http://nocc.sourceforge.net
By now, there have been several reports here about systems rendered unuseable after applying said update. By now, it would be nice to get some reaction from SuSE on that topic... bye, [MH] -- Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und 823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt! gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C
On Mit, 26 Mär 2003, Mathias Homann wrote:
By now, there have been several reports here about systems rendered unuseable after applying said update. By now, it would be nice to get some reaction from SuSE on that topic...
Really? I've seen two reports so far: a) one from somebody who forgot to run mkinitrd (though it was explicitely mentioned in the advisory) b) one from somebody using binary only drivers which taint the kernel. There is nothing SuSE or anybody else could do about that. -- Dirk
Dirk Mueller wrote:
On Mit, 26 Mär 2003, Mathias Homann wrote:
By now, there have been several reports here about systems rendered unuseable after applying said update. By now, it would be nice to get some reaction from SuSE on that topic...
Really?
I've seen two reports so far:
Then you have missed mine and at least one more person's reports of problems with alsa sound modules (possibly yast2, too) and the new kernels.
a) one from somebody who forgot to run mkinitrd (though it was explicitely mentioned in the advisory)
b) one from somebody using binary only drivers which taint the kernel.
There is nothing SuSE or anybody else could do about that.
Selcuk
Am Mittwoch, 26. März 2003 15:56 schrieb Selcuk Ozturk:
I've seen two reports so far:
Then you have missed mine and at least one more person's reports of problems with alsa sound modules (possibly yast2, too) and the new kernels.
as well as the one from that guy who couldn't access his adaptec controller anymore. bye, [MH] -- Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und 823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt! gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C
I have "avoided" the problem by changing the order of the ext3 and jbd drivers in /etc/sysconfig/kernel, so that the loading of the ext3 module fails for initrd, the filesystem is then mounted as ext2, but when the root filesystem is remounted read/write it seems to remount it as ext3 and the system seems happy. Does anyone know if this might cause problems? Mark On Wed, 26 Mar 2003, Vaclav Brunnhofer wrote:
on a SuSE 8.0 installation with an ext3 root filesystem, the new kernel panics on boot, saying that can't access device 03:05 (the root filesystem is on /dev/hda5). The previous kernel did not exhibit this problem. The
I have experienced the same problem with SuSE 7.3 - just in my case it was the disk 80:03 (sda3) .
The computer boots only after I have changed the fstab entry to mount the root system as ext2 - now I have a warning that I am mounting an ext3 system as ext2, but at least the kernel is not in panic.
I have exactly followed the update procedure, namely I have run mk_initrd and lilo (and both initrd files are now rebuilt).
I had no problem when mounting the filesystem in Tiny floppy linux Tomsrtbt.
I know that oficially ext3 was supported only in SuSE 8.0, but with the previous kernel (2.4.16) I had absolutely no problem.
sincerely Vaclav Brunnhofer
___________________________________ NOCC, http://nocc.sourceforge.net
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, 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 http://www.yospace.com 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 attachments, 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@yospace.com and delete it from your system.
participants (5)
-
Dirk Mueller -
Mark O. Stitson -
Mathias Homann -
Selcuk Ozturk -
Vaclav Brunnhofer