From: Thomas Gleixner <tglx@linutronix.de>
To: Waiman Long <llong@redhat.com>, Pavel Machek <pavel@ucw.cz>,
Waiman Long <llong@redhat.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, peterz@infradead.org,
will@kernel.org, miriam.rachel.korenblit@intel.com,
linux-wireless@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
John Ogness <jogness@linutronix.de>
Subject: Re: locking problems in iwlwifi? was Re: 6.16-rcX: crashing way too often on thinkpad X220
Date: Fri, 25 Jul 2025 00:21:16 +0200 [thread overview]
Message-ID: <871pq5qlgj.ffs@tglx> (raw)
In-Reply-To: <6c5e70a8-2db2-4fa6-8a42-35033e480293@redhat.com>
On Thu, Jul 24 2025 at 15:22, Waiman Long wrote:
> On 7/24/25 3:07 PM, Pavel Machek wrote:
>>> The lockdep warning just means that console_owner_lock is acquired both in
>>> softirq context and in task context with interrupt enabled. That can leads
>>> to deadlock. So the remedy is to always take console_owner_lock with
>>> interrupt disabled, i.e. with
>>> raw_spin_lock_irqsave/raw_spin_lock_irqrestore.
>> So you suspect problem is in the printk code?
>
> This lockdep problem is likely unrelated to the IRQ flag problem
> reported in the original email as it shouldn't affect the IRQ flag.
Wrong you are ... :)
next prev parent reply other threads:[~2025-07-24 22:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 17:35 6.16-rcX: crashing way too often on thinkpad X220 Pavel Machek
2025-07-23 15:06 ` Pavel Machek
2025-07-23 15:11 ` Dave Hansen
2025-07-23 20:35 ` Pavel Machek
2025-07-23 15:42 ` locking problems in iwlwifi? was " Pavel Machek
2025-07-23 17:13 ` Johannes Berg
2025-07-23 20:37 ` Pavel Machek
2025-07-24 8:50 ` John Ogness
2025-07-23 21:42 ` Pavel Machek
2025-09-15 9:32 ` Pavel Machek
2025-07-23 17:31 ` Thomas Gleixner
2025-07-23 17:32 ` Thomas Gleixner
2025-07-24 17:15 ` Pavel Machek
2025-07-24 17:51 ` Waiman Long
2025-07-24 17:55 ` Waiman Long
2025-07-24 21:24 ` Thomas Gleixner
2025-07-25 0:33 ` Hillf Danton
2025-07-25 15:23 ` Thomas Gleixner
2025-07-25 19:05 ` Pavel Machek
2025-07-24 19:07 ` Pavel Machek
2025-07-24 19:22 ` Waiman Long
2025-07-24 22:21 ` Thomas Gleixner [this message]
2025-07-25 1:56 ` Waiman Long
2025-07-24 19:45 ` John Ogness
2025-07-25 0:16 ` Waiman Long
2025-07-25 13:44 ` Thomas Gleixner
2025-07-25 19:38 ` Waiman Long
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=871pq5qlgj.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=llong@redhat.com \
--cc=mingo@redhat.com \
--cc=miriam.rachel.korenblit@intel.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=will@kernel.org \
--cc=x86@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.