apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1832383/+attachment/5270204/+files/WifiSyslog.txt
** Description changed: This is connected to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158 + + CORRECTION: ata6 is populated! I made a mistake! 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 - --- - ProblemType: Bug - AlsaDevices: - total 0 - crw-rw---- 1 root audio 116, 1 Jun 11 01:17 seq - crw-rw---- 1 root audio 116, 33 Jun 11 01:17 timer - AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' - ApportVersion: 2.20.9-0ubuntu7.6 - Architecture: amd64 - ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' - AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: - DistroRelease: Ubuntu 18.04 - EcryptfsInUse: Yes - HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2 - InstallationDate: Installed on 2018-03-29 (438 days ago) - InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) - IwConfig: - enp3s0 no wireless extensions. - - lo no wireless extensions. - - enp5s0 no wireless extensions. - MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. - Package: linux (not installed) - PciMultimedia: - - ProcFB: - - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro - ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 - PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. - RelatedPackageVersions: - linux-restricted-modules-4.18.0-21-generic N/A - linux-backports-modules-4.18.0-21-generic N/A - linux-firmware 1.173.6 - RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' - Tags: bionic - Uname: Linux 4.18.0-21-generic x86_64 - UnreportableReason: This report is about a package that is not installed. - UpgradeStatus: Upgraded to bionic on 2018-05-07 (400 days ago) - UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo - _MarkForUpload: False - dmi.bios.date: 04/29/2015 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: P1.50 - dmi.board.name: AM1H-ITX - dmi.board.vendor: ASRock - dmi.chassis.asset.tag: To Be Filled By O.E.M. - dmi.chassis.type: 3 - dmi.chassis.vendor: To Be Filled By O.E.M. - dmi.chassis.version: To Be Filled By O.E.M. - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd04/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM1H-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: - dmi.product.family: To Be Filled By O.E.M. - dmi.product.name: To Be Filled By O.E.M. - dmi.product.sku: To Be Filled By O.E.M. - dmi.product.version: To Be Filled By O.E.M. - dmi.sys.vendor: To Be Filled By O.E.M. + 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 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: This is connected to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158 - CORRECTION: ata6 is populated! I made a mistake! + CORRECTION: ata6 is populated! I made a mistake! Please see Post #14 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832383 Title: failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
