linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Eric Dumazet <eric.dumazet@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] kernel freezes with latest tree
Date: Tue, 10 Jan 2012 08:28:12 -0800	[thread overview]
Message-ID: <CA+55aFwNVutn=Z8N9k3CHLri=EKWX2UcN8skZvMfJ9Tg1LHCpg@mail.gmail.com> (raw)
In-Reply-To: <1326212033.19095.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>

On Tue, Jan 10, 2012 at 8:13 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
> Here are two traces of the lockups, since I had some free time to reproduce the
> bug on current tree (plus a minor change in bnx2 driver to avoid a
> netconsole related stack trace)

Hmm. You have load_balance() and idle_balance() there in the trace, so
I'm getting more hopeful that it really is just the fact that
set_cpu_sd_state_idle() really needs to just be run with interrupts
disabled. That was my main concern about that merge, so if it's that,
I'll be relieved.

If you can please try that change out, that would be great.

[ And if that's not it - Ingo & co, please check out the traces on lkml ]

                       Linus

  reply	other threads:[~2012-01-10 16:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  4:57 [BUG] kernel freezes with latest tree Eric Dumazet
2012-01-10  5:03 ` Eric Dumazet
2012-01-10  8:16   ` Eric Dumazet
2012-01-10 16:13     ` Eric Dumazet
2012-01-10 16:28       ` Linus Torvalds [this message]
2012-01-10 16:37         ` Eric Dumazet
2012-01-10 16:49           ` Linus Torvalds
2012-01-10 16:53             ` Eric Dumazet
2012-01-10 17:00               ` Linus Torvalds
2012-01-10 19:32                 ` Ingo Molnar
2012-01-10 22:23                 ` Eric Dumazet
2012-01-10 23:44                   ` Linus Torvalds
2012-01-11  6:35                     ` David Ahern
2012-01-11  9:04                       ` Peter Zijlstra
2012-01-11 10:28                         ` Eric Dumazet
2012-01-11 11:29                           ` Eric Dumazet
2012-01-11 12:25                         ` Peter Zijlstra
2012-01-11 13:24                           ` Eric Dumazet
2012-01-11 15:56                           ` Ingo Molnar
2012-01-11 16:05                             ` Peter Zijlstra
2012-01-11 16:14                               ` Ingo Molnar
2012-01-11 16:31                               ` Linus Torvalds
2012-01-11 16:58                                 ` Peter Zijlstra
2012-01-12  6:17                               ` [tip:sched/urgent] sched: Fix lockup by limiting load-balance retries on lock-break tip-bot for Peter Zijlstra
2012-01-11  8:22                     ` [BUG] kernel freezes with latest tree Eric Dumazet
2012-01-11 14:20                     ` Frederic Weisbecker
2012-01-10 16:16     ` Linus Torvalds
2012-01-10 16:33       ` Eric Dumazet

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='CA+55aFwNVutn=Z8N9k3CHLri=EKWX2UcN8skZvMfJ9Tg1LHCpg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).