[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#805977: marked as done (linux-image-amd64: offten recive ata error:" failed command: READ FPDMA QUEUED")

Your message dated Sun, 09 May 2021 07:09:45 -0700 (PDT)
with message-id <6097ed29.1c69fb81.d11d4.d477@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #805977,
regarding linux-image-amd64: offten recive ata error:" failed command: READ FPDMA  QUEUED"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
805977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805977
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: linux-image-amd64
Version: 4.2+68
Severity: normal

Dear Maintainer,

On most reboots ot startup i get this ATA errors:
[    9.787144] ata6.00: exception Emask 0x0 SAct 0x2200000 SErr 0x0 action 0x6
[    9.787191] ata6.00: irq_stat 0x40000008
[    9.787219] ata6.00: failed command: READ FPDMA QUEUED
[    9.787256] ata6.00: cmd 60/20:c8:b8:9e:fd/00:00:0d:00:00/40 tag 25 ncq
16384 in
                        res 41/84:20:b8:9e:fd/00:00:0d:00:00/00 Emask 0x410
(ATA bus error) <F>
[    9.787346] ata6.00: status: { DRDY ERR }
[    9.787372] ata6.00: error: { ICRC ABRT }
[    9.787397] ata6: hard resetting link
[   10.107238] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   10.210212] ata6.00: configured for UDMA/133
[   10.210227] ata6: EH complete

I've found that maybe there is some problem with NCQ. I've disable it with
option in grub which
just changed error message to something else related to DMA.
I've run about 5 times short SMART test and 2 times long SMART test without
errors.
Despite that test passed i've get SMART error:   End-to-End_Error become 1200
while threshold is 99.

I've decided that my disk is doing to die so i've backup all my data.
Then i've installed windows  and run seagate tools which is only available for
windows
and my hdd passed all test without any errors. I've read on Seagate site that
some
of this SMART error can't be trusted because they don't have the same meaning
for Seagate drive as for
other manufactures.  I've run all test that Lenovo provide for my laptop and
they all passed without error either.
I have to  mention that iso image of Seagate tools for DOS can't even
initialize my HDD and can't
make any test.

I don't know if this is right place to report this bug but i believe
that there is something wrong with ata module for linux.
My hdd is Seagate Laptop SSHD ST1000LM014-SSHD-8GB.

My hdd often even can't boot with some grub errors and i have to hard reset it
several time until it start. When i have only windows and didn't use grub to
boot,
windows boot every time without any errors.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-rc7-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.2.0-1-amd64  4.2.6-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Божан
--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: