From: Sitsofe Wheler <sitsofe@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: skge killing off snd_via686 interrupts on Fedora Core 5
Date: Sat, 27 May 2006 15:43:30 +0100 [thread overview]
Message-ID: <pan.2006.05.27.14.43.20.450376@yahoo.com> (raw)
We have a few machines which have been upgraded to to D-Link System Inc
DGE-530T Gigabit Ethernet adaptors. The unfortunate news is that shortly
after this was done people found that programs were either going
into the D state or hanging while trying to access the soundcard using
ALSA. Looking in the logs turned up this message:
irq 11: nobody cared (try booting with the "irqpoll" option)
[<c0139893>] __report_bad_irq+0x2b/0x69 [<c0139a54>] note_interrupt+0x183/0x1af
[<c01393fa>] handle_IRQ_event+0x23/0x4c [<c01394bd>] __do_IRQ+0x9a/0xcd
[<c0104c2e>] do_IRQ+0x5c/0x77 =======================
[<c01035b6>] common_interrupt+0x1a/0x20
[<e08e6fd4>] skge_poll+0x20b/0x3fc [skge] [<c028c1f7>] net_rx_action+0x78/0x13f
[<c011f83a>] __do_softirq+0x35/0x7f [<c0104c81>] do_softirq+0x38/0x3f
=======================
[<c011f8d7>] local_bh_enable+0x53/0x5e [<c02ad51a>] tcp_recvmsg+0x317/0x6fb
[<c02842c6>] sock_common_recvmsg+0x2f/0x45 [<c028250d>] sock_recvmsg+0xe9/0x104
[<c012b10b>] autoremove_wake_function+0x0/0x2d [<c02dd4b5>] _spin_unlock_irq+0x5/0x7
[<c01c48b8>] vsnprintf+0x422/0x461 [<c0104c40>] do_IRQ+0x6e/0x77
[<c02835a3>] sys_recvfrom+0xad/0x10c [<c0151e25>] fd_install+0x24/0x50
[<c02dd493>] _read_unlock_irq+0x5/0x7 [<c013a33a>] find_get_page+0x39/0x3f
[<c0104c40>] do_IRQ+0x6e/0x77 [<c01035b6>] common_interrupt+0x1a/0x20
[<c0104c40>] do_IRQ+0x6e/0x77 [<c01035b6>] common_interrupt+0x1a/0x20
[<c028361b>] sys_recv+0x19/0x1d [<c0283c47>] sys_socketcall+0x117/0x19e
[<c0104c40>] do_IRQ+0x6e/0x77 [<c0102be9>] syscall_call+0x7/0xb
handlers:
[<e09dfca3>] (snd_via686_interrupt+0x0/0xcd [snd_via82xx])
Disabling IRQ #11
This has also been reported in the Red Hat bugzilla over here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192980
on a 2.6.16-1.2122_FC5 kernel. The problem is highly reproducible and
unloading/reloading the snd_via686 module temporarily fixes the problem
until the next big burst of network traffic.
next reply other threads:[~2006-05-27 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 14:43 Sitsofe Wheler [this message]
2006-06-01 17:03 ` skge killing off snd_via686 interrupts on Fedora Core 5 Alan Cox
2006-06-02 17:57 ` Sitsofe Wheeler
2006-06-04 9:45 ` Sitsofe Wheeler
2006-06-11 18:08 ` [SOLVED] " Sitsofe Wheeler
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=pan.2006.05.27.14.43.20.450376@yahoo.com \
--to=sitsofe@yahoo.com \
--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 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.