Re: 4.4-rc, intel dri i915, regular hangs and corruptions

[Norbert Preining]

Hi Chris,

thanks for your answer.

I will try the latest intel driver, but in case it helps or
you get an idea, I found that it has to do with the
Antialiasing settings:

I am using an OTF font (Lucida Sans OT Regular) with cinnamon.
Sometimes when I wake the computer up from suspend to ram the 
fonts are gone.

*BUT*: Switching from (in Font Settings of Cinnamon settings)
	Antialiasing:	Grayscale
*away* fixes the problem.

WIth Antialiasing: Rgba or None the fonts remain stable as far as
I can see, while with Grayscale they are disappearing.

In fact I can turn the fonts off and on without a problem by simply 
swithcing the antialiasing.

Maybe this rings a bell at someone.

Thanks

Norbert

(please Cc)


> On 17 December 2015 at 18:34, Norbert Preining <preining@xxxxxxxx> wrote:
> > * font corruption
> >   sometime sets of glyphs, or practically all glyphs disappear
> >   related probably to bug
> >   https://bugs.freedesktop.org/show_bug.cgi?id=55500
> >   I have sent some info there already, without response
> >
> >   Currently my font displays some kind of strange symbols instead of
> >   an m ... looks a bit like a Kanji.
> 
> I remember a similar bug around 2.99.917 but that tag is over a year
> old now and there have been many bug fixes since. You'll need to
> verify you can still reproduce your issue with the latest from
> git://anongit.freedesktop.org/xorg/driver/xf86-video-intel and if so
> do a bisect from the previous working kernel or xf86-video-intel to
> identify the problematic commit.

------------------------------------------------------------------------
PREINING, Norbert                               http://www.preining.info
JAIST, Japan                                 TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/