Mailinglist Archive: opensuse-bugs (4661 mails)
| < Previous | Next > |
[Bug 639152] New: lenovo T61 suspends twice
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 14 Sep 2010 08:34:57 +0000
- Message-id: <bug-639152-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=639152
https://bugzilla.novell.com/show_bug.cgi?id=639152#c0
Summary: lenovo T61 suspends twice
Classification: openSUSE
Product: openSUSE 11.3
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: koenig@xxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---
since I've upgraded my T61 to 11.3 (using xfce4 desktop) suspend2ram has a new
issue:
I trigger suspend with Fn-F4 which does suspend. after resumning either by
closing/opening the lid, or just by pressing Fn key, the system wakes up and
immedately suspends again. only the 2nd wakeup by Fn key then the notebook
stays on.
this re-suspend is quite annoying as it takes quite some additional time, and
if you forget to press Fn again I'm waiting "forever"
I've run "ps axjf" in a tight loop for the suspend/resume cycles which shows
that both "s2ram" processes are started by upowerd (full ps outputs
attached...)
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
1 6169 2062 2062 ? -1 S 0 1:21
/usr/lib/upower/upowerd
6169 16079 2062 2062 ? -1 S 0 0:00 \_ /bin/sh
/usr/sbin/pm-suspend
16079 16979 2062 2062 ? -1 D 0 0:00 \_ s2ram -f
and
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
1 6169 2062 2062 ? -1 S 0 1:21
/usr/lib/upower/upowerd
6169 18904 2062 2062 ? -1 S 0 0:00 \_ /bin/sh
/usr/sbin/pm-suspend
18904 19576 2062 2062 ? -1 D 0 0:00 \_ s2ram -f
if I trigger suspend by running "powersave -u" this re-suspend does not happen,
1st resume will remain running as expected, but it does not start the X screen
lock:-(
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |