From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 218250] New: Regression nouveau driver
Date: Sun, 10 Dec 2023 16:15:52 +0000 [thread overview]
Message-ID: <bug-218250-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218250
Bug ID: 218250
Summary: Regression nouveau driver
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: blocking
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: 19.jaime.91@gmail.com
Regression: No
Created attachment 305577
--> https://bugzilla.kernel.org/attachment.cgi?id=305577&action=edit
dmesg
ae1aadb1eb8d3cbc52e42bee71d67bd4a71f9f07 is the first bad commit
commit ae1aadb1eb8d3cbc52e42bee71d67bd4a71f9f07
Author: Dave Airlie <airlied@redhat.com>
Date: Thu Nov 16 00:39:33 2023 +1000
nouveau: don't fail driver load if no display hw present.
If we get back ENODEV don't fail load. There are nvidia devices
that don't have display blocks and the driver should work on those.
Fixes: 15740541e8f0 ("drm/nouveau/devinit/tu102-: prepare for GSP-RM")
Link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/270
Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Danilo Krummrich <dakr@redhat.com>
Link:
https://patchwork.freedesktop.org/patch/msgid/20231115143933.261287-1-airlied@gmail.com
drivers/gpu/drm/nouveau/nouveau_display.c | 5 +++++
1 file changed, 5 insertions(+)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-12-10 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 16:15 bugzilla-daemon [this message]
2023-12-10 16:16 ` [Bug 218250] Regression nouveau driver bugzilla-daemon
2023-12-11 2:41 ` bugzilla-daemon
2023-12-11 6:18 ` bugzilla-daemon
2023-12-11 10:02 ` bugzilla-daemon
2023-12-11 18:07 ` bugzilla-daemon
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=bug-218250-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.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).