This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1832383
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##############################
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
