From: Nishanth Menon <nm@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: regressions in linux-next?
Date: Tue, 22 Apr 2014 10:13:10 -0500 [thread overview]
Message-ID: <53568706.1050204@ti.com> (raw)
In-Reply-To: <53566C20.6000208@ti.com>
Logs with with DEBUG_LL and early printk below:
Thread: http://marc.info/?t=139817273800014&r=1&w=2
On 04/22/2014 08:18 AM, Nishanth Menon wrote:
> next-20140422-omap2plus_defconfig
> 1: am335x-sk: Boot FAIL: http://slexy.org/raw/s2gh6XsLve
> 2: am3517-evm: Boot PASS: http://slexy.org/raw/s2MTkdzPnb
> 3: am37x-evm: Boot PASS: http://slexy.org/raw/s2SJwrVat8
> 4: am43xx-epos: Boot PASS: http://slexy.org/raw/s2184jfKlq
> 5: am43xx-gpevm: Boot FAIL: http://slexy.org/raw/s21qIYDHqa
>> known
> 6: BeagleBoard-XM: Boot FAIL: http://slexy.org/raw/s21EyANlGX
> 7: beagleboard-vanilla: Boot FAIL: http://slexy.org/raw/s20lc3icwS
> 8: beaglebone-black: Boot PASS: http://slexy.org/raw/s2ykosQg6C
> 9: beaglebone: Boot PASS: http://slexy.org/raw/s2DN9gqlmo
> 10: craneboard: Boot FAIL: http://slexy.org/raw/s21bP0auhl
> 11: DRA7xx-EVM: Boot FAIL: http://slexy.org/raw/s2rBG0C1x6
looks like my fdt_high was 0xFFFFFFFF and fdt was at 0x80f80000 :( so
got stomped all over...
Time for me to verify every platform again.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-04-22 15:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:18 regressions in linux-next? Nishanth Menon
2014-04-22 13:29 ` Peter Ujfalusi
2014-04-22 15:52 ` Javier Martinez Canillas
2014-04-22 19:37 ` Ezequiel Garcia
2014-04-22 22:32 ` Javier Martinez Canillas
2014-04-22 22:00 ` Linus Walleij
2014-04-22 23:03 ` Javier Martinez Canillas
2014-04-22 23:47 ` Tony Lindgren
2014-04-24 15:16 ` Kevin Hilman
2014-04-24 15:25 ` Nishanth Menon
2014-04-24 15:37 ` Javier Martinez Canillas
2014-04-24 15:42 ` Tony Lindgren
2014-04-24 16:33 ` Javier Martinez Canillas
2014-04-24 16:47 ` Tony Lindgren
2014-04-24 15:40 ` Tony Lindgren
2014-04-24 15:46 ` Nishanth Menon
2014-04-24 16:17 ` Tony Lindgren
2014-04-24 17:08 ` Nishanth Menon
2014-04-24 19:59 ` Aaro Koskinen
2014-04-24 19:22 ` Aaro Koskinen
2014-04-28 22:04 ` Paul Walmsley
2014-04-22 15:13 ` Nishanth Menon [this message]
2014-04-22 21:57 ` Nishanth Menon
2014-04-22 22:45 ` Javier Martinez Canillas
2014-04-22 22:52 ` Nishanth Menon
2014-04-22 23:08 ` Javier Martinez Canillas
2014-04-23 1:30 ` Nishanth Menon
2014-04-23 7:24 ` Javier Martinez Canillas
2014-04-23 10:59 ` Peter Ujfalusi
2014-04-23 13:01 ` Linus Walleij
2014-04-23 13:29 ` Nishanth Menon
2014-04-23 14:38 ` Linus Walleij
2014-04-23 14:50 ` Javier Martinez Canillas
2014-04-23 14:52 ` Linus Walleij
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=53568706.1050204@ti.com \
--to=nm@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.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