Re: [Bug] SD card reader in Acer Aspire S5 broken in 4.20-rc

From: Rafael J. Wysocki
Date: Tue Dec 04 2018 - 13:04:22 EST


On Tuesday, December 4, 2018 1:10:09 AM CET Bjorn Helgaas wrote:
> On Wed, Nov 28, 2018 at 02:05:21PM -0600, Bjorn Helgaas wrote:
> > On Wed, Nov 28, 2018 at 6:13 AM Rafael J. Wysocki <rjw@xxxxxxxxxxxxx> wrote:
> > > On Tuesday, November 27, 2018 9:25:14 PM CET Bjorn Helgaas wrote:
> > > > On Mon, Nov 26, 2018 at 11:37:20PM +0100, Rafael J. Wysocki wrote:
> > > > > On Monday, November 26, 2018 7:03:58 PM CET Rafael J. Wysocki wrote:
> > > > > > Hi Bjorn,
> > > > > >
> > > > > > The SD card reader in my Acer Aspire S5 doesn't work with 4.20-rc.
> > > > > >
> > > > > > Here's what lspci -v says about it (in a bad kernel):
> > > > > >
> > > > > > 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader
> > > > > > (rev 01)
> > > > > > Subsystem: Acer Incorporated [ALI] Device 0704
> > > > > > Flags: bus master, fast devsel, latency 0, IRQ 35
> > > > > > Memory at d9001000 (32-bit, non-prefetchable) [size=4K]
> > > > > > Capabilities: [40] Power Management version 3
> > > > > > Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
> > > > > > Capabilities: [70] Express Endpoint, MSI 00
> > > > > > Capabilities: [100] Advanced Error Reporting
> > > > > > Capabilities: [140] Device Serial Number 00-00-00-01-00-4c-e0-00
> > > > > > Kernel driver in use: rtsx_pci
> > > > > > Kernel modules: rtsx_pci
> > > >
> > > > Thanks a lot for bisecting this!
> > > >
> > > > With a good kernel (v4.19 or v4.20-rc with 17c91487364f reverted),
> > > > would you mind collecting "lspci -vv" output, the dmesg log with
> > > > "pci=earlydump", and the FADT dump?
> > >
> > > All of the information is attached to the BZ entry at
> > >
> > > https://bugzilla.kernel.org/show_bug.cgi?id=201801
> >
> > Thanks! I hope Patrick has a chance to look at this. Per the
> > bugzilla mentioned in 17c91487364f, it fixes a problem with a custom
> > proprietary PCIe device, and there's a lot of good detailed analysis
> > there, so hopefully we can figure out a way to address both
> > situations.
>
> I queued up a revert on for-linus, since we haven't made any progress on
> this yet. I'll be on vacation much of this week, but I want to get
> the revert (or better, a fix if we can find one) in before -rc6 comes
> out next Sunday.

Thanks!

> If we figure out a fix before then, I'll drop the revert and use the
> fix instead.