public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Witold Krecicki <adasi@kernel.pl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SiI3112: problemes with shared interrupt line?
Date: Mon, 22 Sep 2003 21:59:12 +0200	[thread overview]
Message-ID: <200309222159.12643.adasi@kernel.pl> (raw)
In-Reply-To: <1064260163.2414.3.camel@sort.fjase.net>

Dnia pon 22. września 2003 21:49, Per Andreas Buer napisał:
> On Mon, 2003-09-22 at 21:42, Allen Martin wrote:
> > There are two issues I know about:
> >
> > 1) Earlier versions of the Asus BIOS would program incorrect timing in
> > the nForce internal P2P bridge, causing failures with SI3112 under high
> > disk activity.  This is fixed in rev 1005 of their BIOS or later.
>
> I am running the latest (1006, I think) ASUS (this is a ASUS A7
> something Deluxe motherboard) BIOS revision.
>
> > 2) PCI interrupts getting put into edge triggered mode when ACPI/APIC are
> > enabled.  Andrew de Quincey said this should be fixed in 2.4.22, but I
> > haven't tested it myself (I have ACPI disabled on all my test systems). 
> > I did verify his patch on 2.6 when he first posted it, and it works.
>
> I've tried disabeling APIC - it did not help.
>
> I'll try 2.6.something tomorrow.
Try to disable both ACPI and APIC, it helped in my case.
-- 
Witold Kręcicki (adasi) adasi [at] culm.net
GPG key: 7AE20871
http://www.culm.net

  reply	other threads:[~2003-09-22 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 19:42 SiI3112: problemes with shared interrupt line? Allen Martin
2003-09-22 19:49 ` Per Andreas Buer
2003-09-22 19:59   ` Witold Krecicki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-22 20:35 Allen Martin
2003-09-22 17:06 Per Andreas Buer
2003-09-22 18:49 ` Alan Cox
2003-09-22 19:59   ` Hugo Mills

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=200309222159.12643.adasi@kernel.pl \
    --to=adasi@kernel.pl \
    --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