Dear Jonathan, I am sorry for not reporting back on this issue. Am Montag, den 06.08.2012, 00:27 -0700 schrieb Jonathan Nieder: > Jonathan Nieder wrote: > > Paul Menzel wrote: > > >> the mouse is not working after resuming from suspend to RAM. Replugging > >> the mouse works although that is quite inconvenient. > [...] > > - how does the 3.4.y kernel from experimental behave? > > - how does the 2.6.32.y kernel from stable behave? (It should work > > fine on a wheezy/sid system.) > > > > Beyond that, I have no great ideas, so if this is reproducible with > > 3.4.y, please send a summary of the symptoms to > > linux-usb@vger.kernel.org, cc-ing either me or this bug log so we can > > track it. Be sure to mention > > Ping. Did you get a chance to try a newer or older kernel, and if > so, what was the result? I contacted linux-usb@vger.kernel.org [1][2] and it looks like that the mouse and the ASUS M2A-VM do not get along. Currently the motherboard is replaced by a different board ASRock A780Full HD and the USB mouse works without any problems with it. I am not certain if I am going to have the chance to test this again with the ASUS M2A-VM. So maybe we should just close this bug as (currently) unreproducible or moreinfo? Thanks, Paul [1] http://www.spinics.net/lists/linux-usb/msg65853.html [2] http://www.spinics.net/lists/linux-usb/msg65903.html
Attachment:
signature.asc
Description: This is a digitally signed message part