From: Frederik Deweerdt <deweerdt@free.fr>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Don Fry <pcnet32@verizon.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Strange soft lockup detected message (looks like spin_lock bug in pcnet32)
Date: Mon, 7 May 2007 16:48:37 +0200 [thread overview]
Message-ID: <20070507144837.GA30865@slug> (raw)
In-Reply-To: <20070507140807.GF8753@csclub.uwaterloo.ca>
On Mon, May 07, 2007 at 10:08:07AM -0400, Lennart Sorensen wrote:
> On Fri, May 04, 2007 at 03:02:36PM -0400, Lennart Sorensen wrote:
> > Well I don't know, but something is going wrong and causing the soft
> > lock up. I must admit I am surprised if an interrupt can occour while
> > handling an interrupt, but then again maybe that is supposed to be
> > allowed.
>
> I tried building a kernel where the only change was enabling the spin
> lock debugging. It doesn't fail, while without spin lock debugging it
> seemed to fail very frequently. Darn! I hate when debugging makes hides
> the problem.
Can you try running on another Geode LX system, just to rule out a
hardware problem on you board?
Regards,
Frederik
next prev parent reply other threads:[~2007-05-07 14:50 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
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 [this message]
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=20070507144837.GA30865@slug \
--to=deweerdt@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.