public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Adam Ford <aford173@gmail.com>,
	Linux OMAP <linux-omap@vger.kernel.org>,
	Saravana Kannan <saravanak@google.com>,
	Linux Stable <stable@vger.kernel.org>,
	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 09:17:39 +0300	[thread overview]
Message-ID: <20230905061739.GX11676@atomide.com> (raw)
In-Reply-To: <ZPZ2zTS9loj06u31@debian.me>

* Bagas Sanjaya <bagasdotme@gmail.com> [230905 00:31]:
> 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.

Adam, maybe check if 6.1 stable series is missing something to be
backported from this mailing list thread:

https://lore.kernel.org/lkml/20230207014207.1678715-2-saravanak@google.com/

That email thread version seemed to work for me based on my reply in the
thread. I recall issues with the earlier revisions but don't remember
what fixed them.

> > 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

Regards,

Tony

  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
2023-09-05  6:17   ` Tony Lindgren [this message]
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=20230905061739.GX11676@atomide.com \
    --to=tony@atomide.com \
    --cc=aford173@gmail.com \
    --cc=bagasdotme@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 \
    /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