[opensuse-kernel] 2.6.27 kernel for 11.0?
http://download.opensuse.org/repositories/home:/ilya_41/openSUSE_11.0/i586/ has these. Anyone know reasons for or against trying to use any of them on a production server? My problem is https://bugzilla.novell.com/show_bug.cgi?id=406035 which is marked fixed, but for 11.1, not 11.0. For the reasons listed in the thread http://lists.opensuse.org/opensuse/2008-12/msg01969.html I'd rather not be forced into 11.1 if possible. Can anyone tell why the above bug's owner claims its fix amounts to a new feature preventing fix's inclusion in 11.0 updates? I installed .27 on an old ICH4 P4 GX260 PATA host I use for testing. Its 11.0 partition is on hda21, and so using piix legacy driver. After a while it locked hard while in runlevel 3. Then I installed .27 on a newer ICH7 P4 RAID1 SATA host "big31" using libata (not my new ICH8 server, but similar in being almost as new). So far big31 hasn't done the same. Can anyone look in the boot.msg & messages logs in http://fm.no-ip.com/tmp/SUSE/110/ and tell me if the lockup might have been due to the .27 kernel rather than piix driver or hardware failure? -- "Train a child in the way he should go, and when he is old he will not turn from it." Proverbs 22:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 2009-01-12T08:55:46, Felix Miata <mrmazda@ij.net> wrote:
http://download.opensuse.org/repositories/home:/ilya_41/openSUSE_11.0/i586/ has these. Anyone know reasons for or against trying to use any of them on a production server? My problem is https://bugzilla.novell.com/show_bug.cgi?id=406035 which is marked fixed, but for 11.1, not 11.0. For the reasons listed in the thread http://lists.opensuse.org/opensuse/2008-12/msg01969.html I'd rather not be forced into 11.1 if possible.
I run the SL111_BRANCH kernels from ftp://ftp.suse.com/pub/projects/kernel/kotd/ on my 11.0 system just fine. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On 2009/01/12 08:55 (GMT-0500) Felix Miata composed:
http://download.opensuse.org/repositories/home:/ilya_41/openSUSE_11.0/i586/ has these. Anyone know reasons for or against trying to use any of them on a production server? My problem is https://bugzilla.novell.com/show_bug.cgi?id=406035 which is marked fixed, but for 11.1, not 11.0. For the reasons listed in the thread http://lists.opensuse.org/opensuse/2008-12/msg01969.html I'd rather not be forced into 11.1 if possible.
Can anyone tell why the above bug's owner claims its fix amounts to a new feature preventing fix's inclusion in 11.0 updates?
I installed .27 on an old ICH4 P4 GX260 PATA host I use for testing. Its 11.0 partition is on hda21, and so using piix legacy driver. After a while it locked hard while in runlevel 3. Then I installed .27 on a newer ICH7 P4 RAID1 SATA host "big31" using libata (not my new ICH8 server, but similar in being almost as new). So far big31 hasn't done the same. Can anyone look in the boot.msg & messages logs in http://fm.no-ip.com/tmp/SUSE/110/ and tell me if the lockup might have been due to the .27 kernel rather than piix driver or hardware failure?
Ping? -- "Train a child in the way he should go, and when he is old he will not turn from it." Proverbs 22:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Hello, On Thu 15-01-09 07:55:48, Felix Miata wrote:
On 2009/01/12 08:55 (GMT-0500) Felix Miata composed:
http://download.opensuse.org/repositories/home:/ilya_41/openSUSE_11.0/i586/ has these. Anyone know reasons for or against trying to use any of them on a production server? My problem is https://bugzilla.novell.com/show_bug.cgi?id=406035 which is marked fixed, but for 11.1, not 11.0. For the reasons listed in the thread http://lists.opensuse.org/opensuse/2008-12/msg01969.html I'd rather not be forced into 11.1 if possible.
Can anyone tell why the above bug's owner claims its fix amounts to a new feature preventing fix's inclusion in 11.0 updates? Sorry, don't know CIFS good enough. But if Jeff claims that fixing this means a new feature then I'd trust him...
I installed .27 on an old ICH4 P4 GX260 PATA host I use for testing. Its 11.0 partition is on hda21, and so using piix legacy driver. After a while it locked hard while in runlevel 3. Then I installed .27 on a newer ICH7 P4 RAID1 SATA host "big31" using libata (not my new ICH8 server, but similar in being almost as new). So far big31 hasn't done the same. Can anyone look in the boot.msg & messages logs in http://fm.no-ip.com/tmp/SUSE/110/ and tell me if the lockup might have been due to the .27 kernel rather than piix driver or hardware failure? I've looked at those messages but they don't show anything suspicious. Neither regarding the kernel, nor about the HW. If you're able to reproduce the lockup, it might be worth reporting into bugzilla (we'd then need more info to debug this like whether the keyboard still reacts when the lockup happens, whether it happens also when the kernel is in console only etc.). Generally, I don't know a reason why 11.0 distro should have problems running a kernel from 11.1. They are quite close.
Honza -- Jan Kara <jack@suse.cz> SUSE Labs, CR -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (3)
-
Felix Miata -
Jan Kara -
Lars Marowsky-Bree