RE: [suse-security] what has become of the latest kernel hang/fre eze bug?
I had a problem last night with the 2.4.21-226 rpm update. I am running SuSE 9.0 Pro on a Dell 1750 2x/2.8Ghz P4 Intel CPUs, with 1GB of RAM. PERC 4/di RAID controllers, 3x/36GB drives, two are in RAID5, the other is stand-alone. I have 5 of these machines with identical hardware configurations. One machine is a dev box, the other is a staging box, and three more machines that make up my production environment. I updated the dev box using the procedures given in the kernel update advisory. rpm -Uhv --nodeps --force <kernel update rpm> It gave the standard output of a successful update, and rebooted successfully. When I ran the same procedure on my staging server, it never came back up. I suspect the initrd didn't install correctly. Could I please get a link to the procedure for re-installing the initrd in 9.0? Preferably from a CDROM. Thanks in advance. Jason -----Original Message----- From: Selcuk Ozturk [mailto:sozturk@fdchemedia.com] Sent: Thursday, June 24, 2004 1:21 PM To: suse-security@suse.com Subject: Re: [suse-security] what has become of the latest kernel hang/freeze bug? Does this only affect the 2.6 kernels? Did anyone have any problems with 2.4 updates? Selcuk Roman Drahtmueller wrote:
I misunderstood your question, then. I wasn't aware these updated kernels had problems - I have 3 9.0 and 1 9.1 systems that don't have any problems running these kernels.
I think we've found it. If you feel like, please try out the kernels of the day (kotd), to be found at http://ftp.suse.com/pub/projects/kernel/kotd/i386/.
There is a kernel update pending to fix the hangs that you might see under some circumstances. And there are some more things in the queue for this update...
Thanks, Roman.
-- 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
Hi Jason, I needed such a CD 3 days ago because of broken boot-sector. I found nothing from SuSE about that, but this solved my problem: http://www.mandrakeusers.org/index.php?showtopic=11801 Greetings, Ralf Counts, Jason wrote:
I had a problem last night with the 2.4.21-226 rpm update. I am running SuSE 9.0 Pro on a Dell 1750 2x/2.8Ghz P4 Intel CPUs, with 1GB of RAM. PERC 4/di RAID controllers, 3x/36GB drives, two are in RAID5, the other is stand-alone. I have 5 of these machines with identical hardware configurations.
One machine is a dev box, the other is a staging box, and three more machines that make up my production environment. I updated the dev box using the procedures given in the kernel update advisory.
rpm -Uhv --nodeps --force <kernel update rpm>
It gave the standard output of a successful update, and rebooted successfully.
When I ran the same procedure on my staging server, it never came back up.
I suspect the initrd didn't install correctly. Could I please get a link to the procedure for re-installing the initrd in 9.0? Preferably from a CDROM. Thanks in advance.
Jason
Hi Jason,
I suspect the initrd didn't install correctly. Could I please get a link to the procedure for re-installing the initrd in 9.0? Preferably from a CDROM. Thanks in advance.
--> boot from your SuSE CD into "Rescue mode". Then mount the boot partition read-write on "/mnt" Run the script "mk_initrd" from /mnt/sbin" with the options "-d /mnt" and maybe "-b /mnt/boot" (don't remember whether the -b is needed. Use -m "eth0 ext3 ..." (customize to your needs) Good luck! Armin
On Friday 25 June 2004 00:52, Armin Schoech wrote:
Hi Jason,
I suspect the initrd didn't install correctly. Could I please get a link to the procedure for re-installing the initrd in 9.0? Preferably from a CDROM. Thanks in advance.
--> boot from your SuSE CD into "Rescue mode". Then mount the boot partition read-write on "/mnt"
Run the script "mk_initrd" from /mnt/sbin" with the options "-d /mnt" and maybe "-b /mnt/boot" (don't remember whether the -b is needed. Use -m "eth0 ext3 ..." (customize to your needs)
In order to avoid any problems (and cmdline args), I typically do a: mount /dev/xxx /mnt # root mount /dev/yyy /mnt/boot # boot (if seperate) chroot /mnt mkinitrd lilo # if not grub Pete
participants (4)
-
Armin Schoech -
Counts, Jason -
Hans-Peter Jansen -
Ralf Ronneburger