Comment 7 for bug 1258837

Revision history for this message
Allan Crooks (amcone) wrote :

Updated the BIOS as you suggested. From the terminal:

allanc@wyvern:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A06
12/05/2013
allanc@wyvern:~$ uname -a
Linux wyvern 3.13.0-031300rc3-generic #201312061335 SMP Fri Dec 6 18:37:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

And looking at the logs after a while:
Dec 18 12:24:23 wyvern kernel: [ 7576.635161] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Dec 18 12:24:23 wyvern kernel: [ 7576.635165] psmouse serio1: issuing reconnect request
Dec 18 12:32:14 wyvern kernel: [ 8048.029215] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Dec 18 12:32:14 wyvern kernel: [ 8048.029218] psmouse serio1: issuing reconnect request
Dec 18 12:42:03 wyvern kernel: [ 8636.722053] psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Dec 18 12:42:03 wyvern kernel: [ 8636.722056] psmouse serio1: issuing reconnect request

I'm using the latest kernel (as suggested in comment 3) and the resetafter parameter (as suggested in comment 5). I find it difficult to recreate on demand. I managed to see those errors within half an hour of resuming the laptop from suspend. I didn't see any such messages in the log while I was testing prior to putting it on standby, and I haven't seen any messages a while after resuming. I'll test with it more.