Ubuntu
linux-source-2.6.15 package

cdrecord, gnomebaker, nautilus burner fail

Bug #15221 reported by audax321
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Ben Collins
Ubuntu ubuntu-6.06

Bug Description

I am reporting this bug regarding an attempt to burn an iso file on Ubuntu Hoary
final. While burning using either cdrecord, gnomebaker, or nautilus burner the
burn fails. Since all of these methods use cdrecord, I believe this to be the
conflicting package. Burning with cdrecord (cdrecord dev=/dev/hdc *.iso) from a
terminal window results in the following output (it hangs on the last line):

cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01a38 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg Schilling
NOTE: this version of cdrecord is an unofficial (modified) release of cdrecord
      and thus may have bugs that are not present in the original version.
      Please send bug reports and support requests to
<email address hidden>.
      The original author should not be bothered with problems of this version.

cdrecord: Warning: Running on Linux-2.6.10-5-686-smp
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'ubuntu-0.8ubuntu1'.
cdrecord: Warning: using unofficial version of libscg (ubuntu-0.8ubuntu1
'@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J. Schilling').
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'CENDYNE_'
Identifikation : '481648AX '
Revision : '150F'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-2 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
resid: 64508
resid: 64508
resid: 64512
cdrecord: Success. read buffer: scsi sendcmd: no error
CDB: 3C 00 00 00 00 00 00 FC 00 00
status: 0xb (Reserved)
Sense Bytes:
Sense Key: 0xFFFFFFFF [], Segment 0
Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
Sense flags: Blk 0 (not valid)
resid: 64512
cmd finished after 85.171s timeout 40s

The relevant output of dmesg during this process is:

attempt to access beyond end of device
hdc: rw=0, want=68, limit=4
attempt to access beyond end of device
hdc: rw=0, want=1252, limit=4
attempt to access beyond end of device
hdc: rw=0, want=1028, limit=4
UDF-fs: No partition found (1)
attempt to access beyond end of device
hdc: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: status error: error=0x00
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdc: request sense failure: error=0x50LastFailedSense 0x05
hdc: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdc: request sense failure: error=0x50LastFailedSense 0x05

Please see the URL attached to this bugzilla for a post on the Ubuntu Forums
regarding this issue
(http://www.ubuntuforums.org/showthread.php?t=25174&page=1&pp=10)

If it is at all possible please consider releasing an update to correct this
problem rather than just including it in the next release since there are others
with this problem and loss of cd burning can be a big inconvenience.

http://www.ubuntuforums.org/showthread.php?t=25174&page=1&pp=10: http://www.ubuntuforums.org/showthread.php?t=25174&page=1&pp=10

See original description
Revision history for this message
Adam Conrad (adconrad) wrote :

Can you still reproduce this bug?... The kernel messages look to me like it was
a dirty or dying CD drive, not a cdrecord issue. cdrecord has worked well for
me in both hoary and breezy.

Revision history for this message
audax321 (audax321) wrote :

(In reply to comment #1)
> Can you still reproduce this bug?... The kernel messages look to me like it was
> a dirty or dying CD drive, not a cdrecord issue. cdrecord has worked well for
> me in both hoary and breezy.
>

Yes, I still have this problem under Hoary and Breezy RC as well. Although the
output is a little different now. Now, the program hangs at the RESID:64512 line
and actually exited after a while. The dmesg output is a little different:

hdc: lost interrupt
cdrom_pc_intr, write: dev hdc: flags = REQ_STARTED REQ_PC REQ_FAILED REQ_QUIET
sector 0, nr/cnr 0/0
bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len 0
cdb: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
hdc: cdrom_pc_intr: The drive appears confused (ireason = 0x02)

I'm not so sure the drive is dying. I can read CDs fine and haven't had a
problem yet. Also, I can burn CDs in Windows as well as using Windows XP on
VMWare under Linux. I used this drive with SuSE over a year ago and used
cdrecord on there successfully (but that was kernel 2.4). The burner has just
never worked under Ubuntu.

Revision history for this message
Björn Janßen (b-janssen) wrote :

I've got the same problem, although i am using a clean 5.10. cdrecord is not
working and consequently all frontends, including nautilus-cd-burner, fail. I
also can exclude a failing CD-Burner, it is working perfectly under Debian Sarge
(with custom kernel w/o SCSI emulation) on the same machine.

If you need more info, feel free to contact me.

Revision history for this message
Adam Conrad (adconrad) wrote :

Based on all the comments to this bug showing some pretty fun dmesg output, I'm
reassigning this to the kernel. We either have a case of the kernel dealing
poorly with sketchy drives, or drives disliking how the kernel is driving them,
I think, but I'm no expert on CD packet writing.

Revision history for this message
Ben Collins (ben-collins) wrote :

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

Revision history for this message
Ben Collins (ben-collins) wrote :

If possible, please upgrade to Dapper's 2.6.15-7 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Revision history for this message
Carthik Sharma (carthik) wrote :

Thank you for reporting this bug and following up on it.

I am marking this bug Closed since there has been no response from you for over three months. We
would like to fix all existing issues, but need need feedback to help with debugging.

Should you still have a problem with the latest up to date Dapper kernel and packages, please reopen this bug, answering the questions that have already been asked of you before.

Thanks again, please report any other issues you have after checking that they haven't already been reported.

Changed in linux-source-2.6.15:
status: Needs Info → Rejected
Revision history for this message
Stefano Costa (steko) wrote : Re: [Bug 15221] Re: cdrecord, gnomebaker, nautilus burner fail

I really had no time to dig on this, sorry. but since I have problems with
reading audio cds too I feel like it's something between my cd drive and the
kernel. I do believe this is solved in 2.6.15, as you pointed out. Thanks

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.