UPDATE: I added the work-around in comment 3, and it seemed to have no
effect.  Then I had to reboot for other reasons, and since that reboot
I've had the messages only once, as follows, which is a great
improvement.

I did *not* mess with /sbin/hdparm as I mentioned I might in comment 25.

Jun 23 22:17:13 mini9 kernel: [167484.988135] ata1: lost interrupt (Status 0x58)
Jun 23 22:17:13 mini9 kernel: [167484.988223] ata1.00: exception Emask 0x0 SAct 
0x0 SErr 0x0 action 0x6 frozen
Jun 23 22:17:13 mini9 kernel: [167484.988239] ata1.00: BMDMA stat 0x24
Jun 23 22:17:13 mini9 kernel: [167484.988253] ata1.00: failed command: WRITE DMA
Jun 23 22:17:13 mini9 kernel: [167484.988282] ata1.00: cmd 
ca/00:08:50:b2:d6/00:00:00:00:00/e0 tag 0 dma 4096 out
Jun 23 22:17:13 mini9 kernel: [167484.988288]          res 
58/00:08:50:b2:d6/00:00:00:00:00/e0 Emask 0x2 (HSM violation)
Jun 23 22:17:13 mini9 kernel: [167484.988303] ata1.00: status: { DRDY DRQ }
Jun 23 22:17:13 mini9 kernel: [167484.988363] ata1: soft resetting link
Jun 23 22:17:13 mini9 kernel: [167485.196524] ata1.00: configured for UDMA/66
Jun 23 22:17:44 mini9 kernel: [167516.000138] ata1: lost interrupt (Status 0x58)
Jun 23 22:17:44 mini9 kernel: [167516.000240] ata1.00: exception Emask 0x0 SAct 
0x0 SErr 0x0 action 0x6 frozen
Jun 23 22:17:44 mini9 kernel: [167516.000257] ata1.00: BMDMA stat 0x24
Jun 23 22:17:44 mini9 kernel: [167516.000271] ata1.00: failed command: WRITE DMA
Jun 23 22:17:44 mini9 kernel: [167516.000300] ata1.00: cmd 
ca/00:10:98:0f:8b/00:00:00:00:00/e0 tag 0 dma 8192 out
Jun 23 22:17:44 mini9 kernel: [167516.000306]          res 
58/00:10:98:0f:8b/00:00:00:00:00/e0 Emask 0x2 (HSM violation)
Jun 23 22:17:44 mini9 kernel: [167516.000320] ata1.00: status: { DRDY DRQ }
Jun 23 22:17:44 mini9 kernel: [167516.000381] ata1: soft resetting link
Jun 23 22:17:44 mini9 kernel: [167516.208571] ata1.00: configured for UDMA/66


## Work-around
[...@mini9:T4:L1:C525:J0:2010-06-24_15:29:18_EDT]
/home/jp$ ll /lib/udev/rules.d/85-hdparm.rules 
-rw-r--r-- 1 root root 116 2010-06-20 15:44 /lib/udev/rules.d/85-hdparm.rules

[...@mini9:T4:L1:C516:J0:2010-06-24_15:25:26_EDT]
/home/jp$ cat /lib/udev/rules.d/85-hdparm.rules 
ACTION=="add", SUBSYSTEM=="block", KERNEL=="[sh]d[a-z]", \
        ATTR{queue/rotational}=="1", \
        RUN+="/lib/udev/hdparm"

[...@mini9:T4:L1:C517:J0:2010-06-24_15:25:45_EDT]
/home/jp$ last reboot
reboot   system boot  2.6.32-22-generi Mon Jun 21 23:46 - 15:26 (2+15:39)   
reboot   system boot  2.6.32-22-generi Mon Jun 21 19:16 - 23:38  (04:21)    
reboot   system boot  2.6.32-22-generi Fri Jun 11 04:12 - 19:15 (10+15:02)  
reboot   system boot  2.6.32-21-generi Thu Jun 10 19:33 - 04:08  (08:35)    

[...@mini9:T4:L1:C521:J0:2010-06-24_15:27:19_EDT]
/home/jp$ zfgrep -c 'ata1: lost interrupt (Status 0x58)' /var/log/syslog*
/var/log/syslog:0
/var/log/syslog.1:2
/var/log/syslog.2.gz:0
/var/log/syslog.3.gz:6
/var/log/syslog.4.gz:14
/var/log/syslog.5.gz:12
/var/log/syslog.6.gz:9
/var/log/syslog.7.gz:15

### Note time changed from :37: to :17:, not sure of the significance, if any
[...@mini9:T4:L1:C522:J0:2010-06-24_15:27:31_EDT]
/home/jp$ zfgrep 'ata1: lost interrupt (Status 0x58)' /var/log/syslog* | head 
-20
/var/log/syslog.1:Jun 23 22:17:13 mini9 kernel: [167484.988135] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.1:Jun 23 22:17:44 mini9 kernel: [167516.000138] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.3.gz:Jun 21 08:37:02 mini9 kernel: [879956.988172] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.3.gz:Jun 21 08:37:33 mini9 kernel: [879988.000117] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.3.gz:Jun 21 12:37:02 mini9 kernel: [894357.000145] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.3.gz:Jun 21 12:37:33 mini9 kernel: [894388.000119] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.3.gz:Jun 21 16:37:02 mini9 kernel: [908757.000144] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.3.gz:Jun 21 16:37:33 mini9 kernel: [908788.000127] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 08:37:02 mini9 kernel: [793556.989177] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 08:37:33 mini9 kernel: [793588.000122] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 12:37:02 mini9 kernel: [807957.000130] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 12:37:33 mini9 kernel: [807988.000131] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 14:37:02 mini9 kernel: [815156.988190] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 16:37:02 mini9 kernel: [822356.988158] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 16:37:33 mini9 kernel: [822387.988250] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 20 18:37:02 mini9 kernel: [829557.000094] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 21 02:37:02 mini9 kernel: [858357.000141] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 21 02:37:33 mini9 kernel: [858388.000116] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 21 04:37:02 mini9 kernel: [865557.000142] ata1: lost 
interrupt (Status 0x58)
/var/log/syslog.4.gz:Jun 21 04:37:33 mini9 kernel: [865588.000123] ata1: lost 
interrupt (Status 0x58)

-- 
udisks-probe-ata-smart causes HSM violations
https://bugs.launchpad.net/bugs/574462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to