New: [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

Bug 98171 [email protected] 2 participants 11 messages May 12, 2015 – Mar 29, 2016 SCSI

Share & tools

[email protected]

author

2015-05-12 22:22 UTC #0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=98171

Bug ID: 98171
Summary: [Regression] Marvell SE91xx SATA 3 controllers not
recognized correctly
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.15
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: [email protected]
Reporter: [email protected]
Regression: No

Created attachment 176571
--> https://bugzilla.kernel.org/attachment.cgi?id=176571&action=edit
full dmesg of my affected system

Starting with kernel 3.15 Marvell SE91xx SATA 3 controllers are not getting recognized correctly. At early boot process, users get messages similar to this:

kernel: ata16: EH complete
kernel: ata16.00: configured for UDMA/66
kernel: ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
kernel: ata16: hard resetting link
kernel: ata16.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 2 dma 16640 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
kernel: cdb[0]=0x12: 12 01 00 00 ff 00
kernel: scsi 15:0:0:0: CDB:
kernel: ata16.00: irq_stat 0x40000001
kernel: ata16.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x6
kernel: scsi 15:0:0:0: Processor Marvell 91xx Config 1.01 PQ: 0 ANSI: 5
kernel: ata8: SATA link down (SStatus 0 SControl 300)

There seems to be a high rate of users affected, and so far this issue can be reproduced with SE9129 and SE9130 chips, see
https://bugs.archlinux.org/task/40776

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

[email protected]

author

2015-05-12 22:22 UTC #1 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

https://bugzilla.kernel.org/show_bug.cgi?id=98171

[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
         Regression|No                          |Yes

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

James Bottomley

maintainer

2015-05-12 22:30 UTC #2 lore raw

In reply to [email protected]

Quoted 27 lines · On Tue, 2015-05-12 at 22:22 +0000, [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=98171
Bug ID: 98171
Summary: [Regression] Marvell SE91xx SATA 3 controllers not
recognized correctly
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.15
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: [email protected]
Reporter: [email protected]
Regression: No
Created attachment 176571
--> https://bugzilla.kernel.org/attachment.cgi?id=176571&action=edit
full dmesg of my affected system
Starting with kernel 3.15 Marvell SE91xx SATA 3 controllers are not getting recognized correctly. At early boot process, users get messages similar to this:

Quoted 12 lines

kernel: ata16: EH complete
kernel: ata16.00: configured for UDMA/66
kernel: ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
kernel: ata16: hard resetting link
kernel: ata16.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 2 dma 16640 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
kernel: cdb[0]=0x12: 12 01 00 00 ff 00
kernel: scsi 15:0:0:0: CDB:
kernel: ata16.00: irq_stat 0x40000001
kernel: ata16.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x6
kernel: scsi 15:0:0:0: Processor Marvell 91xx Config 1.01 PQ: 0 ANSI: 5
kernel: ata8: SATA link down (SStatus 0 SControl 300)

This is a regression against 3.14? There was only one change affecting mvsas between those kernels and that was the libsas change:

commit bc6e7c4b0d1a1f742d96556f63d68f17f4e232c3

Author: Dan Williams <[email protected]>
Date:   Fri Mar 14 13:52:48 2014 -0700

libata, libsas: kill pm_result and related cleanup

Does reverting that make the problem go away?

James

[email protected]

author

2015-06-29 22:27 UTC #3 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

--- Comment #1 from [email protected] ---

Quoted 11 lines

This is a regression against 3.14? There was only one change affecting mvsas between those kernels and that was the libsas change:
commit bc6e7c4b0d1a1f742d96556f63d68f17f4e232c3
Author: Dan Williams <[email protected]>
Date: Fri Mar 14 13:52:48 2014 -0700
libata, libsas: kill pm_result and related cleanup
Does reverting that make the problem go away?

It's a regression starting with linux 3.15, meaning everything still worked with linux 3.14.
I have tried reverting that patch from linux-3.15.10 vanilla sources but it fails... I don't know why, maybe I'm just not leet enough:

Hunk #1 succeeded at 5364 (offset 13 lines).
Hunk #2 succeeded at 5388 (offset 13 lines).
Hunk #3 FAILED at 5390.
Hunk #4 succeeded at 5506 (offset 13 lines).
Hunk #5 succeeded at 5532 (offset 13 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/ata/libata-core.c.rej patching file drivers/ata/libata-eh.c
patching file drivers/scsi/libsas/sas_ata.c
patching file include/linux/libata.h
Hunk #1 succeeded at 850 (offset 2 lines).
Hunk #2 FAILED at 1140.
1 out of 2 hunks FAILED -- saving rejects to file include/linux/libata.h.rej patching file include/scsi/libsas.h
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 172 with fuzz 1.

What shall I do?

Regards,

Philip

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

[email protected]

author

2015-06-30 10:48 UTC #4 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

Tom Yan <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from Tom Yan <[email protected]> ---
Why don't you get linux 3.14 (linux-lts in the current Arch) and patch it with
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=bc6e7c4b0d1a1f742d96556f63d68f17f4e232c3
and see if it reproduce the issue?

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

[email protected]

author

2015-06-30 10:51 UTC #5 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

--- Comment #3 from Tom Yan <[email protected]> ---
By the way why would it be related to mvsas/libsas? Aren't those controllers SATA ones which use the ahci driver?

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

[email protected]

author

2015-08-08 23:58 UTC #6 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

Carlos Guidugli <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #4 from Carlos Guidugli <[email protected]> --- Hi,

I am also having the same issue with Fedora 22, kernel 4.1.3-200.fc22.x86_64. Any recommendations?

[    0.828869] ata9: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610100
irq 35
[    0.828873] ata10: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610180
irq 35
[    0.828877] ata11: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610200
irq 35
[    0.828880] ata12: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610280
irq 35
[    0.828884] ata13: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610300
irq 35
[    0.828887] ata14: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610380
irq 35
[    0.828890] ata15: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610400
irq 35
[    0.828894] ata16: SATA max UDMA/133 abar m2048@0xdf610000 port 0xdf610480
irq 35
[    1.116331] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.117021] ata1.00: ATA-9: WDC WD60EFRX-68MYMN1, 82.00A82, max UDMA/133
[    1.117026] ata1.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32),
AA
[    1.118349] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.119026] ata6.00: ATA-9: WDC WD60EFRX-68MYMN1, 82.00A82, max UDMA/133
[    1.119031] ata6.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32),
AA
[    1.119341] ata8: SATA link down (SStatus 0 SControl 300)
[    1.119346] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.119377] ata7: SATA link down (SStatus 0 SControl 300)
[    1.119394] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.119413] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.119740] ata6.00: configured for UDMA/133
[    1.120073] ata5.00: ATA-9: WDC WD60EFRX-68MYMN1, 82.00A82, max UDMA/133
[    1.120078] ata5.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32),
AA
[    1.120798] ata5.00: configured for UDMA/133
[    1.134350] ata14: SATA link down (SStatus 0 SControl 300)
[    1.134376] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.134401] ata12: SATA link down (SStatus 0 SControl 300)
[    1.134498] ata16.00: ATAPI: MARVELL VIRTUALL, 1.09, max UDMA/66
[    1.134652] ata16.00: configured for UDMA/66
[    1.136354] ata15: SATA link down (SStatus 0 SControl 300)
[    1.136379] ata10: SATA link down (SStatus 0 SControl 300)
[    1.136403] ata11: SATA link down (SStatus 0 SControl 300)
[    1.136425] ata9: SATA link down (SStatus 0 SControl 300)
[    1.136446] ata13: SATA link down (SStatus 0 SControl 300)
[    1.323489] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.327731] ata3.00: HPA detected: current 3907027055, native 3907029168
[    1.327822] ata2.00: ATA-9: WDC WD60EFRX-68MYMN1, 82.00A82, max UDMA/133
[    1.327827] ata2.00: 11721045168 sectors, multi 16: LBA48 NCQ (depth 31/32),
AA
[    1.327839] ata3.00: ATA-8: WDC WD20EARS-00S8B1, 80.00A80, max UDMA/133
[    1.327844] ata3.00: 3907027055 sectors, multi 16: LBA48 NCQ (depth 31/32),
AA
[    1.327966] ata4.00: HPA detected: current 3907027055, native 3907029168
[    1.328069] ata4.00: ATA-8: WDC WD20EARS-00S8B1, 80.00A80, max UDMA/133
[    1.328073] ata4.00: 3907027055 sectors, multi 16: LBA48 NCQ (depth 31/32),
AA
[    1.328281] ata1.00: configured for UDMA/133
[    1.328518] scsi 0:0:0:0: Direct-Access     ATA      WDC WD60EFRX-68M 0A82
PQ: 0 ANSI: 5
[    1.328620] ata2.00: configured for UDMA/133
[    1.328965] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.329004] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00
TB/5.45 TiB)
[    1.329009] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    1.329214] sd 0:0:0:0: [sda] Write Protect is off
[    1.329219] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.329250] scsi 1:0:0:0: Direct-Access     ATA      WDC WD60EFRX-68M 0A82
PQ: 0 ANSI: 5
[    1.329348] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[    1.329652] sd 1:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00
TB/5.45 TiB)
[    1.329657] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[    1.329669] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    1.329782] sd 1:0:0:0: [sdb] Write Protect is off
[    1.329788] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.329880] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[    1.332247] ata3.00: configured for UDMA/133
[    1.332429] scsi 2:0:0:0: Direct-Access     ATA      WDC WD20EARS-00S 0A80
PQ: 0 ANSI: 5
[    1.332811] sd 2:0:0:0: [sdc] 3907027055 512-byte logical blocks: (2.00
TB/1.81 TiB)
[    1.332851] sd 2:0:0:0: Attached scsi generic sg2 type 0
[    1.332899] sd 2:0:0:0: [sdc] Write Protect is off
[    1.332905] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    1.332970] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[    1.332977] ata4.00: configured for UDMA/133
[    1.333102] scsi 3:0:0:0: Direct-Access     ATA      WDC WD20EARS-00S 0A80
PQ: 0 ANSI: 5
[    1.333464] sd 3:0:0:0: Attached scsi generic sg3 type 0
[    1.333469] sd 3:0:0:0: [sdd] 3907027055 512-byte logical blocks: (2.00
TB/1.81 TiB)
[    1.333623] sd 3:0:0:0: [sdd] Write Protect is off
[    1.333628] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[    1.333674] scsi 4:0:0:0: Direct-Access     ATA      WDC WD60EFRX-68M 0A82
PQ: 0 ANSI: 5
[    1.333677] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[    1.333991] sd 4:0:0:0: Attached scsi generic sg4 type 0
[    1.334035] sd 4:0:0:0: [sde] 11721045168 512-byte logical blocks: (6.00
TB/5.45 TiB)
[    1.334040] sd 4:0:0:0: [sde] 4096-byte physical blocks
[    1.334180] sd 4:0:0:0: [sde] Write Protect is off
[    1.334185] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
[    1.334231] scsi 5:0:0:0: Direct-Access     ATA      WDC WD60EFRX-68M 0A82
PQ: 0 ANSI: 5
[    1.334233] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[    1.334527] sd 5:0:0:0: [sdf] 11721045168 512-byte logical blocks: (6.00
TB/5.45 TiB)
[    1.334532] sd 5:0:0:0: [sdf] 4096-byte physical blocks
[    1.334548] sd 5:0:0:0: Attached scsi generic sg5 type 0
[    1.334647] sd 5:0:0:0: [sdf] Write Protect is off
[    1.334653] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
[    1.334768] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[    1.335031] scsi 15:0:0:0: Processor         Marvell  Console          1.01
PQ: 0 ANSI: 5
[    1.346509] ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[    1.346662] ata16.00: irq_stat 0x40000001
[    1.346796] ata16.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 2 dma
16640 in
                        Inquiry 12 01 00 00 ff 00res
00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
[    1.347344] ata16: hard resetting link
[    1.350686] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.350688] sd 1:0:0:0: [sdb] Attached SCSI disk
[    1.354182] sd 5:0:0:0: [sdf] Attached SCSI disk
[    1.355834] sd 4:0:0:0: [sde] Attached SCSI disk
[    1.787613] sd 3:0:0:0: [sdd] Attached SCSI disk
[    1.788180] sd 2:0:0:0: [sdc] Attached SCSI disk
[    1.832932] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.883536] ata16.00: configured for UDMA/66
[    1.883621] ata16: EH complete
[    1.883920] scsi 15:0:0:0: Attached scsi generic sg6 type 3

Have two Marvell controllers:
04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
09:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

[email protected]

author

2016-01-19 14:33 UTC #7 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

Jürgen Hörmann <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #5 from Jürgen Hörmann <[email protected]> --- Having this issue too.
My apt database got corrupted while installing update packages.

[    2.232046] ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[    2.232054] ata14.00: irq_stat 0x40000001
[    2.232067] ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 2 dma
16640 in
                        Inquiry 12 01 00 00 ff 00res

00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)

My System: Ubuntu 15.10 64bit
Kernel: 4.2.0-23-generic

Signature · 5 lines

You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[email protected]

author

2016-02-02 08:01 UTC #8 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #6 from [email protected] ---
I see almost the exact same error across multiple (qty 4, all the same HW configs) Supermicro X10SBA motherboards that I have.

Jan 30 06:52:52 tank2 kernel: [    1.689428] ata12.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x6
Jan 30 06:52:52 tank2 kernel: [    1.689430] ata12.00: irq_stat 0x40000001
Jan 30 06:52:52 tank2 kernel: [    1.689440] ata12.00: cmd
a0/01:00:00:00:01/00:00:00:00:00/a0 tag 2 dma 16640 in
Jan 30 06:52:52 tank2 kernel: [    1.689440]          opcode=0x12 12 01 00 00
ff 00res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
Jan 30 06:52:52 tank2 kernel: [    1.689446] ata12: hard resetting link

These motherboards use the Marvell 9230 chip to add 4 SATA ports to the 2 SATA ports provided by the BayTrail SoC.

I can sometimes recreate this error when placing the filesystem under heavy load. In this case it is a multi-terabyte ZFS "tank" and "zpool" is doing a "scrub".

Gentoo Linux running gentoo-sources-4.1.15-r1

I do not remember when I first started to see this error appear.

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

[email protected]

author

2016-02-05 16:20 UTC #9 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

--- Comment #7 from Clay Harris <[email protected]> --- I'm seeing the following:

ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata16.00: ATAPI: MARVELL VIRTUALL, 1.09, max UDMA/66
ata16.00: configured for UDMA/66
ata16.00: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x6 ata16.00: irq_stat 0x40000001
ata16.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 1 dma 16640 in Inquiry 12 01 00 00 ff 00res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
ata16: hard resetting link

Controller is:
a:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9128 PCIe SATA 6 Gb/s RAID controller with HyperDuo (rev 11) (prog-if 01 [AHCI 1.0])
Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard

Linux 4.3.4-300.fc23.x86_64

I see this error most every boot.

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.

[email protected]

author

2016-03-29 03:34 UTC #10 lore raw

[Bug 98171] [Regression] Marvell SE91xx SATA 3 controllers not recognized correctly

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=98171

[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #8 from [email protected] ---
I am seeing the same error on my Xubuntu 15.10 system at every boot.

[    1.707400] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.707518] ata14.00: ATAPI: MARVELL VIRTUALL, 1.09, max UDMA/66
[    1.707679] ata14.00: configured for UDMA/66
[    1.934951] ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[    1.934998] ata14.00: irq_stat 0x40000001
[    1.935040] ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 1 dma
16640 in Inquiry 12 01 00 00 ff 00res 00/00:00:00:00:00/00:00:00:00:00/00 Emask
0x3 (HSM violation)
[    1.935089] ata14: hard resetting link
[    2.262449] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.262751] ata14.00: configured for UDMA/66
[    2.262825] ata14: EH complete

SATA controller: Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller (rev 11)
Kernel: 4.2.0-34-generic #39-Ubuntu SMP Thu Mar 10 22:13:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux (Xubuntu 15.10)
Motherboard: Gigabyte Technology Co., Ltd. GA-970A-UD3P

Hoping to see this issue addressed shortly.

Signature · 2 lines

You are receiving this mail because:
You are watching the assignee of the bug.