From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: lost interrupt hell - Plea for Help
Date: Mon, 20 May 2002 01:42:08 -0700 [thread overview]
Message-ID: <3CE8B6E0.CFC6879D@bigfoot.com> (raw)
In-Reply-To: <200205191225.OAA25457@harpo.it.uu.se>
Mikael Pettersson wrote:
>
> On Sun, 19 May 2002 00:14:42 -0700, Erik Steffl wrote:
> >> Yeah, the spurious interrupt does seem to be an AMD apic problem, but the lost
> >> interrupt (on ripping audio) seems to be a VIA chipset problem, as people
> >> with KT266 chipsets are having boot problems / audio rip problems regardless
> >> of the processor type. Lucky me, I get both ;)
> >
> > doesn't anybody know what the problem is? while it was reported quite
> >a few times there was no helpful response to the problem (positive
> >(fix)or negative (it's unlikely to be fixed).
>
> As the person who added AMD K7 local APIC support to the kernel, I
> consider the _real_ problem to be the lack of adequate documentation.
> AMD has almost no documentation on the K7's machine-specific features,
> and VIA similarly don't seem keen on documenting their chipsets.
>
> If someone were to find AMD K7 documentation at the level of Intel's
> IA32 Volume 3 manual (245272-006), and AMD K7 errata docs at the level
> of Intel's PIII (244453-nn) and P4 (249199-nn) specification updates,
> then I'd be happy to look at the K7 spurious interrupt problem.
is the same true for 'lost interrupt' during audio ripping problem? I
mean it is fairly specific command so it might not be so hard to debug.
I have no experience with kernel - is there info available to get me
started in right direction?
erik
next prev parent reply other threads:[~2002-05-20 8:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 12:25 lost interrupt hell - Plea for Help Mikael Pettersson
2002-05-20 8:42 ` Erik Steffl [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-19 20:26 Mikael Pettersson
2002-05-19 22:19 ` Kevin P. Fleming
2002-05-20 0:35 ` Kevin P. Fleming
2002-05-07 18:01 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
2002-05-09 11:42 ` Tomasz Rola
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=3CE8B6E0.CFC6879D@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.