From: Len Brown <len.brown@intel.com>
To: Oliver Feiler <kiza@gmx.net>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Marcelo Tosatti <marcelo@hera.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: eth*: transmit timed out since .27 (was: linux-2.4.27 released)
Date: 16 Aug 2004 13:52:15 -0400 [thread overview]
Message-ID: <1092678734.23057.18.camel@dhcppc4> (raw)
In-Reply-To: <566B962EB122634D86E6EE29E83DD808182C3236@hdsmsx403.hd.intel.com>
Oliver,
I'm glad that turning off "pci=noacpi" fixed your system.
I don't know why the legacy irqrouter didn't work, but
as ACPI works, I'm not going to worry about it;-)
I expect the "acpi=off" experiment would behave the same as
"pci=noacpi", but it looks like in your experiment you
mis-spelled that parameter as apci=off, so instead it was the
same as the default ACPI-enabled case.
Re: lots of interrupts on the same IRQ.
There are boot params to balance out the IRQs in PIC mode,
but what you want to do on this system is enable the IOAPIC
in your kernel config. The existence of the MADT in your
ACPI tables suggests you may have one. An IOAPIC will bring
additional interrupt pins to bear, usually allowing
the PCI interrupts to use IRQs > 16 where they may
not have to share so much.
cheers,
-Len
next parent reply other threads:[~2004-08-16 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566B962EB122634D86E6EE29E83DD808182C3236@hdsmsx403.hd.intel.com>
2004-08-16 17:52 ` Len Brown [this message]
2004-08-16 18:44 ` eth*: transmit timed out since .27 Oliver Feiler
2004-08-16 19:08 ` Oliver Feiler
2004-08-16 19:50 ` Len Brown
2004-08-16 23:04 ` Oliver Feiler
2004-08-16 23:42 ` Maciej W. Rozycki
2004-08-17 0:29 ` Alan Cox
2004-08-16 19:38 ` Len Brown
2004-08-16 20:11 ` Maciej W. Rozycki
2004-08-07 23:28 linux-2.4.27 released Marcelo Tosatti
2004-08-10 12:23 ` eth*: transmit timed out since .27 (was: linux-2.4.27 released) Oliver Feiler
2004-08-13 10:15 ` Marcelo Tosatti
2004-08-13 21:56 ` Oliver Feiler
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=1092678734.23057.18.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=kiza@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=marcelo@hera.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