From: AlanCui4080 <me@alancui.cc>
To: Niklas Cassel <cassel@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: Default IDENTIFY timeout is 5000ms which is too short for enterprise disks
Date: Sat, 09 May 2026 04:48:35 +0800 [thread overview]
Message-ID: <DlZIztR2R7G4sZHRUgM9CA@alancui.cc> (raw)
In-Reply-To: <aepGCyy5uXXxw6jT@ryzen>
Hi Cassel,
On Friday, 24 April 2026 00:17，you wrote：
> So as far as I can tell, even increasing the timeout does not solve the
> problem in all cases.
>
> So, right now, I can't even think of a way to quirk the device so that it
> works reliably.
FYI, After I replaced the motherboard from B550 to X570, this problem is
completely gone. So It seems that's a corner case with this drive and my
south bridge.
The only message produced by kernel ata driver is:
May 09 04:42:37 AlanArchDesktop kernel: ata6: link is slow to respond, please be patient (ready=0)
May 09 04:42:37 AlanArchDesktop kernel: ata2: link is slow to respond, please be patient (ready=0)
Looks pretty good to me :)
Due to the B550 motherboard is taken down from my computer, I'm going
to do more tests on ata driver once I got my new CPU.
Alan.
next prev parent reply other threads:[~2026-05-08 21:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 10:21 Default IDENTIFY timeout is 5000ms which is too short for enterprise disks AlanCui4080
2026-04-09 11:55 ` Damien Le Moal
2026-04-09 12:01 ` Damien Le Moal
2026-04-15 12:40 ` Niklas Cassel
2026-04-16 12:59 ` AlanCui4080
2026-04-20 16:27 ` Niklas Cassel
2026-04-23 9:18 ` AlanCui4080
2026-04-23 11:15 ` Niklas Cassel
2026-04-23 14:26 ` AlanCui4080
2026-04-23 16:17 ` Niklas Cassel
2026-05-08 20:48 ` AlanCui4080 [this message]
[not found] ` <14062658.dW097sEU6C@alanarchdesktop>
[not found] ` <4482b737-1454-48cb-a941-165aa84fb2eb@kernel.org>
2026-04-10 11:24 ` AlanCui4080
2026-04-10 12:14 ` AlanCui4080
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DlZIztR2R7G4sZHRUgM9CA@alancui.cc \
--to=me@alancui.cc \
--cc=cassel@kernel.org \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox