linux-kernel - Re: [git pull] drm for 5.8-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 1 Jul 2020 10:59:02 +0300
From:   "Kirill A. Shutemov" <kirill@...temov.name>
To:     James Jones <jajones@...dia.com>
Cc:     Ben Skeggs <bskeggs@...hat.com>, Dave Airlie <airlied@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 5.8-rc1

On Wed, Jul 01, 2020 at 10:57:19AM +0300, Kirill A. Shutemov wrote:
> On Tue, Jun 30, 2020 at 09:40:19PM -0700, James Jones wrote:
> > This implies something is trying to use one of the old
> > DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifiers with DRM-KMS without
> > first checking whether it is supported by the kernel.  I had tried to force
> > an Xorg+Mesa stack without my userspace patches to hit this error when
> > testing, but must have missed some permutation.  If the stalled Mesa patches
> > go in, this would stop happening of course, but those were held up for a
> > long time in review, and are now waiting on me to make some modifications.
> > 
> > Are you using the modesetting driver in X? If so, with glamor I presume?
> 
> Yes and yes. I attached Xorg.log.

Attached now.
-- 
 Kirill A. Shutemov

View attachment "Xorg.0.log" of type "text/plain" (65649 bytes)