Alvaro A. Novo writes:
Hi,
I have a friend of my with a problem in a RH installation... but, I think it is not RH related. He is looking for some pointers. Hope you guys can help him (and win him to SuSE :-) ). The basic problem is that his machine freezes, leaving only the hard reboot choice. Here's his message:
Ref: [HELP] Linux freezes up!
Help... Yesterday I installed Red Hat Linux 6.2 on a Pentium III 600 MHz, 256 MB RAM, 20 GB IDE hard drive, Atapi CD ROM, IDE Zip drive, ViewSonic monitor (17 inches, model E71), SIS video card (model: 63263DAGP - 8 MB of video memory), soundcard 3D Cristal. I am running Gnome + Enlightenment.
All seems to work well, except for one thing: Sometimes (actually, six times in only two days) Linux completely freezes up. Yes! When that happens, I am not able to kill X (CTRL+ALT+Backspace or whatever I try) nor am I able to telnet into my machine. In short, it freezes up, and nothing short of a reboot will put it back at work again.
In some of the "freezes", I did not even have many applications open.
What can be causing that? Could anyone please give me some pointers? Below is my /var/log/dmesg file, in case it contains any useful information.
If you can help, please e-mail me at cribari@de.ufpe.br . Thank you in advance!
Francisco Cribari
It may be X related. I have had problems like this before, they are rare and all related to X. I am not familar with your card, but some problems I have had in the past are: XF86Config probes the card and turns up the wrong values for video memory, probing does not find the right card. Are you using the right X server? Look in /etc/X11/XF86Config and see if everything looks good. Another point here, I have various versions of Redhat and much prefer the Suse way of configuring X (sax and sax2). It seems to be a much more complete configuration tool. Other than this I have nothing to offer. Lockups traditionally occur because two or more devices try to write to the bus at the same time thus causing the lockup. This can occur because they share the same interrupt. You might try doing a 'cat /proc/interrupts' and see what it reports. -- 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 FAQ at http://www.suse.com/support/faq