Hi All, I REALLY want to start using SuSE 8.0 on my workstation, byt up to now I have just had bad luck. It is fighting me all the way. The problem that I still cannot fix is the freezing up of the machine. I am still not sure what the problem is exactly, because there is no trace of problems in the log files. THe machine will just freeze dead. Even the network is dead. At this stage I suspect the ide-scsi emulation, because the common factor seem to be that every time the machine froze, either X-CD-Roast or KonCD was running. They were not always busy writing a CD. Is is possible that the problem can be related to ide-scsi emulation, or is just coincedence? At this stage SuSE is worse than Windows. I have RedHat on the machine also and everything is stable there, so it is not hardware. Any ideas where I can start to look for the problems? Special log files, tracing I can enable that will tell me what happens just before the thing dies? Special monitoring software? Anyone? Please? Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
Are you using automount? If so try and disable it and then try it again. Marshall Heartley A+,Network+ "Nothing is impoissible, We just do not have all the anwsers to make the impossible, possible." On Sat, 2002-06-01 at 12:45, Andre Truter wrote:
Hi All,
I REALLY want to start using SuSE 8.0 on my workstation, byt up to now I have just had bad luck. It is fighting me all the way.
The problem that I still cannot fix is the freezing up of the machine. I am still not sure what the problem is exactly, because there is no trace of problems in the log files.
THe machine will just freeze dead. Even the network is dead. At this stage I suspect the ide-scsi emulation, because the common factor seem to be that every time the machine froze, either X-CD-Roast or KonCD was running. They were not always busy writing a CD.
Is is possible that the problem can be related to ide-scsi emulation, or is just coincedence?
At this stage SuSE is worse than Windows. I have RedHat on the machine also and everything is stable there, so it is not hardware.
Any ideas where I can start to look for the problems? Special log files, tracing I can enable that will tell me what happens just before the thing dies?
Special monitoring software?
Anyone?
Please?
Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net
<-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
Andre Truter wrote:
THe machine will just freeze dead. Even the network is dead. At this stage I suspect the ide-scsi emulation, because the common factor seem to be that every time the machine froze, either X-CD-Roast or KonCD was running. They were not always busy writing a CD.
I had similar problems with APM turned on in the BIOS. See if it is turned on. For me it would lock up when the screensaver activated. Turning off APM fixed it. I'm sure there's a way now days to use APM safely in Linux, but I always just disable it. _____________________ Christopher R. Carlen crobc@earthlink.net Suse 7.3 Linux 2.4.10
On Sat, 2002-06-01 at 22:06, Chris Carlen wrote:
I had similar problems with APM turned on in the BIOS. See if it is turned on. For me it would lock up when the screensaver activated. Turning off APM fixed it. I'm sure there's a way now days to use APM safely in Linux, but I always just disable it.
I don't think it is the APM (it is disabled AFAIK - but I'll check) But I did have a similar problem with specific screensavers under RedHat - that is fixed now. I was thinking a bit more and there is one other common factor to my freezes: One or other GNOME app is running. Could be that GNOME is unstable (or one of the libs) I remember having problems with Ximian GNOME a while back on RH - Ximian fixed this. Does anybody have problems with GNOME apps freezing? -- Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
On Sun, 2002-06-02 at 03:43, Andre Truter wrote:
I remember having problems with Ximian GNOME a while back on RH - Ximian fixed this.
Does anybody have problems with GNOME apps freezing?
Are you running KDE? If so, and you're using SuSE 8.0, then it's KDE 3.0 - which has problems of its own that you wouldn't have experienced on your previous Redhat installation. Which window manager are you using? I'd suggest experimenting with a few others (XFCE, IceWM, FVWM2, Blackbox, and WindowMaker are all good) and see if the problem goes away. - Robert
On Sun, 2002-06-02 at 03:05, Robert Storey wrote:
Are you running KDE? If so, and you're using SuSE 8.0, then it's KDE 3.0 - which has problems of its own that you wouldn't have experienced on your previous Redhat installation. Which window manager are you using? I'd suggest experimenting with a few others (XFCE, IceWM, FVWM2, Blackbox, and WindowMaker are all good) and see if the problem goes away.
I use GNOME by default, but KDE is also installed and it is possible that I had some KDE app running each time it froze. I was focusing on CD writing and GNOME as the culprits.. The last time it froze, I was running KDE, as I thought GNOME was unstable. I use KDE's login manager - would that have an effect, even if I startup GNOME with it? Thanks -- Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
* Andre Truter (andre.truter@intekom.co.za) [020602 00:09]: :: ::I use KDE's login manager - would that have an effect, even if I startup ::GNOME with it? :: No..it wouldn't..but if you have an nVidia card this might be the reason. In the past KDM + nVidia cards = trouble. Try shutting off all those login managers whether it's GDM, XDM or KDM and just type startx at the prompt. See if you still get lockups. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little. -GC --=====-----=====--
On Sun, 2002-06-02 at 11:28, Ben Rosenberg wrote:
* Andre Truter (andre.truter@intekom.co.za) [020602 00:09]: :: ::I use KDE's login manager - would that have an effect, even if I startup ::GNOME with it? ::
No..it wouldn't..but if you have an nVidia card this might be the reason. In the past KDM + nVidia cards = trouble. Try shutting off all those login managers whether it's GDM, XDM or KDM and just type startx at the prompt. See if you still get lockups.
I think I found the reason why my machine crash: It seems to be an filesystem error. When the machine crashed just now, I had a root terminal open and the kernel displayed the following message as it's last dying words: journel-712 :buffer write failed This message never gets written to any log file (the filesystem is broken by then) I googled, but I did not find much, except for the kernel code and some suggestions on changes in the code. Has anybody seen this before? Can I fix it? Thanks -- Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 09 June 2002 01:11, Andre Truter wrote:
On Sun, 2002-06-02 at 11:28, Ben Rosenberg wrote:
* Andre Truter (andre.truter@intekom.co.za) [020602 00:09]: ::I use KDE's login manager - would that have an effect, even if I :: startup GNOME with it?
No..it wouldn't..but if you have an nVidia card this might be the reason. In the past KDM + nVidia cards = trouble. Try shutting off all those login managers whether it's GDM, XDM or KDM and just type startx at the prompt. See if you still get lockups.
I think I found the reason why my machine crash:
It seems to be an filesystem error. When the machine crashed just now, I had a root terminal open and the kernel displayed the following message as it's last dying words: journel-712 :buffer write failed
This message never gets written to any log file (the filesystem is broken by then)
I googled, but I did not find much, except for the kernel code and some suggestions on changes in the code.
Has anybody seen this before?
Can I fix it?
Thanks
Make sure disableapic is in lilo.conf. - -- OMNIVERSAL AWARENESS?? Oh, YEH!! First you need four GALLONS of JELL-O and a BIG WRENCH!! ... I think you drop th' WRENCH in the JELL-O as if it was a FLAVOR, or an INGREDIENT ... or ... I ... um ... WHERE'S the WASHING MACHINES? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj0DfnsACgkQnQ18+PFcZJvfkgCfTxGE3qPgel3zfvcTyRlKyU4H uf8An1iwqL0990GV1fykiEU5jPzyTrBs =cJbo -----END PGP SIGNATURE-----
On Sun, 2002-06-09 at 18:12, Carl wrote:
I think I found the reason why my machine crash:
It seems to be an filesystem error. When the machine crashed just now, I had a root terminal open and the kernel displayed the following message as it's last dying words: journel-712 :buffer write failed
This message never gets written to any log file (the filesystem is broken by then)
I googled, but I did not find much, except for the kernel code and some suggestions on changes in the code.
Has anybody seen this before?
Can I fix it?
Thanks
Make sure disableapic is in lilo.conf.
Hi Everybody, I think I found my problem and it is solved! I disabled DMA on the new drive and I added disableapic to lilo. I found a test on the SuSE SDB that tests hardware - the sig11 test. It ran through 50 cycles without any errors! Thanks for all the input and suggestions -- Andre Truter Software Engineer Registered Linux user #185282 ICQ #40935899 AIM: trusoftzaf http://www.trusoft.za.net <-------------------------------------------------> < The box said: Requires Windows 95 or better... > < So I installed Linux > <------------------------------------------------->
--On lørdag, juni 01, 2002 18:45:48 +0200 Andre Truter
Any ideas where I can start to look for the problems? Special log files, tracing I can enable that will tell me what happens just before the thing dies?
No ideas, but it happening here as well. I am on a Toshiba Satellite 1620 CDS and Yast2 did not recognize the graphic-card so I tried a couple of different standard settings - but nothing helped. On my system the problem seems to be related to graphics problems, anyway. It is almost always Konqueror that causes the freeze and almost always when webpages are opened in new windows. Just before the freeze, the screen display deteriorates notably. When I use Opera, freezes are less frequent - but they still occur. So far, I have not had freezes with other apps than these. Best regards, Jannik Lindquist
participants (7)
-
Andre Truter -
Ben Rosenberg -
Carl -
Chris Carlen -
Jannik Lindquist -
Marshall Heartley -
Robert Storey