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: 11 Oct 2005 23:58:57 +0200 [thread overview]
Message-ID: <m37jcjiula.fsf@telia.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0510112325410.19291@poirot.grange>
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> On Sun, 9 Oct 2005, Peter Osterlund wrote:
>
> > In that case, this patch should also work. Does it?
> >
> > diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
> > index d4b9c17..cb6bda9 100644
> > --- a/drivers/block/pktcdvd.c
> > +++ b/drivers/block/pktcdvd.c
> > @@ -538,7 +538,7 @@ static void pkt_iosched_process_queue(st
> > spin_unlock(&pd->iosched.lock);
> > if (bio && (bio->bi_sector == pd->iosched.last_write))
> > need_write_seek = 0;
> > - if (need_write_seek && reads_queued) {
> > + if (!writes_queued && reads_queued) {
> > if (atomic_read(&pd->cdrw.pending_bios) > 0) {
> > VPRINTK("pktcdvd: write, waiting\n");
> > break;
>
> 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.
> BTW, Peter, I still get errors from mails to you:
>
> <petero2@telia.com>:
> 81.228.8.84_does_not_like_recipient./Remote_host_said:_553_RCPT_TO:<petero2@telia.com>_refused/G
> iving_up_on_81.228.8.84./
It seems like my ISPs mail server doesn't want to talk to your mail
server. I have no idea why. I did get mails from you earlier.
--
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340
next prev parent reply other threads:[~2005-10-11 22:00 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 [this message]
2005-10-15 15:36 ` Peter Osterlund
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=m37jcjiula.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