System Hangs frequently

I'd recommend you do the following (something you've already thought of) :
When your system freezes, kill it (that is, power button for as long as necessary so it gets shutdown cold)
wait like 5 min
start it up again open up the log files post the last 3 or 4 min before the system was freezing and what it did then. this stuff might look innocent but there are a lot of great people around here who will be able to spot the problem :-) [not me most likely]. to me it sounds like an acpi problem (had one of those before...) but that's not necessarily it.

looking forward to your answer!

ANDREA

I'd recommend you do the following (something you've already thought of) :
When your system freezes, kill it (that is, power button for as long as necessary so it gets shutdown cold)
wait like 5 min
start it up again open up the log files post the last 3 or 4 min before the system was freezing and what it did then. this stuff might look innocent but there are a lot of great people around here who will be able to spot the problem :-) [not me most likely]. to me it sounds like an acpi problem (had one of those before...) but that's not necessarily it.

looking forward to your answer!

ANDREA

Thanks a lot for the reply Andrea. Atleast it get me thinking some where. This time my pc hanged at 8:08 pm (IST). After rebooting, these are the logs:

Syslog:

Dec 27 20:04:24 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:05:25 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:06:25 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:07:26 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:08:27 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:08:27 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: CPU Temp: 67.9 C (min = -127.0 C, max = 69.0 C) [ALARM]
Dec 27 20:30:10 zombie syslogd 1.5.0#2ubuntu6: restart.

daemon.log:

Dec 27 20:05:25 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:06:25 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:07:26 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:08:27 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]
Dec 27 20:08:27 zombie sensord: Sensor alarm: Chip dme1737-i2c-0-2e: CPU Temp: 67.9 C (min = -127.0 C, max = 69.0 C) [ALARM]

Only these two logs got updated, when pc stopped responding.

Both these logs point me to same thing, overheating, which i am not able to understand why. Why the same thing never happen in Windows, ever.

hi there
thank you for your reply. would it be possible to paste the couple of lines before those you pasted before? I see that the temperature is high but it's not at the maximum. I do have to mention that I am NOT an expert at these things and have only had a problem similar to this one once.

If you prefer not to disclose further parts of the log that's ok. In that case i'd recommend letting ubuntu hit the wall a couple of times (i.e. let it freeze), note the times it freezes and well compare the logs and post back the results. If you prefer others to analyze the logs you'll have to post them here though :-)

either way, report back :-)

ANDREA

hi abhinav
in case you got this to work, could you please tell us the solution? other people might have similar problems and would appreciate your help at that point.

if you haven't managed to make it work, please do feel free to ask and i'm sure someone will be happy to help!

ANDREA

Hi,

I didn't forget about my post here. I was making sure that i have got this working before posting here as well. :-)

All those logs has same line written several times, so it wouldn't have made much difference if I post 10 lines or full log itself. :-)

My problem actually got solve. I was so tired with all those hanging and stuff that I decided I will try installing Linux one last time if it doesn't work then no more. And after that i tried Debian netinst stable. For the last 10 days or so i have been using it and without any hang ups. I still get those overheating error messages, system has never hanged since then.

Some line from Syslog :

Jan 26 08:03:38 star kernel: CPU1: Running in modulated clock mode
Jan 26 08:03:38 star kernel: CPU0: Running in modulated clock mode
Jan 26 08:03:43 star kernel: CPU0: Temperature/speed normal
Jan 26 08:03:43 star kernel: CPU1: Temperature/speed normal
Jan 26 08:03:48 star kernel: CPU0: Temperature/speed normal

Output of uptime :
 21:16:30 up 23:10, 4 users, load average: 0.08, 0.10, 0.09

Output of uname -a :
Linux zombie 2.6.18-6-686 #1 SMP Fri Dec 12 16:48:28 UTC 2008 i686 GNU/Linux

I have been using it continuously.

I don't know exactly what was the problem, and what that netinst cd didn't or did install, But i am pretty much happy with the way it is working now.

hey me too facing the same problem for the same system configuration given above. Anyone to reply?

hi madhu
unfortunately i cannot give you a direct answer that will solve your problem. i'd suggest however to file a bug report against sensord so the people who "intimately know it" see the log and they'll be able to give you a much more educated suggestion. if you need help with the bug filing process please do feel free to ask and please, once you've created the bug report, link to it here (maybe a remark or so with the url) and as soon as it's solved maybe a quick line regarding the solution! thank YOU!

andrea

Hi madhu and Andrea,
The link D101GGC users may be interested
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/480712