From: Christian Heusel <christian@heusel.eu>
To: Sean Rhodes <sean@starlabs.systems>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
quintafeira@tutanota.com, Arnd Bergmann <arnd@arndb.de>,
Desnes Nunes <desnesn@redhat.com>,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION][BISECTED] SD Cards detection broken leading to boot failures
Date: Thu, 27 Feb 2025 00:46:16 +0100 [thread overview]
Message-ID: <b80dc39c-cfa5-4064-906b-4cbc2ae8fad3@heusel.eu> (raw)
In-Reply-To: <50e67317-62bb-46aa-a539-54bf6dbb245a@heusel.eu>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
Hey Sean,
On 25/02/24 10:27AM, Christian Heusel wrote:
> On 25/02/24 09:09AM, Sean Rhodes wrote:
> > Give me a day, two tops please; ideally we can just push a patch to fix the
> > trivial issue and keep the major fix :)
>
> Sure this is fine by me, I guess you can just hold off applying the
> revert patch that I have sent after gregs comment.
>
> If you need any testers for new patches or debug patches I'll happily
> build them and send them to the reporters on the Forum.
Did you already have a chance to look into this or should we go with a
revert for the time being? Just asking because you wanted to come up
with something quickly :)
Cheers,
Chris
>
> >
> > On Mon, 24 Feb 2025 at 07:07, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > wrote:
> >
> > > On Sat, Feb 22, 2025 at 10:22:34PM +0100, Christian Heusel wrote:
> > > > Hello everyone,
> > > >
> > > > on the Arch Linux Forums[1] multiple users reported issues with their SD
> > > > cards not being recognized during boot or that they needed to re-plug
> > > > them in order for them to be recognized.
> > > >
> > > > One user tracked this down to the following commit:
> > > >
> > > > 235b630eda07 ("drivers/card_reader/rtsx_usb: Restore interrupt based
> > > detection")
> > > >
> > > > They have also created a report on the kernel bugzilla[1], therefore I
> > > > cc'ed them to this thread. We found that reverting the above commit on
> > > > top of v6.14-rc3 fixes the issue.
> > >
> > > Thanks for the report. Do you want to send a revert for this, or do you
> > > need us to create it?
> > >
> > > thanks,
> > >
> > > greg k-h
> > >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-02-26 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 21:22 Christian Heusel
2025-02-24 7:07 ` Greg Kroah-Hartman
[not found] ` <CABtds-2TDWCHqOa+Di2Yh074RukUrjEhKGC82DWZ_7ysK-NCrA@mail.gmail.com>
2025-02-24 9:27 ` Christian Heusel
2025-02-26 23:46 ` Christian Heusel [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=b80dc39c-cfa5-4064-906b-4cbc2ae8fad3@heusel.eu \
--to=christian@heusel.eu \
--cc=arnd@arndb.de \
--cc=desnesn@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quintafeira@tutanota.com \
--cc=regressions@lists.linux.dev \
--cc=sean@starlabs.systems \
/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®