From: James Jones <jajones@nvidia.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Ben Skeggs <bskeggs@redhat.com>
Cc: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 5.8-rc1
Date: Tue, 30 Jun 2020 21:40:19 -0700 [thread overview]
Message-ID: <ef7816b4-72ee-9e0e-8cac-4d80d8343f9f@nvidia.com> (raw)
In-Reply-To: <20200630230808.wj2xlt44vrszqfzx@box>
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? What version of Mesa? Any distro patches? Any non-default
xorg.conf options that would affect modesetting, your X driver if it
isn't modesetting, or glamour?
Thanks,
-James
On 6/30/20 4:08 PM, Kirill A. Shutemov wrote:
> On Tue, Jun 02, 2020 at 04:06:32PM +1000, Dave Airlie wrote:
>> James Jones (4):
> ...
>> drm/nouveau/kms: Support NVIDIA format modifiers
>
> This commit is the first one that breaks Xorg startup for my setup:
> GTX 1080 + Dell UP2414Q (4K DP MST monitor).
>
> I believe this is the crucial part of dmesg (full dmesg is attached):
>
> [ 29.997140] [drm:nouveau_framebuffer_new] Unsupported modifier: 0x300000000000014
> [ 29.997143] [drm:drm_internal_framebuffer_create] could not create framebuffer
> [ 29.997145] [drm:drm_ioctl] pid=3393, ret = -22
>
> Any suggestions?
>
next prev parent reply other threads:[~2020-07-01 4:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 6:06 [git pull] drm for 5.8-rc1 Dave Airlie
2020-06-02 21:21 ` Linus Torvalds
2020-06-02 21:22 ` Linus Torvalds
2020-06-02 21:56 ` Linus Torvalds
2020-06-03 7:18 ` Thomas Zimmermann
2020-06-03 7:43 ` Daniel Vetter
2020-06-02 22:14 ` Linus Torvalds
2020-06-02 23:03 ` Dave Airlie
2020-06-02 22:20 ` pr-tracker-bot
2020-06-03 20:13 ` Jason Gunthorpe
2020-06-04 8:10 ` Christian König
2020-06-04 8:13 ` Christoph Hellwig
2020-06-30 23:08 ` Kirill A. Shutemov
2020-07-01 4:40 ` James Jones [this message]
2020-07-01 7:57 ` Kirill A. Shutemov
2020-07-01 7:59 ` Kirill A. Shutemov
2020-07-01 19:45 ` James Jones
2020-07-02 7:36 ` Daniel Vetter
2020-07-02 7:59 ` Pekka Paalanen
2020-07-02 8:22 ` Daniel Stone
2020-07-02 21:14 ` James Jones
2020-07-03 6:01 ` James Jones
2020-07-03 7:16 ` Daniel Vetter
2020-07-01 11:24 ` Karol Herbst
2020-07-01 15:51 ` James Jones
2020-07-01 16:01 ` Daniel Vetter
2020-07-01 17:04 ` Karol Herbst
2020-07-01 17:37 ` James Jones
2020-07-01 18:08 ` Karol Herbst
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=ef7816b4-72ee-9e0e-8cac-4d80d8343f9f@nvidia.com \
--to=jajones@nvidia.com \
--cc=airlied@gmail.com \
--cc=bskeggs@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kirill@shutemov.name \
--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).