Bug#592640: [linux-image-2.6.32-5-amd64] FTDI driver broken

[Joost Yervante Damad <andete@debian.org>]

On Thursday 12 August 2010 01:26:33 Ben Hutchings wrote:
> On Wed, 2010-08-11 at 19:11 +0200, Joost Yervante Damad wrote:
> > Package: linux-image-2.6.32-5-amd64
> > Version: 2.6.32-18
> > Severity: normal
> > 
> > --- Please enter the report below this line. ---
> > 
> > This version breaks the FTDI usb serial driver as is used to upload
> > software on an Arduino Duemilanove with avrdude.
> > 
> > Booting with an the older kernel linux-image-2.6.31-1-amd64
> > 2.6.31-2 it works again.
> > 
> > relevant parts of dmesg with failing kernel:
> > 
> > when plugging in:
> > 
> > [ 5849.356402] USB Serial support registered for FTDI USB Serial Device
> > [ 5849.356555] ftdi_sio 7-1:1.0: FTDI USB Serial Device converter
> > detected [ 5849.356625] usb 7-1: Detected FT232RL
> > [ 5849.356627] usb 7-1: Number of endpoints 2
> > [ 5849.356630] usb 7-1: Endpoint 1 MaxPacketSize 64
> > [ 5849.356632] usb 7-1: Endpoint 2 MaxPacketSize 64
> > [ 5849.356634] usb 7-1: Setting MaxPacketSize 64
> > [ 5849.358115] usb 7-1: FTDI USB Serial Device converter now attached to
> > ttyUSB0
> > [ 5849.358132] usbcore: registered new interface driver ftdi_sio
> > [ 5849.358134] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
> 
> And then there is a gap of 12 seconds, before:
> > [ 5861.333055] ftdi_sio ttyUSB0: ftdi_submit_read_urb - failed submitting
> > read urb, error -1
> 
> This error message appears whenever the device is closed (which is a
> bug, but a minor one).
> 
> > when trying to upload a new software sketch avrdude says this:
> > 
> > avrdude: stk500_recv(): programmer is not responding
> 
> Can you reproduce this, i.e. have you tried this several times and seen
> the same failure?

Yes, I tried it multiple times, even with a different arduino, I first thought I 
had an arduino with broken firmware.
Then I tried the same arduino on my netbook and it immediately worked.
Then I tried booting with the older kernel and it started working again on my 
main laptop also.

When I made the bugreport, I tried all this again to be sure and the behaviour 
remains the same.

If there's other things you'd like me to test, let me know. As this bug breaks 
basic Arduino development for me, it's quite annoying :)

Thanks, Joost