Bug#678215: USB mouse not recognized after resuming from suspend to RAM
 

reassign 678215 src:linux 3.2.20-1
quit

Hi Paul,

Paul Menzel wrote:

> after replacing a broken PS/2 mouse, which worked fine before that, with
> an USB mouse
[...]
> Bus 003 Device 003: ID 1241:1122 Belkin Typhoon Stream Optical Mouse USB+PS/2
>
> the mouse is not working after resuming from suspend to RAM. Replugging
> the mouse works although that is quite inconvenient.
[...]
> I used that mouse on an ASUS EeePC 701 4G with outdated Debian
> Sid/unstable and Linux 3.0.0 without problems.

Thanks for reporting it. I'd be curious to hear:

- 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

- steps to reproduce, expected result, actual result, and how the
difference indicates a bug
- which kernel versions you have tested and what happened with each
- full "dmesg" output from booting and reproducing the problem with
an affected kernel
- full "lsusb -v" output
- any other weird symptoms or workarounds

Hopefully someone upstream will have ideas for debugging this from
there.

Hope that helps,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120626223505.GA7042@burratino

Bug#678215: USB mouse not recognized after resuming from suspend to RAM
 

Hi again,

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?

In suspense,
Jonathan


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120806072724.GA27874@mannheim-rule.local

Bug#678215: USB mouse not recognized after resuming from suspend to RAM
 

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

Bug#678215: USB mouse not recognized after resuming from suspend to RAM
 

retitle 678215 ASUS M2A-VM: USB mouse not recognized after resume from suspend to RAM
forwarded 678215 http://thread.gmane.org/gmane.linux.usb.general/66109
tags 678215 = unreproducible
quit

Paul Menzel wrote:

> I am sorry for not reporting back on this issue.

No problem. Thanks for the update.

[...]
> 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.

Alan suggested that using a different mouse might work. Did you try
that?

Thanks,
Jonathan


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120806155736.GA28290@mannheim-rule.local