From: Matthias Andree <matthias.andree@gmx.de>
To: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15.4 ide-cd causes 'local unit communication failure' on NEC ND-4550A?
Date: Mon, 13 Feb 2006 21:10:38 +0100 [thread overview]
Message-ID: <20060213201038.GB22578@merlin.emma.line.org> (raw)
In-Reply-To: <20060212155258.GA8860@merlin.emma.line.org>
Matthias Andree schrieb am 2006-02-12:
> Greetings,
>
> catchy subject, here's the story:
>
> SUSE Linux kernels 2.6.13-15.7,
> 2.6.13-15.8 (both SUSE Linux 10.0 i586) and
> Vanilla kernel 2.6.15.4
>
> cause "local unit communication failure" when running "readcd -c2scan"
> on my NEC ND-4550A CD/DVD drive (VIA KT8237, Athlon XP 2500+, 1 GB RAM)
> after at most two seconds of reading.
Detail info: the failed command always takes a touch more than 6.4 s to
timeout. Only the time until it happens for the first time differs.
It appears to me that the drive has an internal watchdog to wait for the
host to do something.
And directions how to dig up useful debug information for this issue?
Have there been related fixes in 2.6.16-rc* that make testing
worthwhile?
--
Matthias Andree
prev parent reply other threads:[~2006-02-13 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 15:52 Matthias Andree
2006-02-13 20:10 ` Matthias Andree [this message]
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=20060213201038.GB22578@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=axboe@suse.de \
--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
all inboxes | Powered by JetHome®