From: Daniel Egger <degger@fhm.edu>
To: Roger Luethi <rl@hellgate.ch>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.20 and 2.5.64 NIC missing interrupts in APIC mode
Date: 14 Mar 2003 18:27:00 +0100 [thread overview]
Message-ID: <1047662819.7452.17.camel@sonja> (raw)
In-Reply-To: <20030313202407.GA10774@k3.hellgate.ch>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Am Don, 2003-03-13 um 21.24 schrieb Roger Luethi:
> > 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).
> You may want to try 2.4.x-ac kernels, I believe Alan fixed some VIA APIC
> issues.
According to Alans changelog the 2.5-ac has a forwardport of the VIA
interrupt line patch, after some difficulties applying 2.5.64-ac3 to
a rsynched post 2.5.64 kernel (some parts of the console changes didn't
apply cleanly) I now tried it and it shows exactly the same symptoms.
Are there more VIA patches floating aroung? A short search on google
didn't find anything particularly interesting.
Almost more annoying is that even after removing the fb support I cannot
see enough of the messages to be helpful here, neither scrolllock nor
shift-pgup help, probably also an interrupt issue though a bit seems
to go through:
atkbd.c: Unknown key (set 2, scancode 0xb6, on isa0060/serio0) pressed.
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-03-14 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 18:58 2.4.20 and 2.5.64 NIC missing interrupts in APIC mode Daniel Egger
2003-03-13 20:24 ` Roger Luethi
2003-03-14 17:27 ` Daniel Egger [this message]
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=1047662819.7452.17.camel@sonja \
--to=degger@fhm.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
/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.