From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: suspend-related lockdep warning
Date: Thu, 06 Dec 2007 11:31:28 +0100 [thread overview]
Message-ID: <1196937088.6788.56.camel@twins> (raw)
In-Reply-To: <200712060121.24837.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]
On Thu, 2007-12-06 at 01:21 +0100, Rafael J. Wysocki wrote:
> On Tuesday, 4 of December 2007, Andrew Morton wrote:
> > [ 34.455096] ipw2200: Failed to send WEP_KEY: Command timed out.
> > [ 34.911876] Syncing filesystems ... done.
> > [ 34.934526] Freezing user space processes ... WARNING: at kernel/lockdep.c:2662 check_flags()
> > [ 34.934917] Pid: 1922, comm: dbus-daemon Not tainted 2.6.24-rc3-mm3 #2
> > [ 34.935036] [<c0104853>] show_trace_log_lvl+0x12/0x25
> > [ 34.935142] [<c010506c>] show_trace+0xd/0x10
> > [ 34.935231] [<c0105850>] dump_stack+0x55/0x5d
> > [ 34.935322] [<c0136125>] check_flags+0x7f/0x11a
> > [ 34.935417] [<c0139210>] lock_acquire+0x3a/0x86
> > [ 34.935511] [<c0318faf>] _spin_lock+0x1c/0x49
> > [ 34.935603] [<c0140fc7>] refrigerator+0x13/0xc8
> > [ 34.935697] [<c01270ac>] get_signal_to_deliver+0x34/0x2e8
> > [ 34.935807] [<c0102edc>] do_notify_resume+0x8c/0x6fe
> > [ 34.935907] [<c0103a2c>] work_notifysig+0x13/0x1b
> > [ 34.936004] =======================
> > [ 34.936072] irq event stamp: 253
> > [ 34.936133] hardirqs last enabled at (253): [<c0103a8d>] syscall_exit_work+0x11/0x26
> > [ 34.936294] hardirqs last disabled at (252): [<c0103956>] syscall_exit+0x14/0x25
> > [ 34.936446] softirqs last enabled at (0): [<c011baf9>] copy_process+0x300/0x1246
> > [ 34.936599] softirqs last disabled at (0): [<00000000>] 0x0
> > [ 34.954308] (elapsed 0.01 seconds) done.
> > [ 34.954389] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
>
> Hmm, do I understand correctly that lockdep expects us to disable interrupts
> before acquiring the task lock in refrigerator()? That would be strange.
>
> Ingo, can you have a look at this, please?
No its complaining that the IRQ state changed without anybody telling it
about it. Usually an unannotated cli/sti.
The particular line it warns, (lockdep.c:2662), suggests...
/me grabs a copy of 24-rc3-mm2
... that hardirqs are disabled, but irq tracking thinks they are still
enabled. So that would be an unannotated cli.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-06 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 10:43 suspend-related lockdep warning Andrew Morton
2007-11-28 22:06 ` Rafael J. Wysocki
2007-12-01 8:33 ` Pavel Machek
2007-12-02 20:33 ` Rafael J. Wysocki
2007-12-03 6:26 ` Andrew Morton
2007-12-03 22:34 ` Rafael J. Wysocki
2007-12-04 1:45 ` Andrew Morton
2007-12-06 0:21 ` Rafael J. Wysocki
2007-12-06 10:31 ` Peter Zijlstra [this message]
2007-12-06 12:01 ` Andrew Morton
2007-12-06 12:04 ` Ingo Molnar
2007-12-06 12:04 ` Peter Zijlstra
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=1196937088.6788.56.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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