[Bug 226019] New: CD burning on external USB recorder does not work
https://bugzilla.novell.com/show_bug.cgi?id=226019 Summary: CD burning on external USB recorder does not work Product: openSUSE 10.2 Version: RC 5 Platform: i686 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: nadvornik@novell.com QAContact: qa@suse.de wodim (and cdrecord) fail to burn on external USB burner via /dev/sg0 The problem is following: - wodim reads the bufer size with SG_GET_RESERVED_SIZE, it returns 32K - wodim tries to set the buffer size to 128K via SG_SET_RESERVED_SIZE. - following SG_GET_RESERVED_SIZE returns 128K - the scsi commands that needs 128K buffer (write_g1) fails with ENOMEM, it seems that the real buffer size is still 32K This seems to be the same problem: http://marc.theaimsgroup.com/?l=linux-kernel&m=116233257826906&w=2 Burning via /dev/sr0 on the same device works without problems, SG_GET_RESERVED_SIZE returns 32K even after the try to set it to 128K. Using /dev/sr0 is probably not the correct fix, because wodim and k3b uses /dev/sg0 by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #1 from nadvornik@novell.com 2006-12-05 05:02 MST ------- Created an attachment (id=108313) --> (https://bugzilla.novell.com/attachment.cgi?id=108313&action=view) hwinfo --all -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #2 from nadvornik@novell.com 2006-12-06 03:51 MST ------- /dev/sg seems to be broken even more. Option ts=32k can be used as a workaround for the original problem, however it fails later. See the attached logs. The only difference is the used device, /dev/sg0 vs. /dev/sr0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #3 from nadvornik@novell.com 2006-12-06 03:52 MST ------- Created an attachment (id=108484) --> (https://bugzilla.novell.com/attachment.cgi?id=108484&action=view) log_fail -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #4 from nadvornik@novell.com 2006-12-06 03:53 MST ------- Created an attachment (id=108485) --> (https://bugzilla.novell.com/attachment.cgi?id=108485&action=view) log_ok -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #5 from nadvornik@novell.com 2006-12-06 03:55 MST ------- Created an attachment (id=108486) --> (https://bugzilla.novell.com/attachment.cgi?id=108486&action=view) diff of the logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 nadvornik@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkukawka@suse.de ------- Comment #6 from nadvornik@novell.com 2006-12-07 06:29 MST ------- The problem in comment #2 is caused by hal check for changed media. I am not sure if it is a generic problem or just a bug in LG firmware. Anyway, when I kill the hal process that monitors the device, burning starts to work. Both hal and wodim uses O_EXCL lock, but it does not help because the lock is not shared between sg and sr. IMHO the clean fix is to make the lock shared. Is it possible? Bug 223165 is probably related. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |hare@novell.com |maintainers@forge.provo.nove| |ll.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 hare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hare@novell.com |kasievers@novell.com ------- Comment #7 from hare@novell.com 2006-12-15 01:41 MST ------- I wouldn't know. Reassigning to the HAL folks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 kasievers@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kasievers@novell.com |dkukawka@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 nadvornik@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-maintainers@forge.provo.novell.com Status|NEEDINFO |ASSIGNED Info Provider|nadvornik@novell.com | ------- Comment #9 from nadvornik@novell.com 2006-12-18 03:48 MST ------- /dev/sg0 and /dev/sr0 is the same device accessed via different kernel drivers, if I understand it correctly. Therefore if wodim opens /dev/sg0 with O_EXCL, it does not prevent HAL access the device via /dev/sr0. The checks in HAL interrupts the recording process, at least with LG recorders. If wodim is called with /dev/sr0, it stops HAL query the device and everything works OK. However k3b calls wodim with dev=0,0,0 which is translated to /dev/sg0. possible fixes: 1) make the O_EXCL shared between the devices in kernel (IMHO correct fix) 2) open both devices with O_EXCL in HAL before running the checks (IMHO the easiest fix) 3) use /dev/sr0 instead of dev=0,0,0 in k3b (partial fix) 4) translate dev=0,0,0 to /dev/sr0 in wodim (ugly hack) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |nadvornik@novell.com ------- Comment #10 from gregkh@novell.com 2006-12-20 16:31 MST ------- Hm, care to show what you mean by the fix 1) above? Why isn't this an issue with the upstream kernel.org releases? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|dkukawka@suse.de |dkukawka@novell.com AssignedTo|dkukawka@novell.com |kernel-maintainers@forge.provo.novell.com Status|NEEDINFO |NEW Info Provider|nadvornik@novell.com | ------- Comment #11 from dkukawka@novell.com 2007-01-08 12:27 MST ------- IMO case 2 (fix in HAL) is not the best idea, because HAL does not care about the second device. IMO this would be only a workaround. I reassign this to the kernel guys. The first proposal in the list would be IMO the better solution. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #12 from nadvornik@novell.com 2007-01-09 03:45 MST ------- Greg: I have no idea how to fix it in kernel, but the current kernel behavior is quite surprising and requires special hacks in userspace. Upstream kernel has the same problem. However it appears only in combination with HAL and LG drives. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |dkukawka@novell.com |maintainers@forge.provo.nove| |ll.com | ------- Comment #13 from lmb@novell.com 2007-01-09 11:23 MST ------- Uhm, you're supposed to use /dev/sr0 if you want to access it as a SCSI CD/DVD drive, not /dev/sg0. The semantics are different, and they are different devices! Note that /dev/sg0 refers to the first generic SCSI device; which might as well be the first physical disk /dev/sda or another SCSI device. And if you're accessing /dev/sr0 or /dev/sda, you're not supposed to access the corresponding generic device. This isn't a kernel bug, but seems to be a mistake in how hal handles things. Reassigning to hal maintainer. And yes, k3b should use /dev/sr0 and not /dev/sg0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 dkukawka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dkukawka@novell.com |kde-maintainers@suse.de Component|Kernel |KDE ------- Comment #14 from dkukawka@novell.com 2007-01-09 13:14 MST ------- but as you can read in comment #9 HAL open as you suppose, if I understand correct, /dev/sr0. So this looks like a problem in k3b and not HAL. Because of this it looks to me like a problem in k3b ... reassing to KDE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nadvornik@novell.com ------- Comment #15 from coolo@novell.com 2007-01-10 01:57 MST ------- I wonder how k3b got in the play. Vladimir - is this limited to k3b? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #16 from coolo@novell.com 2007-01-10 02:15 MST ------- My k3b uses /dev/sr0 btw - but that is for my internal DVD-RW -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 nadvornik@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nadvornik@novell.com | ------- Comment #17 from nadvornik@novell.com 2007-01-10 03:22 MST ------- k3b on 10.2 calls wodim (via cdrecord symlink) with dev=0,0,0 by default. wodim maps it to /dev/sg0. I agree /dev/sr0 should be used everywhere. However, specifying device with dev=0,0,0 which is mapped to /dev/sg0 is the way how cdrecord always worked and it probably won't be easy to drop it from all scripts and frontends, especially when the original cdrecord from Joerg Schilling prints a warning about using the device directly. IMHO we should make /dev/sg0 work too, for compatibility. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #18 from coolo@novell.com 2007-01-10 04:05 MST ------- that is also what is returned from cdrecord -scanbus, no? And it's also what is in all my personal cdrecord scripts. So either wodim needs to fix this or the kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|kernel- | |maintainers@forge.provo.nove| |ll.com | ------- Comment #19 from lmb@novell.com 2007-01-10 04:37 MST ------- Sorry, if you want the device to be accessed like a CD drive, you must use /dev/sr0. And accessing the SCSI generic device concurrently with the block device as well is a user-space error. This simply isn't a kernel bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 nadvornik@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lmb@novell.com ------- Comment #20 from nadvornik@novell.com 2007-01-10 05:36 MST ------- cdrecord -scanbus and dev=X,X,X is supposed to work with SCSI generic, there is nothing to fix. The only way to change it is to call wodim(cdrecord) with dev=/dev/sr0. Lars, do you mean that kernel does not support CD burning via /dev/sg ? Since when? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lmb@novell.com | ------- Comment #21 from lmb@novell.com 2007-01-11 04:45 MST ------- Well, /dev/sg will mostly work as well. The keypoint is that user-space must not access the sg and the sd/sr device concurrently, as it appears to be doing here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #22 from nadvornik@novell.com 2007-01-11 08:42 MST ------- OK, so my proposal is: 1. use dev=/dev/sr in k3b (and other frontends and scripts) as a correct long-term solution. 2. open both devices with O_EXCL in HAL - for compatibility with unfixed 3rd-party frontends and scripts, it can be also released as an update for 10.2. Reasons why it should be fixed in HAL: - users don't expect that HAL accesses the device, it's hard to debug the failures - in theory it could break other programs too, for example firmware updaters -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #23 from dkukawka@novell.com 2007-01-11 10:15 MST ------- I don't see why HAL should open both devices. HAL only know about sr0 and only touch this device file. How should HAL know that it maybe should open any sgX and sgX device with O_EXCL. If this is really needed the kernel should share the O_EXCL between the both device files if one get locked. The point is: this can also happen if there is no HAL if two application/programms open the both devices independently. And if the user expect that HAL provide hardwareinformation and if a media get inserted or the eject button get pressed the user can also expect that HAL need to access the device for this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 nadvornik@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lavrinenko_alex@mail.ru ------- Comment #24 from nadvornik@novell.com 2007-01-17 03:34 MST ------- *** Bug 223165 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 nadvornik@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |goddang@hotmail.com ------- Comment #25 from nadvornik@novell.com 2007-01-17 03:40 MST ------- *** Bug 208995 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 nadvornik@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical Summary|CD burning on external USB |CD burning via /dev/sg does not work with some |recorder does not work |burners ------- Comment #26 from nadvornik@novell.com 2007-01-24 12:02 MST ------- It could become much more serious with libata for IDE in 10.3, increasing severity. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 dmueller@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|CD burning via /dev/sg does |[k3b] CD burning via /dev/sg does not work with |not work with some burners |some burners -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 dmueller@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major Status|NEW |ASSIGNED ------- Comment #27 from dmueller@novell.com 2007-01-26 03:01 MST ------- for 10.3 this should not be an issue at all as the bug is already fixed for 10.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 trueg@k3b.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #30 from trueg@k3b.org 2007-02-16 02:47 MST ------- K3b 1.0 uses the block device instead the generic device on kernel >= 2.6. Thus, this problem should not occur anymore. The reason, Joerg Schilling recommends using the generic devices is probably his preference of the Solaris system. He still claims it is a linux kernel bug and that both variants should work equally. I personally lack the deep kernel knowledge to comment on this and am happy that the block device works properly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #31 from nadvornik@novell.com 2007-03-14 09:56 MST ------- The same bug in debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413960 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226019 ------- Comment #32 from nadvornik@novell.com 2007-04-24 05:46 MST ------- Since 1.1.4 wodim maps dev=X,X,X to /dev/sr where possible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com