From: Andreas Hartmann <andihartmann@01019freenet.de>
To: linux-kernel@vger.kernel.org
Subject: ata3.00: failed command: WRITE FPDMA QUEUED since Linux 4.1
Date: Fri, 24 Jul 2015 12:07:54 +0200 [thread overview]
Message-ID: <mot2pp$16u$1@327.eternal-september.org> (raw)
Hello!
Since Linux 4.1, there are often ata erros like these here:
[ 1.154572] libata version 3.00 loaded.
[ 1.787436] ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 6 Gbps
0x3f impl SATA mode
[ 1.788731] ata1: SATA max UDMA/133 abar m1024@0xfdfff000 port
0xfdfff100 irq 19
[ 1.788733] ata2: SATA max UDMA/133 abar m1024@0xfdfff000 port
0xfdfff180 irq 19
[ 1.788734] ata3: SATA max UDMA/133 abar m1024@0xfdfff000 port
0xfdfff200 irq 19
[ 1.788736] ata4: SATA max UDMA/133 abar m1024@0xfdfff000 port
0xfdfff280 irq 19
[ 1.788738] ata5: SATA max UDMA/133 abar m1024@0xfdfff000 port
0xfdfff300 irq 19
[ 1.788740] ata6: SATA max UDMA/133 abar m1024@0xfdfff000 port
0xfdfff380 irq 19
[ 2.105906] ata4: SATA link down (SStatus 0 SControl 300)
[ 2.109960] ata6: SATA link down (SStatus 0 SControl 300)
[ 2.281699] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.281717] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.281737] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.281752] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.282446] ata2.00: ATA-8: ST3000DM001-1CH166, CC24, max UDMA/133
[ 2.282448] ata2.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth
31/32), AA
[ 2.282893] ata3.00: ATA-9: ST3000DM001-1CH166, CC29, max UDMA/133
[ 2.282895] ata3.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth
31/32), AA
[ 2.283287] ata2.00: configured for UDMA/133
[ 2.283763] ata3.00: configured for UDMA/133
[ 2.289800] ata5.00: ATAPI: HL-DT-ST BD-RE BH10LS38, 1.00, max UDMA/133
[ 2.293383] ata1.00: ATA-8: Corsair Force GT, 1.3.3, max UDMA/133
[ 2.293385] ata1.00: 468862128 sectors, multi 16: LBA48 NCQ (depth
31/32), AA
[ 2.293754] ata5.00: configured for UDMA/133
[ 2.303356] ata1.00: configured for UDMA/133
[ 2.303469] scsi 0:0:0:0: Direct-Access ATA Corsair Force GT
3 PQ: 0 ANSI: 5
[ 2.303760] scsi 1:0:0:0: Direct-Access ATA ST3000DM001-1CH1
CC24 PQ: 0 ANSI: 5
[ 2.304055] scsi 2:0:0:0: Direct-Access ATA ST3000DM001-1CH1
CC29 PQ: 0 ANSI: 5
[ 48.689195] ata3.00: exception Emask 0x0 SAct 0x18 SErr 0x0 action
0x6 frozen
[ 48.690421] ata3.00: failed command: WRITE FPDMA QUEUED
[ 48.691597] ata3.00: cmd 61/58:18:21:ab:eb/05:00:58:00:00/40 tag 3
ncq 700416 out
[ 48.693977] ata3.00: status: { DRDY }
[ 48.695115] ata3.00: failed command: WRITE FPDMA QUEUED
[ 48.696257] ata3.00: cmd 61/00:20:21:a3:eb/08:00:58:00:00/40 tag 4
ncq 1048576 out
[ 48.698702] ata3.00: status: { DRDY }
[ 48.699856] ata3: hard resetting link
[ 49.188612] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 49.385330] ata3.00: configured for UDMA/133
[ 49.385356] ata3.00: device reported invalid CHS sector 0
[ 49.385380] ata3.00: device reported invalid CHS sector 0
[ 49.385393] ata3: EH complete
[ 79.630109] ata3.00: exception Emask 0x0 SAct 0xc0 SErr 0x0 action
0x6 frozen
[ 79.631069] ata3.00: failed command: WRITE FPDMA QUEUED
[ 79.632057] ata3.00: cmd 61/00:30:21:a3:eb/08:00:58:00:00/40 tag 6
ncq 1048576 out
[ 79.634185] ata3.00: status: { DRDY }
[ 79.635267] ata3.00: failed command: WRITE FPDMA QUEUED
[ 79.636378] ata3.00: cmd 61/58:38:21:ab:eb/05:00:58:00:00/40 tag 7
ncq 700416 out
[ 79.638743] ata3.00: status: { DRDY }
[ 79.639935] ata3: hard resetting link
[ 80.129527] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 80.145631] ata3.00: configured for UDMA/133
[ 80.145661] ata3.00: device reported invalid CHS sector 0
[ 80.145680] ata3.00: device reported invalid CHS sector 0
[ 80.145693] ata3: EH complete
[ 110.571021] ata3.00: exception Emask 0x0 SAct 0x1800 SErr 0x0 action
0x6 frozen
[ 110.572263] ata3.00: failed command: WRITE FPDMA QUEUED
[ 110.573505] ata3.00: cmd 61/58:58:21:ab:eb/05:00:58:00:00/40 tag 11
ncq 700416 out
[ 110.576028] ata3.00: status: { DRDY }
[ 110.577267] ata3.00: failed command: WRITE FPDMA QUEUED
[ 110.578508] ata3.00: cmd 61/00:60:21:a3:eb/08:00:58:00:00/40 tag 12
ncq 1048576 out
[ 110.580954] ata3.00: status: { DRDY }
[ 110.582183] ata3: hard resetting link
[ 111.070441] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 111.072173] ata3.00: configured for UDMA/133
[ 111.072198] ata3.00: device reported invalid CHS sector 0
[ 111.072222] ata3.00: device reported invalid CHS sector 0
[ 111.072235] ata3: EH complete
[ 141.511934] ata3.00: NCQ disabled due to excessive errors
[ 141.511943] ata3.00: exception Emask 0x0 SAct 0x30000 SErr 0x0 action
0x6 frozen
[ 141.512904] ata3.00: failed command: WRITE FPDMA QUEUED
[ 141.513894] ata3.00: cmd 61/00:80:21:a3:eb/08:00:58:00:00/40 tag 16
ncq 1048576 out
[ 141.516018] ata3.00: status: { DRDY }
[ 141.517106] ata3.00: failed command: WRITE FPDMA QUEUED
[ 141.518224] ata3.00: cmd 61/58:88:21:ab:eb/05:00:58:00:00/40 tag 17
ncq 700416 out
[ 141.520587] ata3.00: status: { DRDY }
[ 141.521791] ata3: hard resetting link
[ 142.011355] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 142.013292] ata3.00: configured for UDMA/133
[ 142.013322] ata3.00: device reported invalid CHS sector 0
[ 142.013342] ata3.00: device reported invalid CHS sector 0
[ 142.013354] ata3: EH complete
[ 197.237807] ata1.00: configured for UDMA/133
[ 197.237820] ata1: EH complete
These problems don't exist w/ Linux 4.0.9 - so they must have been
introduced w/ Linux 4.1.
A complete dmesg output can be found here:
http://article.gmane.org/gmane.linux.kernel.pci/43666
Any idea how to proceed? The kernel is completely unusable for me.
Thanks,
regards,
Andreas
reply other threads:[~2015-07-24 10:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mot2pp$16u$1@327.eternal-september.org' \
--to=andihartmann@01019freenet.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®