From: jiho@c-zone.net
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: hdX lost interrupt problem
Date: Tue, 08 Jul 2003 14:32:31 -0700 [thread overview]
Message-ID: <3F0B386F.3080902@c-zone.net> (raw)
In-Reply-To: 3F0AE4DF.80808@ifrance.com
Cédric Barboiron wrote:
> Hello,
>
> I'm currently having troubles while trying to listen or rip cds
> audios. `cdparanoia -Q` works fine but `strace cdparanoia 1` hangs
> at : ioctl(3, 0x530e
>
> Then I have from `dmesg` : hdc: lost interrupt hdc: lost interrupt (...)
>
> hdc: lost interrupt hdc: lost interrupt
>
> The only thing I found in archives is : " It seems like the 'lost
> interrupt' while ripping audio CDs is specific to VIA based
> motherboards."
>
> In fact, I have a VIA based motherboard : VIA KT333 and VIA 8233A
What kind of hard drive is it, with which kind of cable (40-line or
80-line), and what transfer mode is it running in?
These "lost interrupt" problems date back to UDMA-33. There were tons
of them early on, with several OSes, and if I'm not mistaken the
association seemed to be more with case cooling issues and ribbon
cables, rather than any particular chipset.
That *seemed* to be true in my case (and in my case), but I don't have
absolute knowledge of that because the problem was rare and impossible
to reproduce on demand. I had a VIA chipset, 82C586B, but there were
clear issues with case cooling, and the problem *seemed* to go away when
those issues were addressed. That *seemed* to be true for the other
cases (and cases) I read about, as well.
Maybe people with VIA chipsets tend to be reckless with their case
setups....
-- Jim Howard <jiho@c-zone.net>
next prev parent reply other threads:[~2003-07-08 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 15:35 hdX lost interrupt problem Cédric Barboiron
2003-07-08 21:32 ` jiho [this message]
2003-07-09 1:00 ` jiho
2003-07-09 5:04 ` jiho
2003-07-10 20:15 ` Cédric
2003-07-10 22:49 ` Cédric
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=3F0B386F.3080902@c-zone.net \
--to=jiho@c-zone.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