--- Begin Message ---
- To: 983672-done@bugs.debian.org
- Subject: Re: Bug#983672: linux-image: fails to recognize certain microSD cards
- From: José Luis González <bugs.jlg@gmail.com>
- Date: Sun, 20 Feb 2022 02:50:20 +0100
- Message-id: <20220220025020.367d202eb7c37a28d9b1951e@gmail.com>
- In-reply-to: <YDv02mTxR/1X594f@eldamar.lan>
- References: <20210228110158.47da3c1dc164b1eeb1fbfc0a@gmail.com> <YDv02mTxR/1X594f@eldamar.lan>
On Sun, 28 Feb 2021 20:54:02 +0100
Salvatore Bonaccorso <carnil@debian.org> wrote:
> Control: tags -1 + moreinfo
>
> hi José,
Hi Salvatore,
> On Sun, Feb 28, 2021 at 11:01:58AM +0100, José Luis González wrote:
> > Package: linux-image-4.19.0-13-amd64
> > Version: 4.19.160-2
> > Tags: patch upstream
> >
> > Certain SD cards set a flag that isn't really defined in the SD spec
> > but the mmc should be ignoring. It turns out it doesn't, so the cards
> > don't get recognized properly making it impossible to use them.
> >
> > There is a bug reported in kernel.org's bugzilla that explains it all:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=202473
> >
> > Contained is a very small patch that fixes the problem:
> >
> > https://patchwork.kernel.org/project/linux-mmc/patch/20190827081043.15443-1-ulf.hansson@linaro.org/
> >
> > Please, incorporate the patch so that we can use these cards.
> >
> > I have tested both version 4.19.160-2 and version 5.9.15-1~bpo10+1
> > (this from buster-backports), and neither mount my card successfully so
> > I understand the patch isn't incorporated to either.
> >
> > I'd very much appreciate if the fix got into buster-backports.
>
> then probably the issue you have is another one though. The above
> patch was commited upstream as 72741084d903 ("mmc: core: Fix init of
> SD cards reporting an invalid VDD range") and landed in 5.3-rc7, and
> got backported to several stable series as in 5.2.12, 4.19.70,
> 4.14.142, 4.9.191, 4.4.191 and 3.16.78.
I didn't realize it was already into these. As far as I am concerned
the bug is fixed. I have tested it now on my bullseye machine.
> The report did not contain any further information, so please do
> attach as well kernel logs, errors, you are seeing, how/if the card is
> detected (when filling the report via reportbug, this information will
> be attached).
Well, it happened that kernel logs were identical to those reported in
the link above. This is the reason I didn't include them again in my
report, but nevermind.
> Regards,
> Salvatore
Cheers,
José Luis
--- End Message ---