linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Andreas Schwab <schwab@suse.de>,
	linux-arm-kernel@lists.infradead.org,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: 6.7 regression: platform 4809c000.mmc: deferred probe pending
Date: Thu, 15 Feb 2024 11:46:40 +0200	[thread overview]
Message-ID: <20240215094640.GS52537@atomide.com> (raw)
In-Reply-To: <c92385d2-1909-43a8-aea8-cd9a8687a898@leemhuis.info>

* Linux regression tracking (Thorsten Leemhuis) <regressions@leemhuis.info> [240214 14:01]:
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
> 
> Hi, Thorsten here, the Linux kernel's regression tracker.
> 
> Thanks for the report.Added the omap list and the omap mmc maintainer;
> the root of the problem might be somewhere else, but maybe we get some
> help from there.
> 
> On 12.02.24 14:46, Andreas Schwab wrote:
> > I'm getting these messages on the PandaBoard since 6.7:
> > 
> > [   29.285522][  T156] platform 4809c000.mmc: deferred probe pending
> > [   29.291748][  T156] platform 4a0ab000.usb_otg_hs: deferred probe pending
> > [   29.298522][  T156] platform 58005000.encoder: deferred probe pending
> > [   29.305053][  T156] platform 58006000.encoder: deferred probe pending
> > [   29.305145][  T156] i2c 0-004b: deferred probe pending
> > [   29.316772][  T156] platform 40132000.target-module: deferred probe pending
> > [   37.382110][  T156] pbias_mmc_omap4: disabling
> > 
> > As a result, the SD card is not found.
> > Any idea what's going on here?
> 
> Haven't heard of anything like that. Unless some developer replies with
> some idea in a day or two I guess you will have to bisect the problem.

There was a regression recently with the PMIC which would cause NFSroot
on devices to keep working but may have affected MMC. Please check that
commit 7a29fa05aeca ("mfd: twl6030-irq: Revert to use of_match_device()")
is applied. If that does not help, then git bisect is the way to go.

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-02-15  9:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 13:46 6.7 regression: platform 4809c000.mmc: deferred probe pending Andreas Schwab
2024-02-14 14:00 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-15  9:46   ` Tony Lindgren [this message]
2024-02-15 10:28     ` Andreas Schwab
2024-02-15 11:16       ` Greg KH
2024-02-16 12:08         ` Tony Lindgren
2024-02-19  9:17           ` Andreas Schwab
2024-02-20 14:35         ` Greg KH
2024-02-29  7:33           ` Linux regression tracking (Thorsten Leemhuis)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240215094640.GS52537@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=schwab@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).