From: Manfred Spraul <manfred@colorfullife.com>
To: Vincent van de Camp <vncnt@vzavenue.net>
Cc: ktech@wanadoo.es, torvalds@osdl.org,
linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: 2.6.7-rc1 breaks forcedeth
Date: Sun, 06 Jun 2004 15:40:29 +0200 [thread overview]
Message-ID: <40C31ECD.9050304@colorfullife.com> (raw)
In-Reply-To: <40C313AE.10503@vzavenue.net>
Vincent van de Camp wrote:
> I do not use the forcedeth driver, but I do have IRQ 11 problems with
> an nforce2 motherboard. I'm not entirely sure if this is the same
> problem, but loading the ehci module (managed by hotplug) triggers the
> kernel to disable IRQ 11. Dmesg with some stack traces:
It's the same bug:
something generates irq 11 events. We don't know who or why. This causes
an irq storm as soon as the first user registeres a handler for irq 11
and the system must shut off irq 11. Then all devices that are connected
to irq 11 fail.
--
Manfred
next prev parent reply other threads:[~2004-06-06 13:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 12:10 Re: 2.6.7-rc1 breaks forcedeth ktech
2004-06-06 12:53 ` Vincent van de Camp
2004-06-06 13:40 ` Manfred Spraul [this message]
2004-06-06 14:17 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2004-06-16 18:40 David Mansfield
2004-06-06 13:49 jjluza
[not found] <E1BWxTh-0002dx-KR@mb06.in.mad.eresmas.com>
2004-06-06 13:31 ` Daniel Schmitt
2004-06-06 1:59 ktech
2004-06-06 3:14 ` Linus Torvalds
2004-06-06 8:36 ` Manfred Spraul
2004-06-06 17:04 ` Linus Torvalds
2004-06-06 18:13 ` Jeff Garzik
2004-06-06 18:21 ` Jeff Garzik
2004-06-06 18:32 ` Linus Torvalds
2004-06-05 23:41 Luis Miguel García Mancebo
2004-06-05 23:50 ` Linus Torvalds
2004-05-31 0:29 jjluza
2004-05-30 17:54 Luis Miguel García Mancebo
2004-05-30 20:47 ` Jeff Garzik
2004-05-30 15:57 Lee Howard
2004-05-30 17:20 ` Jeff Garzik
2004-05-30 22:59 ` Lee Howard
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=40C31ECD.9050304@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=jgarzik@pobox.com \
--cc=ktech@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=vncnt@vzavenue.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