System freezes totally at random, it seems

MFserver · 2012-04-23 13:22:20

I have an issue with my laptop, running Arch x86_64. Sometimes, the system hangs completely, mouse is dead (cursor is not moving), keyboard is dead, the screen freezes completely. Conky clock stops running, tint2 clock stops running, everything freezes completely and there's nothing to do but to restart. So far, I have only noticed a few things in common between these freezes:

- They seem to appear only while I'm at school
- No extra equipment has been connected to the computer when it freezes (USB memories, screens...)
- The computer has been suspended to RAM at least once before every freeze, but it can be hours before.
- The computer is not moved or dropped or anything, so it cannot be physical damage to the HDD directly causing the crash.
- The HDD is a new one, I've had problems with the old HDD, so I bought a new one recently.

Here's some output from /var/log/errors.log:

Apr 23 13:35:48 localhost kernel: [14791.359103] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359109] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359124] ata1.00: cmd 61/08:68:d4:8f:9d/00:00:02:00:00/40 tag 13 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359128]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359135] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359142] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359159] ata1.00: cmd 61/08:70:b4:95:9d/00:00:02:00:00/40 tag 14 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359162]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359169] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359176] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359191] ata1.00: cmd 61/08:78:ac:ad:45/00:00:13:00:00/40 tag 15 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359195]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359202] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359208] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359225] ata1.00: cmd 61/08:80:4c:b8:45/00:00:13:00:00/40 tag 16 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359228]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359235] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359242] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359258] ata1.00: cmd 61/08:88:5c:bd:45/00:00:13:00:00/40 tag 17 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359261]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359269] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359275] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359290] ata1.00: cmd 61/08:90:ac:bd:45/00:00:13:00:00/40 tag 18 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359294]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359301] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359309] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359325] ata1.00: cmd 61/08:98:2c:d3:45/00:00:13:00:00/40 tag 19 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359328]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359336] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359342] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359358] ata1.00: cmd 61/08:a0:9c:d4:45/00:00:13:00:00/40 tag 20 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359361]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359368] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359375] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359390] ata1.00: cmd 61/10:a8:94:cd:ed/00:00:3b:00:00/40 tag 21 ncq 8192 out
Apr 23 13:35:48 localhost kernel: [14791.359394]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359401] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359408] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359424] ata1.00: cmd 61/08:b0:bc:d0:f1/00:00:3b:00:00/40 tag 22 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359427]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359452] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359459] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359475] ata1.00: cmd 61/08:b8:f4:40:a2/00:00:02:00:00/40 tag 23 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359478]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359485] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359492] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359507] ata1.00: cmd 61/08:c0:4c:41:a2/00:00:02:00:00/40 tag 24 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359511]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359518] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359525] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359540] ata1.00: cmd 61/08:c8:ec:41:a2/00:00:02:00:00/40 tag 25 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359544]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359551] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359557] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359573] ata1.00: cmd 61/08:d0:24:42:a2/00:00:02:00:00/40 tag 26 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359576]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359584] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359590] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359606] ata1.00: cmd 61/08:d8:84:42:a2/00:00:02:00:00/40 tag 27 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359609]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359616] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359623] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359638] ata1.00: cmd 61/08:e0:8c:43:a2/00:00:02:00:00/40 tag 28 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359642]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359649] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359656] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359671] ata1.00: cmd 61/08:e8:d4:44:a2/00:00:02:00:00/40 tag 29 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359675]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359682] ata1.00: status: { DRDY }
Apr 23 13:35:48 localhost kernel: [14791.359689] ata1.00: failed command: WRITE FPDMA QUEUED
Apr 23 13:35:48 localhost kernel: [14791.359704] ata1.00: cmd 61/08:f0:6c:45:a2/00:00:02:00:00/40 tag 30 ncq 4096 out
Apr 23 13:35:48 localhost kernel: [14791.359708]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 23 13:35:48 localhost kernel: [14791.359715] ata1.00: status: { DRDY }
Apr 23 13:35:49 localhost kernel: [14791.845267] ata1: softreset failed (device not ready)
Apr 23 13:40:01 localhost /USR/SBIN/CROND[3557]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Apr 23 14:00:01 localhost /USR/SBIN/CROND[8405]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Apr 23 14:20:01 localhost /USR/SBIN/CROND[13284]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Apr 23 14:57:32 localhost /usr/sbin/crond[553]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Apr 23 14:57:32 localhost kernel: [    0.029998] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
Apr 23 14:57:33 localhost kernel: [    1.640036] ata1: softreset failed (device not ready)
Apr 23 14:57:33 localhost kernel: [   23.392057] SP5100 TCO timer: mmio address 0xfec000f0 already in use
Apr 23 14:57:37 localhost laptop-mode: Failed.
Apr 23 14:57:38 localhost dhcpcd[1058]: wlan0: sendmsg: Cannot assign requested address
Apr 23 15:00:01 localhost /USR/SBIN/CROND[1905]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory

I have no idea where to start on this, I've checked /var/log/everything.log too, but without finding anything unusual at the time of freeze. 14:57 is the next startup, the crash happens between Apr 23 14:20:01 and Apr 23 14:57:32.

Some info from /var/log/everything.log:

Apr 23 13:35:49 localhost kernel: [14792.011939] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 23 13:35:52 localhost kernel: [14794.745535] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
Apr 23 13:35:52 localhost kernel: [14794.753470] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
Apr 23 13:35:52 localhost kernel: [14794.753482] ata1.00: configured for UDMA/133
Apr 23 13:35:52 localhost kernel: [14794.754137] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754148] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754155] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754162] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754169] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754176] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754183] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754189] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754196] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754203] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754211] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754217] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754224] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754231] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754238] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754245] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754251] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754259] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754265] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754272] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754279] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754285] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754292] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754299] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754306] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754313] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754320] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754327] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754334] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754340] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754347] ata1.00: device reported invalid CHS sector 0
Apr 23 13:35:52 localhost kernel: [14794.754390] ata1: EH complete
Apr 23 13:40:01 localhost /USR/SBIN/CROND[3555]: (root) CMD (/usr/share/prey-tracker/prey.sh > /var/log/prey.log)
Apr 23 13:40:01 localhost /USR/SBIN/CROND[3554]: (root) CMDOUT (/bin/sh: /usr/share/prey-tracker/prey.sh: No such file or directory)
Apr 23 13:40:01 localhost /USR/SBIN/CROND[3557]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Apr 23 13:40:01 localhost /USR/SBIN/CROND[3554]: (root) MAIL (mailed 68 bytes of output but got status 0x0001
)
Apr 23 13:55:32 localhost dhcpcd[24898]: wlan0: renewing lease of 10.8.2.141
Apr 23 13:55:47 localhost dhcpcd[24898]: wlan0: acknowledged 10.8.2.141 from 10.8.0.1
Apr 23 13:55:47 localhost dhcpcd[24898]: wlan0: leased 10.8.2.141 for 3600 seconds
Apr 23 14:00:01 localhost /USR/SBIN/CROND[8403]: (root) CMD (/usr/share/prey-tracker/prey.sh > /var/log/prey.log)
Apr 23 14:00:01 localhost /USR/SBIN/CROND[8402]: (root) CMDOUT (/bin/sh: /usr/share/prey-tracker/prey.sh: No such file or directory)
Apr 23 14:00:01 localhost /USR/SBIN/CROND[8405]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Apr 23 14:00:01 localhost /USR/SBIN/CROND[8402]: (root) MAIL (mailed 68 bytes of output but got status 0x0001
)
Apr 23 14:01:01 localhost /USR/SBIN/CROND[8647]: (root) CMD (run-parts /etc/cron.hourly)
Apr 23 14:20:01 localhost /USR/SBIN/CROND[13282]: (root) CMD (/usr/share/prey-tracker/prey.sh > /var/log/prey.log)
Apr 23 14:20:01 localhost /USR/SBIN/CROND[13281]: (root) CMDOUT (/bin/sh: /usr/share/prey-tracker/prey.sh: No such file or directory)
Apr 23 14:20:01 localhost /USR/SBIN/CROND[13284]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Apr 23 14:20:01 localhost /USR/SBIN/CROND[13281]: (root) MAIL (mailed 68 bytes of output but got status 0x0001
)
Apr 23 14:25:47 localhost dhcpcd[24898]: wlan0: renewing lease of 10.8.2.141
Apr 23 14:26:03 localhost dhcpcd[24898]: wlan0: acknowledged 10.8.2.141 from 10.8.0.1
Apr 23 14:26:03 localhost dhcpcd[24898]: wlan0: leased 10.8.2.141 for 3600 seconds
Apr 23 14:57:32 localhost kernel: [    0.000000] Initializing cgroup subsys cpuset
Apr 23 14:57:32 localhost kernel: [    0.000000] Initializing cgroup subsys cpu
Apr 23 14:57:32 localhost kernel: [    0.000000] Linux version 3.3.2-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.0 20120407 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 14 09:48:37 CEST 2012
#And then there's a ton more logs, but this is from boot after the crash

Any ideas?

Ashren · 2012-04-23 13:31:35

Found this:
http://wiki.linuxonlinehelp.de/index.ph … DMA_QUEUED

MFserver · 2012-04-23 13:47:01

So, it looks like I should open up my laptop and check the SATA connections. Might this be caused by the hard drive running on SATA-600 while the motherboard of the laptop does not support it? The laptop is old, and the HDD is almost brand new.

Ashren · 2012-04-23 14:33:37

MFserver: You could try upgrading the firmware on the laptop.

MFserver · 2012-04-23 18:01:53

Well, I could upgrade to v1,17, currently I'm on v1,16, but it's not worth the risk of me wrecking my system at the moment. So, that will have to wait until I have time to fix any upcoming issues. Thanks for the help anyway!

Arch Linux

#1 2012-04-23 13:22:20

System freezes totally at random, it seems

#2 2012-04-23 13:31:35

Re: System freezes totally at random, it seems

#3 2012-04-23 13:47:01

Re: System freezes totally at random, it seems

#4 2012-04-23 14:33:37

Re: System freezes totally at random, it seems

#5 2012-04-23 18:01:53

Re: System freezes totally at random, it seems

Board footer