From: Ingo Molnar <mingo@elte.hu>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@googlemail.com>,
tglx@linutronix.de, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20-git15 BUG: soft lockup detected on CPU#0! - timers?
Date: Fri, 23 Feb 2007 11:10:25 +0100 [thread overview]
Message-ID: <20070223101025.GA21127@elte.hu> (raw)
In-Reply-To: <20070223060802.GA8562@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> could you please try the patch below? This is pretty much the only
> condition under which we can silently 'leak' pending softirqs, and
> trigger the new warning: if something does cond_resched_softirq() in
> non-runnable state. (which is a no-no, but nothing enforced this, so
> it could in theory happen.) So the question is, with this patch
> applied, do you get these new warnings from sched.c?
it just triggered on one of my boxes:
BUG: at kernel/sched.c:4692 cond_resched_softirq()
[<c03ce128>] cond_resched_softirq+0x5f/0x7b
[<c0369078>] release_sock+0x42/0x81
[<c03693bc>] sk_wait_data+0x57/0x9d
[<c0129a00>] autoremove_wake_function+0x0/0x33
[<c03942ff>] tcp_recvmsg+0x39c/0x973
[<c0368e39>] sock_common_recvmsg+0x3e/0x54
[<c0367903>] sock_aio_read+0x106/0x112
[<c0159b0c>] do_sync_read+0xc8/0x105
[<c0129a00>] autoremove_wake_function+0x0/0x33
[<c0159e82>] vfs_read+0xc1/0x15a
[<c015a7d2>] sys_read+0x41/0x67
[<c0103c10>] syscall_call+0x7/0xb
=======================
so tcp_recvmsg() definitely gets into this condition.
Ingo
next prev parent reply other threads:[~2007-02-23 10:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 18:54 Michal Piotrowski
2007-02-20 21:56 ` Thomas Gleixner
2007-02-20 22:37 ` Michal Piotrowski
2007-02-21 15:33 ` Thomas Gleixner
2007-02-21 15:38 ` Michal Piotrowski
2007-02-21 20:00 ` Thomas Gleixner
2007-02-22 1:47 ` Michal Piotrowski
2007-02-22 10:50 ` Michal Piotrowski
2007-02-23 6:08 ` Ingo Molnar
2007-02-23 7:32 ` Mike Galbraith
2007-02-23 10:10 ` Ingo Molnar [this message]
2007-02-24 22:45 ` Michal Piotrowski
2007-02-25 9:53 ` Thomas Gleixner
2007-02-26 13:01 ` Michal Piotrowski
2007-02-26 13:25 ` [patch] sched: fix SMT scheduler bug Ingo Molnar
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=20070223101025.GA21127@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=michal.k.k.piotrowski@googlemail.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome