From: Daniel Egger <degger@fhm.edu>
To: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: 2.4.20 and 2.5.64 NIC missing interrupts in APIC mode
Date: 13 Mar 2003 19:58:21 +0100 [thread overview]
Message-ID: <1047581900.1513.36.camel@sonja> (raw)
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Hija,
I just bought a new motherboard "ECS L7VTA" sporting a VIA KT400 chipset
and found an annoying bug which took me quite some time to track down:
As soon as I enable the APIC mode in the BIOS the onboard PHY seems
to ignore any packets which are thrown at it *after* the kernel
initialised itself which is especially nasty since the system is booting
from network effectively stopping its boot when trying to get an IP
using DHCP or mounting a NFS volume in case the IP is fixed. The onboard
NIC is a VIA Rhine II (VT6102).
The startup process looks like:
- POST
- BIOS check
- PXE BIOS initialisation
- PXE boot into etherboot
- Correct detection and initialisation of the NIC in etherboot
- Boot of linux kernel
- Correct initialisation of system including NIC (via-rhine driver from
Donald Becker as in the standard kernels)
- Endless loop like the following:
-------->
eth0: Setting full-duplex based on MII #1 link partner capability of 41e1.
Sending DCHP requests ...... timed out!
<--------
The NIC initialised itself with the correct interrupt according to the
BIOS screen. As soon as I shut down the APIC mode, everything works as
expected.
Ideas?
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-03-13 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 18:58 Daniel Egger [this message]
2003-03-13 20:24 ` 2.4.20 and 2.5.64 NIC missing interrupts in APIC mode Roger Luethi
2003-03-14 17:27 ` Daniel Egger
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=1047581900.1513.36.camel@sonja \
--to=degger@fhm.edu \
--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