All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Corentin Labbe <clabbe.montjoie@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
Date: Wed, 9 Mar 2022 10:37:27 +0000	[thread overview]
Message-ID: <YiiDZ7jjG38gqP+Q@shell.armlinux.org.uk> (raw)
In-Reply-To: <CA+G9fYtpy8VgK+ag6OsA9TDrwi5YGU4hu7GM8xwpO7v6LrCD4Q@mail.gmail.com>

On Wed, Mar 09, 2022 at 03:18:12PM +0530, Naresh Kamboju wrote:
> While boting linux next-20220308 on BeagleBoard-X15 and qemu arm the following
> kernel crash reported which is CONFIG_KASAN enabled build [1] & [2].

The unwinder is currently broken in linux-next. Please try reverting
532319b9c418 ("ARM: unwind: disregard unwind info before stack frame is
set up")

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Corentin Labbe <clabbe.montjoie@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck
Date: Wed, 9 Mar 2022 10:37:27 +0000	[thread overview]
Message-ID: <YiiDZ7jjG38gqP+Q@shell.armlinux.org.uk> (raw)
In-Reply-To: <CA+G9fYtpy8VgK+ag6OsA9TDrwi5YGU4hu7GM8xwpO7v6LrCD4Q@mail.gmail.com>

On Wed, Mar 09, 2022 at 03:18:12PM +0530, Naresh Kamboju wrote:
> While boting linux next-20220308 on BeagleBoard-X15 and qemu arm the following
> kernel crash reported which is CONFIG_KASAN enabled build [1] & [2].

The unwinder is currently broken in linux-next. Please try reverting
532319b9c418 ("ARM: unwind: disregard unwind info before stack frame is
set up")

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

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

  reply	other threads:[~2022-03-09 10:37 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  9:48 [next] arm: Internal error: Oops: 5 PC is at __read_once_word_nocheck Naresh Kamboju
2022-03-09  9:48 ` Naresh Kamboju
2022-03-09 10:37 ` Russell King (Oracle) [this message]
2022-03-09 10:37   ` Russell King (Oracle)
2022-03-09 10:46   ` Ard Biesheuvel
2022-03-09 10:46     ` Ard Biesheuvel
2022-03-09 14:07     ` Naresh Kamboju
2022-03-09 14:07       ` Naresh Kamboju
2022-03-09 14:44       ` Naresh Kamboju
2022-03-09 14:44         ` Naresh Kamboju
2022-03-09 14:57         ` Ard Biesheuvel
2022-03-09 14:57           ` Ard Biesheuvel
2022-03-09 15:06           ` Russell King (Oracle)
2022-03-09 15:06             ` Russell King (Oracle)
2022-03-09 15:10             ` Ard Biesheuvel
2022-03-09 15:10               ` Ard Biesheuvel
2022-03-09 16:38             ` Naresh Kamboju
2022-03-09 16:38               ` Naresh Kamboju
2022-03-09 16:47               ` Ard Biesheuvel
2022-03-09 16:47                 ` Ard Biesheuvel
2022-03-09 17:11               ` Russell King (Oracle)
2022-03-09 17:11                 ` Russell King (Oracle)
2022-03-09 17:43                 ` Ard Biesheuvel
2022-03-09 17:43                   ` Ard Biesheuvel
2022-03-09 18:48                   ` Russell King (Oracle)
2022-03-09 18:48                     ` Russell King (Oracle)
2022-03-09 19:14                     ` Ard Biesheuvel
2022-03-09 19:14                       ` Ard Biesheuvel
2022-03-09 19:36                       ` Russell King (Oracle)
2022-03-09 19:36                         ` Russell King (Oracle)
2022-03-09 20:42                         ` Ard Biesheuvel
2022-03-09 20:42                           ` Ard Biesheuvel
2022-03-10 12:35                           ` Russell King (Oracle)
2022-03-10 12:35                             ` Russell King (Oracle)
2022-03-10 13:01                             ` Russell King (Oracle)
2022-03-10 13:01                               ` Russell King (Oracle)
2022-03-10 13:14                               ` Ard Biesheuvel
2022-03-10 13:14                                 ` Ard Biesheuvel
2022-03-10 21:17                                 ` Naresh Kamboju
2022-03-10 21:17                                   ` Naresh Kamboju
2022-03-10 21:25                                   ` Ard Biesheuvel
2022-03-10 21:25                                     ` Ard Biesheuvel
2022-03-10 21:50                                     ` Naresh Kamboju
2022-03-10 21:50                                       ` Naresh Kamboju
2022-03-10 22:06                                       ` Ard Biesheuvel
2022-03-10 22:06                                         ` Ard Biesheuvel
2022-03-10 22:09                                         ` Russell King (Oracle)
2022-03-10 22:09                                           ` Russell King (Oracle)
2022-03-14  9:01                                           ` Naresh Kamboju
2022-03-14  9:01                                             ` Naresh Kamboju
2022-03-14  9:02                                             ` Ard Biesheuvel
2022-03-14  9:02                                               ` Ard Biesheuvel

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=YiiDZ7jjG38gqP+Q@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=clabbe.montjoie@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /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.