From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>, intel-gfx@lists.freedesktop.org
Subject: Re: Possible i915 regression with 4.4-rc
Date: Fri, 4 Dec 2015 11:40:59 +0200 [thread overview]
Message-ID: <20151204094059.GM4437@intel.com> (raw)
In-Reply-To: <87zixqzjgz.fsf@intel.com>
On Fri, Dec 04, 2015 at 10:49:48AM +0200, Jani Nikula wrote:
> On Thu, 03 Dec 2015, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > On Thu, Dec 03, 2015 at 09:00:55PM +0100, Takashi Iwai wrote:
> >> Hi,
> >>
> >> I've experienced a few graphics issues recently, and I tend to believe
> >> that it has happened since 4.4-rc. Namely, after some long time usage
> >> on my HSW laptop (two or three days), the mouse cursor vanished
> >> suddenly. It kept pointing but just became invisible. Also, after
> >> some S3 cycles, some glyphs on a console or on Firefox became
> >> invisible, too. The windows and graphics were shown well, and X core
> >> fonts were still shown properly, too. Switching to VT1 and back
> >> didn't change the situation.
> >
> > I think I have a fix for this *very* annoying problem. I'v been cursing
> > on irc for weeks about it, until I finally got off my arse and debugged
> > it.
> >
> > I pushed out my my cursor branch:
> > git://github.com/vsyrjala/linux.git disappearing_cursor_fix
> >
> > It has lots of other junk too, but it should be just there two that fix it:
> > 59f65fa270fb ("drm/i915: Kill intel_crtc->cursor_bo")
> > 25651a198d17 ("drm/i915: Drop the broken curcor base==0 special casing")
> >
> > Unfortunatleey I've managed to keep myself busy on other stuff, so didn't
> > send them out yet. Maybe tomorrow...
>
> So I've hit this too, albeit very rarely, on a Haswell running Debian
> stable with the stock v3.16 kernel. Haven't seen it on any other
> machine. It's really too rare to even debug or verify a fix. Is it
> possible we just happened to make an old bug occur more frequently now?
The potential for it has definitely been there for a long time.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-04 9:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 20:00 Possible i915 regression with 4.4-rc Takashi Iwai
2015-12-03 20:33 ` Ville Syrjälä
2015-12-03 21:08 ` Takashi Iwai
2015-12-03 21:25 ` Ville Syrjälä
2015-12-03 21:35 ` Chris Wilson
2015-12-04 8:44 ` Jani Nikula
2015-12-04 15:57 ` Daniel Vetter
2015-12-04 12:00 ` Dave Gordon
2015-12-04 12:06 ` Chris Wilson
2015-12-04 12:16 ` Chris Wilson
2015-12-04 12:45 ` Chris Wilson
2015-12-03 21:38 ` Lukas Wunner
2015-12-08 7:03 ` Takashi Iwai
2015-12-04 8:49 ` Jani Nikula
2015-12-04 9:40 ` Ville Syrjälä [this message]
2015-12-04 16:02 ` Daniel Vetter
2015-12-04 16:12 ` Takashi Iwai
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=20151204094059.GM4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=tiwai@suse.de \
/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