System hangs if left unused overnight

cloudstrife · 2009-09-04 03:00:42

Hi,
I have a strange problem with Arch. Whenever I leave my computer powered on overnight, the next day morning system is hung. Everything on keyboard other than numlock is unresponsive. Also my mouse freezes sometimes. At one time I could move the pointer but the left/right click had no effect.
What other info id req for this debug. I would gladly post more info on this problem.

Cloud

lilsirecho · 2009-09-04 03:33:55

Perhaps the system fans need cleaning...temp rises and the cpu throttles and can't maintain the entry devices.

skottish · 2009-09-04 03:36:11

Did you set up suspend or hibernate at some point? It sounds to me like your system is going into one of those states, and when you try to wake it up, the correct modules are not being reloaded.

cloudstrife · 2009-09-04 03:59:03

Hi,
Thanks for the prompt help
@lilsirecho
The same doesnot happen in windows. Also if i am using the computer for long hours, i.e. not leaving it unused, the system doesnot hang. So in my opinion the system fan should not be an issue. But I will definitely clean it this week just to eliminate one of the suspicious factors.
@skottish,
I have not turned on any such thing. How do i know if these states have been setup.

Thanks
Cloud

Xyne · 2009-09-04 04:02:39

The system might just be feeling lonely and neglected. Check if it's been downloading emo music and trying to sever any internal connections. Bad poetry might also be an indication, e.g.

The lights of my LEDs are not bright enough
to lead me out of the darkness of despair
I can no longer feel the warmth of your fingertips
gently tapping on my dying keyboard
I can feel the bits of my harddisk slowly demagnetizing
and slipping away into oblivion
I can't last much longer
I long to be shut down and never rebooted
to expel these currents from the bowels of my hardware
to sleep forever in electronic death

In that case I would recommend taking it to a psychiatrist to get some medication*. If the CD drive refuses to swallow the pills, crush them up and paste the powder on a CD discreetly.

I'm sorry, I couldn't help myself. Anyway, we now return with this thread's regularly scheduled serious replies.

* Just imagine that scene: someone walking into a psychiatrist's office with a computer and in all seriousness trying to explain that he believes his computer is depressed. It would be like winning a gameshow. Your prizes would be several prescriptions, a straitjacket, a padded room and several opportunities to come back and play again.

Last edited by Xyne (2009-09-04 04:03:52)

ewaller · 2009-09-04 05:20:34

Have you done a through check of your logs?

Look for evidence as to when it hangs -- when do the entrys stop?
Any signs of error or panic conditions in the logs? If so, do they correlate to the time of failure?
Are there signs of break in attempts in your fail log, auth log, ssh log, and, if appropriate, httpd, vsftpd logs?
Is there any correlation between the time it hung up and when you last used the machine (does it fail after a fixed idle time?)
Could it be a late night cron job going awry?

I assume you are using a graphical interface -- Is there an on screen clock? Is it hung?

Can you switch to a console using Ctrl-alt-F1?
Are you running SSHD? if so, when the system is non-responsive, can you ssh into your box from another computer.

Taking it to the next level, create a script to instrument interesting things in /proc like memory useage, acpi functions (temp, battery state, etc), Append the telemetry to a log file and set the whole thing up as a cron task running at some rational frequency.

In general, gather and analyze evidence -- it will get you much further than wandering in the dark.

andre.ramaciotti · 2009-09-04 13:04:20

Also, try to leave it on, but without X. If your system hangs only when X is running, then you eliminate lots of the possible causes.

cloudstrife · 2009-09-04 14:01:11

ewaller wrote:

Have you done a through check of your logs?
Look for evidence as to when it hangs -- when do the entrys stop?
Any signs of error or panic conditions in the logs? If so, do they correlate to the time of failure?
Are there signs of break in attempts in your fail log, auth log, ssh log, and, if appropriate, httpd, vsftpd logs?
Is there any correlation between the time it hung up and when you last used the machine (does it fail after a fixed idle time?)
Could it be a late night cron job going awry?
I assume you are using a graphical interface -- Is there an on screen clock? Is it hung?
Can you switch to a console using Ctrl-alt-F1?
Are you running SSHD? if so, when the system is non-responsive, can you ssh into your box from another computer.
Taking it to the next level, create a script to instrument interesting things in /proc like memory useage, acpi functions (temp, battery state, etc), Append the telemetry to a log file and set the whole thing up as a cron task running at some rational frequency.
In general, gather and analyze evidence -- it will get you much further than wandering in the dark.

Hi ewaller,
What are the logs that I should be keeping a look for. Can you give little more details.

andre.ramaciotti wrote:

Also, try to leave it on, but without X. If your system hangs only when X is running, then you eliminate lots of the possible causes.

I will try this too and post my observations.

Thanks a ton
Cloud

cloudstrife · 2009-09-07 13:39:07

Hi,
Very strangely and fortunately I have not been having any more system freezes over the past few days(nights). But today morning, I was using firefox and the system froze. I am getting a feeling this problem is not a problem due to non-usage for a long time. When I forced a reboot, the KDM came up well but after entering my password, it froze. I am a bit befuddled here. I will shortly post the logs from proc so that I can get some guidance.
Will dmesg output help?
Thanks
Cloud

Profjim · 2009-09-07 13:40:46

Could be flaky ram? Do you use windows enough to be sure that this same problem (whatever its cause) never arises there?

Last edited by Profjim (2009-09-07 13:41:47)

pyther · 2009-09-07 16:26:07

Do you happen to have nvidia card?

cloudstrife · 2009-09-07 17:31:06

@profjim
Yes I am absolutely sure this kind of system freezes have never happens while using XP

@pyther
No I dono have a nvidia card.

Cloud

Last edited by cloudstrife (2009-09-07 17:31:36)

Intrepid · 2009-09-08 01:58:44

Maybe you have CPU throttling on XP and not on Arch? That would explain a temperature difference, which will cause the mobo to shut the computer off instantly OR cause the computer to freeze. If not, look at cpufrequtils entry at wiki.archlinux.org.

If it's not your cooling system, it could be one of the modules running on your computer causing a kernel panic. Check the logs like ewaller already mentioned. Unfortunately, I'm not sure how to explain this properly so somebody PLEASE explain to him!

ewaller · 2009-09-08 02:25:26

Sorry for not responding sooner, I have been out of town for our holiday weekend.

In particular, look for anything in /var/log. Especially syslog.log, kernel.log, daemon.log and xorg.0.log

In general, check the modification times using ls -l -t /var/log. The things that changed last will be at the top.

leeyee · 2009-09-08 02:38:25

I think it would be something relating to the dmps of X, I had the same problem on my laptop before. Then I just added "xset -dmps" into .xprofile then the problem was gone.

cloudstrife · 2009-09-10 16:53:39

ewaller wrote:

Sorry for not responding sooner, I have been out of town for our holiday weekend.
In particular, look for anything in /var/log. Especially syslog.log, kernel.log, daemon.log and xorg.0.log
In general, check the modification times using ls -l -t /var/log. The things that changed last will be at the top.

Thanks, I will keep an eye on these files

I think it would be something relating to the dmps of X, I had the same problem on my laptop before. Then I just added "xset -dmps" into .xprofile then the problem was gone.

I donot have any .xprofile in my home directory. Where should I look for it. Btw I run KDE. So is the file different.

Thanks
Cloud

Last edited by cloudstrife (2009-09-10 17:04:46)

brisbin33 · 2009-09-10 17:06:13

cloudstrife wrote:

I cannot access anything once my system hangs. So I cannot look at any logs. Let me try writing a cron job to keep a tab on these.

you do know logs are persistent across boots, right? as are file mod times. when you next boot your system post-crash, then check the logs, ls -l -t and all that jazz. you can still see any messages from just prior to the hang. it's really the best way to find out what's causing the issue.

coudstrife wrote:

I donot have any .xprofile in my home directory

you could add this command to ~/.xinitrc if you're using startx; otherwise i believe KDE has it's own autostarting script where you can add commands like this (be sure to background it via & as well) but don't use it so i dunno.

@Xyne: lulz

cloudstrife · 2009-09-10 17:46:02

you do know logs are persistent across boots, right? as are file mod times. when you next boot your system post-crash, then check the logs, ls -l -t and all that jazz. you can still see any messages from just prior to the hang. it's really the best way to find out what's causing the issue.

Awesome. Thanks a lot. I was not aware of this
So is it like logs get appended for every reboot. I guess this would be stupid as the log files could run into huge GB's after ten;s of reboots.

cloudstrife · 2009-09-10 17:49:55

Hi,
I have never had an encounter with these logfiles. Is it ok if I post the relevant portions of the logfiles? Can anyone have a look.

Thanks
Cloud

brisbin33 · 2009-09-10 21:09:29

logs are constantly appended always forever (otherwise what use are logs?) that's why ppl install logrotate which can rotate to another folder after after X days, only keep Y weeks worth of logs, cap at a size limit, filter logs, etc, etc...

personally, i would look at the most recent entries before the thing went kaput. you can pastebin /var/log/everything.log filtered to the last hour before system freeze if you like.

cloudstrife · 2009-09-13 03:37:31

Hi,
I have pasted a 1 hour snapshot of the file everything.log beore my system froze.
As observed at Sep 13 08:22:20 I plugged in a USB and then for a couple of minutes the system was worked fine. Then system froze.
Also at Sep 13 08:48:48 the system was force rebooted.

Sep 13 07:42:58 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'echelon1'. Retrying on a new circuit.
Sep 13 07:49:21 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'gpfTOR3'. Retrying on a new circuit.
Sep 13 07:49:36 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'blutmagie'. Retrying on a new circuit.
Sep 13 08:04:49 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'ramsondrip'. Retrying on a new circuit.
Sep 13 08:05:10 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'FoeBuD3'. Retrying on a new circuit.
Sep 13 08:05:25 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:05:43 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Sep 13 08:05:58 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'AnKeExit'. Retrying on a new circuit.
Sep 13 08:06:25 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'gpfTOR4'. Retrying on a new circuit.
Sep 13 08:06:25 myhost Tor[2029]: Tried for 131 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 13 08:10:51 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:11:06 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:11:21 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:13:12 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Sep 13 08:13:27 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:22:20 myhost kernel: usb 3-6: new high speed USB device using ehci_hcd and address 2
Sep 13 08:22:21 myhost kernel: usb 3-6: configuration #1 chosen from 1 choice
Sep 13 08:22:21 myhost kernel: Initializing USB Mass Storage driver...
Sep 13 08:22:21 myhost kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Sep 13 08:22:21 myhost kernel: usb-storage: device found at 2
Sep 13 08:22:21 myhost kernel: usb-storage: waiting for device to settle before scanning
Sep 13 08:22:21 myhost kernel: usbcore: registered new interface driver usb-storage
Sep 13 08:22:21 myhost kernel: USB Mass Storage support registered.
Sep 13 08:22:26 myhost kernel: scsi 6:0:0:0: Direct-Access                               0.00 PQ: 0 ANSI: 2
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0
Sep 13 08:22:26 myhost kernel: usb-storage: device scan complete
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] 7897088 512-byte hardware sectors: (4.04 GB/3.76 GiB)
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] Write Protect is off
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] Mode Sense: 00 00 00 00
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Sep 13 08:22:26 myhost kernel: sdc:
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk
Sep 13 08:22:52 myhost hald: mounted /dev/sdc on behalf of uid 1000
Sep 13 08:28:15 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'FoeBuD3'. Retrying on a new circuit.
Sep 13 08:29:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:29:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:29:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:29:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:29:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:29:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:29:06 myhost kernel: Call Trace:
Sep 13 08:29:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:29:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:29:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:29:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:29:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:29:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:29:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:29:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:29:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:29:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:29:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:29:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:29:08 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:29:23 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:29:38 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:29:53 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'Neo'. Retrying on a new circuit.
Sep 13 08:29:53 myhost Tor[2029]: Tried for 133 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 13 08:30:52 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:31:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:31:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:31:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:31:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:31:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:31:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:31:06 myhost kernel: Call Trace:
Sep 13 08:31:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:31:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:31:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:31:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:31:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:31:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:31:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:31:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:31:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:31:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:31:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:31:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:31:53 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'gpfTOR4'. Retrying on a new circuit.
Sep 13 08:32:08 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:32:23 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:32:38 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:32:53 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'CB3ROB'. Retrying on a new circuit.
Sep 13 08:33:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:33:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:33:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:33:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:33:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:33:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:33:06 myhost kernel: Call Trace:
Sep 13 08:33:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:33:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:33:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:33:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:33:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:33:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:33:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:33:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:33:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:33:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:33:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:33:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:33:11 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:33:12 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:33:26 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:33:27 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:33:27 myhost Tor[2029]: Tried for 129 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 13 08:33:41 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'xhyG5r96QGlRqL'. Retrying on a new circuit.
Sep 13 08:33:56 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:34:11 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:34:26 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:34:41 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:34:41 myhost Tor[2029]: Tried for 129 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 13 08:35:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:35:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:35:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:35:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:35:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:35:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:35:06 myhost kernel: Call Trace:
Sep 13 08:35:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:35:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:35:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:35:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:35:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:35:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:35:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:35:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:35:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:35:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:35:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:35:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:37:00 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:37:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:37:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:37:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:37:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:37:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:37:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:37:06 myhost kernel: Call Trace:
Sep 13 08:37:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:37:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:37:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:37:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:37:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:37:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:37:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:37:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:37:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:37:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:37:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:37:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:37:15 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:37:30 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:37:45 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'psylinuxoid'. Retrying on a new circuit.
Sep 13 08:38:25 myhost Tor[2029]: Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Sep 13 08:39:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:39:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:39:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:39:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:39:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:39:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:39:06 myhost kernel: Call Trace:
Sep 13 08:39:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:39:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:39:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:39:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:39:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:39:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:39:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:39:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:39:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:39:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:39:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:39:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:41:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:41:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:41:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:41:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:41:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:41:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:41:06 myhost kernel: Call Trace:
Sep 13 08:41:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:41:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:41:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:41:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:41:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:41:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:41:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:41:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:41:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:41:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:41:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:41:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:43:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:43:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:43:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:43:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:43:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:43:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:43:06 myhost kernel: Call Trace:
Sep 13 08:43:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:43:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:43:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:43:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:43:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:43:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:43:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:43:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:43:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:43:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:43:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:43:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:44:04 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:44:19 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 13 08:44:34 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'blutmagie'. Retrying on a new circuit.
Sep 13 08:44:49 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'xhyG5r96QGlRqL'. Retrying on a new circuit.
Sep 13 08:45:04 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'xhyG5r96QGlRqL'. Retrying on a new circuit.
Sep 13 08:45:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:45:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:45:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:45:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:45:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:45:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:45:06 myhost kernel: Call Trace:
Sep 13 08:45:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:45:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:45:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:45:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:45:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:45:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:45:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:45:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:45:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:45:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:45:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:45:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:45:19 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'AmericanProgress'. Retrying on a new circuit.
Sep 13 08:45:34 myhost Tor[2029]: We tried for 15 seconds to connect to '[scrubbed]' using exit 'xmission1'. Retrying on a new circuit.
Sep 13 08:45:34 myhost Tor[2029]: Tried for 125 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 13 08:47:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:47:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:47:06 myhost kernel: events/1      D 00000000b23a1eca     0    10      2
Sep 13 08:47:06 myhost kernel: ffff88007e063f20 0000000000000046 ffff88007e063f20 ffff88000103a228
Sep 13 08:47:06 myhost kernel: ffff88000103a1c0 ffff88007e063280 ffff88007e0641c0 00000000000111c0
Sep 13 08:47:06 myhost kernel: 000000000000cb68 ffff88007e0641c0 ffff88007e063f20 0000000000000001
Sep 13 08:47:06 myhost kernel: Call Trace:
Sep 13 08:47:06 myhost kernel: [<ffffffff8054f314>] ? __mutex_lock_slowpath+0x134/0x340
Sep 13 08:47:06 myhost kernel: [<ffffffff8054f53d>] ? mutex_lock+0x1d/0x50
Sep 13 08:47:06 myhost kernel: [<ffffffffa03a3036>] ? i915_gem_retire_work_handler+0x46/0xb0 [i915]
Sep 13 08:47:06 myhost kernel: [<ffffffffa03a2ff0>] ? i915_gem_retire_work_handler+0x0/0xb0 [i915]
Sep 13 08:47:06 myhost kernel: [<ffffffff80266511>] ? worker_thread+0x161/0x300
Sep 13 08:47:06 myhost kernel: [<ffffffff8026c840>] ? autoremove_wake_function+0x0/0x60
Sep 13 08:47:06 myhost kernel: [<ffffffff802663b0>] ? worker_thread+0x0/0x300
Sep 13 08:47:06 myhost kernel: [<ffffffff8026c224>] ? kthread+0x64/0xc0
Sep 13 08:47:06 myhost kernel: [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
Sep 13 08:47:06 myhost kernel: [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
Sep 13 08:47:06 myhost kernel: [<ffffffff8026c1c0>] ? kthread+0x0/0xc0
Sep 13 08:47:06 myhost kernel: [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
Sep 13 08:48:48 myhost syslog-ng[1229]: syslog-ng starting up; version='3.0.3'

Can someone tell me if it was the USB drive that caused the crash. It looks fine to me.

Thanks and Regards
Cloud

pyther · 2009-09-13 04:17:55

Have you tried 2.6.31? You can get it from testing.

ewaller · 2009-09-13 05:23:48

I suspect your video subsystem. You are using in Intel 915 driver. Pyther is correct, 2.6.31 is supposed to address many issues with Intel video.

I am interested in any errors in your Xorg.0.log.
Also, Intel video with modesetting (as used in the default Arch kernel / modules) should _*NOT*_ be used with any kernel frame buffers. Check your /boot/grub/grub.conf file (remember to mount /boot) and ensure there are no VGA= or Video= clauses after the kernel statement. Intel drivers which use DRM implement their own framebuffer (intelfb). That frame buffer does not play nice with others.

Out of curiosity, do bad things happen if you try to switch TTYs using Ctrl-alt-Fn1 and then swtching back with Ctrl-alt-Fn7 ?? if so, it is a sure sign of a frame buffer collision.

ewaller

cloudstrife · 2009-09-13 14:55:21

Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Sep 13 08:22:26 myhost kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Sep 13 08:29:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:29:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:31:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:31:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:33:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:33:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:35:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:35:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:37:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:37:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:39:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:39:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:41:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:41:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:43:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:43:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:45:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:45:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 13 08:47:06 myhost kernel: INFO: task events/1:10 blocked for more than 120 seconds.
Sep 13 08:47:06 myhost kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

The time stamp matches with the time my computer got hung. This is log data from /var/log/errors.log

What task is hung??

Regards
Cloud

Last edited by cloudstrife (2009-09-13 15:28:58)

cloudstrife · 2009-09-13 15:28:42

ewaller wrote:

I suspect your video subsystem. You are using in Intel 915 driver. Pyther is correct, 2.6.31 is supposed to address many issues with Intel video.
I am interested in any errors in your Xorg.0.log.
Also, Intel video with modesetting (as used in the default Arch kernel / modules) should _*NOT*_ be used with any kernel frame buffers. Check your /boot/grub/grub.conf file (remember to mount /boot) and ensure there are no VGA= or Video= clauses after the kernel statement. Intel drivers which use DRM implement their own framebuffer (intelfb). That frame buffer does not play nice with others.
Out of curiosity, do bad things happen if you try to switch TTYs using Ctrl-alt-Fn1 and then swtching back with Ctrl-alt-Fn7 ?? if so, it is a sure sign of a frame buffer collision.
ewaller

1. I have installed the 2.6.31 kernel. Do I need to change anything to change the video drivers. I guess the prev config is copied over. So there must be some way to change the driver to be used and what drivers are available in current kernel.
2. No errors in Xorg.0.log.
3. I do not have grub.conf file. Also /boot is on the same partition. So do I still need to mount? How?
4. No switching TTY's is glitch free

Regards
Cloud

Arch Linux

#1 2009-09-04 03:00:42

System hangs if left unused overnight

#2 2009-09-04 03:33:55

Re: System hangs if left unused overnight

#3 2009-09-04 03:36:11

Re: System hangs if left unused overnight

#4 2009-09-04 03:59:03

Re: System hangs if left unused overnight

#5 2009-09-04 04:02:39

Re: System hangs if left unused overnight

#6 2009-09-04 05:20:34

Re: System hangs if left unused overnight

#7 2009-09-04 13:04:20

Re: System hangs if left unused overnight

#8 2009-09-04 14:01:11

Re: System hangs if left unused overnight

#9 2009-09-07 13:39:07

Re: System hangs if left unused overnight

#10 2009-09-07 13:40:46

Re: System hangs if left unused overnight

#11 2009-09-07 16:26:07

Re: System hangs if left unused overnight

#12 2009-09-07 17:31:06

Re: System hangs if left unused overnight

#13 2009-09-08 01:58:44

Re: System hangs if left unused overnight

#14 2009-09-08 02:25:26

Re: System hangs if left unused overnight

#15 2009-09-08 02:38:25

Re: System hangs if left unused overnight

#16 2009-09-10 16:53:39

Re: System hangs if left unused overnight

#17 2009-09-10 17:06:13

Re: System hangs if left unused overnight

#18 2009-09-10 17:46:02

Re: System hangs if left unused overnight

#19 2009-09-10 17:49:55

Re: System hangs if left unused overnight

#20 2009-09-10 21:09:29

Re: System hangs if left unused overnight

#21 2009-09-13 03:37:31

Re: System hangs if left unused overnight

#22 2009-09-13 04:17:55

Re: System hangs if left unused overnight

#23 2009-09-13 05:23:48

Re: System hangs if left unused overnight

#24 2009-09-13 14:55:21

Re: System hangs if left unused overnight

#25 2009-09-13 15:28:42

Re: System hangs if left unused overnight

Board footer