From: "K.M. Liu" <kmliu@sis.com>
To: "Daniel Blueman" <daniel.blueman@gmx.net>,
<linux-kernel@vger.kernel.org>
Subject: RE: [BUG] 2.6.0-t1 sis900 timeout
Date: Mon, 4 Aug 2003 18:06:23 +0800 [thread overview]
Message-ID: <FGEKKPFILEAJKNBBAFMCOENADJAA.kmliu@sis.com> (raw)
In-Reply-To: <8723.1059984634@www20.gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Please see the attached file for the SiS IO-APIC workaround.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Daniel Blueman
Sent: Monday, August 04, 2003 4:11 PM
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.0-t1 sis900 timeout
Can you check if the IRQ allocated to the SiS900 is the same on kernels
where it does work, and try without ACPI support, and/or any IO-APIC support
disabled?
I've seen this before with the network card in one of my systems - the
IO-APIC setup code, or ACPI table parsing was misprogramming the IRQ routing
tables, and it was being allocated the wrong level-triggered IRQ line.
Dan
--
Daniel J Blueman
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: ioapic.tar.gz --]
[-- Type: application/x-gzip, Size: 14855 bytes --]
next prev parent reply other threads:[~2003-08-04 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 8:10 [BUG] 2.6.0-t1 sis900 timeout Daniel Blueman
2003-08-04 10:06 ` K.M. Liu [this message]
2003-08-09 11:47 ` Gaël Le Mignot
-- strict thread matches above, loose matches on Subject: below --
2003-08-03 10:21 Gaël Le Mignot
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=FGEKKPFILEAJKNBBAFMCOENADJAA.kmliu@sis.com \
--to=kmliu@sis.com \
--cc=daniel.blueman@gmx.net \
--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;
as well as URLs for NNTP newsgroup(s).