[Intel-gfx] [PATCH] drm/i915: Replicate BIOS eDP bpp clamping hack for hsw

2013-11-17 Thread Daniel Vetter
Haswell's DDI encoders have their own ->get_config callback and in commit c6cd2ee2d59111a07cd9199564c9bdcb2d11e5cf Author: Jani Nikula Date: Mon Oct 21 10:52:07 2013 +0300 drm/i915/dp: workaround BIOS eDP bpp clamping issue we've forgotten to replicate this hack. So let's do it that. Not

[Intel-gfx] [PATCH] drm: Don't split up debug output

2013-11-17 Thread Daniel Vetter
Otherwise we risk that the 2nd part of the line ends up on a line of it's own, which means a kernel dmesg line without a log level. This then upsets the dmesg checker in piglit. Only really happens in some of the truly nasty igt testcases which race cache dropping (through debugfs) with other gem

Re: [Intel-gfx] kernel 3.11.6 general protection fault

2013-11-17 Thread Borislav Petkov
On Sun, Nov 17, 2013 at 05:45:18PM +0100, MPhil. Emanoil Kotsev wrote: > How - new libraries - more exhaustive algorythms - higher cpu usage > etc. Some of the things M$ is doing on purpose to force you upgrade > your hardware every 2-3years That would be too easy and machines would be dying left

Re: [Intel-gfx] corrupted display on macbook pro 11,2

2013-11-17 Thread Daniel Vetter
On Sat, Nov 16, 2013 at 9:09 PM, heathmatlock wrote: > Hey Daniel, I see that you are actively participating in > https://bugs.freedesktop.org/show_bug.cgi?id=71049 My company recently > purchased a Macbook Pro 11,2 for me, but I've used Linux for ~13 years > now, and I don't plan on changing my c

Re: [Intel-gfx] kernel 3.11.6 general protection fault

2013-11-17 Thread MPhil. Emanoil Kotsev
Hi On Sunday 17 November 2013 16:06:07 you wrote: > On Sun, Nov 17, 2013 at 03:45:34PM +0100, MPhil. Emanoil Kotsev wrote: > > this is also true - which makes me sad as the notebook was working > > thgreat in e past 7y > > Hmm, maybe it is heading slowly for the eternal hunting fields... :-) may

Re: [Intel-gfx] Watermark computation on i830 - potential bug?

2013-11-17 Thread Daniel Vetter
On Sun, Nov 17, 2013 at 12:48 PM, Thomas Richter wrote: >> First: Have you tried my little patch, since the current watermark >> code for i830M is clearly completely busted? > > > Yes. And it broke things completely. I send a report on Friday night. Now > neither the display on the internal nor on

Re: [Intel-gfx] kernel 3.11.6 general protection fault

2013-11-17 Thread Borislav Petkov
On Sun, Nov 17, 2013 at 03:45:34PM +0100, MPhil. Emanoil Kotsev wrote: > this is also true - which makes me sad as the notebook was working > thgreat in e past 7y Hmm, maybe it is heading slowly for the eternal hunting fields... :-) > > What kind of upgrade exactly did you do to a laptop? > > I

Re: [Intel-gfx] kernel 3.11.6 general protection fault

2013-11-17 Thread MPhil. Emanoil Kotsev
Hi, On Sunday 17 November 2013 13:07:34 Borislav Petkov wrote: > On Sun, Nov 17, 2013 at 12:35:16PM +0100, MPhil. Emanoil Kotsev wrote: > > After doing all of this I was able to reproduce the issue by > > overloading the system with following simple steps: > > 1. start a compilation of something (

Re: [Intel-gfx] intel_drv.so segfault

2013-11-17 Thread Grant
>>> > Thank you, here's what I get: >>> > >>> > # addr2line -e /usr/lib64/xorg/modules/drivers/intel_drv.so -i >>> > 0x2fe79 0x3037f >>> >>> Grant - I'm assuming that this was done on the emerged >>> xf86-video-intel, not the git-compiled one? >>> >>> >>> > /var/tmp/portage/x11

Re: [Intel-gfx] kernel 3.11.6 general protection fault

2013-11-17 Thread Borislav Petkov
On Sun, Nov 17, 2013 at 12:35:16PM +0100, MPhil. Emanoil Kotsev wrote: > After doing all of this I was able to reproduce the issue by > overloading the system with following simple steps: > 1. start a compilation of something (ex. kernel) > 2. run another process hungry application (flashplayer in

Re: [Intel-gfx] Watermark computation on i830 - potential bug?

2013-11-17 Thread Thomas Richter
On 17.11.2013 12:19, Daniel Vetter wrote: as reported yesterday, the watermark levels - the values of the FW_BLC register are completely off on my R31. This renders the display unusable after Daniel's patch from Friday, both the internal and the external. The fwater_lo values for planes A and B

Re: [Intel-gfx] kernel 3.11.6 general protection fault

2013-11-17 Thread MPhil. Emanoil Kotsev
Hi I listened to your advise and installed 3.12 kernel (no other modules on top that would taint the kernel like vmware/player). So it turned out I have to enable /proc/acpi (depreciated) and acpi_cpufreq, so that I may have a proper support for cooling and frequency. $ acpi -t Thermal 0: ok, 5

Re: [Intel-gfx] Watermark computation on i830 - potential bug?

2013-11-17 Thread Daniel Vetter
On Sat, Nov 16, 2013 at 9:57 PM, Thomas Richter wrote: > Hi Daniel, dear intel experts, > > as reported yesterday, the watermark levels - the values of the FW_BLC > register are completely off on my R31. This renders the display unusable > after Daniel's patch from Friday, both the internal and th

Re: [Intel-gfx] [PATCH] drm/i915: restore the early forcewake cleanup

2013-11-17 Thread Daniel Vetter
On Sun, Nov 17, 2013 at 11:53 AM, Chris Wilson wrote: > On Sat, Nov 16, 2013 at 04:00:09PM +0100, Daniel Vetter wrote: >> Some BIOS just leak the forcewak bits, which we clean up. >> Unfortunately this has been broken in >> >> commit 521198a2e7095c8c7daa8d7d3a76a110c346be6f >> Author: Mika Kuoppal

Re: [Intel-gfx] [PATCH] drm/i915: restore the early forcewake cleanup

2013-11-17 Thread Chris Wilson
On Sat, Nov 16, 2013 at 04:00:09PM +0100, Daniel Vetter wrote: > Some BIOS just leak the forcewak bits, which we clean up. > Unfortunately this has been broken in > > commit 521198a2e7095c8c7daa8d7d3a76a110c346be6f > Author: Mika Kuoppala > Date: Fri Aug 23 16:52:30 2013 +0300 > > drm/i915

Re: [Intel-gfx] [PATCH] Partially revert "drm/i915: tune the RC6 threshold for stability"

2013-11-17 Thread Chris Wilson
On Sat, Nov 16, 2013 at 04:06:01PM +0100, Daniel Vetter wrote: > This reverts commit 351aa5666d02062b52329bcfe4bcf9d1f882fba9. > > It breaks rc6 on at least one snb machine. Since we don't yet have a > report for ivb let's keep it there for now. > > Bugzilla: https://bugs.freedesktop.org/show_bug