linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Intel Gfx Mailing List <intel-gfx@freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel      Sandybridge (was: Re: Linux 4.9-rc4)
Date: Mon, 07 Nov 2016 15:29:27 +0100	[thread overview]
Message-ID: <2766000.XjMLcDtyKU@merkaba> (raw)
In-Reply-To: <87twbj8sb3.fsf@intel.com>

Am Montag, 7. November 2016, 13:04:16 CET schrieb Jani Nikula:
> On Sun, 06 Nov 2016, Martin Steigerwald <martin@lichtvoll.de> wrote:
> > Hi.
> > 
> > Am Samstag, 5. November 2016, 16:46:33 CET schrieb Linus Torvalds:
> >> So it's once again a Saturday afternoon rather than Sunday, this time
> >> because I felt this rc was already big enough.
> > 
> > With kernel 4.9-rc4 I saw gfx corruptions like
> > 
> > https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png
> 
> Is this the same issue or a different issue from [1]? Since you mention
> -rc4, was this introduced in -rc4, or earlier?

Yes, the gfx corruption look similar. So I bet it is the same issue as in [1].


It is also the same kind of corruptions as shown in

[Bug 177701] warning in intel_dp_aux_transfer
https://bugzilla.kernel.org/show_bug.cgi?id=177701

Just compare

https://bugzilla.kernel.org/attachment.cgi?id=241801

with 

https://martin-steigerwald.de/tmp/display-issues-with-kernel-4.9-rc4.png


However that bug report links to

https://bugs.freedesktop.org/show_bug.cgi?id=97344

yet the patch mentioned in there does not fix the issue. So I wonder whether 
bug #97344 and bug #177701 are really the same.

> Please file a bug over at [2]. One issue per bug if this is different
> from [1].

As #177701 seem to have the same corruptions, yet I do not have any

merkaba:~#1> zgrep intel_dp_aux_transfer /var/log/kern.log*
merkaba:~#1>

Of course I can report a bug at fdo as well, but I am a bit confused whether 
it may not already have been reported. Well I hope I get a chance to report it 
there as well and you get to decide.

Thank you,
Martin

> [1] http://lkml.kernel.org/r/20161031215454.GB3473@suse.de
> [2]
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
> > in Konversation, Konsole, Akregator and other KDE/Qt related apps up to
> > the
> > point of not being able to use these applications in a meaningful way.
> > 
> > I first thought this might be due to upgrading Qt from 5.6.1 to 5.7.1, yet
> > after rebooting into 4.8 Linux kernel as packaged in Debian I saw no gfx
> > glitches like that anymore.
> > 
> > Anything known about this?
> > 
> > Machine is ThinkPad T520 with Sandybridge graphics.
> > 
> > Kernel compiled with Debian distro GCC 6 but using no-pie makefile patch.
> > 
> > Next week and weekend will be pretty busy and this is a production
> > machine, so bisection or any other time-consuming work on this is out of
> > question for me. I can provide additional details in case they are easy
> > and quick enough to obtain.
> > 
> > 
> > System information (now back on 4.8 kernel):
> > 
> > # phoronix-test-suite system-info
> > 
> > Phoronix Test Suite v5.2.1
> > System Information
> > 
> > Hardware:
> > Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
> > 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB,
> > Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd
> > Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED,
> > Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205
> > 
> > Software:
> > OS: Debian unstable, Kernel: 4.8.0-1-amd64 (x86_64), Desktop: KDE
> > Frameworks 5, Display Server: X Server 1.18.4, Display Driver:
> > modesetting 1.18.4, OpenGL: 3.3 Mesa 12.0.3, Compiler: GCC 6.2.0
> > 20161103, File-System: btrfs, Screen Resolution: 3840x1080
> > 
> > 
> > # apt-show-versions | egrep
> > "(^libgl1-mesa-dri|^libdrm-intel1|xserver-xorg-
> > core)" | grep amd64
> > libdrm-intel1:amd64/sid 2.4.71-1 uptodate
> > libgl1-mesa-dri:amd64/sid 12.0.3-3 uptodate
> > xserver-xorg-core:amd64/sid 2:1.18.4-2 uptodate
> > 
> > 
> > Excerpt of glxinfo:
> > 
> > Extended renderer info (GLX_MESA_query_renderer):
> >     Vendor: Intel Open Source Technology Center (0x8086)
> >     Device: Mesa DRI Intel(R) Sandybridge Mobile  (0x126)
> >     Version: 12.0.3
> >     Accelerated: yes
> >     Video memory: 1536MB
> >     Unified memory: yes
> >     Preferred profile: core (0x1)
> >     Max core profile version: 3.3
> >     Max compat profile version: 3.0
> >     Max GLES1 profile version: 1.1
> >     Max GLES[23] profile version: 3.0
> > 
> > X.org runs with modesetting driver (default was changed in Debian Sid a
> > while back).
> > 
> > Thanks,
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx


-- 
Martin

  reply	other threads:[~2016-11-07 14:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 23:46 Linux 4.9-rc4 Linus Torvalds
2016-11-06 14:48 ` [REGRESSION] Linux 4.9-rc4: gfx glitches on Intel Sandybridge (was: Re: Linux 4.9-rc4) Martin Steigerwald
2016-11-06 15:25   ` Mihai Donțu
2016-11-06 15:40     ` Martin Steigerwald
2016-11-06 17:50     ` Martin Steigerwald
2016-11-07 11:04   ` [Intel-gfx] " Jani Nikula
2016-11-07 14:29     ` Martin Steigerwald [this message]
2016-11-07 17:09       ` Jani Nikula
2016-11-07 22:53         ` Martin Steigerwald
2016-11-08 15:11         ` Martin Steigerwald
2016-11-08 15:17           ` Martin Steigerwald
2016-11-09  8:20             ` Martin Steigerwald
2016-11-09  9:42               ` Jani Nikula
2016-11-09  9:59                 ` Martin Steigerwald

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=2766000.XjMLcDtyKU@merkaba \
    --to=martin@lichtvoll.de \
    --cc=intel-gfx@freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).