From: Pavel Machek <pavel@ucw.cz>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Nishanth Menon <nm@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
sre@debian.org, sre@ring0.de, aaro.koskinen@iki.fi,
tony@atomide.com, ivo.g.dimitrov.75@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: v3.19-rc1 regression(?) on N900
Date: Thu, 25 Dec 2014 10:11:21 +0100 [thread overview]
Message-ID: <20141225091121.GA20355@amd> (raw)
In-Reply-To: <201412250932.40403@pali>
On Thu 2014-12-25 09:32:40, Pali Rohár wrote:
> On Wednesday 24 December 2014 23:57:38 Nishanth Menon wrote:
> > 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/omap2plu
> > s_defconfig/n900.txt
> >
> > v3.19-rc1: hung
> > https://github.com/nmenon/kernel-test-logs/blob/v3.19-rc1/omap
> > 2plus_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
Early hang, independend on config. That's "dtb too big". Delete
something, and it should work again.
Plus you'll note video regression.
# > I test-merged 3315764efceaccfb02c7d4c99ef8eed6716cd861, and boom,
# > video is gone.
#
# I reverted
#
# > 4b4123f0c7b02f7cf1a3189f967f079197578c3a..9051909e451a0368c95ccf74562adb53fd2719f8
# in 3.19, and voila, video is back.
> CCing other people.
>
> I see same problem in qemu with 3.19-rc1 kernel when doing DT
> boot. In qemu I'm using direct booting from OneNAND (X-Loader -->
> NOLO --> kernel) without U-Boot. After NOLO load & boot kernel I
> do not see any other output from serial console. Also on qemu
> screen there is no new output (just NOKIA logo from bootloader).
>
> I do not have this problem when doing legacy/board code boot with
> 3.19-rc1 kernel, so this problem is related to DT.
>
> Kernel 3.18-rc1 worked fine for both DT and legacy boot.
>
> Can somebody look what broke DT booting?
It was too big dtb, at least for me.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.19-rc1 regression(?) on N900
Date: Thu, 25 Dec 2014 10:11:21 +0100 [thread overview]
Message-ID: <20141225091121.GA20355@amd> (raw)
In-Reply-To: <201412250932.40403@pali>
On Thu 2014-12-25 09:32:40, Pali Roh?r wrote:
> On Wednesday 24 December 2014 23:57:38 Nishanth Menon wrote:
> > 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/omap2plu
> > s_defconfig/n900.txt
> >
> > v3.19-rc1: hung
> > https://github.com/nmenon/kernel-test-logs/blob/v3.19-rc1/omap
> > 2plus_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
Early hang, independend on config. That's "dtb too big". Delete
something, and it should work again.
Plus you'll note video regression.
# > I test-merged 3315764efceaccfb02c7d4c99ef8eed6716cd861, and boom,
# > video is gone.
#
# I reverted
#
# > 4b4123f0c7b02f7cf1a3189f967f079197578c3a..9051909e451a0368c95ccf74562adb53fd2719f8
# in 3.19, and voila, video is back.
> CCing other people.
>
> I see same problem in qemu with 3.19-rc1 kernel when doing DT
> boot. In qemu I'm using direct booting from OneNAND (X-Loader -->
> NOLO --> kernel) without U-Boot. After NOLO load & boot kernel I
> do not see any other output from serial console. Also on qemu
> screen there is no new output (just NOKIA logo from bootloader).
>
> I do not have this problem when doing legacy/board code boot with
> 3.19-rc1 kernel, so this problem is related to DT.
>
> Kernel 3.18-rc1 worked fine for both DT and legacy boot.
>
> Can somebody look what broke DT booting?
It was too big dtb, at least for me.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Nishanth Menon <nm@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
sre@debian.org, sre@ring0.de, aaro.koskinen@iki.fi,
tony@atomide.com, ivo.g.dimitrov.75@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: v3.19-rc1 regression(?) on N900
Date: Thu, 25 Dec 2014 10:11:21 +0100 [thread overview]
Message-ID: <20141225091121.GA20355@amd> (raw)
In-Reply-To: <201412250932.40403@pali>
On Thu 2014-12-25 09:32:40, Pali Rohár wrote:
> On Wednesday 24 December 2014 23:57:38 Nishanth Menon wrote:
> > 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/omap2plu
> > s_defconfig/n900.txt
> >
> > v3.19-rc1: hung
> > https://github.com/nmenon/kernel-test-logs/blob/v3.19-rc1/omap
> > 2plus_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
Early hang, independend on config. That's "dtb too big". Delete
something, and it should work again.
Plus you'll note video regression.
# > I test-merged 3315764efceaccfb02c7d4c99ef8eed6716cd861, and boom,
# > video is gone.
#
# I reverted
#
# > 4b4123f0c7b02f7cf1a3189f967f079197578c3a..9051909e451a0368c95ccf74562adb53fd2719f8
# in 3.19, and voila, video is back.
> CCing other people.
>
> I see same problem in qemu with 3.19-rc1 kernel when doing DT
> boot. In qemu I'm using direct booting from OneNAND (X-Loader -->
> NOLO --> kernel) without U-Boot. After NOLO load & boot kernel I
> do not see any other output from serial console. Also on qemu
> screen there is no new output (just NOKIA logo from bootloader).
>
> I do not have this problem when doing legacy/board code boot with
> 3.19-rc1 kernel, so this problem is related to DT.
>
> Kernel 3.18-rc1 worked fine for both DT and legacy boot.
>
> Can somebody look what broke DT booting?
It was too big dtb, at least for me.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-12-25 9:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 22:57 v3.19-rc1 regression(?) on N900 Nishanth Menon
2014-12-25 8:32 ` Pali Rohár
2014-12-25 8:32 ` Pali Rohár
2014-12-25 9:11 ` Pavel Machek [this message]
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=20141225091121.GA20355@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.com \
--cc=sre@debian.org \
--cc=sre@ring0.de \
--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 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.