Re: Bug Report: Delayed Wake from Suspend with Genesys Logic GL9755 SD Host Controller

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Ilpo

That worked! I can now wake almost instantly from suspension.

Thanks for the quick responses!

On Mon, 26 Feb 2024 at 12:49, Ilpo Järvinen
<ilpo.jarvinen@xxxxxxxxxxxxxxx> wrote:
>
> On Mon, 26 Feb 2024, Mathias De Weerdt wrote:
>
> > Hi Bjorn
> >
> > This has indeed never worked. I have even tried plenty of older
> > kernels and now also the latest mainline.
> >
> > I collected the data you requested on the following kernel (Latest
> > mainline as of yesterday)
> > Linux core-arch 6.8.0-rc5-1-mainline #1 SMP PREEMPT_DYNAMIC Sun, 25
> > Feb 2024 21:59:28 +0000 x86_64 GNU/Linux
> >
> > After booting the laptop I put it to sleep and woke it up and
> > collected the dmesg and lspci logs. (They have been attached)
> >
> > Thanks for your quick response.
> > If you need anything else please let me know.
> >
> > Kinds regards
> > Mathias
> >
> > On Mon, 26 Feb 2024 at 00:31, Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote:
> > >
> > > On Sun, Feb 25, 2024 at 11:38:35PM +0100, Mathias De Weerdt wrote:
> > > > Hi
> > > >
> > > > I am writing to report a potential bug in the Linux kernel related to
> > > > waking from suspend on a system(Laptop) with a Genesys Logic GL9755 SD
> > > > Host Controller. Below are the details of the issue:
> > >
> > > Hi Mathias, thanks very much for this report.  A few questions below.
> > >
> > > > Issue Description:
> > > > After suspending the system, waking it up takes an extended amount of
> > > > time, typically 1 to 2 minutes. The delay occurs consistently and is
> > > > observed in the dmesg logs.
> > > >
> > > >
> > > > System Information:
> > > > - OS: Arch Linux x86_64
> > > > - Kernel: 6.7.5-arch1-1 and 6.7.6-arch1-1
> > > > - SD Host Controller: Genesys Logic GL9755 SD Host Controller (PCI ID:
> > > > 17a0:9755)
> > > >
> > > > Observed Logs (dmesg):
> > > > [ 642.483972] sdhci-pci 0000:2f:00.0: not ready 1023ms after resume; waiting
> > > > [ 643.537370] sdhci-pci 0000:2f:00.0: not ready 2047ms after resume; waiting
> > > > [ 645.724028] sdhci-pci 0000:2f:00.0: not ready 4095ms after resume; waiting
> > > > [ 649.990655] sdhci-pci 0000:2f:00.0: not ready 8191ms after resume; waiting
> > > > [ 658.310658] sdhci-pci 0000:2f:00.0: not ready 16383ms after resume; waiting
> > > > [ 675.590673] sdhci-pci 0000:2f:00.0: not ready 32767ms after resume; waiting
> > > > [ 709.723965] sdhci-pci 0000:2f:00.0: not ready 65535ms after resume; giving up
> > > > [ 709.724183] sdhci-pci 0000:2f:00.0: Unable to change power state
> > > > from D3cold to D0, device inaccessible
>
> Hi Mathias,
>
> In your dmesg, there's the Target Speed quirk triggering. Please try these
> two patches, they should fix the logic bug that causes the long delay you
> see:
>
> https://lore.kernel.org/linux-pci/alpine.DEB.2.21.2402092125070.2376@xxxxxxxxxxxxxxxxx/T/#t
>
> (They won't help to the link not coming up issue though).
>
> --
>  i.





[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux