mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: "Luis Miguel García Mancebo" <ktech@wanadoo.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc1 breaks forcedeth
Date: Sat, 5 Jun 2004 16:50:01 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0406051646030.7010@ppc970.osdl.org> (raw)
In-Reply-To: <200406060141.09394.ktech@wanadoo.es>



On Sun, 6 Jun 2004, Luis Miguel García Mancebo wrote:
> 
> I have not been able to make my ethernet card to work in post-2.6.6 kernels. 
> This is a nforce2 motherboard, and as Jeff pointed, nothing has changed in 
> the driver (forcedeth), and the problem could be acpi or routing in the 
> kernel. In fact, I have a "Disabling IRQ #11" message. Here is the dmesg:
> 
> P.S.: I have tested noapic, acpi=off, pci=noapic. But this doesn't fix 
> nothing.

Can you do a "diff" between the dmesg output of a working kernel, and a 
nonworking one? Also, please do the same with /proc/interrupts...

It sounds like your ethernet card is on irq11 (sharing it with USB), but 
that something has incorrectly decided that it must be somewhere else and 
then when the ethernet irq happens, it continually screams on irq11 until 
the kernel decides that it has to shut it up. At which point both ethernet 
and USB is dead (the former because it is on the wrong interrupt, the 
latter because the kernel had to shut up the irq that it was sharing in 
order to avoid endless irqs).

		Linus

  reply	other threads:[~2004-06-05 23:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 23:41 Luis Miguel García Mancebo
2004-06-05 23:50 ` Linus Torvalds [this message]
  -- 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 12:10 ktech
2004-06-06 12:53 ` Vincent van de Camp
2004-06-06 13:40   ` Manfred Spraul
2004-06-06 14:17 ` Manfred Spraul
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-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=Pine.LNX.4.58.0406051646030.7010@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=ktech@wanadoo.es \
    --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®