Bug 1328944

Summary: SATA/eSATA ports on Marvell-88SE9172 chips fail to function
Product: [Fedora] Fedora Reporter: Dan Beard <zytemp2g>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 23CC: gansalmon, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, mike, zytemp2g
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-03 15:00:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg output none

Description Dan Beard 2016-04-20 16:38:10 UTC 
Description of problem:eSATA ports on Marvell-88SE9172 non-functional


Version-Release number of selected component (if applicable):
4.4.6-301.fc23.x86_64 #1 SMP

How reproducible: Install F23 on Gigabyte GA-990FXA-UD5 R5 Rev 1.0
All SATA/eSATA functions/ports through the 88SE9172 chip fail.  

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
http://www.gigabyte.us/products/product-page.aspx?pid=5292#ov
(Marvell-88SE9172 controlled SATA and eSATA) 
AMD FX-6300
16G RAM
F23 4.4.6-301.fc23.x86_64 #1 SMP  

See lspci readout below:

[dan@office-23 ~]$ lspci -nnk
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] (rev 02)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD/ATI] RD990 I/O Memory Management Unit (IOMMU) [1002:5a23]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD990 I/O Memory Management Unit (IOMMU) [1002:5a23]
00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H) [1002:5a1c]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A) [1002:5a1d]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] (rev 40)
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:b002]
	Kernel driver in use: ahci
00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
	Kernel driver in use: ohci-pci
00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
	Kernel driver in use: ehci-pci
00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
	Kernel driver in use: ohci-pci
00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
	Kernel driver in use: ehci-pci
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 42)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385]
	Kernel driver in use: piix4_smbus
	Kernel modules: i2c_piix4, sp5100_tco
00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] (rev 40)
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:a056]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d]
00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge [1002:4384] (rev 40)
00:14.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399]
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
	Kernel driver in use: ohci-pci
00:15.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:15.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2) [1002:43a2]
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:16.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
	Kernel driver in use: ohci-pci
00:16.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:5004]
	Kernel driver in use: ehci-pci
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 [1022:1600]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 [1022:1601]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 [1022:1602]
	Kernel modules: amd64_edac_mod
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 [1022:1603]
	Kernel driver in use: k10temp
	Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 [1022:1604]
	Kernel driver in use: fam15h_power
	Kernel modules: fam15h_power
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 [1022:1605]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1)
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:368d]
	Kernel driver in use: nouveau
	Kernel modules: nouveau
01:00.1 Audio device [0403]: NVIDIA Corporation GK107 HDMI Audio Controller [10de:0e1b] (rev a1)
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:368d]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
02:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01)
	Subsystem: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483]
	Kernel driver in use: xhci_hcd
03:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 12)
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:b000]
	Kernel driver in use: ahci
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
	Subsystem: Gigabyte Technology Co., Ltd Motherboard [1458:e000]
	Kernel driver in use: r8169
	Kernel modules: r8169
06:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 12)
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:b000]
	Kernel driver in use: ahci
[dan@office-23 ~]$
Comment 1 Laura Abbott 2016-04-20 18:28:51 UTC 
Did this drive ever work? Can you share dmesg?
Comment 2 Dan Beard 2016-04-20 19:52:12 UTC 
Created attachment 1149176 [details]
dmesg output
Comment 3 Dan Beard 2016-04-20 19:55:05 UTC 
The drive works on the other SATA ports, and on a SATA/eSATA bracket to the rear, but neither of those go through the Marvell chip.

I have (4) drives connected to the non-Marvell SATA chain.   Those are nominally functional.   The two internal and two external SATA/eSATA ports running through the Marvell chip are the ones in failure.

I have attempted to plug and access an IcyDock (4) drive eSATA connected device in order to generate a dmesg which might be useful.   There is also a USB 3.0 Sandisk thumbdrive in the mix.   I had to repair Grub2 in order to get it to boot from the USB 3.0 system on this motherboard. (added to kernel line amd_iommu iommu=pt) 

dmesg output (after attempting to connect IcyDock) is provided below.   I also have the "before" file if you would like to see it for comparison.
Comment 4 Dan Beard 2016-04-20 20:06:05 UTC 
Supplemental info:

I just re-inserted then pulled the jump drive, everything went well on the USB 3.0 line, then tried to connect a single ext eSATA drive to the Marvell chip port(s)  it failed and generated the following additional info to dmesg.

(starting at line #1163)

[ 9207.497857] show_signal_msg: 18 callbacks suppressed
[ 9207.497863] gnome-disks[4668]: segfault at 0 ip 00007f05d7bad62f sp 00007ffd4a1aa800 error 4 in libgio-2.0.so.0.4600.2[7f05d7ac4000+178000]
[ 9222.283165] usb 9-4: new SuperSpeed USB device number 3 using xhci_hcd
[ 9222.294781] usb 9-4: New USB device found, idVendor=0781, idProduct=5583
[ 9222.294789] usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9222.294793] usb 9-4: Product: Ultra Fit
[ 9222.294798] usb 9-4: Manufacturer: SanDisk
[ 9222.294801] usb 9-4: SerialNumber: 4C531001400105106351
[ 9222.295819] usb-storage 9-4:1.0: USB Mass Storage device detected
[ 9222.297309] scsi host11: usb-storage 9-4:1.0
[ 9223.299852] scsi 11:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
[ 9223.300834] sd 11:0:0:0: [sde] 242614272 512-byte logical blocks: (124 GB/116 GiB)
[ 9223.301163] sd 11:0:0:0: Attached scsi generic sg4 type 0
[ 9223.301919] sd 11:0:0:0: [sde] Write Protect is off
[ 9223.301926] sd 11:0:0:0: [sde] Mode Sense: 43 00 00 00
[ 9223.302394] sd 11:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 9223.316554]  sde: sde1 sde2 sde3 sde4 < sde5 >
[ 9223.318615] sd 11:0:0:0: [sde] Attached SCSI removable disk
[ 9245.276799] sde: detected capacity change from 124218507264 to 0
[ 9251.450496] usb 9-4: USB disconnect, device number 3
[ 9289.297419] ata8: exception Emask 0x10 SAct 0x0 SErr 0x1d0002 action 0xe frozen
[ 9289.297427] ata8: irq_stat 0x80400000, PHY RDY changed
[ 9289.297432] ata8: SError: { RecovComm PHYRdyChg CommWake 10B8B Dispar }
[ 9289.297440] ata8: hard resetting link
[ 9290.020013] ata8: SATA link down (SStatus 0 SControl 300)
[ 9290.020030] ata8: EH complete
[ 9372.346487] ata8: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
[ 9372.346495] ata8: irq_stat 0x80000040, connection status changed
[ 9372.346500] ata8: SError: { PHYRdyChg CommWake DevExch }
[ 9372.346509] ata8: hard resetting link
[ 9373.173357] ata8: SATA link down (SStatus 0 SControl 300)
[ 9373.173372] ata8: EH complete
[ 9373.250393] ata8: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
[ 9373.250400] ata8: irq_stat 0x80000040, connection status changed
[ 9373.250406] ata8: SError: { PHYRdyChg CommWake DevExch }
[ 9373.250414] ata8: hard resetting link
[ 9378.741977] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9378.741987] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9378.777008] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9378.777017] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9378.922400] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9378.923166] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00420 flags=0x0070]
[ 9378.923176] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00430 flags=0x0070]
[ 9378.923181] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6680 flags=0x0070]
[ 9378.923185] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a003e0 flags=0x0070]
[ 9378.923193] ata8.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 9378.923197] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6800 flags=0x0070]
[ 9378.923202] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6840 flags=0x0070]
[ 9378.923206] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b66c0 flags=0x0070]
[ 9378.923210] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6700 flags=0x0070]
[ 9378.923213] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6740 flags=0x0070]
[ 9378.923217] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6780 flags=0x0070]
[ 9378.923221] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b67c0 flags=0x0070]
[ 9383.922451] ata8: hard resetting link
[ 9383.925587] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9383.925593] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9384.236951] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9384.236961] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9384.382499] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 9384.383233] ata8.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 9384.383240] ata8: limiting SATA link speed to 1.5 Gbps
[ 9384.383271] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00420 flags=0x0070]
[ 9384.383280] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00430 flags=0x0070]
[ 9384.383285] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6680 flags=0x0070]
[ 9384.383289] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a003e0 flags=0x0070]
[ 9384.383293] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6800 flags=0x0070]
[ 9384.383297] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6840 flags=0x0070]
[ 9384.383300] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6700 flags=0x0070]
[ 9384.383304] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b66c0 flags=0x0070]
[ 9384.383307] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6740 flags=0x0070]
[ 9384.383311] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6780 flags=0x0070]
[ 9384.383314] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b67c0 flags=0x0070]
[ 9389.382542] ata8: hard resetting link
[ 9389.384739] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9389.384749] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9389.389982] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9389.389991] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9389.698085] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9389.698095] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9389.843570] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 9389.844345] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00420 flags=0x0070]
[ 9389.844355] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00430 flags=0x0070]
[ 9389.844364] ata8.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 9389.844369] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6680 flags=0x0070]
[ 9389.844374] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a003e0 flags=0x0070]
[ 9389.844378] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6800 flags=0x0070]
[ 9389.844381] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6840 flags=0x0070]
[ 9389.844385] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b66c0 flags=0x0070]
[ 9389.844389] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6700 flags=0x0070]
[ 9389.844393] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6740 flags=0x0070]
[ 9389.844396] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b6780 flags=0x0070]
[ 9389.844400] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x00000004289b67c0 flags=0x0070]
[ 9394.843682] ata8: hard resetting link
[ 9394.845852] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9394.845862] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9395.158113] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00440 flags=0x0070]
[ 9395.158123] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.1 domain=0x0000 address=0x0000000428a00450 flags=0x0070]
[ 9395.303653] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 9395.303667] ata8: EH complete


Can't read this one, either.
Comment 5 Dan Beard 2016-04-20 20:18:04 UTC 
Now I have hooked the IcyDock to the non-Marvell SATA/eSATA line, and it successfully found and made all drives therein mountable and useable.

This resulted in the following lines being appended to dmesg:  (starting at line 1261)


[ 9395.303667] ata8: EH complete
[ 9970.232583] ata8: exception Emask 0x10 SAct 0x0 SErr 0x190002 action 0xe frozen
[ 9970.232590] ata8: irq_stat 0x80400000, PHY RDY changed
[ 9970.232596] ata8: SError: { RecovComm PHYRdyChg 10B8B Dispar }
[ 9970.232604] ata8: hard resetting link
[ 9970.955606] ata8: SATA link down (SStatus 0 SControl 300)
[ 9970.955618] ata8: EH complete
[10087.712318] ata5: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0xe frozen
[10087.712326] ata5: irq_stat 0x00400040, connection status changed
[10087.712332] ata5: SError: { PHYRdyChg CommWake 10B8B DevExch }
[10087.712340] ata5: hard resetting link
[10093.639413] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[10093.639636] ata5.15: Port Multiplier 1.2, 0x197b:0x5755 r0, 5 ports, feat 0x5/0xf
[10093.642454] ata5.00: hard resetting link
[10099.155535] ata5.00: link is slow to respond, please be patient (ready=0)
[10102.062801] ata5.00: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[10102.062833] ata5.01: hard resetting link
[10102.522809] ata5.01: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[10102.522842] ata5.02: hard resetting link
[10102.982752] ata5.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[10102.982779] ata5.03: hard resetting link
[10103.442843] ata5.03: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
[10103.442874] ata5.04: hard resetting link
[10103.747920] ata5.04: SATA link down (SStatus 0 SControl 330)
[10103.749701] ata5.00: ATA-8: Hitachi HDS5C3030ALA630, MEAOA5C0, max UDMA/133
[10103.749708] ata5.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[10103.751502] ata5.00: configured for UDMA/133
[10103.752033] ata5.01: ATA-9: WDC WD30EZRX-00SPEB0, 80.00A80, max UDMA/133
[10103.752038] ata5.01: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[10103.752616] ata5.01: configured for UDMA/133
[10103.753155] ata5.02: ATA-9: WDC WD30EZRZ-00WN9B0, 80.00A80, max UDMA/133
[10103.753160] ata5.02: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[10103.753728] ata5.02: configured for UDMA/133
[10103.759300] ata5.03: ATA-8: SAMSUNG HD502HJ, 1AJ10001, max UDMA/133
[10103.759307] ata5.03: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[10103.764939] ata5.03: configured for UDMA/133
[10103.764996] ata5: EH complete
[10103.765242] scsi 4:0:0:0: Direct-Access     ATA      Hitachi HDS5C303 A5C0 PQ: 0 ANSI: 5
[10103.765640] sd 4:0:0:0: [sde] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[10103.765732] sd 4:0:0:0: [sde] Write Protect is off
[10103.765739] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
[10103.765775] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[10103.765992] sd 4:0:0:0: Attached scsi generic sg4 type 0
[10103.766816] scsi 4:1:0:0: Direct-Access     ATA      WDC WD30EZRX-00S 0A80 PQ: 0 ANSI: 5
[10103.767219] sd 4:1:0:0: [sdf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[10103.767227] sd 4:1:0:0: [sdf] 4096-byte physical blocks
[10103.767286] sd 4:1:0:0: [sdf] Write Protect is off
[10103.767292] sd 4:1:0:0: [sdf] Mode Sense: 00 3a 00 00
[10103.767319] sd 4:1:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[10103.769621] sd 4:1:0:0: Attached scsi generic sg5 type 0
[10103.780340] scsi 4:2:0:0: Direct-Access     ATA      WDC WD30EZRZ-00W 0A80 PQ: 0 ANSI: 5
[10103.795896]  sdf: sdf1 sdf2 sdf3
[10103.796410] sd 4:2:0:0: [sdg] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[10103.796418] sd 4:2:0:0: [sdg] 4096-byte physical blocks
[10103.796477] sd 4:2:0:0: [sdg] Write Protect is off
[10103.796484] sd 4:2:0:0: [sdg] Mode Sense: 00 3a 00 00
[10103.796541] sd 4:2:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[10103.797223] sd 4:1:0:0: [sdf] Attached SCSI removable disk
[10103.800154] sd 4:2:0:0: Attached scsi generic sg6 type 0
[10103.840104] scsi 4:3:0:0: Direct-Access     ATA      SAMSUNG HD502HJ  0001 PQ: 0 ANSI: 5
[10103.852061]  sde: sde1 sde2 sde3 sde4
[10103.852190] sd 4:3:0:0: [sdh] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[10103.852284] sd 4:3:0:0: [sdh] Write Protect is off
[10103.852292] sd 4:3:0:0: [sdh] Mode Sense: 00 3a 00 00
[10103.852363] sd 4:3:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[10103.852786] sd 4:3:0:0: Attached scsi generic sg7 type 0
[10103.881072]  sdh: sdh1
[10103.918862] sd 4:0:0:0: [sde] Attached SCSI removable disk
[10103.918868] sd 4:3:0:0: [sdh] Attached SCSI removable disk
[10103.918937]  sdg: sdg1 sdg2 sdg3 sdg4 sdg5
[10104.033513] sd 4:2:0:0: [sdg] Attached SCSI removable disk
Comment 6 Laura Abbott 2016-04-20 20:38:58 UTC 
This looks like a known issue between this controller + AMD IOMMU. 
https://bugzilla.kernel.org/show_bug.cgi?id=42679#c118
https://bugzilla.kernel.org/show_bug.cgi?id=42679#c126

I suspect this is going to need another quirk but you will probably need to work with the SATA/IOMMU maintainers to figure out the right one. You should also check for BIOS updates as well since that seems to be related.

Another option based on comment 126 might be verifying if older kernels worked and then trying to bisect where exactly it broke.
Comment 7 Dan Beard 2016-05-01 15:57:56 UTC 
Sorry for the delayed response.   Real life happens sometimes.

I don't have any older kernels here that function.   I have seen reports on the web that back in kernel 3.x it seemed to be working.

Regarding working with the SATA/IOMMU maintainers, that's foreign ground for me.   I'm none too sure how to go about that.   If you could kick-start that ball rolling, I'd appreciate it bunches and heaps.

This may or may not be related.

On the same motherboard, the VIA VL805??? chip which is supposed to handle USB 3.0 is also in failure mode.   There are "work-arounds" listed on the web, but they are only partially effective.   Once the machine has gone through a sleep/wake cycle, the USB 3.0 ports no longer function again.  In fact, functioning after a fresh boot is haphazard, too.

So any guidance you have to offer on finding a solution to this/these (which is within my rather limited scope of technical skills) is welcome and appreciated.
Comment 8 Dan Beard 2016-05-19 10:33:23 UTC 
Update:

After more looking around, it appears this is issue only effects motherboards using these chips which are also using the American Megatrends BIOS.
Comment 9 Laura Abbott 2016-09-23 19:40:39 UTC 
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.
Comment 10 Dan Beard 2016-10-03 14:28:01 UTC 
Probably not much need to chase this rabbit any further down the hole.   I have since replaced the Gigabyte board with these offending/offensive chips in it with an ASUS board which works properly without tweaks, clunks, pokes and prods.  

I use this box for daily production in the real world, (when I'm home) and the need for it to just work outweighed most other considerations.

Thus, I cannot provide any more input on the problem.

Hope this helps.

Dan
Comment 11 Laura Abbott 2016-10-03 15:00:00 UTC 
Thanks for letting us know. I'm going to close the bug. This can be reopened if someone else finds the problem or has a fix.