On Thu 15-01-09 07:55:48, Felix Miata wrote:
On 2009/01/12 08:55 (GMT-0500) Felix Miata composed:
has these. Anyone know reasons for or against trying to use any of them on
a production server? My problem is
which is marked fixed,
but for 11.1, not 11.0. For the reasons listed in the thread
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?
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
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.
Jan Kara <jack(a)suse.cz>
SUSE Labs, CR
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org