System freeze if reading from DVD Toshiba SD-R6112
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Using a Toshiba SD-R6112 slim DVD drive with the latest firmware on Hardy.
Since upgrading to Hardy, I've had several problems with this drive.
- previously burned single layer DVD-R aren't recognized. When trying to mount them, I get the message "No medium".
- Burning ends with no error but disks are end up blank.
- worse, each time I try to read a commercial dual-layer DVD, I get a complete system freeze : no mouse, no keyboard, I have to hard reboot my machine. It happens in xine, in DVD Shrink via wine, and even when I try to "cat /dev/scd0 > /dev/null".
The freezing happens on all DVD, totally randomly (it happens right away or after a few seconds on the same disk).
No message in the various logs.
The system even froze with a burned xubuntu CD.
I've just read 2 DVDs flawlessly with XP.
First I thought the drive was dead, but it seems to work with XP, so it might be a hal or a kernel problem. I don't mind the burning problem, but it's a real pain not be able to read a DVD on a laptop without damaging my hard drives...
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:
1) If you are comfortable installing packages on your own, the linux-image- 2.6.27- * package is currently available for you to install and test.
--or--
2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http:// www.ubuntu. com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.
Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.