From: Matti Aarnio <matti.aarnio@zmailer.org>
To: linux-kernel@vger.kernel.org
Subject: Soft lockup in e100 driver ?
Date: Tue, 9 Aug 2005 16:36:47 +0300 [thread overview]
Message-ID: <20050809133647.GK22165@mea-ext.zmailer.org> (raw)
Running very recent Fedora Core Development kernel I can following
soft-oops.. ( 2.6.12-1.1455_FC5smp )
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
BUG: soft lockup detected on CPU#0!
Pid: 10743, comm: ifconfig
EIP: 0060:[<f88bf2f9>] CPU: 0
EIP is at e100_clean_cbs+0x2f/0x12b [e100]
EFLAGS: 00000293 Not tainted (2.6.12-1.1455_FC5smp)
EAX: 495c7c2b EBX: 495c7c2b ECX: f6c311a0 EDX: 00000000
ESI: 00000040 EDI: f6c30000 EBP: f71a4b20 DS: 007b ES: 007b
CR0: 8005003b CR2: 0804a544 CR3: 01e9cd80 CR4: 000006f0
[<f88c0708>] e100_down+0x66/0x9a [e100]
[<f88c1623>] e100_close+0xa/0xd [e100]
[<c02b7adb>] dev_close+0x40/0x7e
[<c02b8f59>] dev_change_flags+0x46/0xf5
[<c02f76b3>] devinet_ioctl+0x564/0x5df
[<c02af22c>] sock_ioctl+0xc3/0x250
[<c02af169>] sock_ioctl+0x0/0x250
[<c01762ef>] do_ioctl+0x1f/0x6d
[<c017648f>] vfs_ioctl+0x50/0x1c6
[<c0176662>] sys_ioctl+0x5d/0x6f
[<c010394d>] syscall_call+0x7/0xb
[<c014473f>] softlockup_tick+0x6f/0x80
[<c01085b8>] timer_interrupt+0x2d/0x75
[<c01448dd>] handle_IRQ_event+0x2e/0x5a
[<c01449cb>] __do_IRQ+0xc2/0x127
[<c0105f7e>] do_IRQ+0x4e/0x86
=======================
[<c01160cc>] smp_apic_timer_interrupt+0xc1/0xca
[<c0104382>] common_interrupt+0x1a/0x20
[<f88bf2f9>] e100_clean_cbs+0x2f/0x12b [e100]
[<f88c0708>] e100_down+0x66/0x9a [e100]
[<f88c1623>] e100_close+0xa/0xd [e100]
[<c02b7adb>] dev_close+0x40/0x7e
[<c02b8f59>] dev_change_flags+0x46/0xf5
[<c02f76b3>] devinet_ioctl+0x564/0x5df
[<c02af22c>] sock_ioctl+0xc3/0x250
[<c02af169>] sock_ioctl+0x0/0x250
[<c01762ef>] do_ioctl+0x1f/0x6d
[<c017648f>] vfs_ioctl+0x50/0x1c6
[<c0176662>] sys_ioctl+0x5d/0x6f
[<c010394d>] syscall_call+0x7/0xb
Preconditions for this are:
- E100 card stopped working for some reason (no idea why, it just
does sometimes at this oldish 2x P-III machine)
- There are active datastreams running in and out
(around 0.2 Mbps out, multiple megabits in.)
- Commanding then "ifconfig eth0 down" results in what feels like
system freezing, but it does recover in about 30-60 seconds
(it takes long enough for me to sweat bullets...)
- While in freeze state, keyboard can go crazy, but mouse does
respond, as well as tvtime shows bt848 captured live video.
next reply other threads:[~2005-08-09 13:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 13:36 Matti Aarnio [this message]
2005-08-09 13:55 ` Jesper Juhl
2005-08-09 14:37 ` Matti Aarnio
2005-08-09 15:41 ` Steven Rostedt
2005-08-09 15:55 ` Matti Aarnio
2005-08-09 16:14 ` Steven Rostedt
2005-08-09 14:58 ` Lee Revell
2005-08-09 15:23 ` Steven Rostedt
2005-08-09 15:32 ` Daniel Walker
2005-08-09 16:16 ` Daniel Walker
2005-08-09 16:36 ` Matti Aarnio
2005-08-11 0:29 ` Stephen D. Williams
2005-08-11 0:32 ` Stephen D. Williams
2005-08-11 7:39 ` Matti Aarnio
2005-08-12 3:11 ` Stephen D. Williams
2005-08-12 5:45 ` Jesse Brandeburg
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=20050809133647.GK22165@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®