Help with computer not waking from sleep

[Was_Just19]

Unsure what TOP is, can you tell me how to use it? I was wondering if there is some sort of log or record someplace that I can access that might show what is happening when I get the freeze ups.

Open a terminal - Konsole - and type in    top  .....  that's it

It will show the running processes that are using the most resources ....

[SuperKev]

Can't make much of it. Says a 153 processes running 150 idle, and nothing is showing using more than about 5% cpu, of course that fluctuates. Was going to monitor the cpu temp but, naturally, synaptic has decided to play up as well so I can't install a sysmon that has temp readings. Although I have looked at it each time I have had to reboot and it seems to be running a full 10C cooler than what I remember seeing recently.

There really is only 4 things it can be, GFX card, Mobo, cpu or software, I have pretty much replaced everything else. I just can't figure what is causing this, since the pc works fine, until it doesn't LOL. I really thought the heat issue was it but it is appearing as if that was not it either.

[SuperKev]

Ok, going to bed so I wanted to leave this for you.

Just had another freeze up after being on the pc for a good hour or more and it working fine, cruising the net and was, ironically, doing more research in to the freezing issue. I was coming to the conclusion that it is some sort of error with X and was just going to look at the xorg.conf file when it froze. As usual on reboot I checked the cpu temp and it was 51C, which is at least 14C lower than what I had been seeing before I applied the Arctic Silver paste, so my thought is that heat is not the issue.

I had left the pc running for a while earlier tonight and came back to a blank screen, it had been long enough for the screen saver to be done as well, and it would not wake. All this is making me think it is something with X and/or the Nvidia drivers. I don't think running at 50C now that heat in the cpu is the issue.

When it froze up I got the blinking lights on my keyboard which I think was said is a sign of a kernel panic. If so that is something different from a freeze up due to excessive heat.

Your thoughts? Anyone's thoughts?

[Old-Polack]

Ok, going to bed so I wanted to leave this for you.

Just had another freeze up after being on the pc for a good hour or more and it working fine, cruising the net and was, ironically, doing more research in to the freezing issue. I was coming to the conclusion that it is some sort of error with X and was just going to look at the xorg.conf file when it froze. As usual on reboot I checked the cpu temp and it was 51C, which is at least 14C lower than what I had been seeing before I applied the Arctic Silver paste, so my thought is that heat is not the issue.

I had left the pc running for a while earlier tonight and came back to a blank screen, it had been long enough for the screen saver to be done as well, and it would not wake. All this is making me think it is something with X and/or the Nvidia drivers. I don't think running at 50C now that heat in the cpu is the issue.

When it froze up I got the blinking lights on my keyboard which I think was said is a sign of a kernel panic. If so that is something different from a freeze up due to excessive heat.

Your thoughts? Anyone's thoughts?

Check the installed OS /var/log/messages from a liveCD, for indications of what was happening just before the kernel panic. If you check the end of /var/log/dmesg of the installed OS, from the liveCD it may also help. Don't try to boot the system to the installed OS beforehand as dmesg starts fresh with each boot. You want to see the dmesg from the last run, that ended with a kernel panic.

[SuperKev]

Ok, did that but have no idea what to look for. I was not able to access the 'messages' file, no matter what I did via Live CD or while in the installed OS, I could not get permission to access it, even logged in as root.

The files I was able to get  (I just got anything that I thought might help)

dmesg

dmesg.old

pm-powersave.log

pm-suspend.log

Xorg.old.log

Xorg.9.log

What info will help that I can get from these files? Anything? Like I said no matter what I tried, I could not gain access to the 'messages' file.

[Old-Polack]

Ok, did that but have no idea what to look for. I was not able to access the 'messages' file, no matter what I did via Live CD or while in the installed OS, I could not get permission to access it, even logged in as root.

The files I was able to get  (I just got anything that I thought might help)

dmesg

dmesg.old

pm-powersave.log

pm-suspend.log

Xorg.old.log

Xorg.9.log

What info will help that I can get from these files? Anything? Like I said no matter what I tried, I could not gain access to the 'messages' file.

[root@littleboy ~]# ls -l /var/log |grep messages
-rw------- 1 root  root   102222 2010-11-08 22:20 messages
-rw------- 1 root  root    42475 2010-11-07 04:02 messages.1.gz
-rw------- 1 root  root    23573 2010-10-31 04:02 messages.2.gz
-rw------- 1 root  root    50311 2010-10-26 16:11 messages.3.gz
-rw------- 1 root  root    80141 2010-10-17 04:02 messages.4.gz

Owned by root so editable as root. As messages is appended to, rather than started new with each boot, anything interesting will be in the last 10-20 lines before the kernel panic, at the end of the file. I just opened mine with kwrite, as root. Nothing really interesting except to see how often it makes log entries.

Nov  8 22:18:30 littleboy klogd: generic-usb 0003:045E:0029.0051: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb-0000:00:02.0-3/input0
Nov  8 22:20:18 littleboy klogd: usb 2-3: USB disconnect, address 83
Nov  8 22:20:18 littleboy klogd: usb 2-3: new low speed USB device using ohci_hcd and address 84
Nov  8 22:20:18 littleboy klogd: usb 2-3: New USB device found, idVendor=045e, idProduct=0029
Nov  8 22:20:18 littleboy klogd: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov  8 22:20:18 littleboy klogd: usb 2-3: Product: Microsoft IntelliMouse® Optical
Nov  8 22:20:18 littleboy klogd: usb 2-3: Manufacturer: Microsoft
Nov  8 22:20:18 littleboy klogd: input: Microsoft Microsoft IntelliMouse® Optical as /devices/pci0000:00/0000:00:02.0/usb2/2-3/2-3:1.0/input/input87
Nov  8 22:20:18 littleboy klogd: generic-usb 0003:045E:0029.0052: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb-0000:00:02.0-3/input0
Nov  8 22:24:45 littleboy ntpd_initres[10495]: host name not found: 0.us.pool.ntp.org
Nov  8 22:24:45 littleboy ntpd_initres[10495]: host name not found: 1.us.pool.ntp.org
Nov  8 22:24:45 littleboy ntpd_initres[10495]: host name not found: 2.us.pool.ntp.org

My USB mouse has a small break in one of the wires, so the signal often gets interrupted, and a new disconnect message is generated, but the mouse is re recognized almost instantly and a new instance is generated. The mouse keeps on working but the message tells me I should probably fix it before it gets worse. The lines shown are from line 1076 to 1087, at the end of the file.

[timeth]

Hey SuperKev,

I just found this thread and thought I should mention that I'm having the same trouble on my old Dell Latitude cpx running fully updated LXDE. The same thing was happening on my previous LXDE install on this machine. I leave it for a while (usually around 2-3 hours) and when I return, it won't wake from suspend no matter what I do. Just a black screen and I have to hard shutdown. I have suspected some hardware/heat issues for a while but it's so old that I've just been putting up with it. I went into the LXDE config and deselected the suspend option. Now when I come back, it wakes up from the screensaver every time no problems.     

[SuperKev]

@OP: Did the suggested in terminal and got one line that said nothing really. I might be doing the thing wrong though. Seems now my install is borked completely, acts as if my drivers for my gfx card have been uninstalled. I thought to maybe turn off 3d effects and see if it might be the rendering engine in X locking things up, locked up anyhow, and when I went to re-enable compiz it will not let me do so. Will not bring up my hardware information either, just sits with the pulsing icon and nothing appears.

Top that off with synaptic not working either and I think I am facing yet another full reinstall. I am about at my wits end with this machine anyhow, been beating my head against a wall for two weeks now trying to get it to work and not lock up on me. Either PCLOS does not like my hardware or my hardware does not like it- I am inclined to the latter.

@timeth: I was looking for the place to do that in Gnome and could not find it. Oddly, I seem to remember just doing that very thing and now I can't seem to even find the dialogue where I did. Been having so many hardships with this bloody thing sometimes it's difficult to remember where you saw a setting in the menus.

[johnmart]

I think you'll find that setting in the Power Management section of *Configure Your Desktop*

[SuperKev]

Hi,

Well I was all set to trash this POS but don't like to admit defeat and I got the fangs and the one eyebrow, so I took it all apart, pulled out everything including the motherboard and removed some rather funky peripherals. Had a nondescript sound card, some really strange gameport 'thing' I had never seen the like of and a USB pci card, all of which I removed then put it all back together, figured it didn't cost anything to try it out, so far, no freezes- we will see overnight. Somehow I fixed synaptic too so I ran an update and again, no freeze up. so far, so good.
 
One odd problem now though is at login I don't get the normal GDM login screen but a big white box that says:

"Welcome to localhost.localdomain"

I can login and everything but I have no idea what caused this, what it means, or how to get back to the normal login.

Anyone ever seen something like that before?

Not out of the woods yet and may still need to do a reinstall but

[SuperKev]

Small Update:

Left it on overnight, screen saver stayed on all night but a movement of the mouse brought it back to my desktop. Seems the OS did not like one of those peripherals? Not sure why that would affect suspend/wake though. I had also removed an ethernet card and am just using the onboard Ethernet port, seems to work fine.

Hopefully someone will know what the "localhost.localdomain" thing is about but looks like this may be -almost- fixed.