Matthew Dillon wrote:
 >     Ok, this is definitely the same bug as issue 1016 and I've got it
 >     reproduced and will be committing a fix today.

I think you already found the bug. It is definitively related to CAM,
because for some reason, after I cvs-updated my sources and those CAM
changes came in (for some reasons they came in after I committed the usb
changes), the error started to appeared.

Thanks! This fix allows me to start with the real USB changes.

Regards,

   Michael