From: Peter Osterlund <petero2@telia.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: [2.6.13] pktcdvd: IO-errors
Date: 15 Oct 2005 17:36:52 +0200 [thread overview]
Message-ID: <m3acharduz.fsf@telia.com> (raw)
In-Reply-To: <m37jcjiula.fsf@telia.com>
Peter Osterlund <petero2@telia.com> writes:
> Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
>
> > Well, I've had this patch (to 2.6.13) failing once, whereas I still
> > haven't been able to reproduce the error with your previous patch. What
> > now? A bit worrying is that test results are not 100% deterministic now...
> > Which means, until recently my standard test (copy about 150M co the
> > CD-RW && sync) produced always consistent results, now I've seen a couple
> > of times the same driver version either failing or succeeding...
>
> My current theory is that there is something wrong with the firmware
> or hardware in your drive, and different I/O patterns have different
> probabilities of triggering this problem.
>
> Maybe you could use Jens' IO tracing patch to identify the sequence of
> commands that make the drive fail. See subject "[PATCH] Block device
> io tracing" posted by Jens earlier today.
>
> If the problem is always caused by some well defined sequence of
> commands, it might be possible to implement a workaround in the
> pktcdvd driver.
I have found a problem on one of my drives. On my FC4 system, hald and
kded are constantly doing something with the drive, and this makes it
fail when I try to do packet writing. Killing those processes make
that drive work correctly. Maybe this helps in your case too. Try
packet writing from single user mode to see if it helps.
I don't know yet how to make hald and kded stay away from the drive
while packet writing is in progress.
--
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340
next prev parent reply other threads:[~2005-10-15 15:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 19:32 [2.6.13] pktcdvd: IO-errors Guennadi Liakhovetski
2005-09-25 9:09 ` Peter Osterlund
2005-09-25 21:06 ` Guennadi Liakhovetski
2005-09-26 18:36 ` Peter Osterlund
2005-09-26 19:29 ` Guennadi Liakhovetski
2005-09-26 19:48 ` Peter Osterlund
2005-09-26 22:06 ` Guennadi Liakhovetski
2005-09-28 21:02 ` Peter Osterlund
2005-09-29 19:18 ` Guennadi Liakhovetski
2005-10-02 12:11 ` Peter Osterlund
2005-10-08 22:37 ` Guennadi Liakhovetski
2005-10-09 21:23 ` Guennadi Liakhovetski
2005-10-09 21:54 ` Peter Osterlund
2005-10-10 5:05 ` Guennadi Liakhovetski
2005-10-10 17:48 ` Guennadi Liakhovetski
2005-10-10 20:48 ` Guennadi Liakhovetski
2005-10-11 21:31 ` Guennadi Liakhovetski
2005-10-11 21:58 ` Peter Osterlund
2005-10-15 15:36 ` Peter Osterlund [this message]
2005-10-17 21:11 ` Guennadi Liakhovetski
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=m3acharduz.fsf@telia.com \
--to=petero2@telia.com \
--cc=axboe@suse.de \
--cc=g.liakhovetski@gmx.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