From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Adam Ford <aford173@gmail.com>,
Linux OMAP <linux-omap@vger.kernel.org>,
Saravana Kannan <saravanak@google.com>
Cc: Linux Stable <stable@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 6.1.y Regression found on AM3517
Date: Tue, 5 Sep 2023 07:31:09 +0700 [thread overview]
Message-ID: <ZPZ2zTS9loj06u31@debian.me> (raw)
In-Reply-To: <CAHCN7xJjK=BaNHa=+OKzOmFtNRYKX_APTp5Zj3g-X_iQcpyK6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
On Mon, Sep 04, 2023 at 11:37:46AM -0500, Adam Ford wrote:
> I have an AM3517-EVM board that I am trying to use the latest 6.1.y
> stable, currently 6.1.51.
>
> With git bisect, I narrowed the regression between 6.1.15 and 6.1.16 to commit
> eaf9b5612a47 ("driver core: fw_devlink: Don't purge child fwnode's
> consumer links")
>
> In the regression, 48002000.scm appears as not ready. This affects a
> variety of dependent peripherals making them unavailable:
>
> wl12xx_buf platform: supplier 48002000.scm not ready
> wl12xx_vmmc2 platform: supplier wl12xx_buf not ready
> 48050000.dss platform: supplier display@0 not ready
> 48064800.ehci platform: supplier hsusb1_phy not ready
> backlight platform: supplier 48002000.scm not ready
> display@0 platform: supplier backlight not ready
> dmtimer-pwm@11 platform: supplier 48002000.scm not ready
> hsusb1_phy platform: supplier 48002000.scm not ready
> gpio-leds platform: supplier 48002000.scm not ready
> 480b4000.mmc platform: supplier wl12xx_vmmc2 not ready
>
> If I build 6.1.51 but I checkout drivers/base/core.c from commit
> 2455b81afe68 ("driver core: fw_devlink: Add DL_FLAG_CYCLE support to
> device links"),
> the regression is gone.
>
> I checked the 6.5 kernel, and it appears fine, so I think there is a
> possible backport commit missing, and I was hoping Saravana or Tony
> might have a suggestion as to which one(s) I should try. I don't know
> if this is found on other OMAP3 boards, but I wouldn't be surprised.
>
Thanks for the regression report. I'm adding it to regzbot as stable-specific
entry:
#regzbot ^introduced: eaf9b5612a47f0
#regzbot title: keeping consumer links of child fwnode doesn't prepare AM3517-EVM suppliers
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-05 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 16:37 6.1.y Regression found on AM3517 Adam Ford
2023-09-05 0:31 ` Bagas Sanjaya [this message]
2023-09-05 6:17 ` Tony Lindgren
2023-09-06 10:59 ` Adam Ford
2023-09-12 11:14 ` Linux regression tracking #update (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=ZPZ2zTS9loj06u31@debian.me \
--to=bagasdotme@gmail.com \
--cc=aford173@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=saravanak@google.com \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.