linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: John Ogness <john.ogness@linutronix.de>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-serial@vger.kernel.org
Subject: Re: [rt-devel:linux-6.6.y-rt-rebase] [serial] 7ae7fa6bcb: dmesg.inconsistent{INITIAL_USE}->{IN-NMI}usage
Date: Mon, 2 Oct 2023 12:44:59 +0200	[thread overview]
Message-ID: <20231002104459.-sjvh8h2@linutronix.de> (raw)
In-Reply-To: <202309301045.1475d353-oliver.sang@intel.com>

On 2023-09-30 10:40:09 [+0800], kernel test robot wrote:
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202309301045.1475d353-oliver.sang@intel.com
> [  504.779539][    C1] NMI backtrace for cpu 1
> [  504.779544][    C1] 
> [  504.779546][    C1] ================================
> [  504.779547][    C1] WARNING: inconsistent lock state
> [  504.779549][    C1] 6.6.0-rc3-00047-g7ae7fa6bcb29 #1 Tainted: G        W        N
> [  504.779551][    C1] --------------------------------
> [  504.779552][    C1] inconsistent {INITIAL USE} -> {IN-NMI} usage.
> [  504.779554][    C1] swapper/0/1 [HC1[1]:SC0[0]:HE0:SE1] takes:

I posted already a patch for the NMI usage before this report popped up.

Sebastian

      reply	other threads:[~2023-10-02 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-30  2:40 [rt-devel:linux-6.6.y-rt-rebase] [serial] 7ae7fa6bcb: dmesg.inconsistent{INITIAL_USE}->{IN-NMI}usage kernel test robot
2023-10-02 10:44 ` Sebastian Andrzej Siewior [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=20231002104459.-sjvh8h2@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=john.ogness@linutronix.de \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.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;
as well as URLs for NNTP newsgroup(s).