Re: [resend] i915: high power consumption after suspend/resume

2009-11-10 Thread Andrew Lutomirski
Just to confuse matters further, the following patch does *not* help. Even with this patch applied, power consumption often goes high when resuming, and writing 1 to i915_wedged after fully resuming fixes it. I now officially have no clue what's going on. Maybe there's something wrong with the

Re: [resend] i915: high power consumption after suspend/resume

2009-10-31 Thread Andrew Lutomirski
On Thu, Oct 29, 2009 at 12:47 PM, Jesse Barnes jbar...@virtuousgeek.org wrote: On Wed, 7 Oct 2009 23:44:35 -0400 Andrew Lutomirski l...@mit.edu wrote: I probably need to save/restore some more of the power saving state across suspend/resume...  Can you file a bug

Re: [resend] i915: high power consumption after suspend/resume

2009-10-31 Thread Andrew Lutomirski
On Thu, Oct 29, 2009 at 1:22 PM, Andrew Lutomirski l...@mit.edu wrote: On Thu, Oct 29, 2009 at 12:47 PM, Jesse Barnes jbar...@virtuousgeek.org wrote: On Wed, 7 Oct 2009 23:44:35 -0400 Andrew Lutomirski l...@mit.edu wrote: I probably need to save/restore some more of the power saving state

Re: [resend] i915: high power consumption after suspend/resume

2009-10-31 Thread Andrew Lutomirski
On Fri, Oct 30, 2009 at 11:37 AM, Jesse Barnes jbar...@virtuousgeek.org wrote: On Fri, 30 Oct 2009 02:25:21 -0400 Andrew Lutomirski l...@mit.edu wrote: On Thu, Oct 29, 2009 at 1:40 PM, Andrew Lutomirski l...@mit.edu wrote: I just suspended and resumed and power consumption stayed low

Re: [resend] i915: high power consumption after suspend/resume

2009-10-31 Thread Andrew Lutomirski
On Thu, Oct 29, 2009 at 1:40 PM, Andrew Lutomirski l...@mit.edu wrote: I just suspended and resumed and power consumption stayed low.  I'll try and get an intel_reg_dumper diff next time I trigger this bug. intel_reg_dumper blames RENCLK_GATE_D2. Patch coming. Maybe my BIOS doesn't always

Re: [resend] i915: high power consumption after suspend/resume

2009-10-08 Thread Andrew Lutomirski
On Mon, Oct 5, 2009 at 12:21 PM, Jesse Barnes jbar...@virtuousgeek.org wrote: On Sat, 3 Oct 2009 12:50:01 -0400 Andrew Lutomirski l...@mit.edu wrote: [resend b/c the intel-gfx list doesn't allow non-member posting] Hi- First, thanks for all the great work on i915's power saving features

[resend] i915: high power consumption after suspend/resume

2009-10-03 Thread Andrew Lutomirski
[resend b/c the intel-gfx list doesn't allow non-member posting] Hi- First, thanks for all the great work on i915's power saving features -- power consumption on my laptop (Lenovo X200s) is now almost as low on Linux as on Windows. After a suspend/resume cycle, though, my power consumption

Re: [PATCH 1/2] radeon: fix radeon kms framebuffer device

2009-06-23 Thread Andrew Lutomirski
On Tue, Jun 23, 2009 at 9:35 AM, Jerome Glissegli...@freedesktop.org wrote: On Tue, 2009-06-23 at 09:12 -0400, Andy Lutomirski wrote: Andy Lutomirski wrote: Jerome Glisse wrote: smem.start is a physical address which kernel can remap to access video memory of the fb buffer. We now pin the

Re: [git pull] drm: previous pull req + 1.

2009-06-22 Thread Andrew Lutomirski
On Sun, Jun 21, 2009 at 3:47 PM, Linus Torvaldstorva...@linux-foundation.org wrote: What *has* changed is that we have a newradeon driver, and it looks like that new radeon driver is crap, and does this:        info-fix.smem_start = (unsigned long)fbptr; which is totally screwed up. It

Re: [git pull] drm: previous pull req + 1.

2009-06-22 Thread Andrew Lutomirski
On Sun, Jun 21, 2009 at 1:16 AM, Dave Airlieairl...@linux.ie wrote: I tried this tree (specifically, a merge of Linus' fb20871 this tree) on Fedora 11 with modesetting enabled on an integrated Radeon 2100, and plymouthd crashes immediately with a corrupt page table.  Photo attached.  After

Re: [git pull] drm: previous pull req + 1.

2009-06-22 Thread Andrew Lutomirski
On Sun, Jun 21, 2009 at 5:14 PM, Andrew Lutomirskil...@mit.edu wrote: On Sun, Jun 21, 2009 at 3:47 PM, Linus Torvaldstorva...@linux-foundation.org wrote: What *has* changed is that we have a newradeon driver, and it looks like that new radeon driver is crap, and does this: