Hi Emil,
Am Samstag 07 März 2015, 14:26:17 schrieb Emil Goode:
Just to clarify, suspend/resume is working but it takes more than 60 sec for
suspend to complete?
yes, suspend/resume is working. I did three cycles and measured the time for
suspend:
The first suspend took approx. 60 seconds,
Hello Rainer,
On Sat, Mar 07, 2015 at 06:47:31PM +0100, Rainer Dorsch wrote:
Hi Emil,
Am Samstag 07 März 2015, 14:26:17 schrieb Emil Goode:
Just to clarify, suspend/resume is working but it takes more than 60 sec for
suspend to complete?
yes, suspend/resume is working. I did three
Hello Rainer,
On Thu, Mar 05, 2015 at 10:09:04PM +0100, Rainer Dorsch wrote:
Hi Emil,
sorry for the long silence, but I did not have physical access to the machine
for which I
reported the bug and I did not want to install new kernel from remote...
I recompiled a recent kernel with
Hi Emil,
sorry for the long silence, but I did not have physical access to the machine
for which I
reported the bug and I did not want to install new kernel from remote...
I recompiled a recent kernel with PM_TRACE_RTC enabled, but still get no log
data in
pm-suspend.log:
Hello Rainer,
On Sat, Jan 03, 2015 at 04:23:44PM +0100, Rainer Dorsch wrote:
Hi Emil,
I have only remote access to the system for the next few weeks and I feel
somewhat uncomfortable to experiment with my self-compiled kernels on the
system or changing networking configurations.
So
Hi Emil,
I have only remote access to the system for the next few weeks and I feel
somewhat uncomfortable to experiment with my self-compiled kernels on the
system or changing networking configurations.
So please apologize that I may need 3-4 weeks to test that.
I assume you suggest to follow
Hello Rainer,
On Tue, Dec 30, 2014 at 12:15:31AM +0100, Rainer Dorsch wrote:
Hi Emil,
Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode:
Hello Rainer,
The below procedure would give more information:
Add the following line to the top of the file
Hello Rainer,
The below procedure would give more information:
Add the following line to the top of the file /usr/lib/pm-utils/pm-functions.
export PM_DEBUG=true
Then suspend with:
echo 1 /sys/power/pm_trace
echo mem /sys/power/state
Post dmesg and the contents of /var/log/pm-suspend.log.
Hi Emil,
Am Montag 29 Dezember 2014, 14:02:55 schrieb Emil Goode:
Hello Rainer,
The below procedure would give more information:
Add the following line to the top of the file
/usr/lib/pm-utils/pm-functions.
export PM_DEBUG=true
Then suspend with:
echo 1 /sys/power/pm_trace
echo
Package: src:linux
Version: 3.16.7-ckt2-1
Followup-For: Bug #774036
Dear Ben,
many thanks for the superfast response and thanks for pointing out
that I was running the nvidia driver. I run now with nouveau and also
purge the virtualbox stuff.
Unfortunately, the behavior is exactly the same
Hello,
On Sun, Dec 28, 2014 at 11:15:21AM +0100, Rainer Dorsch wrote:
Package: src:linux
Version: 3.16.7-ckt2-1
Followup-For: Bug #774036
Dear Ben,
many thanks for the superfast response and thanks for pointing out
that I was running the nvidia driver. I run now with nouveau and also
Hi Emil,
Am Sonntag, 28. Dezember 2014, 15:56:28 schrieb Emil Goode:
Hello,
On Sun, Dec 28, 2014 at 11:15:21AM +0100, Rainer Dorsch wrote:
Package: src:linux
Version: 3.16.7-ckt2-1
Followup-For: Bug #774036
Dear Ben,
many thanks for the superfast response and thanks for
Hi Emil,
thanks again for our response. I have additional information, the behavior is
not a hang, but the system simply needs around additional 30s to really power
off.
I copied the dmesg output form
dmesg dmesg_before; echo mem /sys/power/state; dmesg dmesg_after
into
13 matches
Mail list logo
