From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Frederik Deweerdt <deweerdt@free.fr>
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, 4 Jun 2007 11:06:20 -0400 [thread overview]
Message-ID: <20070604150620.GC10008@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20070507174511.GL8751@csclub.uwaterloo.ca>
On Mon, May 07, 2007 at 01:45:11PM -0400, Lennart Sorensen wrote:
> Hmm, I thought I saw it on two systems already, but I should go try that
> again.
Hmm, still haven't figured this out. I just saw this one this morning:
BUG: soft lockup detected on CPU#0!
[<c0103fc4>] dump_stack+0x24/0x30
[<c013d36e>] softlockup_tick+0x7e/0xc0
[<c011eb23>] update_process_times+0x33/0x80
[<c01062c9>] timer_interrupt+0x39/0x80
[<c013d6fd>] handle_IRQ_event+0x3d/0x70
[<c013da59>] __do_IRQ+0xa9/0x150
[<c0104e55>] do_IRQ+0x25/0x60
[<c010313a>] common_interrupt+0x1a/0x20
[<c013d6d8>] handle_IRQ_event+0x18/0x70
[<c013da59>] __do_IRQ+0xa9/0x150
[<c0104e55>] do_IRQ+0x25/0x60
[<c010313a>] common_interrupt+0x1a/0x20
[<c0119cda>] __do_softirq+0x3a/0xa0
[<c0119d6d>] do_softirq+0x2d/0x30
[<c0119fb7>] irq_exit+0x37/0x40
[<c0104e5a>] do_IRQ+0x2a/0x60
[<c010313a>] common_interrupt+0x1a/0x20
[<c013dcee>] setup_irq+0xce/0x1e0
[<c013de97>] request_irq+0x97/0xb0
[<d0851f9d>] pcnet32_open+0x4d/0x3d0 [pcnet32]
[<c023a4f9>] dev_open+0x39/0x80
[<c0238cea>] dev_change_flags+0xfa/0x130
[<c027eb9f>] devinet_ioctl+0x4ff/0x6f0
[<c022dab1>] sock_ioctl+0xf1/0x1f0
[<c017413c>] do_ioctl+0x2c/0x80
[<c01741e2>] vfs_ioctl+0x52/0x2f0
[<c01744ef>] sys_ioctl+0x6f/0x80
[<c0102ef7>] syscall_call+0x7/0xb
[<b7f41d04>] 0xb7f41d04
And it is happening on multiple systems. I am starting to wonder if it
is a bug in the soft lockup detection. Maybe it really isn't locked up
but just momentarily appears to be. I will try turning off the soft
lockup detection and see what happens.
--
Len Sorensen
prev parent reply other threads:[~2007-06-04 15:06 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
2007-05-07 17:45 ` Lennart Sorensen
2007-06-04 15:06 ` Lennart Sorensen [this message]
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=20070604150620.GC10008@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=deweerdt@free.fr \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox