All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: bof@bof.de
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: stable 5.4.135 REGRESSION / once-a-day WARNING: at kthread_is_per_cpu+0x1c/0x20
Date: Wed, 28 Jul 2021 19:45:46 +0200	[thread overview]
Message-ID: <YQGXyiMb1IntqacG@kroah.com> (raw)
In-Reply-To: <61018d93.xsvXcO161PFLQFCX%bof@bof.de>

On Wed, Jul 28, 2021 at 07:02:11PM +0200, bof@bof.de wrote:
> Hi,
> 
> first regression report in a long while... hope I'm doing this right.
> 
> I run self-build, from time to time, mainline kernels, in production, both on HP DL hosts + inside kvm VMs on these. I usually stick to a certain
> long term stable line for a year or three. As such, for a bit longer already, I'm running 5.4, starting somewhere at 5.4.4x. At the moment, I started
> to roll out 5.4.135 on a few of the hosts, and encounter a rare "WARNING: CPU ... PID ... at kthread_is_per_cpu+0x1c/0x20" splat (see full dmesg below)
> 
> Previous kernel I was running there, never seeing that, was 5.4.114
> 
> Searching a bit, turns up this 5.4.118 commit / backport:
> 	https://lore.kernel.org/stable/162074016514831@kroah.com/
> 	https://lore.kernel.org/lkml/20210407220628.3798191-2-valentin.schneider@arm.com/
> pointing to exactly the place shown in the dmesg trace.

Can you narrow this down to a specific commit using 'git bisect'?

thanks,

greg k-h

  reply	other threads:[~2021-07-28 17:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 17:02 stable 5.4.135 REGRESSION / once-a-day WARNING: at kthread_is_per_cpu+0x1c/0x20 bof
2021-07-28 17:45 ` Greg KH [this message]
2021-07-28 17:51   ` Patrick Schaaf
2021-08-31  4:46   ` Patrick Schaaf
2021-08-31  4:46     ` Patrick Schaaf
2021-08-31  7:00     ` Peter Zijlstra
2021-08-31 14:57       ` Patrick Schaaf
2021-07-28 17:40 bof

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=YQGXyiMb1IntqacG@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bof@bof.de \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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.