Bug#293953: cdrecord: Still present in wodim

2006-10-07 Thread Byron Clark
On Thu, Oct 05, 2006 at 09:22:04AM +0200, Eduard Bloch wrote:
 Thank you. However I don't think it is really resolved. Something still
 goes wrong in the communication between wodim and the kernel, otherwise
 we would not have to wait so long.

What happens is that the first read_buffer command issued in
get_dmaspeed (cdrecord/cdrecord.c:4143) causes a timeout.  In older
versions of cdrecord this timeout was never reported as an error and so
the get_dmaspeed function ran for almost 60 minutes.

 What happens if you attach this drive to the IDE bus directly? Maybe it
 is a drive failure. Or maybe a wodim/cdrecord problem, independent from
 the kernel.

I'm sorry, I only have a laptop and an nslu2 here so I don't have
anywhere to easily plug the drive into an IDE chain.

--
Byron Clark


signature.asc
Description: Digital signature


Bug#293953: cdrecord: Still present in wodim

2006-10-05 Thread Eduard Bloch
#include hallo.h
* Byron Clark [Wed, Oct 04 2006, 09:23:35PM]:
 On Wed, Oct 04, 2006 at 06:10:47PM +0200, Eduard Bloch wrote:
  #include hallo.h
  * Byron Clark [Tue, Oct 03 2006, 10:34:57PM]:
   Package: cdrecord
   Followup-For: Bug #293953
   
   
   This bug is still present in latest wodim in testing.
  
  Well, well, well, then we should try to isolate the trouble maker.
  
  Please report which USB middleware you are using (lsusb).
  
  Could you borrow another USB case somewhere and try with that? Because I
  can burn CDs without any problems with wodim and the cheapest noname USB
  adapter here.
  
  Can you reproduce the problem with kernel 2.4.x kernels?
 
 After further testing (and a little more patience) I can report that
 this bug _is_ resolved in the latest wodim.  I have to wait 40 seconds
 for the burn process to start, but after the 40 seconds everything works
 as expected.

Thank you. However I don't think it is really resolved. Something still
goes wrong in the communication between wodim and the kernel, otherwise
we would not have to wait so long.

What happens if you attach this drive to the IDE bus directly? Maybe it
is a drive failure. Or maybe a wodim/cdrecord problem, independent from
the kernel.

I hope on your help.

Eduard.

-- 
Kunst im überlieferten Sinne gibt es nicht mehr. Es gibt nur noch
kurzlebige modische Einfälle, denen man das Etikett Kunst aufklebt.
-- Giorgio de Chirico


signature.asc
Description: Digital signature


Bug#293953: cdrecord: Still present in wodim

2006-10-04 Thread Eduard Bloch
#include hallo.h
* Byron Clark [Tue, Oct 03 2006, 10:34:57PM]:
 Package: cdrecord
 Followup-For: Bug #293953
 
 
 This bug is still present in latest wodim in testing.

Well, well, well, then we should try to isolate the trouble maker.

Please report which USB middleware you are using (lsusb).

Could you borrow another USB case somewhere and try with that? Because I
can burn CDs without any problems with wodim and the cheapest noname USB
adapter here.

Can you reproduce the problem with kernel 2.4.x kernels?

Eduard.

-- 
Der Geist ist willig, vom Fleisch ganz zu schweigen.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#293953: cdrecord: Still present in wodim

2006-10-04 Thread Byron Clark
On Wed, Oct 04, 2006 at 06:10:47PM +0200, Eduard Bloch wrote:
 #include hallo.h
 * Byron Clark [Tue, Oct 03 2006, 10:34:57PM]:
  Package: cdrecord
  Followup-For: Bug #293953
  
  
  This bug is still present in latest wodim in testing.
 
 Well, well, well, then we should try to isolate the trouble maker.
 
 Please report which USB middleware you are using (lsusb).

Bus 003 Device 001: ID :  
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed hub
  bMaxPacketSize064
  idVendor   0x 
  idProduct  0x 
  bcdDevice2.06
  iManufacturer   3 Linux 2.6.17-2-686 uhci_hcd
  iProduct2 UHCI Host Controller
  iSerial 1 :00:1d.2
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   25
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed hub
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0002  1x 2 bytes
bInterval 255
Hub Descriptor:
  bLength   9
  bDescriptorType  41
  nNbrPorts 2
  wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
  bPwrOn2PwrGood1 * 2 milli seconds
  bHubContrCurrent  0 milli Ampere
  DeviceRemovable0x00
  PortPwrCtrlMask0xff
 Hub Port Status:
   Port 1: .0100 power
   Port 2: .0100 power
Device Status: 0x0003
  Self Powered
  Remote Wakeup Enabled

Bus 002 Device 002: ID 03ee: Mitsumi CD-R/RW Drive
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x03ee Mitsumi
  idProduct  0x CD-R/RW Drive
  bcdDevice2.47
  iManufacturer   1 MITSUMI Electric Co.,Ltd.
  iProduct2 USB CD-R/RW Drive
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   39
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xc0
  Self Powered
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  2 SFF-8020i, MMC-2 (ATAPI)
  bInterfaceProtocol  0 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0002  1x 2 bytes
bInterval   1
Device Status: 0x0001
  Self Powered

Bus 002 Device 001: ID :  
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol  

Bug#293953: cdrecord: Still present in wodim

2006-10-04 Thread Byron Clark
On Wed, Oct 04, 2006 at 06:10:47PM +0200, Eduard Bloch wrote:
 #include hallo.h
 * Byron Clark [Tue, Oct 03 2006, 10:34:57PM]:
  Package: cdrecord
  Followup-For: Bug #293953
  
  
  This bug is still present in latest wodim in testing.
 
 Well, well, well, then we should try to isolate the trouble maker.
 
 Please report which USB middleware you are using (lsusb).
 
 Could you borrow another USB case somewhere and try with that? Because I
 can burn CDs without any problems with wodim and the cheapest noname USB
 adapter here.
 
 Can you reproduce the problem with kernel 2.4.x kernels?

After further testing (and a little more patience) I can report that
this bug _is_ resolved in the latest wodim.  I have to wait 40 seconds
for the burn process to start, but after the 40 seconds everything works
as expected.

--
Byron Clark


signature.asc
Description: Digital signature


Bug#293953: cdrecord: Still present in wodim

2006-10-03 Thread Byron Clark
Package: cdrecord
Followup-For: Bug #293953


This bug is still present in latest wodim in testing.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]