From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: lost interrupt hell - Plea for Help
Date: Sat, 11 May 2002 01:48:38 -0700 [thread overview]
Message-ID: <3CDCDAE6.CB851FB6@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020509132713.1987A-100000@pioneer> <200205101112.g4ABCoX29098@Port.imtp.ilyichevsk.odessa.ua> <3CDC3B90.AADE1835@bigfoot.com> <3CDCD708.6000208@notnowlewis.co.uk>
mikeH wrote:
>
> You can try compiling without VIA chipset support, but it makes no
> difference.
> Now, with the latest prepatches, -ac patches and ide patches, I am
> getting spurious "8259A interrupt: IRQ7."
> all over the place too. Seems like the linux kernel does not play well
> with AMD Cpus + VIA chipsets, which
> is a real shame as thats what all my machines are :(
FWIW I have intel processor. It seems like the 'lost interrupt' while
ripping audio CDs is specific to VIA based motherboards.
erik
>
> mikeH
>
> Erik Steffl wrote:
>
> > this is with stable kernel (I tried 2.4.17 and 2.4.18), via config
> >option compiled in (I haven't tried without via support in kernel yet,
> >I'll try that).
> >
> > any ideas? TIA
> >
> > erik
next prev parent reply other threads:[~2002-05-11 8:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 18:01 lost interrupt hell - Plea for Help mikeH
2002-05-09 11:34 ` Tomasz Rola
2002-05-10 16:15 ` Denis Vlasenko
2002-05-10 21:28 ` Erik Steffl
2002-05-11 8:32 ` mikeH
2002-05-11 8:38 ` Rudmer van Dijk
2002-05-11 8:53 ` mikeH
2002-05-11 8:48 ` Rudmer van Dijk
2002-05-16 20:50 ` Rudmer van Dijk
2002-05-17 8:49 ` Mike
2002-05-19 7:14 ` Erik Steffl
2002-05-19 18:43 ` Kevin P. Fleming
2002-05-11 8:48 ` Erik Steffl [this message]
2002-05-09 11:42 ` Tomasz Rola
-- strict thread matches above, loose matches on Subject: below --
2002-05-19 12:25 Mikael Pettersson
2002-05-20 8:42 ` Erik Steffl
2002-05-19 20:26 Mikael Pettersson
2002-05-19 22:19 ` Kevin P. Fleming
2002-05-20 0:35 ` Kevin P. Fleming
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=3CDCDAE6.CB851FB6@bigfoot.com \
--to=steffl@bigfoot.com \
--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