From: Roger Luethi <rl@hellgate.ch>
To: Enver Haase <enver@convergence.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Rokas Masiulis <roma1390@uosis.mif.vu.lt>,
linux-kernel@vger.kernel.org
Subject: Re: IO-APIC/VIA-RHINE problem on 2.4.x
Date: Thu, 29 Jan 2004 11:57:40 +0100 [thread overview]
Message-ID: <20040129105740.GA4086@k3.hellgate.ch> (raw)
In-Reply-To: <4018D74A.1000107@convergence.de>
On Thu, 29 Jan 2004 10:50:02 +0100, Enver Haase wrote:
> Here's output from my machine; it's a VIA-based one.
> [...]
> This (IO-APIC configured) does not work:
> [...]
> This, however, DOES work (IO APIC NOT configured)
I've seen plenty of reports from people who complain about IO APIC
breakage on VIA. It might be fixed in 2.6, but I wouldn't know since I
don't have any IO APIC hardware. Or maybe the reporters found it easier
to turn off that option than to get somebody to fix it. If 2.6 fails
as well I suggest you try bugzilla.kernel.org so at least the report
won't go away.
Roger
prev parent reply other threads:[~2004-01-29 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 9:50 IO-APIC/VIA-RHINE problem on 2.4.x Enver Haase
2004-01-29 10:57 ` Roger Luethi [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=20040129105740.GA4086@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=enver@convergence.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roma1390@uosis.mif.vu.lt \
/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