public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Frederik Deweerdt <deweerdt@free.fr>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Strange soft lockup detected message (looks like spin_lock bug in pcnet32)
Date: Fri, 4 May 2007 11:19:34 -0400	[thread overview]
Message-ID: <20070504151934.GA8754@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20070504143326.GD24769@slug>

On Fri, May 04, 2007 at 04:33:26PM +0200, Frederik Deweerdt wrote:
> On Fri, May 04, 2007 at 10:10:24AM -0400, Lennart Sorensen wrote:
> > On Thu, May 03, 2007 at 04:31:43PM -0400, Lennart Sorensen wrote:
> [...]
> > Should line 2563 be a spin_lock_irqsave instead along with the
> > appropriate unluck later?
> IIRC, when you enable lockdep, it will complain about spinlocks used in
> an invalid context.

What is lockdep and how do I enable it?

I enabled SPINLOCK_DEBUG and am going to try that kernel now (except it
hit the bug before I could even log in and install the kernel this time,
so another reboot first).

--
Len Sorensen

  reply	other threads:[~2007-05-04 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 20:31 Strange soft lockup detected message Lennart Sorensen
2007-05-04 14:10 ` Strange soft lockup detected message (looks like spin_lock bug in pcnet32) Lennart Sorensen
2007-05-04 14:33   ` Frederik Deweerdt
2007-05-04 15:19     ` Lennart Sorensen [this message]
2007-05-04 15:34       ` Frederik Deweerdt
2007-05-04 15:40         ` Lennart Sorensen
2007-05-04 17:44           ` Lennart Sorensen
2007-05-04 17:50             ` Lennart Sorensen
2007-05-04 18:24               ` Don Fry
2007-05-04 19:02                 ` Lennart Sorensen
2007-05-07 14:08                   ` Lennart Sorensen
2007-05-07 14:48                     ` Frederik Deweerdt
2007-05-07 17:45                       ` Lennart Sorensen
2007-06-04 15:06                         ` Lennart Sorensen

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=20070504151934.GA8754@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=deweerdt@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox