From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: BUG: scheduling while atomic: swapper/1/0/0xffff0000
Date: Thu, 23 Jun 2022 14:27:57 +0100 [thread overview]
Message-ID: <YrRqXcNPNfykaCv3@shell.armlinux.org.uk> (raw)
In-Reply-To: <mvmwnd7o7yr.fsf@suse.de>
On Thu, Jun 23, 2022 at 02:55:08PM +0200, Andreas Schwab wrote:
> I'm getting a lot of these messages on a panda board:
>
> [ 572.187805] BUG: scheduling while atomic: swapper/1/0/0xffff0000
This looks like a preempt count underflow of hard interrupts, which
means the backtrace won't be useful in tracking it down, sadly.
If it's a regression, bisecting might be the easiest way to find the
offending commit.
--
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
prev parent reply other threads:[~2022-06-23 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 12:55 BUG: scheduling while atomic: swapper/1/0/0xffff0000 Andreas Schwab
2022-06-23 13:27 ` Russell King (Oracle) [this message]
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=YrRqXcNPNfykaCv3@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=schwab@suse.de \
/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.