looks like this is in fact somehow related to laptop-mode-tools / r8169
misbehaves if shut down.
In the end it is enough to shut down the interface via:
ip link set dev eth0 down
to produce the errors messages:
[90830.764253] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000,
delay: 10)
Package: src:linux
Version: 4.3.3-7~bpo8+1
Severity: normal
Dear Maintainer,
after suspend to ram there are lots of error messages from the r8169
module and there are some strange side-effects (multiload_applet
produces 100% cpu load trying to read network interface statistics ...)
as workaround
Package: src:linux
Version: 3.16.7-ckt7-1
Severity: normal
Dear Maintainer,
On A20-OLinuXino-{MICRO,LIME,LIME2,...?} power off doesn't work.
after enabling
CONFIG_MFD_AXP20X=y
CONFIG_REGULATOR_AXP20X=y
in
debian/config/armhf/config.armmp
power off works for me on A20-OLinuXino-LIME2
s.a.
Messag
Jens Thiele writes:
> Don't have the time to test this now and will wait for the security
> update. (downgraded to 3.2.63-2+deb7u2 for now now)
For the archive:
After updating to 3.2.65-1+deb7u1 suspend works for me again.
Thanks,
jens
--
To UNSUBSCRIBE, email to debian-
Nathan Wallach writes:
> Jens - I found your bug-report:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775178
> I also had a problem with resume from suspend failing after the update to
> kernel 3.2.65-1, and found a number of other similar bug-reports. Many
> pointed to the patched kernel
Jens Thiele writes:
> maybe this is related to #746411? Maybe the same code got in again?
unfortunately not that simple. The patch for #746411 is still there:
karme@amalthea:/tmp/linux-3.2.65$ find -iname "*revert-perf-x86-amd-ibs-fix*"
./debian/patches/bugfix/x86/revert-perf-x8
Package: src:linux
Version: 3.2.65-1
Severity: normal
Dear Maintainer,
suspend/resume not working after update from 3.2.63-2+deb7u2 to
3.2.65-1.
maybe this is related to #746411? Maybe the same code got in again?
Suspend itself seems to work.
On a resume a reboot happens (this is different from
Ben Hutchings writes:
> Thanks a lot. This should be reverted in the next security update.
> (Yes, even though it is not a security issue.)
looking forward for the update, thanks!
greetings,
jens
PS:
i could imagine the revert will break stuff for other machines and
likely a fixed version of
if i revert the commit:
commit e07518e9ce84547ef7a81478dbd3fed1539726da
Author: Robert Richter
Date: Wed Jan 15 15:57:29 2014 +0100
perf/x86/amd/ibs: Fix waking up from S3 for AMD family 10h
suspend/resume works for me again
$ git branch -v
* linux-3.2.y f453538 Linux 3.2.58
$ git diff-tree
Jens Thiele writes:
> Ben Hutchings writes:
>
>> How is it 'not working'?
>
> didn't have time to inspect the details yet
did some more tests
- it doesn't matter wether i am on power or battery
- I have a reproducible crash on every second resume
(first
Ben Hutchings writes:
> How is it 'not working'?
didn't have time to inspect the details yet
> - Crash/hang when trying to suspend?
suspend itself seems to work
> - Immediate resume after suspending?
no
> - Unresponsive when trying to resume?
> - Crash/hang after resuming?
looks like a com
Jens Thiele writes:
> can't reproduce at the moment :(
>
> maybe this bug report is invalid/can be closed
now it happened again
looks like it only happens on suspend to ram on battery
device is a thinkpad edge 11" (amd version)
** Model information
sys_vendor: LENOVO
pr
can't reproduce at the moment :(
maybe this bug report is invalid/can be closed
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87ioprcj76@karme.de
Package: src:linux
Version: 3.2.57-3
Severity: normal
suspend/resume not working after update from 3.2.54-2 to 3.2.57-3
maybe this is caused by the change:
"- perf/x86/amd/ibs: Fix waking up from S3 for AMD family 10h"
introduced in
3.2.57-1
cpu family : 16
model : 6
model name
maximilian attems <[EMAIL PROTECTED]> writes:
> as debian supports partial upgrades and initramfs-tools is not gonna
> start depend on lilo this inocation can only be used after Lenny
> release. marking as wontfix.
Let me see if I got you right:
You want to mark it as wontfix because older versi
maximilian attems <[EMAIL PROTECTED]> writes:
> i fail to find the mentioned lilo -H mention in the lilo manpage.
> dpkg -l lilo | grep ^ii
> ii lilo 22.6.1-9.3 LInux LOader - The Classic OS loader can
> loa
>
> a lilo -H invocation leads into usage() message. what are you guys usin
On 17 Sep 2007, [EMAIL PROTECTED] wrote:
> hey guys sorry if you still use lilo, you need to do
> manual intervence, i see no other way.
>
> unless a real strong argument comes up, i'll close that bug in a
> month.
AFAIK grub does not support LVM on top of md raid1 whereas lilo does?
The installer
17 matches
Mail list logo
