On Sun, 2011-05-15 at 17:19 +0000, Peter . wrote: > Ben, > > I pointed apt to squeeze and fetched the 2.6.32-5-amd64 image and the > issue persists. For these logs I've swapped the video to point to > vesa (instead of tainting nvidia drivers), but I don't think it going > to be relevant. > > I've attached the output from dmesg in this environment as requeasted > - I don't think this is logging all of the events of interest, so I > have also attached kern and xorg logs. There are logs of interest in > kern.log where usb device fail to be configured (error -71), and it > also looks like both usb 6-2 and generic-usb are trying to handle the > device. 'usb 6-2' is the address that Linux assigned to the device. The messages with these prefix are generated by the USB core, not a driver. > I think we've ruled out that an issue was introduced between 2.6.32 > and 2.6.38 kernel. Please let me know if you have any suggestions or > if there's anything else I can do to help diagnose. Agreed. Please report this bug upstream at <https://bugzilla.kernel.org> under product 'Drivers', component 'Input Devices'. Include the kernel log from Linux 2.6.38 and the fact that the behaviour under 2.6.32 is the same. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Description: This is a digitally signed message part