Coping with System Hanging
Until recently I had never had a problem of SuSE 7.2 hanging. Just now ALL the display entities dissapeared, leaving an unframed console pane. Keyboard, mouse - everything else was totally disabled. I was e.g. able to successfully "ping" the system from my networked WinME box, but that was all. Eventually I pushed the h/w reset button and (fortunately) the disk recovered. I have (while generally playing around) had a disk NOT recover this way - and needed to reinstall SuSE, so all this was not without a little trepidation. This was apparently a *rare* occurence, but are there any useful ways to prepare for this kind of thing - allow telnet from my WinME system perhaps? Fwiw, the only (major) changes I have made recently have been to trim the swap file from 256MB to 128MB. (I have 128MB of RAM. Can SuSE effectively use more than 128MB for a swap file and *should* it be bigger?) I do also admit to trimming the /boot partition from 24MB to 16MB (1 cylinder) for NO real good reason. I had e.g. found out that SuSE objects if it's less than 12MB. Could these explain the above - Maybe I should desist from fiddling? :-) Chris
On Tue, 2 Jul 2002 16:08:24 +0000 Chris Roberts <jhcr@lineone.net> wrote:
Until recently I had never had a problem of SuSE 7.2 hanging. Just now ALL the display entities dissapeared, leaving an unframed console pane. Keyboard, mouse - everything else was totally disabled. I was e.g. able to successfully "ping" the system from my networked WinME box, but that was all. Eventually I pushed the h/w reset button and (fortunately) the disk recovered. I have
Fwiw, the only (major) changes I have made recently have been to trim the swap file from 256MB to 128MB. (I have 128MB of RAM. Can SuSE effectively use more than 128MB for a swap file and *should* it be bigger?) I do also admit to trimming the /boot partition from 24MB to 16MB (1 cylinder) for NO real good reason. I had e.g. found out that SuSE objects if it's less than 12MB. Could these explain the above - Maybe I should desist from fiddling? :-)
It is probably heat or power related, especially if it's appearing this time of the year. First thing to do is check your cooling fans, add a cooling fan to push alot of air thru the box, or remove the box cover. If that don't fix it, try a UPS, if your line voltage is getting low. I just had a similar incident with the summer heat. My monitor would just start dropping out of svga mode, BOOM! , and at random times. I could turn it off-on then everything would be back. Totally had me baffled. The culprit?: My XF86config was set to making my video at 85hz, for a nice display. This was alright during the cooler weather, but it couldn't handle the summer heat. The solution was to slow down my video card to 75Hz. -- use Perl; #powerful programmable prestidigitation
participants (2)
-
Chris Roberts -
zentara