From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207581] New: [amdgpu] Framebuffer no image CARRIZO and STONEY
Date: Tue, 05 May 2020 13:06:02 +0000 [thread overview]
Message-ID: <bug-207581-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=207581
Bug ID: 207581
Summary: [amdgpu] Framebuffer no image CARRIZO and STONEY
Product: Drivers
Version: 2.5
Kernel Version: 5.4.27
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: Jan.Burgmeier@unicon-software.com
Regression: No
Created attachment 288907
--> https://bugzilla.kernel.org/attachment.cgi?id=288907&action=edit
Path for 5.4.27 to fix framebuffer
Hi,
we have some ancient software which uses DirectFB to draw to the framebuffer
during installation.
After upgrading from kernel 4.14.99 to 5.4.27 the framebuffer stall the GPU and
only a black image was shown. This could be reprocuded on an Igel UD 7
(CARRIZO) and a Lenovo 14w (STONEY) lspci -vv is attached from both devices.
We did some more investigation to find the breaking change please see attached
git bisect log:
6c8d74caa2fa33908ecd07fb1cf1b7bc629b367a is the first bad commit
After finding the bad commit we reverted the changes on the 5.4.27 and
framebuffer started working again. Patch for reverting is also attached.
Kind regards,
Jan Burgmeier
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-05-05 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:06 bugzilla-daemon [this message]
2020-05-05 13:07 ` [Bug 207581] [amdgpu] Framebuffer no image CARRIZO and STONEY bugzilla-daemon
2020-05-05 13:08 ` bugzilla-daemon
2020-05-05 13:08 ` bugzilla-daemon
2020-05-05 13:46 ` bugzilla-daemon
2020-05-05 14:29 ` bugzilla-daemon
2020-05-06 7:38 ` 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-207581-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.