From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm@lists.linux-foundation.org,
"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>
Subject: Re: Linux 2.6.22-rc4
Date: Tue, 5 Jun 2007 12:26:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0706051219560.4921@woody.linux-foundation.org> (raw)
In-Reply-To: <4665B169.2030803@googlemail.com>
On Tue, 5 Jun 2007, Michal Piotrowski wrote:
>
> It is too stable for me.
I wish all our testers were you ;)
> this looks harmless
>
> [ 116.733327] PM: suspend-to-disk mode set to 'shutdown'
> [ 116.738849] swsusp: Basic memory bitmaps created
> [ 116.745353] Stopping tasks ... WARNING: at /home/devel/linux-git/kernel/lockdep.c:2414 check_flags()
> [ 116.754921] [<c0404fbf>] show_trace_log_lvl+0x1a/0x2f
> [ 116.754937] [<c0405bd6>] show_trace+0x12/0x14
> [ 116.754947] [<c0405c5d>] dump_stack+0x16/0x18
> [ 116.754957] [<c043c3e5>] check_flags+0x95/0x143
> [ 116.754967] [<c043f158>] lock_acquire+0x29/0x82
> [ 116.754977] [<c06313a7>] _spin_lock+0x35/0x42
> [ 116.754990] [<c044894a>] refrigerator+0x14/0xc6
> [ 116.755002] [<c042d4b3>] get_signal_to_deliver+0x33/0x397
> [ 116.755016] [<c0403597>] do_notify_resume+0x94/0x6ed
> [ 116.755029] [<c0404099>] work_notifysig+0x13/0x1a
> [ 116.755044] =======================
> [ 116.755052] irq event stamp: 69
> [ 116.755060] hardirqs last enabled at (69): [<c04040f9>] syscall_exit_work+0x11/0x26
> [ 116.755084] hardirqs last disabled at (68): [<c0403fdd>] syscall_exit+0x9/0x1a
> [ 116.755109] softirqs last enabled at (0): [<c042150c>] copy_process+0x4dd/0x1286
> [ 116.755139] softirqs last disabled at (0): [<00000000>] 0x0
> [ 116.945776] done.
>
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4/git-dmesg
> http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.22-rc4/git-config
Well, it's harmless in the sense that "yeah, the system still works", but
it does seem to be a real bug. We have hardware interrupts disabled when
we _think_ we should have them on, so our irq tracking is off.
Ingo, do you see what's up? It looks like we got a signal to a process
that just got created, is the setup stuff for "tsk->hardirqs_enabled"
perhaps off a bit?
Linus
next prev parent reply other threads:[~2007-06-05 19:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 3:50 Linus Torvalds
2007-06-05 9:29 ` David Greaves
2007-06-05 16:14 ` Linux 2.6.22-rc4 - sata_promise regression since -rc3 David Greaves
2007-06-05 18:54 ` Linux 2.6.22-rc4 Michal Piotrowski
2007-06-05 19:26 ` Linus Torvalds [this message]
2007-06-05 19:37 ` Ingo Molnar
2007-06-05 19:50 ` Linus Torvalds
2007-06-05 20:16 ` Pavel Machek
2007-06-05 20:19 ` Pavel Machek
2007-06-05 22:01 ` Rafael J. Wysocki
2007-06-07 14:46 ` Jan Engelhardt
2007-06-07 15:24 ` Gene Heskett
2007-06-07 15:38 ` Jan Engelhardt
2007-06-07 16:06 ` Gene Heskett
2007-06-07 16:54 ` Jan Engelhardt
2007-06-07 20:21 ` Gene Heskett
2007-06-07 21:14 ` Pavel Machek
2007-06-05 21:11 ` Badari Pulavarty
2007-06-10 6:15 ` Avuton Olrich
2007-06-05 10:41 Mikael Pettersson
2007-06-05 15:51 ` Jeff Garzik
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=alpine.LFD.0.98.0706051219560.4921@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=michal.k.k.piotrowski@gmail.com \
--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
all inboxes | Powered by JetHome®