linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: mpartap@gmx.net, merlijn@wizzup.org, martin_rysavy@centrum.cz,
	kernel list <linux-kernel@vger.kernel.org>,
	sre@kernel.org, nekit1000@gmail.com, linux-omap@vger.kernel.org,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Droid 4 on 5.5-rc3
Date: Wed, 1 Jan 2020 23:02:37 +0100	[thread overview]
Message-ID: <20200101220237.GA13059@amd> (raw)
In-Reply-To: <20191230173507.GM35479@atomide.com>


[-- Attachment #1.1: Type: text/plain, Size: 1066 bytes --]

On Mon 2019-12-30 09:35:07, Tony Lindgren wrote:
> * Pavel Machek <pavel@ucw.cz> [191228 19:37]:
> > Hi!
> > 
> > > 5.4-based kernel works ok on my droid 4.
> > > 
> > > 5.5-rc3 based kernel has problems; it reboots when I try to kexec it.
> > > 
> > > Vanilla 5.5-rc3 reboots, too.
> > > 
> > > If you have any ideas, let me know.
> > 
> > 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..

Hmmm. I'm too lazy to think. 5.4 is okay, 5.5-rc3 is broken... Let me
try 5.5-rc1 and then bisect. Unfortunately getting serial output is
tricky, too, since I need the USB for kexec...

If you know that there's known bug somewhere in 5.5-rc1, tell
me. Bisect can only locate one bug....

Best regards,
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-01-01 22:03 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 [this message]
     [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
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=20200101220237.GA13059@amd \
    --to=pavel@ucw.cz \
    --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=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;
as well as URLs for NNTP newsgroup(s).