I have a brand-new XPS 13 Skylake laptop. It's running 4.3 plus some
wireless-next bits. Everything seems to more-or-less work (even
suspend/resume, although resume feels a bit slower than it should be
to my untrained eye, which may be related). When I resume my Dell XPS
13, I get:
[ 1870.38026
I've twice seen my laptop start sucking power. Both times, turbostat (the
fancy new linux-3.8 pending version) shows GFX_W > 7. Restarting
gnome-shell has no effect. Suspending and resuming it seems to bring the
average power down to well under 1W. I have no funny i915 module options
set. I'm
On Mon, Apr 2, 2012 at 1:52 PM, Daniel Vetter wrote:
> On Mon, Apr 02, 2012 at 01:45:39PM -0700, Andrew Lutomirski wrote:
>> On Mon, Apr 2, 2012 at 11:48 AM, Daniel Vetter
>> wrote:
>> > Inspired by the recent ppgtt regression report, where switching of
>> > d
On Mon, Apr 2, 2012 at 11:48 AM, Daniel Vetter wrote:
> Inspired by the recent ppgtt regression report, where switching of
> dmar only for the gpu seems to fix things completely, I've looked
> again at the semaphores+vt-d situation.
>
> Contrary to my earlier testing a few months back my system is
On Tue, Feb 21, 2012 at 12:02 PM, Daniel Vetter wrote:
> On Tue, Feb 21, 2012 at 01:37:37PM +, Daniel J Blueman wrote:
>> On 16 February 2012 13:07, Daniel Vetter wrote:
>> > On Thu, Feb 16, 2012 at 11:44:46AM +, Daniel J Blueman wrote:
>> >> When charging Dell E5420 laptops, I see the Sa
On Thu, Nov 17, 2011 at 1:22 AM, Daniel Vetter wrote:
> Oops, sorry for wasting your time, wrong branch. Can you try the
> for-poland one? And also please try what happens when enabling the
> iommu.
for-poland with semaphores, rc6, and iommu on seems to work. I'm
sending this email from that ker
On Wed, Nov 16, 2011 at 6:19 PM, Matthew Garrett wrote:
> On Thu, Nov 17, 2011 at 01:26:37AM +0100, Mario Kleiner wrote:
>> On Nov 16, 2011, at 7:48 PM, Matthew Garrett wrote:
>> >For Radeon, I'd have thought you could handle this by scheduling
>> >an irq
>> >for the beginning of scanout (avivo ha
2011/11/16 Matthew Garrett :
> On Wed, Nov 16, 2011 at 06:03:15PM +0100, Michel Dänzer wrote:
>
>> I thought the main reason for the delay wasn't broken hardware but to
>> avoid constantly ping-ponging the vblank IRQ between on and off with
>> apps which regularly neeed the vblank counter value, as
On Wed, Nov 16, 2011 at 9:16 AM, Keith Packard wrote:
> On Wed, 16 Nov 2011 16:49:40 +0100, Daniel Vetter
> wrote:
>
>> So we need to check whether DMAR is enabled (on the
>> entire system, i.e. the variable exported for the ilk workaround is
>> not good enough)
>
> Can you figure out what *woul
On Wed, Oct 5, 2011 at 9:38 AM, Jesse Barnes wrote:
> On Tue, 4 Oct 2011 18:50:18 -0700
> "Kay, Allen M" wrote:
>
>> I'm working on assigning Intel graphics to a guest OS in Xen/KVM
>> environment. Before assigning the device to the guest OS, I need to first
>> unbind the i915 driver from the
I'm up and running again. What's the latest patch I'm supposed to test?
i915.semaphores=1 intel_iommu=off appears to work.
--Andy
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
On Sep 26, 2011 9:00 PM, "Daniel Vetter" wrote:
>
> Only do it in the hope of resurrecting the gpu. Disable when reset is
> disabled because it seems to tremendously increases our changes to
> actually capture an error_state before the system goes all belly-up.
>
> Signed-off-by: Daniel Vetter
>
On Wed, Sep 7, 2011 at 6:19 PM, Ben Widawsky wrote:
>
>
> On Sep 7, 2011, at 5:30 PM, Andrew Lutomirski wrote:
>
>> On Wed, Sep 7, 2011 at 4:12 PM, Ben Widawsky wrote:
>>> While I think the previous code is correct, it was hard to follow and
>>> hard to
On Wed, Sep 7, 2011 at 4:12 PM, Ben Widawsky wrote:
> While I think the previous code is correct, it was hard to follow and
> hard to debug. Since we already have a ring abstraction, might as well
> use it to handle the semaphore updates and compares.
>
> I don't expect this code to make semaphore
Yes. I suspect that, as soon as any 3D happens, the machine locks hard.
How does it even get into a state that makes the hardware reset button not
work?
On Aug 31, 2011 3:08 PM, "Keith Packard" wrote:
> On Wed, 31 Aug 2011 14:30:00 -0400, Andrew Lutomirski
wrote:
>
>>
On Mon, Aug 22, 2011 at 12:53 PM, Jesse Barnes
wrote:
> On Fri, 10 Jun 2011 10:06:39 -0400
> Andrew Lutomirski wrote:
>
>> On Tue, Jun 7, 2011 at 3:12 AM, Eric Anholt wrote:
>> > I fear this bug is just "getting more asynchronous with the GPU means
we
>> &
On Wed, Jul 27, 2011 at 1:17 PM, Jesse Barnes wrote:
> Mainly for use in debugging and benchmarking, this file allows the user
> to control the max frequency used by the GPU. Frequency may still vary
> based on workload (if the frequency is set to higher than the minimum)
> but won't go over the
On Tue, Jul 26, 2011 at 1:54 AM, Keith Packard wrote:
> From 59b920597999381fab70c485c161dd50590e561a Mon Sep 17 00:00:00 2001
> From: Keith Packard
> Date: Mon, 25 Jul 2011 22:37:51 -0700
> Subject: [PATCH] Revert and fix "drm/i915/dp: remove DPMS mode tracking from
> DP"
>
> This reverts commi
On Mon, Jul 25, 2011 at 1:37 PM, Jesse Barnes wrote:
> On Mon, 25 Jul 2011 10:10:29 -0700
> Keith Packard wrote:
>
>> Hotplug detection is a mode setting operation and must hold the
>> struct_mutex or risk colliding with other mode setting operations.
>>
>> In particular, the display port hotplug
Will test tonight.
It looks like there is a lot of hotplug activity when 'xset dpms force
off' gets run. (That's not a typo. I do mean "off," not "on."
See attached trace. perf rocks, even over ssh :)
--Andy
On Mon, Jul 25, 2011 at 1:37 PM, Jesse Barnes wrote:
> On Mon, 25 Jul 2011 10:10:29
On Mon, Jul 25, 2011 at 12:08 PM, Keith Packard wrote:
> On Mon, 25 Jul 2011 11:23:17 -0400, Andrew Lutomirski wrote:
>
>> A debugging patch and its output are attached.
>
> I didn't get any attachment.
>
>> If I had to guess, though, it's a race:
On Mon, Jul 25, 2011 at 12:54 AM, Keith Packard wrote:
> On Sat, 23 Jul 2011 14:40:36 -0400, Andrew Lutomirski wrote:
>> I have a Q67 (DQ67SW board) attached to a Dell U2711 via DP. In
>> previous kernels, the DP link has worked flawlessly. I just booted
>> 3.0-final and s
On Sat, Jul 23, 2011 at 2:40 PM, Andrew Lutomirski wrote:
> I have a Q67 (DQ67SW board) attached to a Dell U2711 via DP. In
> previous kernels, the DP link has worked flawlessly. I just booted
> 3.0-final and simultaneously enabled SNA, and now when my screen goes
> to sleep I
I have a Q67 (DQ67SW board) attached to a Dell U2711 via DP. In
previous kernels, the DP link has worked flawlessly. I just booted
3.0-final and simultaneously enabled SNA, and now when my screen goes
to sleep I don't get an image back until I power cycle the monitor.
dmesg says:
[drm:intel_dp_c
On Fri, Jun 24, 2011 at 12:44 PM, Andi Kleen wrote:
> Andrew Lutomirski writes:
>
> [Putting the Intel graphics driver developers in cc.]
My Sandy Bridge laptop is to blame, the graphics aren't the culprit. It's this:
BIOS-e820: 0001 - 00010060 (usable
On Tue, Jun 21, 2011 at 3:11 PM, Chris Wilson wrote:
> On Tue, 21 Jun 2011 20:38:51 +0200 (CEST), "Nicolas Kalkhof"
> wrote:
>> Thanks for bringing that up. Is there a bug report for this issue? I was
>> just about to file a report myself but I don't want to create any duplicates.
>>
>> @Chris:
On Tue, Jun 21, 2011 at 2:18 PM, Chris Wilson wrote:
> On Tue, 21 Jun 2011 19:41:52 +0200 (CEST), "Nicolas Kalkhof"
> wrote:
>> However now it seems I'm unable to get my framebuffer console back after I
>> bailed out of X. The screen stays black but my system is still responsive
>> via ssh. Th
On Tue, Jun 7, 2011 at 3:12 AM, Eric Anholt wrote:
> On Thu, 19 May 2011 16:50:00 -0400, Andrew Lutomirski wrote:
>> On Thu, May 19, 2011 at 3:56 PM, Keith Packard wrote:
>> > On Fri, 13 May 2011 12:14:54 -0400, Andy Lutomirski wrote:
>> >
>> >> My Q
On Thu, May 19, 2011 at 4:50 PM, Andrew Lutomirski wrote:
> On Thu, May 19, 2011 at 3:56 PM, Keith Packard wrote:
>> On Fri, 13 May 2011 12:14:54 -0400, Andy Lutomirski wrote:
>>
>>> My Q67 / i7-2600 box has rev09 Sandy Bridge graphics. It hangs
>>> instantly
On two different Sandy Bridge machines, modprobe eeprom does this:
[ 35.627075] [drm] GMBUS timed out, falling back to bit banging on
pin 0 [i915 gmbus disabled]
[ 35.679006] [drm] GMBUS timed out, falling back to bit banging on
pin 0 [i915 gmbus disabled]
[ 35.730938] [drm] GMBUS timed out,
On Thu, May 19, 2011 at 3:56 PM, Keith Packard wrote:
> On Fri, 13 May 2011 12:14:54 -0400, Andy Lutomirski wrote:
>
>> My Q67 / i7-2600 box has rev09 Sandy Bridge graphics. It hangs
>> instantly when GNOME loads and it hangs so hard the reset button
>> doesn't work. Setting i915.semaphore=0 fi
On Fri, May 13, 2011 at 1:38 AM, Andrew Lutomirski wrote:
> Hi-
>
> Something in the range ^8aa7500 40c7f2112ce18fa5eb ^b04d0a90908c
> causes by Q67 Sandy Bridge box to lock hard about one second after I
> start GNOME. It locks so hard that the reset button doesn't work and
Hi-
Something in the range ^8aa7500 40c7f2112ce18fa5eb ^b04d0a90908c
causes by Q67 Sandy Bridge box to lock hard about one second after I
start GNOME. It locks so hard that the reset button doesn't work and
netconsole doesn't say anything.
I'm about to have trouble finishing the bisection becaus
Intel DH67GD connected to Dell U2711 over DP works fine on recent
kernels. (U2711 is even higher bandwidth than anything Apple makes.)
--Andy
On Tue, Apr 26, 2011 at 9:42 PM, Paul McGarry wrote:
> Hi all,
>
> Can someone tell me whether the info on:
>
> http://www.x.org/wiki/DisplayPort
>
> "Th
On Wed, Apr 20, 2011 at 3:38 PM, Jesse Barnes wrote:
>> > Andrew, do you have anything hacked together for this yet?
>>
>> Nope. I gave up because I couldn't even get the mode to set. :)
>
> Ok well you should be able to now. :) Using the patchset I posted
> earlier along with the two attached p
On Wed, Apr 20, 2011 at 3:05 PM, Jesse Barnes wrote:
> On Tue, 27 Jul 2010 11:03:56 -0400
> Adam Jackson wrote:
>
>> On Fri, 2010-07-23 at 16:29 -0400, Andrew Lutomirski wrote:
>>
>> > Does that include not breaking DirectColor? If we program the gamma
>>
On Wed, Feb 16, 2011 at 8:20 AM, Andrew Lutomirski wrote:
> On Wed, Feb 16, 2011 at 8:13 AM, Ivan Bulatovic wrote:
>> On Tue, 2011-02-15 at 11:46 +1000, Ted Phelps wrote:
>>> Hi Andy,
>>>
>>> Andi Kleen writes:
>>> > Ted Phelps writes:
>>
On Wed, Feb 16, 2011 at 8:33 AM, Ivan Bulatovic wrote:
> On Wed, 2011-02-16 at 08:20 -0500, Andrew Lutomirski wrote:
>> I'm curious what userspace you're all running. I'm using
>> xf86-video-intel from git on Feb 4 with 2.6.37 (completely unpatched!)
>> and m
On Wed, Feb 16, 2011 at 8:13 AM, Ivan Bulatovic wrote:
> On Tue, 2011-02-15 at 11:46 +1000, Ted Phelps wrote:
>> Hi Andy,
>>
>> Andi Kleen writes:
>> > Ted Phelps writes:
>> >
>> > > Apologies if this is a known issue, but I haven't been able to convince
>> > > myself that someone is looking afte
On Mon, Dec 20, 2010 at 10:47 PM, Keith Packard wrote:
> On Mon, 20 Dec 2010 22:34:12 -0500, Andrew Lutomirski wrote:
>
>> But five seconds is a *long* time, and anything short enough that the
>> interrupt actually gets turned off in normal use risks the same race.
>
> R
On Mon, Dec 20, 2010 at 10:23 PM, Keith Packard wrote:
> On Mon, 20 Dec 2010 14:00:54 -0500, Andy Lutomirski wrote:
>
>> Enabling and disabling the vblank interrupt (on devices that
>> support it) is cheap. So disable it quickly after each
>> interrupt.
>
> So, the concern (and reason for the or
On Thu, Dec 9, 2010 at 1:23 PM, Jesse Barnes wrote:
> On Thu, 9 Dec 2010 12:47:52 -0500
> Andrew Lutomirski wrote:
>
>> On Thu, Dec 9, 2010 at 12:20 PM, Jesse Barnes
>> wrote:
>> > On Wed, 8 Dec 2010 13:33:20 -0500
>> > Andrew Lutomirski wrote:
&g
On Thu, Dec 9, 2010 at 12:20 PM, Jesse Barnes wrote:
> On Wed, 8 Dec 2010 13:33:20 -0500
> Andrew Lutomirski wrote:
>
>> On Wed, Dec 8, 2010 at 1:17 PM, Andrew Lutomirski wrote:
>> > On Tue, Dec 7, 2010 at 5:13 PM, Chris Wilson
>> > wrote:
>> >&
On Wed, Dec 8, 2010 at 1:17 PM, Andrew Lutomirski wrote:
> On Tue, Dec 7, 2010 at 5:13 PM, Chris Wilson wrote:
>> On Tue, 7 Dec 2010 16:31:24 -0500, Andrew Lutomirski wrote:
>>> On Tue, Dec 7, 2010 at 4:03 PM, Andrew Lutomirski wrote:
>>> > Hi all-
>>> &g
On Wed, Dec 8, 2010 at 1:14 PM, Vasily Khoruzhick wrote:
> On Wednesday 08 December 2010 19:54:59 Andrew Lutomirski wrote:
>> On Wed, Dec 8, 2010 at 12:00 PM, Vasily Khoruzhick
> wrote:
>> > On Wednesday 08 December 2010 18:54:21 Chris Wilson wrote:
>> >>
On Tue, Dec 7, 2010 at 5:13 PM, Chris Wilson wrote:
> On Tue, 7 Dec 2010 16:31:24 -0500, Andrew Lutomirski wrote:
>> On Tue, Dec 7, 2010 at 4:03 PM, Andrew Lutomirski wrote:
>> > Hi all-
>> >
>> > Somewhere between Fedora 13 (with 2.6.35, I think) and Fed
On Wed, Dec 8, 2010 at 12:00 PM, Vasily Khoruzhick wrote:
> On Wednesday 08 December 2010 18:54:21 Chris Wilson wrote:
>> On Wed, 8 Dec 2010 18:44:41 +0200, Vasily Khoruzhick
> wrote:
>> > On Wednesday 08 December 2010 18:24:35 Chris Wilson wrote:
>> > > This is just a preliminary attempt to see
On Tue, Dec 7, 2010 at 5:13 PM, Chris Wilson wrote:
> On Tue, 7 Dec 2010 16:31:24 -0500, Andrew Lutomirski wrote:
>> On Tue, Dec 7, 2010 at 4:03 PM, Andrew Lutomirski wrote:
>> > Hi all-
>> >
>> > Somewhere between Fedora 13 (with 2.6.35, I think) and Fed
On Tue, Dec 7, 2010 at 4:03 PM, Andrew Lutomirski wrote:
> Hi all-
>
> Somewhere between Fedora 13 (with 2.6.35, I think) and Fedora 14 +
> 2.6.36.1, i915 started generating exactly 50 interrupts per second
> (suspiciously equal to my refresh rate) when X is running. I have th
Hi all-
Somewhere between Fedora 13 (with 2.6.35, I think) and Fedora 14 +
2.6.36.1, i915 started generating exactly 50 interrupts per second
(suspiciously equal to my refresh rate) when X is running. I have the
Xorg driver 2.12.0 (specifically
xorg-x11-drv-intel-2.12.0-6.fc14.1.x86_64). When I
Out of curiousity, what happened to ACPI_BM_BREAK_EN here:
https://bugs.freedesktop.org/show_bug.cgi?id=30364
On my box, that register is (according to setpci) 0x00, but I'm
testing on an ICH9M and I don't seem to be affected anyway.
--Andy
On Mon, Nov 1, 2010 at 4:23 PM, Eric Anholt wrote:
On Wed, Oct 6, 2010 at 10:50 AM, Rasto Sramek wrote:
>> AFAICT Zaphod mode is one device but multiple X servers (presumably
>> used independently by different people). I think very few drivers
>> support it these days.
> Well, whatever it is called, I am referring to the configuration when I
> ha
On Wed, Oct 6, 2010 at 10:03 AM, Rasto Sramek wrote:
> Hello *,
>
> sorry in case this has been raised many times. Zaphod mode support (In
> my understanding one card, one xserver, multiple screens) seems to not
> work in intel drivers anymore. Is that so?
AFAICT Zaphod mode is one device but mul
On Wed, Aug 18, 2010 at 5:05 PM, Jesse Barnes wrote:
> On Wed, 18 Aug 2010 21:48:50 +0100
> Owain Ainsworth wrote:
>
>> On Wed, Aug 18, 2010 at 12:00:36PM -0700, Jesse Barnes wrote:
>> > Waiting for a hard coded 20ms isn't always enough to make sure a vblank
>> > period has actually occurred, so
On Mon, Jul 26, 2010 at 1:41 PM, Eric Anholt wrote:
> On Sun, 25 Jul 2010 15:29:25 -0400, Andrew Lutomirski wrote:
>> For well over a year now, I (and apparently lots of other people) have
>> had to run patched kernels to avoid crippling hotplug storms.
>>
>> As far
I've been running 2.6.35 rc's and xf86-drv-intel git master for
awhile, and X has been a bit unstable. Every now and then, graphics
freeze completely, except that the mouse still works (I think) and
capslock toggles the LED.
If I switch to a different VT and killall -9 Xorg, everything recovers.
For well over a year now, I (and apparently lots of other people) have
had to run patched kernels to avoid crippling hotplug storms.
As far as I can tell, on my laptop, enabling DPC_HOTPLUG_INT_EN is
safe, but setting either DPB_... or DPD_... (or both) will cause
intermittent hotplug interrupt st
On Fri, Jul 23, 2010 at 4:13 PM, Eric Anholt wrote:
> On Fri, 23 Jul 2010 14:00:30 -0400, Andrew Lutomirski wrote:
>> AFAICT intel hardware wants a 129-entry LUT when using high precision
>> gamma ramps. Rather than hacking some kind of decimation into the
>> kernel driv
AFAICT intel hardware wants a 129-entry LUT when using high precision
gamma ramps. Rather than hacking some kind of decimation into the
kernel driver (and thus silently breaking DirectColor), I'd like to
teach userspace how to deal with variable gamma sizes.
gnome-color-manager already more-or-le
On Fri, Jul 23, 2010 at 8:26 AM, Chris Wilson wrote:
> On Thu, 22 Jul 2010 17:34:09 -0400, Andrew Lutomirski wrote:
>> [resend b/c I used the wrong from address last time]
>>
>> I have a 10 bit/channel monitor (DisplayPort) which works quite nicely
>> in 8 bit mod
[resend b/c I used the wrong from address last time]
I have a 10 bit/channel monitor (DisplayPort) which works quite nicely
in 8 bit mode. I saw some patches from Peter Clifton related to 10
bit support go in awhile ago.
There are (at least) three modes that would be nice:
(1) 8bpp framebuffer,
On Mon, Jun 28, 2010 at 7:48 PM, Dave Airlie wrote:
> On Sat, Jun 12, 2010 at 7:21 PM, Andy Lutomirski wrote:
>> Commit 7a772c492fcfffae812ffca78a628e76fa57fe58 has two bugs which
>> made the hotplug problems on my laptop worse instead of better.
>>
>> First, it did not, in fact, disable the CRT
On Sun, Jun 20, 2010 at 11:29 AM, Andrew Lutomirski wrote:
> On Fri, Jun 18, 2010 at 4:04 PM, Jesse Barnes
> wrote:
>> On Thu, 17 Jun 2010 19:44:10 -0700
>> Jesse Barnes wrote:
>>
>>> On Fri, 18 Jun 2010 02:20:23 +0200
>>> Marc Deop i Argemí wrote:
On Fri, Jun 18, 2010 at 4:04 PM, Jesse Barnes wrote:
> On Thu, 17 Jun 2010 19:44:10 -0700
> Jesse Barnes wrote:
>
>> On Fri, 18 Jun 2010 02:20:23 +0200
>> Marc Deop i Argemí wrote:
>>
>> > On Friday June 18 2010 02:17:53 Andrew Lutomirski wrote:
On Thu, Jun 17, 2010 at 4:32 PM, Jesse Barnes wrote:
> On Wed, 16 Jun 2010 11:07:21 -0400
> Andrew Lutomirski wrote:
>
>> On Wed, Jun 16, 2010 at 7:38 AM, Andrew Lutomirski wrote:
>> > On Wed, Jun 16, 2010 at 7:25 AM, Marc Deop i Argemí
>> > wrote:
>>
On Wed, Jun 16, 2010 at 7:38 AM, Andrew Lutomirski wrote:
> On Wed, Jun 16, 2010 at 7:25 AM, Marc Deop i Argemí
> wrote:
>> On Wednesday June 16 2010 11:20:09 Chris Wilson wrote:
>>
>> Freeze is... freeze :P
>>
>> Now, seriously, the computer stops respon
On Wed, Jun 16, 2010 at 7:25 AM, Marc Deop i Argemí wrote:
> On Wednesday June 16 2010 11:20:09 Chris Wilson wrote:
>> After a freeze, can you grab a copy of dmesg, Xorg.log, intel_reg_dump,
>> and /sys/kernel/debug/dri/0/i915_error_state. From my perspective, the
>> last contains the most interes
Hi all-
Just a friendly regression reminder: a recent patch intended to fix
the long-standing hotplug storm bugs in i915 instead made it a good
deal worse -- I now get hotplug interrupts constantly as long as
anything (plymouth or Xorg, for example) is querying CRT status.
Analysis and potential
On Tue, Jun 8, 2010 at 10:09 AM, Adam Jackson wrote:
> On Tue, 2010-06-08 at 04:12 -0400, Andrew Lutomirski wrote:
>> On my trusty X200s (GM45), I still have such frequent i915 hotplug
>> storms that any standard kernel is essentially unusable.
>
> You're not running m
On Tue, Jun 8, 2010 at 6:43 AM, Andrew Lutomirski wrote:
>
> Time for the next try.
Now I have SDVO and HDMI disabled and the bug's still there.
$ ls /sys/class/drm/card0
card0-DisplayPort-1 card0-DisplayPort-3 card0-VGA-1 device subsystem
card0-DisplayPort-2 card0-LVDS-1
On Tue, Jun 8, 2010 at 4:12 AM, Andrew Lutomirski wrote:
> On my trusty X200s (GM45), I still have such frequent i915 hotplug
> storms that any standard kernel is essentially unusable.
>
[...]
>
> I'll try selectively disabling outputs and seeing if I can narrow it down.
On my trusty X200s (GM45), I still have such frequent i915 hotplug
storms that any standard kernel is essentially unusable.
Here's an example:
[ 138.717645] hotplug event received, iir 0x0002, stat
0x2020, mask 0x38000800
[ 138.718029] hotplug event received, iir 0x0002, stat
0x282
On Tue, May 25, 2010 at 10:46 AM, Adam Jackson wrote:
> On Mon, 2010-05-24 at 21:46 -0400, Andrew Lutomirski wrote:
>> On Mon, May 24, 2010 at 4:46 PM, Adam Jackson wrote:
>> > Disable the CRT plug interrupt while doing the force cycle, explicitly
>> > clear an
On Mon, May 24, 2010 at 4:46 PM, Adam Jackson wrote:
> Disable the CRT plug interrupt while doing the force cycle, explicitly
> clear any CRT interrupt we may have generated, and restore when done.
> Should mitigate interrupt storms from hotplug detection.
>
Is there any locking in here to protec
On Fri, May 14, 2010 at 8:17 PM, SD wrote:
>
>
> --- On Sat, 5/15/10, Andrew Lutomirski wrote:
>
>> From: Andrew Lutomirski
>> Subject: Re: [Intel-gfx] Picture quality on laptop LCD with i915GM chipset.
>> To: "SD"
>> Cc: intel-gfx@lists.freedeskto
On Fri, May 14, 2010 at 7:17 PM, SD wrote:
> Dear All.
>
> My question may look strange but I have some serious problem that prevent me
> of using any linuxes on kernel higher then 2.6.27.
>
> Explanation: I have laptop i686 Celeron i915GM video. On it there is two OS -
> OpenSuse 11.1 (kernel 2
On Mon, May 10, 2010 at 12:59 PM, Simon Farnsworth
wrote:
> On Monday 10 May 2010, Simon Farnsworth wrote:
>> On Friday 7 May 2010, Simon Farnsworth wrote:
>> > I've attached my test program (it's based on our C++ OpenGL compositor,
>> > but cut down to just test OpenGL pageflipping) as performa
On Fri, May 7, 2010 at 9:07 AM, Simon Farnsworth
wrote:
> Hello,
>
I don't know exactly what this program is supposed to do, but here's
what it does right now, on GM45 and F13 with -linus
be1066bbcd443a65df312fdecea7e4959adedb45 (approx 2.6.34-rc6).
(Note: I have an extra patch to turn off all d
This might be the wrong list, but here goes...
On my X200s (GM45) laptop, my system sometimes lags badly on resume.
This seems to mostly happen after the laptop has been suspended for a
long time (an hour or more, maybe). The symptoms are that, starting a
second or two after resuming, nothing upd
Should this patch be enough to output 10 bits/channel on a digital
output? I just ordered some 10-bit monitors and it would be fun to
use them in all their high-precision glory?
It should be relatively easy to use spotread (from Argyll) along with
some hacked-up gamma loader to verify that it's w
80 matches
Mail list logo
