From: Jon Hunter <jonathanh@nvidia.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [BISECTED] v4.3-rc5: OMAP1 boot hang
Date: Fri, 13 Nov 2015 09:21:08 +0000 [thread overview]
Message-ID: <5645AB84.2070004@nvidia.com> (raw)
In-Reply-To: <20151113005722.GQ32536@n2100.arm.linux.org.uk>
On 13/11/15 00:57, Russell King - ARM Linux wrote:
> On Wed, Nov 11, 2015 at 11:44:44PM +0200, Aaro Koskinen wrote:
>> Hi,
>>
>> Any suggestions how to debug this further? This happens also with v4.3
>> final. Is the CPU_SW_DOMAIN_PAN supposed to work with this CPU?
>>
>> I tried to disable various drivers (e.g. NAND, USB) and it still
>> hangs... And it seems always at the same printk time stamp (roughly at
>> 25 seconds).
>
> No idea what so ever, and I have zero knowledge of this ARM925 thing -
> never had one, and never seen any specs on it. The weird thing is
> that it's not producing any oops dump - I guess the kernel is totally
> dead and unresponsive. I'd ask if you have a heartbeat LED, but I'd
> guess the answer will be that the hardware is too limited.
Both the 1510 and 5910 had the ARM925T CPU. Probably the best source of
info is the 5910 documentation [0], specifically the MPU subsystem
document [1]. Hope this helps.
Jon
[0] http://www.ti.com/product/OMAP5910/technicaldocuments
[1] http://www.ti.com/lit/pdf/spru671
prev parent reply other threads:[~2015-11-13 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 7:30 [BISECTED] v4.3-rc5: OMAP1 boot hang Aaro Koskinen
2015-11-11 21:44 ` Aaro Koskinen
2015-11-13 0:57 ` Russell King - ARM Linux
2015-11-13 9:21 ` Jon Hunter [this message]
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=5645AB84.2070004@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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).