From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109487] drm-next-5.1-wip broken as of 672c6238
Date: Mon, 28 Jan 2019 19:42:28 +0000 [thread overview]
Message-ID: <bug-109487-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 999 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109487
Bug ID: 109487
Summary: drm-next-5.1-wip broken as of 672c6238
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: irherder@gmail.com
Created attachment 143242
--> https://bugs.freedesktop.org/attachment.cgi?id=143242&action=edit
dmesg with backtrace
Currently https://cgit.freedesktop.org/~agd5f/linux/tree/?h=drm-next-5.1-wip is
totally broken at least for raven 2400g apu.
4.20.5 works pretty well on this machine.
Dmesg with backtrace attached.
Dear AMD developers: it would be bad if drm-next-5.1-wip code in its current
state went into mainline, please review and fix.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2498 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-28 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 19:42 bugzilla-daemon [this message]
2019-01-28 19:54 ` [Bug 109487] drm-next-5.1-wip broken as of 672c6238 bugzilla-daemon
2019-01-28 19:56 ` bugzilla-daemon
2019-01-28 21:39 ` bugzilla-daemon
2019-01-29 15:28 ` bugzilla-daemon
2019-01-29 15:35 ` bugzilla-daemon
2019-01-29 16:29 ` bugzilla-daemon
2019-11-19 9:11 ` 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-109487-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.