[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
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
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
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.
From: Selcuk Ozturk [mailto:sozturk@xxxxxxxxxxxxxx]
Sent: Thursday, June 24, 2004 1:21 PM
Subject: Re: [suse-security] what has become of the latest kernel
Does this only affect the 2.6 kernels? Did anyone have any problems with
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...
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