From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
Andreas Kemnade <andreas@kemnade.info>
Subject: Re: Regression with e428e250fde6 on BeagleBoard Rev C2
Date: Sat, 25 Sep 2021 17:55:22 +0300 [thread overview]
Message-ID: <18a27933-e412-c1ed-a744-62cfbcd6a81b@bitmer.com> (raw)
In-Reply-To: <YU14FjzAMU0uUubW@atomide.com>
On 9/24/21 10:02 AM, Tony Lindgren wrote:
> * Jarkko Nikula <jarkko.nikula@bitmer.com> [210923 18:04]:
>> On 9/23/21 8:41 AM, Tony Lindgren wrote:
>>> * Jarkko Nikula <jarkko.nikula@bitmer.com> [210922 17:22]:
>>>> Better luck with this one but looks like idling cause "undefined
>>>> instruction" crash. Cache/memory etc corruption perhaps? Serial console
>>>> log attached.
>>>
>>> Hmm. If you comment out the twl power node, does the omap3-beagle-ab4.dtb
>>> boot normally for you? It should behave the same as current mainline then
>>> with the omap3isp issue.
>>>
>> Commenting the twl_power node out or removing the twl section leads to
>> immediately rebooting kernel:
>
> Below is an updated patch to move the timer quirks to omap3-beagle-ab4.dtb
> with no twl changes.
>
Sigh, I found the reason for immediately rebooting kernel from bash history:
"rm arch/arm/boot/zImage" followed by "cat
arch/arm/boot/dts/omap3-beagle-ab4.dtb >>arch/arm/boot/zImage; ma
LOADADDR=0x80008000 uImage", i.e. forgot to build the zImage between.
(alias ma='nice make -j `getconf _NPROCESSORS_ONLN` ARCH=arm
CROSS_COMPILE="ccache arm-linux-gnueabihf-"')
So yes, with your latest patch omap3-beagle-ab4.dtb behaves as unpatched
omap3-beagle.dtb (boots but timer issues when omap3_isp not loaded).
Jarkko
next prev parent reply other threads:[~2021-09-25 14:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 17:41 Regression with e428e250fde6 on BeagleBoard Rev C2 Jarkko Nikula
2021-09-20 13:34 ` Tony Lindgren
2021-09-20 14:52 ` Andreas Kemnade
2021-09-21 7:00 ` Tony Lindgren
2021-09-21 16:25 ` Andreas Kemnade
2021-09-20 16:35 ` Jarkko Nikula
2021-09-21 7:00 ` Tony Lindgren
2021-09-21 17:49 ` Jarkko Nikula
2021-09-22 10:07 ` Tony Lindgren
2021-09-22 17:21 ` Jarkko Nikula
2021-09-23 5:41 ` Tony Lindgren
2021-09-23 18:03 ` Jarkko Nikula
2021-09-24 7:02 ` Tony Lindgren
2021-09-25 14:55 ` Jarkko Nikula [this message]
2021-09-30 7:04 ` Tony Lindgren
2021-10-20 17:52 ` Jarkko Nikula
2021-10-21 13:58 ` Tony Lindgren
2021-10-21 18:10 ` Jarkko Nikula
2021-10-24 6:41 ` Tony Lindgren
2021-09-20 18:19 ` H. Nikolaus Schaller
2021-09-21 7:02 ` 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=18a27933-e412-c1ed-a744-62cfbcd6a81b@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=andreas@kemnade.info \
--cc=hns@goldelico.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--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