Linux ATA/IDE development
 help / color / mirror / Atom feed
* AM4 B350 chipset Sata/IDE problem
@ 2017-11-21 16:01 Mark Hounschell
  0 siblings, 0 replies; 5+ messages in thread
From: Mark Hounschell @ 2017-11-21 16:01 UTC (permalink / raw)
  To: Linux-kernel, linux-ide

I'm running a 4.13.13 kernel on an AM4 MSI B350 Tomahawk Arctic MB. 
I have a couple of these setups and both do the same. I get this output just building
a kernel. My drives are older Seagate ST3160815AS, 3.AAD, max UDMA/133 configured
at boot time for UDMA/133 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
I can take this very disk and boot it up on an AM3 based setup and I will not
get these messages. I also have a pci-e Sata card in this AM4 box and when
connected to it instead of the MB Sata ports, I also don't get these messages.

I don't really know where the problem is but since this is a fairly new chip set I guess
it could be a kernel issue so thought I would post it for you all.

The kernel does in fact build and run. I get no user level errors.



Nov 21 10:28:01 harley kernel: ata1.00: exception Emask 0x11 SAct 0x7ffeffff SErr 0x400000 action 0x6 frozen
Nov 21 10:28:03 harley kernel: ata1.00: irq_stat 0x48000008, interface fatal error
Nov 21 10:28:03 harley kernel: ata1: SError: { Handshk }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:00:00:a0:f6/08:00:0c:00:00/40 tag 0 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:08:00:a8:f6/08:00:0c:00:00/40 tag 1 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:10:00:b0:f6/08:00:0c:00:00/40 tag 2 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:18:00:b8:f6/08:00:0c:00:00/40 tag 3 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:20:00:c0:f6/08:00:0c:00:00/40 tag 4 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:28:00:c8:f6/08:00:0c:00:00/40 tag 5 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:30:00:d0:f6/08:00:0c:00:00/40 tag 6 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:38:00:d8:f6/08:00:0c:00:00/40 tag 7 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:40:00:e0:f6/08:00:0c:00:00/40 tag 8 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:48:00:e8:f6/08:00:0c:00:00/40 tag 9 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:50:00:f0:f6/08:00:0c:00:00/40 tag 10 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:58:00:f8:f6/08:00:0c:00:00/40 tag 11 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:60:00:00:f7/08:00:0c:00:00/40 tag 12 ncq dma 1048576 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/10:68:d0:df:2c/00:00:0b:00:00/40 tag 13 ncq dma 8192 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/20:70:60:bf:2e/00:00:0b:00:00/40 tag 14 ncq dma 16384 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/e0:78:80:be:32/04:00:0b:00:00/40 tag 15 ncq dma 638976 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/e0:88:a8:95:32/03:00:0b:00:00/40 tag 17 ncq dma 507904 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/e8:90:88:99:32/03:00:0b:00:00/40 tag 18 ncq dma 512000 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:98:70:9d:32/04:00:0b:00:00/40 tag 19 ncq dma 524288 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/e8:a0:70:a1:32/03:00:0b:00:00/40 tag 20 ncq dma 512000 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/48:a8:58:a5:32/04:00:0b:00:00/40 tag 21 ncq dma 561152 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/18:b0:a0:a9:32/04:00:0b:00:00/40 tag 22 ncq dma 536576 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/00:b8:b8:ad:32/04:00:0b:00:00/40 tag 23 ncq dma 524288 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/10:c0:b8:b1:32/04:00:0b:00:00/40 tag 24 ncq dma 532480 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/e8:c8:c8:b5:32/04:00:0b:00:00/40 tag 25 ncq dma 643072 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/d0:d0:b0:ba:32/03:00:0b:00:00/40 tag 26 ncq dma 499712 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/c0:d8:00:88:f6/07:00:0c:00:00/40 tag 27 ncq dma 1015808 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/40:e0:c0:8f:f6/00:00:0c:00:00/40 tag 28 ncq dma 32768 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/60:e8:00:90:f6/07:00:0c:00:00/40 tag 29 ncq dma 966656 out
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Nov 21 10:28:03 harley kernel: ata1.00: cmd 61/a0:f0:60:97:f6/08:00:0c:00:00/40 tag 30 ncq dma 1130496 ou
         res 40/00:30:00:d0:f6/00:00:0c:00:00/40 Emask 0x10 (ATA bus error)
Nov 21 10:28:03 harley kernel: ata1.00: status: { DRDY }
Nov 21 10:28:03 harley kernel: ata1: hard resetting link
Nov 21 10:28:03 harley kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Nov 21 10:28:03 harley kernel: ata1.00: configured for UDMA/133
Nov 21 10:28:03 harley kernel: ata1: EH complete

Regards
Mark

^ permalink raw reply	[flat|nested] 5+ messages in thread
* Re: AM4 B350 chipset Sata/IDE problem
@ 2017-11-22 11:02 sonofagun
  2017-11-22 15:39 ` Mark Hounschell
  0 siblings, 1 reply; 5+ messages in thread
From: sonofagun @ 2017-11-22 11:02 UTC (permalink / raw)
  To: linux-ide

 Hello, you have a brand new AMD box and an old seagate HDD. That does NOT sound good... I am an AMD fan as well. Many years ago my brother and I bought our first AMD board with SB700. A good chip that had many annoying errata... A SATA II chip paired with the best iGPU of its era. Only a good HDD was suitable for such a board! That was an HDD from the seagate 7200.10 family. A family full of innovations. The first SATA II family, the first PMR HDD family and the first family offering 5 year warranty. Those disks are very reliable compared to 7200.7 and to 7200.11!!! Actually their access time is like 7200RPM disks while the 7200.11 had access times of 5400RPM class disks... Unfortunately those disks had a compatibility issue with the AMD AHCI implementation. All revisions of the SB7x0 southbridge family were affected and transfer speed was hurt badly when NCQ was enabled! I wrote about it(https://ata.wiki.kernel.org/index.php/Known_issues#SATA_hard_drives_which_show_poor_performance_with_sequential_reads_.28e.g._hdparm_-t.29) so that everyone will know it.
At that time there was no official firmware for any SATA disk. Firmware was given only when something was really wrong such as the deathstars. That attitude applied to all HDD manufacturers. My brother had to phone seagate at their headquarters in order to ask for a fix. Our next seagate disks(7200.11) were all having the same transfer speed issues with NCQ. They were too arrogant to admit the issue and very reluctant to release new firmware. We were informed that there will be no fix even though the 7200.11 family was just released. We were forced to RMA 4x 320GB and 4x 500GB of them at once and switch to the legendary WD RE3(all those still work flawlessly from 2008!). This was just prior seagate admitted the rest firmware issues of this family... After that mess, new firmware has been released gradually for most seagate HDD families!

As you can guess I am not surprised that you have an issue with such a disk on an AMD board. Compared to current disks it is very power hungry and not suitable for your board. What is worse, you are using an out of warranty HDD here.

Your SATA II HDD is attached on a SATA 3.x AMD chip. This HDD cannot even reach SATA I speeds(average well below 100MB/s). If your disk operates in 1.5 Gbps you will not have noticeable performance degradation. You will just lose maximum burst speed. Some time ago I saw this: "https://marc.info/?t=150843788300002&r=1&w=2", but I have not fallen on it as I have never used SATA hotplug. You have not mentioned hotplug here but it might be related as the libata EH is invoked!

I still have a 320GB 7200.10 ST3320620AS with 3.AAK firmware and will try to measure it with SATA I speed on my AMD KABINI box. We were given a newer firmware for this one while the seagate firmware finder site says it has no firmware! The new firmware is 3.AAM for this GALAXY HDD but the speed problem on AMD AHCI was not completely resolved but it made a difference so we have kept this HDD. We had a couple 320GB too, with 3.AAE firmware but seagate supplied no new firmware so they were RMAed.

As I said above, those disks have had speed issues with NCQ. Let's start from that. Please boot with NCQ disabled and see if it helps...

Since your HDD is old, please run:
sudo smartctl /dev/sd@ -x
sudo hdparm -I /dev/sd@
sudo hdparm --Istdout /dev/sd@
dmesg
and upload their output here(replace @ with your drive letter) so that I can view its current condition and give proper advice.


AMD SATA hosts have various issues with old HDDs:

On SB7x0 and SB950 all SATA I WD ****JD series went crazy when DIPM was enabled. Its heads parked then unparked and that was repeated endlessly. This has been fixed by Tejun after this issue was reported to the kernel...

Also SB950 will not even detect some MAXTOR HDDs unless they have the latest firmware! Again that firmware does "NOT" exist...

^ permalink raw reply	[flat|nested] 5+ messages in thread
* Re: AM4 B350 chipset Sata/IDE problem
@ 2017-11-23  6:40 sonofagun
  2017-11-27 20:50 ` Mark Hounschell
  0 siblings, 1 reply; 5+ messages in thread
From: sonofagun @ 2017-11-23  6:40 UTC (permalink / raw)
  To: linux-ide


Hello again, I wonder why my previous mail was wrapped like that. Leafpad and me are to blame!


> libata.force=noncq option seems to prevent the messages from occurring. 5 kernel builds (j16) with none.
I knew it, I was sure!

> [    2.314441] ata2.00: ATA-7: ST3160815AS, 4.AAB, max UDMA/133
I suppose that your third ST3160815AS with 4.AAB firmware has no issue, correct?
> [    2.933706] ata5.00: ATA-7: ST3160811AS, 3.AAE, max UDMA/133
I suppose that your second ST3160815AS with 3.AAE firmware has no issue, correct?

They were produced in different years but all of them have no firmware update!
If you see the datecode on its sticker, the 3.AAD datecode must start from 07 or 08 while the 3.AAE datecode must start from 08 or 09 while the 4.AAB must start from 08, 09 or even 10.
You must contact seagate and inform them that the older one is incompatible with B350 when NCQ enabled. I bet they already know it but you can try.

> [    1.721248] ata9.00: ATA-6: ST3500320NS, SN04, max UDMA/133
I assume that your Barracuda ES.2 has caused no trouble, right?

Maybe all 7200.10 with 3.* must have NCQ disabled on AMD SATA controllers. It can be done but that would only do the trick for some affected disks not for all.
OEMs like HP have different firmware with different versions. A blacklist for 3.* would not detect an HP ST3160815AS with HPF0 firmware.
The same applies to DELL disks and so on...


> [    1.680035] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [    2.248065] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [    2.872065] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Clearly you are stuck with SATA I speeds. This can be done using two or three ways. I will not say a thing on that.
My brother read the information you uploaded and reminded me that those disks have a small jumper which can limit the maximum SATA interface speed.
That was needed to make them work on VT8237 series chipsets.
I suppose you have used that jumper configuration on all three disks but forgot it since you must have done it around 8 or more years ago...


>   5 Reallocated_Sector_Ct   PO--CK   100   100   036    -    0
>  10 Spin_Retry_Count        PO--C-   100   100   097    -    0
> 187 Reported_Uncorrect      -O--CK   100   100   000    -    0
> 189 High_Fly_Writes         -O-RCK   100   100   000    -    0
> 198 Offline_Uncorrectable   ----C-   100   100   000    -    0
Your disk is in great condition despite its 75675 hours.
As I said before: "Those disks are very reliable".

I would suggest running all self tests(with NCQ disabled) as the last one occured at 9725 hours. That was 65950 hours ago. It is a very long time.
I have not seen any disk reaching 50000 operating hours!


Can you please measure the speed of all three disks on the Ryzen board with AHCI with queue depth 31, 2 and 1?


> hpet0: 3 comparators, 32-bit...
AMD still uses 32bit for HPET! I wonder why.

^ permalink raw reply	[flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-11-27 20:56 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-21 16:01 AM4 B350 chipset Sata/IDE problem Mark Hounschell
  -- strict thread matches above, loose matches on Subject: below --
2017-11-22 11:02 sonofagun
2017-11-22 15:39 ` Mark Hounschell
2017-11-23  6:40 sonofagun
2017-11-27 20:50 ` Mark Hounschell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox