Re: [SLE] Random system freeze after YOU update
Yongtao Yang <yongtao.yang@telia.com> writes:
On Tue, 2002-11-26 at 16:04, Joost van der Lugt wrote:
I do read this list to little, but if it is reiserfs you are using you may want to try Michael's advice:
----
What does it look like to mount barrier=none? Is this just as good as installing a new kernel? Mostly because I don't want to go through this hastle right now, but I too am having the kernel panic problems.
Add this option to the line in /etc/fstab. For example, if by default it is "defaults", change it to "defaults,barrier=none".
Michael -----
Joost
Hi, Joost:
Thank you ver much for your email, but I am not using reiserfs, all my partitions are formatted as Ext3.
Looking through the 'barrier' patch that SuSE applied to the stock 2.4.19 kernel it appears that ext3 is screwed up by it too, as well as ide.c -- but unfortunately barrier=none is not a valid mount option for ext3.
I have just repeated the test , this time I switched to the console(Ctrl+Alt+F10), then before the freeze, I saw error messages like:
... kernel oops... interrupt handler terminated. and some memory pinter information.
I think SuSE really should work this out. :(
They have a 2.4.18 version of the kernel that does not use barrier available on their ftp server.
Mark Gray <markgray-list-1037215486@iago.nac.net> writes:
Yongtao Yang <yongtao.yang@telia.com> writes:
On Tue, 2002-11-26 at 16:04, Joost van der Lugt wrote:
I do read this list to little, but if it is reiserfs you are using you may want to try Michael's advice:
----
What does it look like to mount barrier=none? Is this just as good as installing a new kernel? Mostly because I don't want to go through this hastle right now, but I too am having the kernel panic problems.
Add this option to the line in /etc/fstab. For example, if by default it is "defaults", change it to "defaults,barrier=none".
Michael -----
Joost
Hi, Joost:
Thank you ver much for your email, but I am not using reiserfs, all my partitions are formatted as Ext3.
Looking through the 'barrier' patch that SuSE applied to the stock 2.4.19 kernel it appears that ext3 is screwed up by it too, as well as ide.c -- but unfortunately barrier=none is not a valid mount option for ext3.
I have just repeated the test , this time I switched to the console(Ctrl+Alt+F10), then before the freeze, I saw error messages like:
... kernel oops... interrupt handler terminated. and some memory pinter information.
I think SuSE really should work this out. :(
They have a 2.4.18 version of the kernel that does not use barrier available on their ftp server.
Hello, Mark, Thank you very much, you explaination sounds very cogent. Can you please give me a link to 2.4.18 ketrnel? I have looked throught the suse server, both 8.1/suse/i[56]86 and update/8.1/rpm/i[56]86, no such packages. BTW, maybe this should be put into the unofficial SuSEFAQ. Best Regards! -- Yongtao Yang email: yongtao.yang@telia.com
* Yongtao Yang; <yongtao.yang@telia.com> on 26 Nov, 2002 wrote:
BTW, maybe this should be put into the unofficial SuSEFAQ.
Pleasure, just wrap it up so it's in a understandable format and place it as a Feature request at http://sourceforge.net/tracker/?atid=439830&group_id=42064&func=browse -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
participants (3)
-
Mark Gray -
Togan Muftuoglu -
Yongtao Yang