6.7 regression: platform 4809c000.mmc: deferred probe pending
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?
Signature · 8 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
[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.
Quoted 10 lines · Andreas Schwab
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
Quoted 2 lines
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.
[TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.]
Anyway, to be sure the issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression tracking bot:
#regzbot ^introduced v6.6..v6.7
#regzbot title arm: omap: platform 4809c000.mmc: deferred probe pending #regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply and tell me -- ideally while also telling regzbot about it, as explained by the page listed in the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing to the report (the parent of this mail). See page linked in footer for details.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) --
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Quoted 20 lines · Linux regression tracking (Thorsten Leemhuis)
[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.
Quoted 10 lines · Andreas Schwab
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
Quoted 5 lines
Quoted 2 lines
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
Quoted 4 lines · Tony Lindgren
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 useof_match_device()") is applied.
That commit hasn't hit stable yet. Maybe it's because it references a non-existant commit id (1e0c866887f4 instead of 830fafce06e6).
Signature · 3 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Quoted 9 lines · Andreas Schwab
Quoted 4 lines · Tony Lindgren
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 useof_match_device()") is applied.That commit hasn't hit stable yet. Maybe it's because it references a non-existant commit id (
1e0c866887f4instead of830fafce06e6).
Yeah, our tools can't do about a commit that does not have a cc: stable@ tag in it AND the only commit it does reference is not one actually in the tree at all.
An impossible task for us here, please ask [email protected] to take the commit if this is needed, and let us know how far back it should go.
thanks,
greg k-h
Quoted 11 lines · Greg KH
Quoted 9 lines · Andreas Schwab
Quoted 4 lines · Tony Lindgren
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 useof_match_device()") is applied.That commit hasn't hit stable yet. Maybe it's because it references a non-existant commit id (
1e0c866887f4instead of830fafce06e6).
Quoted 7 lines
Yeah, our tools can't do about a commit that does not have a cc: stable@ tag in it AND the only commit it does reference is not one actually in the tree at all.
An impossible task for us here, please ask [email protected] to take the commit if this is needed, and let us know how far back it should go.
Andreas, did commit 7a29fa05aeca solve the issue? If so please send and email to the stable list.
Regards,
Tony
Quoted 1 line · Tony Lindgren
Andreas, did commit
7a29fa05aecasolve the issue?
Yes, it does. Thanks.
Signature · 3 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Quoted 11 lines · Greg KH
Quoted 9 lines · Andreas Schwab
Quoted 4 lines · Tony Lindgren
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 useof_match_device()") is applied.That commit hasn't hit stable yet. Maybe it's because it references a non-existant commit id (
1e0c866887f4instead of830fafce06e6).
Quoted 7 lines
Yeah, our tools can't do about a commit that does not have a cc: stable@ tag in it AND the only commit it does reference is not one actually in the tree at all.
An impossible task for us here, please ask [email protected] to take the commit if this is needed, and let us know how far back it should go.
To be explicit, does this need to be applied to the stable tree(s)? If so, please email [email protected] with the git id to do so.
thanks,
greg k-h
Quoted 16 lines · Greg KH
Quoted 15 lines · Greg KH
Quoted 9 lines · Andreas Schwab
Quoted 4 lines · Tony Lindgren
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 useof_match_device()") is applied.That commit hasn't hit stable yet. Maybe it's because it references a non-existant commit id (
1e0c866887f4instead of830fafce06e6).Yeah, our tools can't do about a commit that does not have a cc: stable@ tag in it AND the only commit it does reference is not one actually in the tree at all.
Quoted 6 lines
Quoted 3 lines
An impossible task for us here, please ask [email protected] to take the commit if this is needed, and let us know how far back it should go.
To be explicit, does this need to be applied to the stable tree(s)? If so, please email [email protected] with the git id to do so.
Andreas, Tony afaics asked you to do that here:
https://lore.kernel.org/all/[email protected]/
But unless I missed something nothing happened since then. Did it fall through the cracks? Reminder, if that patch clearly applied to 6.7.y then all that's afaics needed is a mail with a simple text along the lines of "Greg, please pick up 7a29fa05aeca2c ("mfd: twl6030-irq: Revert to use of_match_device()") for linux-6.7.y, it fixes a bug I ran into and Tony is fine with it."
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) --
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.