From: Niklas Cassel <cassel@kernel.org>
To: jhon cadena <jhon_jairo_cadena@protonmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-pcmcia@lists.infradead.org"
<linux-pcmcia@lists.infradead.org>
Subject: Re: [REGRESSION] pata_pcmcia: ~80 second delay after physically removing PC Card CF device
Date: Fri, 4 Sep 2026 00:09:29 +0200 [thread overview]
Message-ID: <apnwGStb-9FRo95y@ryzen> (raw)
In-Reply-To: <1zX3C-O2LeyhM2Zkz1FCkoqLUvxXWI_b5CfSB7DfI37xPsH9vIz1YlzPLWxAWUJi4rYcww6jDfuyKWZRBRQrzfUb0aLwkSHQxm9z_OHyMLU=@protonmail.com>
Hello Jhon,
On Thu, Sep 03, 2026 at 08:12:56PM +0000, jhon cadena wrote:
> The same type of PC Card storage worked normally on Debian 9 on my previous Toughbook.
> After moving to Debian 11 with a newer kernel, physically removing the card causes an
> approximately 79-second delay while the kernel continues trying to access the device
> before finally disabling it.
(snip)
> Current software:
>
> - Debian 11
>
> - Kernel: 5.10.0-46-amd64
Debian 9 uses kernel v4.9, released in 2016.
Debian 11 uses kernel v5.10, released in 2020.
On this mailing list, we only care about the latest kernel version.
At this point in time, v7.3-rc1, released Aug 30 2026.
Please thest on the latest kernel version, or report the problem to the
debian bug tracker.
Normally, we recommend to do a git bisect to find the commit that
introduced the problem. However, you know that v4.9 is good.
You should first see if v7.3-rc1 is good or bad before starting a
git bisect.
Kind regards,
Niklas
prev parent reply other threads:[~2026-09-03 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 20:12 [REGRESSION] pata_pcmcia: ~80 second delay after physically removing PC Card CF device jhon cadena
2026-09-03 22:09 ` 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=apnwGStb-9FRo95y@ryzen \
--to=cassel@kernel.org \
--cc=jhon_jairo_cadena@protonmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=regressions@lists.linux.dev \
/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