public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Steven Noonan <steven@uplinklabs.net>
To: Keith Packard <keithp@keithp.com>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: REGRESSION 3.14 i915 warning & mouse cursor vanishing
Date: Mon, 14 Apr 2014 11:56:03 -0700	[thread overview]
Message-ID: <20140414185602.GA892@falcon> (raw)
In-Reply-To: <867g6ryd2e.fsf@hiro.keithp.com>

On Mon, Apr 14, 2014 at 11:35:05AM -0700, Keith Packard wrote:
> Steven Noonan <steven@uplinklabs.net> writes:
> 
> > Was using my machine normally, then my mouse cursor vanished. After switching
> > to a VT and back to X11, my cursor came back. But I did notice a nasty trace in
> > dmesg (below).
> 
> I don't think the trace below is related to the cursor disappearing.

Any idea what the trace is all about then? Seems it has something to do
with runtime power management (maybe my aggressive kernel command-line
options are triggering it).

> I found a pair of bugs (one in the intel driver, one in the X server)
> which can cause cursor disappearances. I just sent an intel driver patch
> to the intel-gfx list with the subject:
> 
>         [PATCH] load_cursor_argb is supposed to return a Bool, not void
> 
> I've posted the X server patch once, and will respond to some review
> comments. Either is sufficient to get a cursor back, the intel driver
> one means you get a working hardware cursor again, rather than using a
> software cursor by mistake.

OK, good to know. Thanks for pointing those out!

  reply	other threads:[~2014-04-14 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 16:40 REGRESSION 3.14 i915 warning & mouse cursor vanishing Steven Noonan
2014-04-14 18:35 ` Keith Packard
2014-04-14 18:56   ` Steven Noonan [this message]
2014-04-14 19:42     ` Keith Packard
2014-04-15 19:43     ` Daniel Vetter
2014-04-15 19:59       ` Imre Deak
2014-04-15 23:34         ` Steven Noonan
2014-04-16 21:46         ` Jani Nikula
2014-04-16 22:03           ` Steven Noonan
2014-06-10 19:35             ` Steven Noonan
2014-06-10 20:40               ` Imre Deak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140414185602.GA892@falcon \
    --to=steven@uplinklabs.net \
    --cc=airlied@linux.ie \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox