|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
[PLUG] Karmic ata kernel logs?
|
Anyone have a clue what these kernel/ata logs are, and if they are bad?
I'm getting them "periodically" [1] via logcheck, on my Mini9 (16G SSD,
not a "real" hard drive) on Karmic LPIA, upgraded from clean installed
Jaunty LPIA. I have no idea if they:
1) existed previously but logcheck didn't report them
2) just started for some reason, regardless of OS
3) are new to karmic, but OK, and logcheck should ignore
4) are new to karmic, and not OK
IIRC, Karmic is now using the ext4 driver, even for ext<4 file systems,
so #3 may be the most likely. But /proc/config.gz isn't turned on (why
not?) and I don't feel like figuring out which package they stash the
stock kernel configs in...
$ uname -a
Linux mini9 2.6.31-14-lpia #48-Ubuntu SMP Fri Oct 16 14:03:04 UTC 2009
i686 GNU/Linux
----- cut here -----
Oct 24 19:49:52 mini9 kernel: [237853.989187] ata1: lost interrupt
(Status 0x58)
Oct 24 19:49:52 mini9 kernel: [237853.989276] ata1.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 24 19:49:52 mini9 kernel: [237853.989292] ata1.00: BMDMA stat 0x24
Oct 24 19:49:52 mini9 kernel: [237853.989324] ata1.00: cmd
ca/00:08:97:e2:f9/00:00:00:00:00/e0 tag 0 dma 4096 out
Oct 24 19:49:52 mini9 kernel: [237853.989331] res
58/00:08:97:e2:f9/00:00:00:00:00/e0 Emask 0x2 (HSM violation)
Oct 24 19:49:52 mini9 kernel: [237853.989346] ata1.00: status: { DRDY DRQ }
Oct 24 19:49:52 mini9 kernel: [237853.989408] ata1: soft resetting link
Oct 24 19:49:52 mini9 kernel: [237854.197582] ata1.00: configured for
UDMA/66
Oct 24 19:50:23 mini9 kernel: [237885.000134] ata1: lost interrupt
(Status 0x58)
Oct 24 19:50:23 mini9 kernel: [237885.004101] ata1: drained 2048 bytes
to clear DRQ.
Oct 24 19:50:23 mini9 kernel: [237885.007610] ata1.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 24 19:50:23 mini9 kernel: [237885.007625] ata1.00: BMDMA stat 0x24
Oct 24 19:50:23 mini9 kernel: [237885.007657] ata1.00: cmd
c8/00:08:0f:18:85/00:00:00:00:00/e1 tag 0 dma 4096 in
Oct 24 19:50:23 mini9 kernel: [237885.007664] res
58/00:08:0f:18:85/00:00:00:00:00/e1 Emask 0x2 (HSM violation)
Oct 24 19:50:23 mini9 kernel: [237885.007678] ata1.00: status: { DRDY DRQ }
Oct 24 19:50:23 mini9 kernel: [237885.007740] ata1: soft resetting link
Oct 24 19:50:23 mini9 kernel: [237885.176539] ata1.00: configured for
UDMA/66
----- cut here -----
[1] Where "periodically" is defined as:
----- cut here -----
[root@mini9:T3:L1:C1303:J0:2009-10-25_14:59:35_EDT]
/var/log# zgrep 'ata1: lost interrupt .Status' *
dmesg:[ 72.804159] ata1: lost interrupt (Status 0x58)
kern.log:Oct 25 14:49:53 mini9 kernel: [306255.000135] ata1: lost
interrupt (Status 0x58)
kern.log:Oct 25 14:50:35 mini9 kernel: [306297.000129] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 22 01:46:54 mini9 kernel: [ 72.804159] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 22 01:48:25 mini9 kernel: [ 167.804157] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 22 01:49:07 mini9 kernel: [ 209.816140] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 22 19:49:52 mini9 kernel: [65054.000144] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 22 19:50:23 mini9 kernel: [65084.988170] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 23 19:49:52 mini9 kernel: [151454.000156] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 23 19:50:23 mini9 kernel: [151485.000138] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 24 01:49:52 mini9 kernel: [173054.000156] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 24 19:49:52 mini9 kernel: [237853.989187] ata1: lost
interrupt (Status 0x58)
kern.log.1:Oct 24 19:50:23 mini9 kernel: [237885.000134] ata1: lost
interrupt (Status 0x58)
messages:Oct 25 14:49:53 mini9 kernel: [306255.000135] ata1: lost
interrupt (Status 0x58)
messages:Oct 25 14:50:35 mini9 kernel: [306297.000129] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 22 01:46:54 mini9 kernel: [ 72.804159] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 22 01:48:25 mini9 kernel: [ 167.804157] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 22 01:49:07 mini9 kernel: [ 209.816140] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 22 19:49:52 mini9 kernel: [65054.000144] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 22 19:50:23 mini9 kernel: [65084.988170] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 23 19:49:52 mini9 kernel: [151454.000156] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 23 19:50:23 mini9 kernel: [151485.000138] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 24 01:49:52 mini9 kernel: [173054.000156] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 24 19:49:52 mini9 kernel: [237853.989187] ata1: lost
interrupt (Status 0x58)
messages.1:Oct 24 19:50:23 mini9 kernel: [237885.000134] ata1: lost
interrupt (Status 0x58)
syslog:Oct 25 14:49:53 mini9 kernel: [306255.000135] ata1: lost
interrupt (Status 0x58)
syslog:Oct 25 14:50:35 mini9 kernel: [306297.000129] ata1: lost
interrupt (Status 0x58)
syslog.1:Oct 24 19:49:52 mini9 kernel: [237853.989187] ata1: lost
interrupt (Status 0x58)
syslog.1:Oct 24 19:50:23 mini9 kernel: [237885.000134] ata1: lost
interrupt (Status 0x58)
syslog.2.gz:Oct 23 19:49:52 mini9 kernel: [151454.000156] ata1: lost
interrupt (Status 0x58)
syslog.2.gz:Oct 23 19:50:23 mini9 kernel: [151485.000138] ata1: lost
interrupt (Status 0x58)
syslog.2.gz:Oct 24 01:49:52 mini9 kernel: [173054.000156] ata1: lost
interrupt (Status 0x58)
syslog.3.gz:Oct 22 01:46:54 mini9 kernel: [ 72.804159] ata1: lost
interrupt (Status 0x58)
syslog.3.gz:Oct 22 01:48:25 mini9 kernel: [ 167.804157] ata1: lost
interrupt (Status 0x58)
syslog.3.gz:Oct 22 01:49:07 mini9 kernel: [ 209.816140] ata1: lost
interrupt (Status 0x58)
syslog.3.gz:Oct 22 19:49:52 mini9 kernel: [65054.000144] ata1: lost
interrupt (Status 0x58)
syslog.3.gz:Oct 22 19:50:23 mini9 kernel: [65084.988170] ata1: lost
interrupt (Status 0x58)
----- cut here -----
Thanks,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP |:::======| http://bashcookbook.com/
My Account, My Opinions |=========| http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|