problem reading DVD after starting packetwriting with empty drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-source-2.6.22
Some symptoms are similar to https:/
Under some circumstances, it is impossible to read the complete content of a DVD. Only the beginning is accessible, everithing beyond a certain point is not.
dmesg reports something like
[ 271.520000] attempt to access beyond end of device
[ 271.520000] sr0: rw=0, want=7097048, limit=2097151
[ 271.520000] Buffer I/O error on device sr0, logical block 1774261
Ways to reproduce
Configure Packetwriting for the DVD-drive in /etc/default/
1. Boot with empty DVD drive. Insert and mount DVD.
or 2. Stop udftools; rmmod pktcdvd sr-mod; reload modules and restart udftools with empty drive, insert DVD
How to make it work again
Stop udftools; rmmod pktcdvd sr-mod; insert DVD (does not have to remain in the drive); reload modules and restart udftools
Just restarting udftools does not work, both pktcdvd and sr-mod need to be reloaded.
Additional information
$ uname -a
Linux schlupp 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux
The drive is a LiteOn LH-20A1L. I remember having similar reading problems with my old IDE writer, which I thought to be dying. I also configured packetwriting the IDE drive (read-only) in my Thinkpad X20 (which normally does not make sense, admittedly) - same problem. I expect the problem to occur with any drive for which packet writing is enabled in /etc/default/
Additional information
$ uname -a
Linux schlupp 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux
lspci and dmesg follow.
description: | updated |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Hi David,
The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. I don't suppose you'd be willing to test the latest Hardy Alpha release and verify if this bug is still an issue? http:// www.ubuntu. com/testing . Please let us know. We'll keep this report open against the actively developed kernel but will close against 2.6.22. Thanks.