From: Wakko Warner <wakko@animx.eu.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pierre Rousselet <pierre.rousselet@wanadoo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.16 with es1370 pci
Date: Sat, 2 Feb 2002 15:37:42 -0500 [thread overview]
Message-ID: <20020202153742.A3701@animx.eu.org> (raw)
In-Reply-To: <20020101104611.A30843@animx.eu.org> <E16LSVd-0000pj-00@the-village.bc.nu>
In-Reply-To: <E16LSVd-0000pj-00@the-village.bc.nu>; from Alan Cox on Tue, Jan 01, 2002 at 05:15:28PM +0000
> > used the 2nd dsp on this card since this boot, but I know it works since I
> > used it the last boot. When the first quits, they both are gone. But
> > seeing how no interrupts are being delivered, makes sense (see below)
>
> Boot withg the "noapic" option. Quite how your system has managed to
> lose an interrupt in the APIC hardware I don't know, but the APIC's
> certainly have bugs. It could also be an edge/level trigger but if the BIOS
> confused it because IRQ15 was for some kind of IDE device, but I see no
> evidence of that.
>
> If it happens with APIC disabled ("noapic") then the second option might
> be worth investigating.
It's been a while since I've added more to this.
so far, alan, noapic has kept my es1370 card working w/o problems. Any clue
why it doesn't work when apic is used? It will usually stop working during
play and will not work again until a reboot. (I don't even need to
hardreset the system)
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2002-02-02 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 11:55 2.4.16 with es1370 pci Wakko Warner
2001-12-31 13:19 ` Alan Cox
[not found] ` <3C3065CE.1070608@wanadoo.fr>
[not found] ` <20011231122440.B29342@animx.eu.org>
[not found] ` <3C316C47.4080406@wanadoo.fr>
2002-01-01 15:46 ` Wakko Warner
2002-01-01 17:15 ` Alan Cox
2002-01-04 14:18 ` Roeland Th. Jansen
2002-02-02 20:37 ` Wakko Warner [this message]
2002-01-01 18:53 ` Pierre Rousselet
2002-01-02 3:35 ` Wakko Warner
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=20020202153742.A3701@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre.rousselet@wanadoo.fr \
/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