All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kees Cook <keescook@chromium.org>,
	Nicolas Pitre <nico@fluxnic.net>,
	Russell King <rmk+kernel@armlinux.org.uk>
Cc: Merlijn Wajer <merlijn@wizzup.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
	"Arthur D." <spinal.by@gmail.com>,
	"H. Nikolaus Schaller" <hns@goldelico.com>,
	linux-arm-kernel@lists.infradead.org,
	Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: Nokia N900 on 5.4 and 5.5
Date: Fri, 7 Feb 2020 08:36:23 -0800	[thread overview]
Message-ID: <20200207163623.GA64767@atomide.com> (raw)
In-Reply-To: <185CD173-C13C-4D56-B3DE-9A8D7784963C@goldelico.com>

Hi,

* H. Nikolaus Schaller <hns@goldelico.com> [200207 15:52]:
> 
> > Am 07.02.2020 um 15:54 schrieb Merlijn Wajer <merlijn@wizzup.org>:
> > 
> > Hi,
> > 
> > I've tried to build 5.4.18 and 5.5.2 for the Nokia N900, using
> > omap2plus_defconfig. Using appended DTB, like so:
> > 
> > $ cat arch/arm/boot/zImage arch/arm/boot/dts/omap3-n900.dtb > zImage.dtb
> > $ mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -n
> > zImage -d zImage.dtb uImage
> > 
> > But they both fail to boot for me - the device resets almost instantly:
> > 
> >> data abort
> >> 
> >>    MAYBE you should read doc/README.arm-unaligned-accesses
> >> 
> >> pc : [<8000c878>]          lr : [<80008160>]
> >> sp : 803c46c8  ip : 003a1870     fp : 003a1848
> >> r10: 803ba890  r9 : 00caa42c     r8 : 80000100
> >> r7 : 000007a3  r6 : 803a9878     r5 : 80000100  r4 : 80008000
> >> r3 : 00004e6c  r2 : 00019fa8     r1 : 803a9878  r0 : 00000000
> >> Flags: nZcv  IRQs off  FIQs on  Mode SVC_32
> >> Resetting CPU ...
> >> 
> >> resetting ...
> > 
> > Full log below. I tried the same with "-Os" instead of "-O2" ; to no avail.
> > 
> > Any clue what could be up?
> 
> I can only tell that I have successfully running 5.5.2 on GTA04A5 (dm3730
> but with our own defconfig). This may reduce the number of problem areas
> a little.

Looks like there's a regression in general for appended dtb booting that
was caused by commit 9f671e58159a ("security: Create "kernel hardening"
config area"). With that change we now get STACKPROTECTOR_PER_TASK
selected by default with Kconfig.

Merlijn, care to try to disable STACKPROTECTOR_PER_TASK in your
.config to see if that helps?

Not sure why appended dtb boot now breaks though.. Could be just the
zImage uncompressing over dtb again? Any ideas?

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Kees Cook <keescook@chromium.org>,
	Nicolas Pitre <nico@fluxnic.net>,
	Russell King <rmk+kernel@armlinux.org.uk>
Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	"H. Nikolaus Schaller" <hns@goldelico.com>,
	Merlijn Wajer <merlijn@wizzup.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Arthur D." <spinal.by@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Nokia N900 on 5.4 and 5.5
Date: Fri, 7 Feb 2020 08:36:23 -0800	[thread overview]
Message-ID: <20200207163623.GA64767@atomide.com> (raw)
In-Reply-To: <185CD173-C13C-4D56-B3DE-9A8D7784963C@goldelico.com>

Hi,

* H. Nikolaus Schaller <hns@goldelico.com> [200207 15:52]:
> 
> > Am 07.02.2020 um 15:54 schrieb Merlijn Wajer <merlijn@wizzup.org>:
> > 
> > Hi,
> > 
> > I've tried to build 5.4.18 and 5.5.2 for the Nokia N900, using
> > omap2plus_defconfig. Using appended DTB, like so:
> > 
> > $ cat arch/arm/boot/zImage arch/arm/boot/dts/omap3-n900.dtb > zImage.dtb
> > $ mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -n
> > zImage -d zImage.dtb uImage
> > 
> > But they both fail to boot for me - the device resets almost instantly:
> > 
> >> data abort
> >> 
> >>    MAYBE you should read doc/README.arm-unaligned-accesses
> >> 
> >> pc : [<8000c878>]          lr : [<80008160>]
> >> sp : 803c46c8  ip : 003a1870     fp : 003a1848
> >> r10: 803ba890  r9 : 00caa42c     r8 : 80000100
> >> r7 : 000007a3  r6 : 803a9878     r5 : 80000100  r4 : 80008000
> >> r3 : 00004e6c  r2 : 00019fa8     r1 : 803a9878  r0 : 00000000
> >> Flags: nZcv  IRQs off  FIQs on  Mode SVC_32
> >> Resetting CPU ...
> >> 
> >> resetting ...
> > 
> > Full log below. I tried the same with "-Os" instead of "-O2" ; to no avail.
> > 
> > Any clue what could be up?
> 
> I can only tell that I have successfully running 5.5.2 on GTA04A5 (dm3730
> but with our own defconfig). This may reduce the number of problem areas
> a little.

Looks like there's a regression in general for appended dtb booting that
was caused by commit 9f671e58159a ("security: Create "kernel hardening"
config area"). With that change we now get STACKPROTECTOR_PER_TASK
selected by default with Kconfig.

Merlijn, care to try to disable STACKPROTECTOR_PER_TASK in your
.config to see if that helps?

Not sure why appended dtb boot now breaks though.. Could be just the
zImage uncompressing over dtb again? Any ideas?

Regards,

Tony

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-02-07 16:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 14:54 Nokia N900 on 5.4 and 5.5 Merlijn Wajer
2020-02-07 15:51 ` H. Nikolaus Schaller
2020-02-07 16:36   ` Tony Lindgren [this message]
2020-02-07 16:36     ` Tony Lindgren
2020-02-07 16:48     ` Merlijn Wajer
2020-02-07 16:48       ` Merlijn Wajer
2020-02-07 16:53       ` Tony Lindgren
2020-02-07 16:53         ` Tony Lindgren
2020-02-07 17:01         ` Tony Lindgren
2020-02-07 17:01           ` Tony Lindgren
2020-02-07 20:20           ` Arthur D.
2020-02-07 20:20             ` Arthur D.
2020-02-08  1:49             ` Merlijn Wajer
2020-02-08  1:49               ` Merlijn Wajer
2020-02-13 21:33               ` Ard Biesheuvel
2020-02-13 21:33                 ` Ard Biesheuvel
2020-02-13 21:44                 ` Tony Lindgren
2020-02-13 21:44                   ` 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=20200207163623.GA64767@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=hns@goldelico.com \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=merlijn@wizzup.org \
    --cc=nico@fluxnic.net \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=spinal.by@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.