From: Pavel Machek <pavel@ucw.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Marcel Partap <mpartap@gmx.net>, Tony Lindgren <tony@atomide.com>,
merlijn@wizzup.org, martin_rysavy@centrum.cz,
kernel list <linux-kernel@vger.kernel.org>,
Sebastian Reichel <sre@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 13:29:10 +0100 [thread overview]
Message-ID: <20200102122910.zcodrxmkslrpcd2m@ucw.cz> (raw)
In-Reply-To: <CAK8P3a2Ya+GZRRA_THZBVDq7SWO8UYoUPwW5fEyorCVjPnd1qA@mail.gmail.com>
Hi!
> > > > I managed to get partial serial dump. This should be 5.5-rc3: And then
> > > > a bit better serial dump (below). But it is silent for few seconds,
> > > > and then it restarts...
> > >
> > > If spi or regulators have problems, nothing will really work..
> >
> > arm-soc merge seems to be responsible:
> >
> > bad 38206c24ab09b4f4c2a57de5c1af0bb2e69cf5b6 Merge tag 'armsoc-soc' of
> > good d9e48dc2a71a836f17d1febbedb31470f957edb4 Merge tag
> >
> Among these, the most likely candidates would be
>
> 0b491904f053 ARM: OMAP2+: Add missing put_device() call in omapdss_init_of()
> 06bd77f965ae ARM: OMAP2+: make omap44xx_sha0_hwmod and
> omap44xx_l3_main_2__des static
> c145649bf262 ARM: OMAP2+: Configure voltage controller for cpcap to low-speed
> 71065d3fe82d ARM: OMAP2+: Configure voltage controller for retention
> 21a18129edd7 ARM: OMAP2+: Simplify code for clkdm_clock_enable and disable
> 4873843718f9 ARM: OMAP2+: Initialize voltage controller for omap4
> caf8c87d7ff2 ARM: OMAP2+: Allow core oswr for omap4
> 623429d5b901 ARM: OMAP2+: Allow per oswr for omap4
> d44fa156dcb2 ARM: OMAP2+: Configure voltage controller for cpcap
> 32236a84906f ARM: OMAP2+: Update 4430 voltage controller operating points
> ccd369455a23 ARM: OMAP2+: Remove bogus warnings for machines without twl PMIC
> dfc065aa8963 ARM: OMAP2+: Drop bogus wkup domain oswr setting
> 5395b5557acb ARM: OMAP2+: Remove unused wakeup_cpu
>
> Maybe try reverting these on top of the latest version to narrow it
> down further?
Thanks for your support. I'm continuing the bisect, should have result
soon. (Unless all the "good"s in a row are sign of something strange.)
# bad: [38206c24ab09b4f4c2a57de5c1af0bb2e69cf5b6] Merge tag 'armsoc-soc'
# of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
git bisect bad 38206c24ab09b4f4c2a57de5c1af0bb2e69cf5b6
# good: [d9e48dc2a71a836f17d1febbedb31470f957edb4] Merge tag
# 'pwm/for-5.5-rc1' of
# git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm
git bisect good d9e48dc2a71a836f17d1febbedb31470f957edb4
# good: [cd4744645959ebfc97e4b0c676006d2d76d34f25] Merge tag
# 'omap-for-v5.5/soc-signed' of
# git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into
# arm/soc
git bisect good cd4744645959ebfc97e4b0c676006d2d76d34f25
# good: [3166c3dd4c87d118cbf66f827f4b41765a0b1ba6] Merge tag
# 'samsung-soc-5.5' of
# https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into
# arm/soc
git bisect good 3166c3dd4c87d118cbf66f827f4b41765a0b1ba6
# good: [0f3dac611060058524c68dadcc0ddaf923c84d1c] Merge tag
# 'imx-soc-5.5' of
# git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into
# arm/soc
git bisect good 0f3dac611060058524c68dadcc0ddaf923c84d1c
Best regards,
next prev parent reply other threads:[~2020-01-02 12:29 UTC|newest]
Thread overview: 16+ 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
2020-01-02 11:00 ` Droid 4 regression in 5.5-rc1, armsoc-soc tree Pavel Machek
2020-01-02 11:49 ` Arnd Bergmann
2020-01-02 12:29 ` Pavel Machek [this message]
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
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=20200102122910.zcodrxmkslrpcd2m@ucw.cz \
--to=pavel@ucw.cz \
--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=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox