[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#416388: linux-source-2.6.18: Wodim hangs and system may freeze



Now on kernel 2.6.22 and still getting the same problem.

I do:
~$ wodim dev=/dev/cdrw "/data/Our Old Documents 2005-07 oncd"

I get:

wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.Device type : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'SAMSUNG '
Identification : 'CDRW/DVD SM-308B'
Revision       : 'M002'
Device seems to be: Generic mmc2 DVD-ROM.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-2 SWABAUDIO
Supported modes: TAO PACKET SAO SAO/R96R RAW/R16 RAW/R96R
Segmentation fault

Syslog reads after the hang:

Dec 12 08:45:11 localhost kernel: hdc: irq timeout: status=0xd0 { Busy }
Dec 12 08:45:11 localhost kernel: ide: failed opcode was: unknown
Dec 12 08:45:11 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Dec 12 08:45:11 localhost kernel: ide: failed opcode was: unknown
Dec 12 08:45:11 localhost kernel: hdc: drive not ready for command
Dec 12 08:45:11 localhost kernel: Clocksource tsc unstable (delta = 4687083277 ns)
Dec 12 08:45:11 localhost kernel: Time: acpi_pm clocksource has been installed.
Dec 12 08:45:14 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Dec 12 08:45:14 localhost kernel: ide: failed opcode was: unknown
Dec 12 08:45:14 localhost kernel: hdc: drive not ready for command
Dec 12 08:45:19 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Dec 12 08:45:19 localhost kernel: ide: failed opcode was: unknown
Dec 12 08:45:19 localhost kernel: hdc: drive not ready for command
Dec 12 08:45:24 localhost kernel: hdc: status timeout: status=0xd0 { Busy }
Dec 12 08:45:24 localhost kernel: ide: failed opcode was: unknown
Dec 12 08:45:24 localhost kernel: hdc: drive not ready for command

etc.

Is there any reason to think that 2.6.23 would be any different? (I am using the testing distribution, I would rather not get involved in backporting.)

John




Reply to: