lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 26 Nov 2013 23:19:21 +0100
From:	Manuel Krause <manuelkrause@...scape.net>
To:	linux-kernel@...r.kernel.org
Subject: 3.12.x looses serial mouse over hibernate + resume

Since kernel 3.12.0 I have a problem with hibernate+resume not 
reactivating my serial mouse (trackball) with my HP notebook.
Kernels 3.11.0 til 9 don't show this behaviour.

Machine:           HP Notebook with Core2Duo CPU (Penryn)
Distro:            openSUSE 12.3, 64bit, continuously updated
Desktop:           KDE 4.11.3
MESA & drm & Xorg: most recent ones from:
 
http://download.opensuse.org/repositories/home:/pontostroy:/X11/openSUSE_12.3/x86_64/
Current kernel:    3.12.1 vanilla from openSUSE repos, with
                    -ck1 and BFQ patches

The Logitech Trackman Marble FX is a PS/2 device and connected 
via an original Logitech PS/2-COM-port adapter and manually 
configured via my xorg.conf.

At first, I blamed the -ck1 patches from Con Kolivas for this 
behaviour that I use in addition to the BFQ patches, what has 
showed up as not right: This happens with the normal vanilla 
kernel schedulers for CPU and disk I/O, too.

By coincidence I found a weird(!) way to reactivate the serial mouse:
(1) call Hibernate (suspend-to-disk) from KDE desktop as normal
(2) resume --> the PS/2 touchpad is working, the serial trackball NOT
(3) call suspend-to-RAM (Sleep) from KDE, serial trackball still dead
(4) execute `setserial -a /dev/ttyS0` in a konsole window or a 
tty* console
(5) ==> serial trackball is back with all configuration from 
xorg.conf

It's fully reproducible over multiple hibernations. This also 
happens when calling `pm-hibernate` (to-disk) and `pm-suspend` 
(to-RAM) and the setserial from a root shell in KDE or any tty*.

Please, _always_CC_me_ -- as I'm not on the kernel mailing list.

Thank you in advance and best regards,
Manuel Krause
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ