DVDs and CDs do not mount and drive is seen as empty after media is inserted.

[executorvs]

Binary package hint: gvfs

I'm running Karmic from a fresh install with all current updates as of 11:30PM central standard in the US 9/28/09.
this problem is present in Jaunty as well.
my computer is an acer aspire timeline 5810TZ-4274.
The lshw output for the drive empty is:
*-cdrom
       description: DVD-RAM writer
       product: DVD-RAM UJ862AS
       vendor: MATSHITA
       physical id: 1
       bus info: scsi@4:0.0.0
       logical name: /dev/cdrom
       logical name: /dev/cdrw
       logical name: /dev/dvd
       logical name: /dev/dvdrw
       logical name: /dev/scd0
       logical name: /dev/sr0
       version: 1.10
       capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
       configuration: ansiversion=5 status=nodisc

after inserting media (karmic daily from which I installed) lshw freezes while running "sudo lshw -C drives".

dmesg for the period outputs:
[ 4301.527235] ata5: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
[ 4301.527242] ata5: irq_stat 0x40000001
[ 4334.000060] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 4334.000075] ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 4334.000076] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 4334.000078] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[ 4334.000083] ata5.00: status: { DRDY }
[ 4334.000089] ata5: hard resetting link
[ 4339.864105] ata5: failed to reset engine (errno=-5)
[ 4344.004096] ata5: softreset failed (device not ready)
[ 4344.004103] ata5: hard resetting link
[ 4349.868101] ata5: failed to reset engine (errno=-5)
[ 4354.008102] ata5: softreset failed (device not ready)
[ 4354.008109] ata5: hard resetting link
[ 4359.872100] ata5: failed to reset engine (errno=-5)
[ 4365.076104] ata5: link is slow to respond, please be patient (ready=0)
[ 4389.048106] ata5: softreset failed (device not ready)
[ 4389.048115] ata5: limiting SATA link speed to 1.5 Gbps
[ 4389.048119] ata5: hard resetting link
[ 4394.576116] ata5: failed to reset engine (errno=-5)
[ 4440.520115] INFO: task hald-addon-stor:918 blocked for more than 120 seconds.
[ 4440.520121] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4440.520124] hald-addon-st D c080b3a0 0 918 773 0x00000000
[ 4440.520131] f408bb8c 00000086 f6861558 c080b3a0 f42b8298 c080b3a0 09ca264f 000003ea
[ 4440.520140] c080b3a0 c080b3a0 f42b8298 c080b3a0 09c943bd 000003ea c080b3a0 f65748c0
[ 4440.520149] f42b8000 f408bc3c 7fffffff f408bc40 f408bbe8 c0569b15 f694e800 f683f5f8
[ 4440.520157] Call Trace:
[ 4440.520167] [<c0569b15>] schedule_timeout+0x185/0x200
[ 4440.520174] [<c030d25d>] ? kobject_put+0x1d/0x50
[ 4440.520181] [<c03adb98>] ? scsi_dispatch_cmd+0x158/0x260
[ 4440.520186] [<c030251e>] ? blk_add_timer+0x6e/0xc0
[ 4440.520192] [<c056b243>] ? _spin_lock_irq+0x13/0x20
[ 4440.520197] [<c03b3c43>] ? scsi_request_fn+0xc3/0x4b0
[ 4440.520202] [<c0569832>] wait_for_common+0xa2/0x120
[ 4440.520208] [<c0137c50>] ? default_wake_function+0x0/0x10
[ 4440.520213] [<c0569942>] wait_for_completion+0x12/0x20
[ 4440.520218] [<c03017f5>] blk_execute_rq+0x75/0xd0
[ 4440.520223] [<c03016b0>] ? blk_end_sync_rq+0x0/0x30
[ 4440.520229] [<c02fe31d>] ? get_request_wait+0x1d/0x160
[ 4440.520235] [<c01f1bc0>] ? pollwake+0x0/0x60
[ 4440.520240] [<c056b243>] ? _spin_lock_irq+0x13/0x20
[ 4440.520245] [<c03b3c43>] ? scsi_request_fn+0xc3/0x4b0
[ 4440.520250] [<c02fe85b>] ? blk_get_request+0x5b/0x80
[ 4440.520255] [<c03b50d2>] scsi_execute+0xb2/0x140
[ 4440.520261] [<c03b5305>] scsi_execute_req+0x85/0x140
[ 4440.520266] [<c03c16a3>] sr_test_unit_ready+0x63/0xd0
[ 4440.520272] [<c03c2631>] sr_media_change+0x61/0x160
[ 4440.520277] [<c02fdb59>] ? __blk_put_request+0x79/0xb0
[ 4440.520283] [<c03ff1a2>] media_changed+0x62/0xa0
[ 4440.520287] [<c03ff20f>] cdrom_media_changed+0x2f/0x40
[ 4440.520292] [<c03c1901>] sr_block_media_changed+0x11/0x20
[ 4440.520298] [<c0209b21>] check_disk_change+0x21/0x60
[ 4440.520303] [<c0401f0f>] cdrom_open+0xdf/0x1c0
[ 4440.520308] [<c030d3c2>] ? kobject_get+0x12/0x20
[ 4440.520313] [<c0303781>] ? get_disk+0x41/0x70
[ 4440.520317] [<c03037ba>] ? exact_lock+0xa/0x20
[ 4440.520322] [<c030d3c2>] ? kobject_get+0x12/0x20
[ 4440.520327] [<c03c1a68>] sr_block_open+0x58/0xa0
[ 4440.520332] [<c03c1a10>] ? sr_block_open+0x0/0xa0
[ 4440.520337] [<c020ad99>] __blkdev_get+0x1a9/0x310
[ 4440.520343] [<c0482550>] ? apparmor_file_alloc_security+0x20/0x90
[ 4440.520349] [<c020af0a>] blkdev_get+0xa/0x10
[ 4440.520354] [<c020af6e>] blkdev_open+0x5e/0xb0
[ 4440.520360] [<c01e0dd9>] __dentry_open+0xb9/0x230
[ 4440.520365] [<c01e1035>] nameidata_to_filp+0x55/0x70
[ 4440.520370] [<c020af10>] ? blkdev_open+0x0/0xb0
[ 4440.520375] [<c01eeb6a>] do_filp_open+0x53a/0x890
[ 4440.520380] [<c056b507>] ? unlock_kernel+0x27/0x30
[ 4440.520385] [<c039aa9f>] ? put_device+0xf/0x20
[ 4440.520390] [<c01f5660>] ? iput+0x20/0x60
[ 4440.520396] [<c01e0b70>] do_sys_open+0x50/0x150
[ 4440.520402] [<c0160a81>] ? do_gettimeofday+0x11/0x40
[ 4440.520407] [<c01e0cd9>] sys_open+0x29/0x40
[ 4440.520412] [<c010334c>] syscall_call+0x7/0xb
[ 4440.520424] INFO: task devkit-disks-da:1490 blocked for more than 120 seconds.
[ 4440.520427] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4440.520430] devkit-disks- D c080b3a0 0 1490 1488 0x00000000
[ 4440.520436] f3cafdf8 00000082 00000000 c080b3a0 f65473a8 c080b3a0 09d791c3 000003ea
[ 4440.520444] c080b3a0 c080b3a0 f65473a8 c080b3a0 09d74436 000003ea c080b3a0 f6a29180
[ 4440.520452] f6547110 f6d88610 f6d88614 ffffffff f3cafe24 c056a1b6 c0303440 f6d88618
[ 4440.520459] Call Trace:
[ 4440.520465] [<c056a1b6>] __mutex_lock_slowpath+0xc6/0x130
[ 4440.520470] [<c0303440>] ? exact_match+0x0/0x10
[ 4440.520475] [<c056a0d0>] mutex_lock+0x20/0x40
[ 4440.520480] [<c020ac1f>] __blkdev_get+0x2f/0x310
[ 4440.520486] [<c0482550>] ? apparmor_file_alloc_security+0x20/0x90
[ 4440.520491] [<c020af0a>] blkdev_get+0xa/0x10
[ 4440.520496] [<c020af6e>] blkdev_open+0x5e/0xb0
[ 4440.520502] [<c01e0dd9>] __dentry_open+0xb9/0x230
[ 4440.520507] [<c01e1035>] nameidata_to_filp+0x55/0x70
[ 4440.520512] [<c020af10>] ? blkdev_open+0x0/0xb0
[ 4440.520516] [<c01eeb6a>] do_filp_open+0x53a/0x890
[ 4440.520522] [<c056b21a>] ? _spin_lock_irqsave+0x2a/0x40
[ 4440.520527] [<c039aa9f>] ? put_device+0xf/0x20
[ 4440.520532] [<c01f5660>] ? iput+0x20/0x60
[ 4440.520537] [<c01e0b70>] do_sys_open+0x50/0x150
[ 4440.520542] [<c0160a81>] ? do_gettimeofday+0x11/0x40
[ 4440.520547] [<c01e0cd9>] sys_open+0x29/0x40
[ 4440.520552] [<c010334c>] syscall_call+0x7/0xb

ProblemType: Bug
Architecture: i386
Date: Mon Sep 28 23:24:03 2009
DistroRelease: Ubuntu 9.10
Package: gvfs 1.4.0-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: gvfs
Uname: Linux 2.6.31-11-generic i686

[Chris Coulson (chrisccoulson)]

The information provided suggests this is more likely a kernel issue rather than gvfs

[executorvs (executorvs)]

still an issue in current beta with updates.

[penalvch (penalvch)]

executorvs, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]