From: Nishanth Menon <nm@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: "Pali Rohár" <pali.rohar@gmail.com>
Subject: v3.19-rc1 regression(?) on N900
Date: Wed, 24 Dec 2014 16:57:38 -0600 [thread overview]
Message-ID: <549B44E2.6080202@ti.com> (raw)
based on automated testing with u-boot as a chained bootloader..
v3.18: boots fine:
https://github.com/nmenon/kernel-test-logs/blob/v3.18/omap2plus_defconfig/n900.txt
v3.19-rc1: hung
https://github.com/nmenon/kernel-test-logs/blob/v3.19-rc1/omap2plus_defconfig/n900.txt
in the interim, my farm had a bit of breakdown around the time of n900
breakdown..
as per my last functional linux-next logs:
https://github.com/nmenon/kernel-test-logs/blob/next-20141204/omap2plus_defconfig/n900.txt
-> hung.
https://github.com/nmenon/kernel-test-logs/blob/next-20141112/omap2plus_defconfig/n900.txt
-> working.
DEBUG_LL, CONFIG_DEBUG_OMAP3UART3=y and early_printk did not yield
information either
Note: I am using the combined uImage+dtb image.[2]
I think this might just be my setup..(i use chained loader ->
NOLO->u-boot->serial download->kernel) but anyways.. Since Pali
thought others might be interested in sharing experience...
[1] http://slexy.org/raw/s2osxhhwbR
[2]
https://github.com/nmenon/linux-2.6-playground/commit/177f5f71b3f21ea484ee4b09a2e0c015de522417
--
Regards,
Nishanth Menon
next reply other threads:[~2014-12-24 22:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 22:57 Nishanth Menon [this message]
2014-12-25 8:32 ` v3.19-rc1 regression(?) on N900 Pali Rohár
2014-12-25 8:32 ` Pali Rohár
2014-12-25 9:11 ` Pavel Machek
2014-12-25 9:11 ` Pavel Machek
2014-12-25 9:11 ` Pavel Machek
2014-12-25 22:21 ` Aaro Koskinen
2014-12-25 22:21 ` Aaro Koskinen
2014-12-29 8:04 ` Tomi Valkeinen
2014-12-29 8:04 ` Tomi Valkeinen
2014-12-29 18:02 ` Aaro Koskinen
2014-12-29 18:02 ` Aaro Koskinen
2014-12-30 17:39 ` Pavel Machek
2014-12-30 17:39 ` Pavel Machek
2014-12-25 10:48 ` Pavel Machek
2014-12-25 10:48 ` Pavel Machek
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=549B44E2.6080202@ti.com \
--to=nm@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.