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: 26 Sep 2005 20:36:51 +0200 [thread overview]
Message-ID: <m34q873ccc.fsf@telia.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0509252026290.3089@poirot.grange>
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> On Sun, 25 Sep 2005, Peter Osterlund wrote:
>
> > Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> >
> > > Just tried pktcdvd on 2.6.13.1. The setup went fine:
...
> > > But, as I tried to copy some files to the CD-RW, it first went ok, but
> > > then produced the following:
> > >
> > > 20:41:01: ide-cd: cmd 0x2a timed out
> > > ^^^^ ---------> write10
> > > 20:41:01: hdc: DMA timeout retry
> > > 20:41:01: hdc: timeout waiting for DMA
...
> > > the "cp" finished earlier, I did a sync, and it also finished. The good
> > > parts - no Oops, no process stuck in "D", tha bad parts - it didn't
> > > work:-), the IDE LED stays on and I cannot eject the CD. The CD-R is a
> > > BenQ 52x32x52 Seamless Link alone on ide1, the disk does indeed say
> > > 4x-10x. The cd-writer works mostly... if I am gentle to it - I usually
> > > burn at 32x even if the media says 52x... Is it just a hw-failure or a
> > > driver bug?
> >
> > Did it ever work with this hardware, for example using 2.6.12?
>
> It was the first time I ever tried it. Now as you asked I also tried
> 2.6.12-rc5. Surprise, surprise - it worked... But very strange. First, I
> did
>
> # time cp -a source /cdrom/ ; time sync
>
> It took a few minutes to copy 190MB, but it finished successfully. Now to
> the strange things: even after it finished the LED on the writer continued
> flashing red... Only after I performed a read access to /cdrom/ it
> stopped. Actually, just wrote a small file to it, did a sync, sync
> returned, LED is flashing red. Now I cannot stop it by reading. Only
> unmounting it helped.
...
> Besides, it works under 2.6.12-rc5...
What gcc versions were used when compiling the kernels? (Boot both
kernels, run "cat /proc/version" to find out.)
I just discovered that the driver doesn't work correctly on my laptop
if I use "gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)" from Fedora
Core 4. "pktsetup 0 /dev/hdc ; cat /proc/driver/pktcdvd/pktcdvd0"
OOPSes. If I use gcc32 it does seem to work though.
--
Peter Osterlund - petero2@telia.com
http://web.telia.com/~u89404340
next prev parent reply other threads:[~2005-09-26 18:36 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 [this message]
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
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=m34q873ccc.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