From: pali.rohar@gmail.com (Pali Rohár)
To: linux-arm-kernel@lists.infradead.org
Subject: n900 in 4.2-rc0: repeating oopses
Date: Mon, 29 Jun 2015 12:45:53 +0200 [thread overview]
Message-ID: <20150629104553.GD16230@pali> (raw)
In-Reply-To: <20150629091146.GA5103@amd>
Hi!
On Monday 29 June 2015 11:11:46 Pavel Machek wrote:
> Hi!
>
> Just tried booting 4.2-rc0 on n900 (commit
> 4a10a91756ef381bced7b88cfb9232f660b92d93) and it is broken. Previous
> -rc0 version worked. This time, there's some output on console, but
> too fast for me to read.
>
What happen after errors are reported? Maybe you can enable R&D mode and
disable HW watchdogs to prevent device reboots...
> It seems oopses happen before mounting root. If you have serial
> console, they should be easy to see.
>
> I tried booting same kernel in qemu, but it seems to work ok there.
>
Hm... Maybe problem with HS code?
By chance, can you try to disable (omap) sham node in n900 DT file?
(same way like omap aes is disabled)
> Any ideas? Thanks,
> Pavel
--
Pali Roh?r
pali.rohar at gmail.com
next prev parent reply other threads:[~2015-06-29 10:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 9:32 n900 in 4.1-rc0 Pavel Machek
2015-04-16 9:37 ` Marc Zyngier
2015-04-16 16:35 ` Tony Lindgren
2015-04-26 10:15 ` Pavel Machek
2015-04-16 16:45 ` Tyler Baker
2015-04-26 10:20 ` Pavel Machek
2015-04-27 18:58 ` Tyler Baker
[not found] ` <20150629091146.GA5103@amd>
2015-06-29 10:45 ` Pali Rohár [this message]
2015-06-30 9:24 ` n900 in 4.2-rc0: repeating oopses Pavel Machek
2015-06-30 9:53 ` Pali Rohár
2015-07-01 6:59 ` Tony Lindgren
2015-07-01 7:22 ` Pali Rohár
2015-07-01 9:59 ` Pavel Machek
2015-07-01 10:34 ` Tony Lindgren
2015-07-01 13:09 ` Pavel Machek
2015-07-02 6:16 ` Tony Lindgren
2015-07-26 22:31 ` Pavel Machek
2015-07-27 7:12 ` Pali Rohár
2015-07-02 20:25 ` Pavel Machek
2015-07-26 9:26 ` Pavel Machek
2015-07-28 6:01 ` Tony Lindgren
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=20150629104553.GD16230@pali \
--to=pali.rohar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).