[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#696531: marked as done (Power saving regression on Sandy Bridge)

Your message dated Tue, 25 Dec 2012 16:30:32 +0000
with message-id <1356453032.21837.81.camel@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#696531: Power saving regression on Sandy Bridge
has caused the Debian Bug report #696531,
regarding Power saving regression on Sandy Bridge
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
696531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696531
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.6-trunk-amd64
Version: 3.6-1~experimental.1

Hi,

On Dell Latitude E6220 (Sandy Bridge i5-2520M, integrated graphics),
power saving stops working after some time.  The symptoms are that idle
power consumption goes from 7W to 28W (!), and Powertop reports that PC7
is never entered.  A reliable way to reproduce it is to suspend the
laptop, but it sometimes happens spontaneously.

This is most possibly identical to

  https://bugs.freedesktop.org/show_bug.cgi?id=54089

-- Juliusz

--- End Message ---
--- Begin Message --- 
Version: 3.7.1-1~experimental.1

On Tue, 2012-12-25 at 17:21 +0100, Juliusz Chroboczek wrote:
> >> On Dell Latitude E6220 (Sandy Bridge i5-2520M, integrated graphics),
> >> power saving stops working after some time.  The symptoms are that idle
> >> power consumption goes from 7W to 28W (!), and Powertop reports that PC7
> >> is never entered.  A reliable way to reproduce it is to suspend the
> >> laptop, but it sometimes happens spontaneously.
> 
> > I expect that
> > we'll have to wait for a backported bug fix in the 3.7.y stable series.
> 
> It looks like it's fixed in linux-image-3.7-trunk-amd64 version
> 3.7.1-1~experimental.1 -- at least I couldn't reproduce it in five minutes'
> testing.

Might be fixed by this:

commit 20b46e59dd102665ce7168baa215e5b1ee66b69b
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Thu Jul 26 11:16:14 2012 +0200

    drm/i915: Only set the down rps limit when at the loweset frequency

but I don't think we need to care exactly what fixed it.

> (Now somebody is tweaking my cpufreq parameters whenver I unplug the cord,
> but that's most probably a userspace issue, so not your problem.)

I would tend to blame laptop-mode (or possibly BIOS settings).  The
kernel + udev should be enough to get cpufreq working properly.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: