From: Michael Walle <michael@walle.cc>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Guillaume Tucker <guillaume.tucker@collabora.com>
Subject: Regression for duplicate (?) console parameters on next-20220630
Date: Thu, 30 Jun 2022 15:11:58 +0200 [thread overview]
Message-ID: <8460ecf2a963c85793cf325e16725044@walle.cc> (raw)
Hi,
I'm not sure it these are the correct recipients, feel free to CC
others.
Since next-20220630 (or maybe also since next-20220629) I'm getting the
[ 3.707900] WARNING: CPU: 0 PID: 38 at fs/kernfs/dir.c:531
kernfs_put.part.0+0x1a0/0x1d4
[ 3.716313] kernfs_put: console/active: released with incorrect
active_ref 0
on both arm and arm64 boards. See for example:
https://linux.kernelci.org/test/case/id/62bd840b330c4851eaa39c16/
I have the console set in the device tree as well as on the commandline.
Up until recently that wasn't a problem and I guess that should be a
valid
configuration. That being said, the warn() will go away if I remove the
console= parameter on the commandline.
I haven't had time to do a bisect yet. That will probably my next step;
or maybe kernelci will already do that for me, Guillaume? Unless someone
has some more insights/ideas.
-michael
next reply other threads:[~2022-06-30 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 13:11 Michael Walle [this message]
2022-06-30 19:35 ` Regression for duplicate (?) console parameters on next-20220630 Nathan Chancellor
2022-06-30 21:18 ` Michael Walle
2022-07-01 4:42 ` Imran Khan
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=8460ecf2a963c85793cf325e16725044@walle.cc \
--to=michael@walle.cc \
--cc=gregkh@linuxfoundation.org \
--cc=guillaume.tucker@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox