From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Marcel Partap <mpartap@gmx.net>, Arnd Bergmann <arnd@arndb.de>,
merlijn@wizzup.org, martin_rysavy@centrum.cz,
Sebastian Reichel <sre@kernel.org>,
kernel list <linux-kernel@vger.kernel.org>,
nekit1000@gmail.com, Olof Johansson <olof@lixom.net>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Droid 4 regression in 5.5-rc1, armsoc-soc tree
Date: Thu, 2 Jan 2020 11:25:40 -0800 [thread overview]
Message-ID: <20200102192540.GD16702@atomide.com> (raw)
In-Reply-To: <20200102191804.nhnpd7q2eh4ul5a5@ucw.cz>
* Pavel Machek <pavel@ucw.cz> [200102 19:18]:
> > * Arnd Bergmann <arnd@arndb.de> [200102 14:48]:
> > > On Thu, Jan 2, 2020 at 3:06 PM Pavel Machek <pavel@ucw.cz> wrote:
> > >
> > > > # good: [ab818f0999dc73af3f966194d087e9f6650f939f] Merge tag
> > > > # 'omap-for-v5.5/maintainers-signed' of
> > > > # git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into
> > > > # arm/soc
> > > > git bisect good ab818f0999dc73af3f966194d087e9f6650f939f
> > > > # first bad commit: [38206c24ab09b4f4c2a57de5c1af0bb2e69cf5b6] Merge tag
> > > > # 'armsoc-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
> > > >
> > > > ...and am not sure how to interpret the result, or what to do next :(.
> > >
> > > This means that either the bisection is unreliable (it might be 100%
> > > reproducible or you mixed up good/bad once), or that the arm-soc
> > > branch was indeed good by itself but had a conflict with some other
> > > change that torvalds merged earlier.
> > >
> > > I would suggest to go back to the list I had extracted in my previous
> > > email and revert all the commits that I identify there, on top of
> > > linux-5.5-rc4. If some commit is not easily reverted, skip that one
> > > at first.
> > >
> > > Ideally this gets you a working kernel based on -rc4, and then
> > > you can bisect that to find which revert fixed it.
> >
> > Also please check your dtb is up to date. We still have a lot of
> > stuff missing from the device tree meaning an old dtb will likely
> > be incomplete for many devices.
>
> Aha, so it works ok when using matching kernel + dtb.
OK good to hear.
> Is 5.5 kernel with 5.3 dtb situation worth debugging?
Well producing a warning based on something would be good. Not sure
what the logic would be though, checking for some minimum dtb version
required would have to be bumped until we have complete dts data.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-02 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 16:29 Droid 4 on 5.5-rc3 Pavel Machek
2019-12-28 19:36 ` Pavel Machek
2019-12-30 17:35 ` Tony Lindgren
2020-01-01 20:11 ` Pavel Machek
2020-01-02 17:09 ` Tony Lindgren
2020-01-01 22:02 ` Pavel Machek
[not found] ` <20200102110025.GA29035@amd>
2020-01-02 11:49 ` Droid 4 regression in 5.5-rc1, armsoc-soc tree Arnd Bergmann
2020-01-02 12:29 ` Pavel Machek
2020-01-02 14:06 ` Pavel Machek
2020-01-02 14:47 ` Arnd Bergmann
2020-01-02 17:11 ` Tony Lindgren
2020-01-02 18:39 ` Pavel Machek
2020-01-02 19:18 ` Pavel Machek
2020-01-02 19:25 ` Tony Lindgren [this message]
2020-01-03 15:11 ` Stefan Wahren
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=20200102192540.GD16702@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martin_rysavy@centrum.cz \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=olof@lixom.net \
--cc=pavel@ucw.cz \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).