* Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> [220615 08:54]: > Hi Tony, > > On Wed, Jun 15, 2022 at 10:08 AM Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > * Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> [220615 09:40]: > > > Hi Tony, Ulf, > > > > > > On Thu, May 5, 2022 at 7:03 AM Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > > > > > Hi, > > > > > > > > * Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> [220504 09:12]: > > > > > Hi Tony, all, > > > > > > > > > > During the kernel boot I see the following error. The device is still > > > > > working afterwards. 5.17.5 shows the same behavior. Is this a known > > > > > issue? > > > > > > > > Thanks for reporting it, I was not aware of this one. Might be worth > > > > bisecting. Adding linux-mmc and Ulf. > > > > > > This is my bisect result: > > > > > > f433e8aac6b94218394c6e7b80bb89e4e79c9549 is the first bad commit > > > commit f433e8aac6b94218394c6e7b80bb89e4e79c9549 > > > Author: Tony Lindgren <tony@xxxxxxxxxxx> > > > Date: Fri Oct 15 13:47:18 2021 +0300 > > > > > > mmc: sdhci-omap: Implement PM runtime functions > > > > > > Implement PM runtime functions and enable autosuspend. > > > > > > Note that we save context in probe to avoid restoring invalid context > > > on the first resume. For system suspend, we have the new PM runtime > > > functions do most of the work. > > > > > > Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> > > > Link: https://lore.kernel.org/r/20211015104720.52240-5-tony@xxxxxxxxxxx > > > Signed-off-by: Ulf Hansson <ulf.hansson@xxxxxxxxxx> > > > > OK thanks this makes sense based on what Arnd replied a few days ago. > > > > Regards, > > Your patch did the trick: all warnings/errors are gone. Thanks > everyone for the help. OK thanks for testing, will send out a proper patch today for this. Regards, Tony
