[Arm-netbook] RAM, uboot

Mike Thompson mpthompson at gmail.com
Sun May 20 21:52:50 BST 2012


David,

Thanks to your efforts with the kernel I have a Debian Wheezy armhf
system running on the Mele A1000.  Unfortunately, as I've started to
use this system to run builds of some large Debian packages I'm seeing
infrequent SATA errors that are corrupting the ext4 file system and
causing my builds to fail.

Attached below are the types of errors being reported to the system
console.  These were made over a 12 hours period building a large
Debian package -- something that is pretty disk intensive.

Unfortunately, I don't even know where to begin looking to figure out
the source of these errors.

Are you or anyone else seeing similar errors on SATA mounted hard
drives using the 3.0.31 kernel?

Mike Thompson

------

 <3>ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[51815.040000] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
<3>ata1.00: failed command: WRITE FPDMA QUEUED
[51815.050000] ata1.00: failed command: WRITE FPDMA QUEUED
<3>ata1.00: cmd 61/08:00:88:97:08/00:00:1e:00:00/40 tag 0 ncq 4096 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[51815.060000] ata1.00: cmd 61/08:00:88:97:08/00:00:1e:00:00/40 tag 0
ncq 4096 out
[51815.060000]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
0x4 (timeout)
<3>ata1.00: status: { DRDY }
[51815.070000] ata1.00: status: { DRDY }
<6>ata1: hard resetting link
<6>ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
<6>ata1.00: configured for UDMA/133
<4>ata1.00: device reported invalid CHS sector 0
[51815.440000] ata1.00: device reported invalid CHS sector 0
<6>ata1: EH complete
<6>kmemleak: 15 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
<6>kmemleak: 12 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
<3>ata1.00: exception Emask 0x10 SAct 0xfc SErr 0x280100 action 0x6 frozen
[101718.400000] ata1.00: exception Emask 0x10 SAct 0xfc SErr 0x280100
action 0x6 frozen
<3>ata1.00: irq_stat 0x08000000, interface fatal error
[101718.410000] ata1.00: irq_stat 0x08000000, interface fatal error
<3>ata1: SError: { UnrecovData 10B8B BadCRC }
[101718.420000] ata1: SError: { UnrecovData 10B8B BadCRC }
<3>ata1.00: failed command: READ FPDMA QUEUED
[101718.430000] ata1.00: failed command: READ FPDMA QUEUED
<3>ata1.00: cmd 60/08:10:10:9c:19/00:00:02:00:00/40 tag 2 ncq 4096 in
         res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[101718.430000] ata1.00: cmd 60/08:10:10:9c:19/00:00:02:00:00/40 tag 2
ncq 4096 in
[101718.430000]          res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask
0x10 (ATA bus error)
<3>ata1.00: status: { DRDY }
[101718.440000] ata1.00: status: { DRDY }
<3>ata1.00: failed command: READ FPDMA QUEUED
[101718.450000] ata1.00: failed command: READ FPDMA QUEUED
<3>ata1.00: cmd 60/08:18:18:9c:19/00:00:02:00:00/40 tag 3 ncq 4096 in
         res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[101718.460000] ata1.00: cmd 60/08:18:18:9c:19/00:00:02:00:00/40 tag 3
ncq 4096 in
[101718.460000]          res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask
0x10 (ATA bus error)
<3>ata1.00: status: { DRDY }
[101718.470000] ata1.00: status: { DRDY }
<3>ata1.00: failed command: READ FPDMA QUEUED
[101718.480000] ata1.00: failed command: READ FPDMA QUEUED
<3>ata1.00: cmd 60/08:20:20:9c:19/00:00:02:00:00/40 tag 4 ncq 4096 in
         res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[101718.490000] ata1.00: cmd 60/08:20:20:9c:19/00:00:02:00:00/40 tag 4
ncq 4096 in
[101718.490000]          res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask
0x10 (ATA bus error)
<3>ata1.00: status: { DRDY }
[101718.500000] ata1.00: status: { DRDY }
<3>ata1.00: failed command: READ FPDMA QUEUED
[101718.510000] ata1.00: failed command: READ FPDMA QUEUED
<3>ata1.00: cmd 60/08:28:28:9c:19/00:00:02:00:00/40 tag 5 ncq 4096 in
         res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[101718.520000] ata1.00: cmd 60/08:28:28:9c:19/00:00:02:00:00/40 tag 5
ncq 4096 in
[101718.520000]          res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask
0x10 (ATA bus error)
<3>ata1.00: status: { DRDY }
[101718.530000] ata1.00: status: { DRDY }
<3>ata1.00: failed command: READ FPDMA QUEUED
[101718.530000] ata1.00: failed command: READ FPDMA QUEUED
<3>ata1.00: cmd 60/08:30:30:9c:19/00:00:02:00:00/40 tag 6 ncq 4096 in
         res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[101718.540000] ata1.00: cmd 60/08:30:30:9c:19/00:00:02:00:00/40 tag 6
ncq 4096 in
[101718.540000]          res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask
0x10 (ATA bus error)
<3>ata1.00: status: { DRDY }
[101718.550000] ata1.00: status: { DRDY }
<3>ata1.00: failed command: READ FPDMA QUEUED
[101718.560000] ata1.00: failed command: READ FPDMA QUEUED
<3>ata1.00: cmd 60/08:38:38:9c:19/00:00:02:00:00/40 tag 7 ncq 4096 in
         res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
[101718.570000] ata1.00: cmd 60/08:38:38:9c:19/00:00:02:00:00/40 tag 7
ncq 4096 in
[101718.570000]          res 40/00:3c:38:9c:19/00:00:02:00:00/40 Emask
0x10 (ATA bus error)
<3>ata1.00: status: { DRDY }
[101718.580000] ata1.00: status: { DRDY }
<6>ata1: hard resetting link
<6>ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
<6>ata1.00: configured for UDMA/133
<6>ata1: EH complete



More information about the arm-netbook mailing list