mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Kyrylo Biryuk <illofspeed@gmail.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ata: libahci: re-enable FBS after error handling on a port multiplier
Date: Thu, 15 Oct 2026 09:21:06 +0200	[thread overview]
Message-ID: <atB-4s_ffWEr6yDP@ryzen> (raw)
In-Reply-To: <eb21b333-3047-4f8c-a1d7-9d390d935abb@kernel.org>

On Thu, Oct 15, 2026 at 07:37:45AM +0200, Damien Le Moal wrote:
> On 2026/10/12 12:39, Kyrylo Biryuk wrote:
> > ahci_do_softreset() disables FBS before resetting a device behind a port
> > multiplier, as required by AHCI 1.2 section 9.3.9, and re-enables it only
> > when that softreset succeeds. If it fails, for example because a
> > hot-plugged drive is still spinning up ("softreset failed (device not
> > ready)"), EH escalates to a hardreset of the PMP link, and nothing turns
> > FBS back on: only ahci_pmp_attach() does, which runs at the next boot.
> > The port keeps working with command-based switching until then.
> > 
> > Seen on a Marvell 88SE9235 (1b4b:9235) with Marvell 88SM9705 port
> > multipliers (1b4b:9705, in a Synology DX1222 expansion unit): after
> > hot-plugging a drive, the kernel logged "FBS is disabled" followed by
> > "softreset failed (device not ready)" and a PMP hardreset, and never
> > "FBS is enabled" again (twice, on two different ports).
> > 
> > At the end of ahci_error_handler(), re-enable FBS if a PMP is still
> > attached and FBS is supported but disabled.
> > 
> > Fixes: 89dafa20f3da ("ahci: disabled FBS prior to issuing software reset")
> > Assisted-by: LLM
> > Signed-off-by: Kyrylo Biryuk <illofspeed@gmail.com>
> 
> Looks good.
> 
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

Commit was updated to pick up Damien's tag:
https://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git/commit/?id=23eab9e877497397a0e2394ee9174d576816209e


Kind regards,
Niklas

      reply	other threads:[~2026-10-15  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 10:39 Kyrylo Biryuk
2026-10-12 11:15 ` Niklas Cassel
2026-10-15  5:37 ` Damien Le Moal
2026-10-15  7:21   ` Niklas Cassel [this message]

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=atB-4s_ffWEr6yDP@ryzen \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=illofspeed@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®