From: Peter Hurley <peter@hurleysoftware.com>
To: Manuel Krause <manuelkrause@netscape.net>
Cc: linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org,
linux-serial <linux-serial@vger.kernel.org>
Subject: Re: 3.12.x looses serial mouse over hibernate + resume
Date: Sun, 01 Dec 2013 10:43:27 -0500 [thread overview]
Message-ID: <529B591F.1020909@hurleysoftware.com> (raw)
In-Reply-To: <52951E69.7090602@netscape.net>
[ +cc Dmitry Torokhov, Greg Kroah-Hartman, linux-input, linux-serial ]
On 11/26/2013 05:19 PM, Manuel Krause wrote:
> 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.
Manuel,
Please attach complete dmesgs (zipped, if necessary) of a suspend/resume cycle
on a vanilla 3.12.x (where resume fails) _and_ a vanilla 3.11.x (where resume succeeds).
For the test configurations, please do not apply patches.
Regards,
Peter Hurley
next parent reply other threads:[~2013-12-01 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52951E69.7090602@netscape.net>
2013-12-01 15:43 ` Peter Hurley [this message]
2013-12-02 16:08 ` 3.12.x looses serial mouse over hibernate + resume Manuel Krause
2013-12-02 16:38 ` Dmitry Torokhov
2013-12-02 16:45 ` Dmitry Torokhov
2013-12-02 18:35 ` Manuel Krause
2013-12-02 18:44 ` Shuah Khan
2013-12-02 19:08 ` Dmitry Torokhov
2013-12-02 19:30 ` Shuah Khan
2013-12-02 19:07 ` Dmitry Torokhov
2013-12-02 20:40 ` Manuel Krause
2013-12-04 17:16 ` Dmitry Torokhov
2013-12-04 20:33 ` Manuel Krause
2013-12-05 0:41 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=529B591F.1020909@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=manuelkrause@netscape.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).