[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1392eba8-d869-aa1a-b154-cec870017115@gmail.com>
Date: Thu, 19 May 2022 10:38:04 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: stable@...r.kernel.org
Cc: Ulf Hansson <ulf.hansson@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Avri Altman <avri.altman@....com>,
Bean Huo <beanhuo@...ron.com>,
Nishad Kamdar <nishadkamdar@...il.com>,
Christian Löhle <CLoehle@...erstone.com>,
"open list:MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND..."
<linux-mmc@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>, alcooperx@...il.com,
kdasu.kdev@...il.com
Subject: Re: [PATCH stable 4.19 0/3] MMC timeout back ports
On 5/17/2022 11:22 AM, Florian Fainelli wrote:
> These 3 commits from upstream allow us to have more fine grained control
> over the MMC command timeouts and this solves the following timeouts
> that we have seen on our systems across suspend/resume cycles:
>
> [ 14.907496] usb usb2: root hub lost power or was reset
> [ 15.216232] usb 1-1: reset high-speed USB device number 2 using
> xhci-hcd
> [ 15.485812] bcmgenet 8f00000.ethernet eth0: Link is Down
> [ 15.525328] mmc1: error -110 doing runtime resume
> [ 15.531864] OOM killer enabled.
>
> Thanks!
Looks like I managed to introduce a build warning due to the unused
timeout variable, let me submit a fresher version for 4.19, 4.14 and 4.9.
--
Florian
Powered by blists - more mailing lists