Steelseries Xai mouse causing slow resume from suspend

[Cas]

It was taking nearly 30seconds to resume from suspend while testing Oneiric 11.10. I unplugged my Steelseries Xai mouse and it only took 6secs to resume.

I ran a pm_trace I got the warning below with the mouse plugged in. This warning does not appear with the mouse unplugged.

[ 489.862512] ------------[ cut here ]------------
[ 489.862519] WARNING: at /build/buildd/linux-3.0.0/kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90()
[ 489.862522] Hardware name: Precision M4300
[ 489.862523] Component: resume devices, time: 27324
[ 489.862525] Modules linked in: usbhid hid rfcomm bnep vesafb nvidia(P) snd_hda_codec_idt binfmt_misc snd_hda_intel snd_hda_codec snd_usb_audio snd_hwdep snd_usbmidi_lib pata_pcmcia snd_pcm snd_seq_midi snd_seq_midi_event arc4 iwl3945 snd_seq ati_remote uvcvideo videodev snd_timer snd_rawmidi v4l2_compat_ioctl32 iwl_legacy pcmcia snd_seq_device joydev mac80211 snd btusb soundcore snd_page_alloc yenta_socket dell_laptop cfg80211 bluetooth pcmcia_rsrc dell_wmi dcdbas ppdev pcmcia_core sparse_keymap psmouse serio_raw parport_pc wmi video acpiphp lp parport usb_storage uas firewire_ohci firewire_core crc_itu_t tg3
[ 489.862564] Pid: 3063, comm: pm-suspend Tainted: P 3.0.0-12-generic #19-Ubuntu
[ 489.862566] Call Trace:
[ 489.862572] [<ffffffff8105e83f>] warn_slowpath_common+0x7f/0xc0
[ 489.862575] [<ffffffff8105e936>] warn_slowpath_fmt+0x46/0x50
[ 489.862578] [<ffffffff810a23d6>] suspend_test_finish+0x86/0x90
[ 489.862581] [<ffffffff810a20da>] suspend_devices_and_enter+0xca/0x1b0
[ 489.862584] [<ffffffff810a22dd>] enter_state+0x11d/0x150
[ 489.862586] [<ffffffff810a1707>] state_store+0xb7/0xf0
[ 489.862590] [<ffffffff812e997f>] kobj_attr_store+0xf/0x30
[ 489.862595] [<ffffffff811d6c9f>] sysfs_write_file+0xef/0x170
[ 489.862599] [<ffffffff81167813>] vfs_write+0xb3/0x180
[ 489.862601] [<ffffffff81167b3a>] sys_write+0x4a/0x90
[ 489.862606] [<ffffffff815f22c2>] system_call_fastpath+0x16/0x1b
[ 489.862608] ---[ end trace 062d645a09a21691 ]---

[Cas (calumlind)]

Testing some more seems to reveal that the mouse takes much longer to be detected than is normal when plugging it in which I had not noticed before.

I have found a similar bug on debian which points to this being a kernel issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628750

[Vadim Rutkovsky (roignac)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 863504
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Cas (calumlind)]

Just to update this, it appears to be an issue with Xai mice due to its hardware not responding either correctly or too slowly.

I have found that it is not isolated to Linux as under Windows upon booting it takes an extra 30secs however it does not affect resuming from standby.

[Cas (calumlind)]

I don't know why people insist on trying to close this, it is still a bug in resuming from standby.

I would rather my desktop was fully loaded and simply waiting for the mouse rather than waiting 30secs for the mouse and then wait again for the desktop to load.

[Daniel van Vugt (vanvugt)]

This bug is in a broken state and launchpad is timing out instead of letting me fix it. I also probably don't have enough permission to fix it fully...

Instead of:
    linux (Ubuntu) New Unknown debbugs #628750

It should say:
    linux (Debian) New Unknown debbugs #628750
    linux (Ubuntu) Confirmed Unknown Unassigned

[Evan Peck (colors)]

This error is not specific to Ubuntu as calumlind said.
this seems to be a problem with the hardware of the mouse itself that is causing compatibilty issues.
I'd contact Steelseries customer support.

For now I think this should be Incomplete,
I will mark it as so,
because this is not a problem with Ubuntu.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Please contact customer support of the manufacturer of the accessory for further information.

[Simplehuman (simplehuman)]

Why it is in Ubuntu "Fix Released", but in linux (Ubuntu) status is "New"?
Why Bug Watch Updater change it back? I am a user of Steelseries Xai and I have no such problems.

[Dave Gilbert (ubuntu-treblig)]

Setting to Medium because it seems to fall between High ( a problem with an essential component - the mouse), and Low (an easy work around - wait !).

I think for those who have it, it would be interesting to add the output of lsusb after boot - to try and figure out which people are affected and which aren't.