From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111792] [AMD tahiti xt] amd-staging-drm-next broken since linux 5.3.0-rc3 rebase
Date: Mon, 23 Sep 2019 21:11:20 +0000 [thread overview]
Message-ID: <bug-111792-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 775 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111792
Bug ID: 111792
Summary: [AMD tahiti xt] amd-staging-drm-next broken since
linux 5.3.0-rc3 rebase
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: highest
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: sylvain.bertrand@gmail.com
got the rebased amd-staging-drm-next branch today, configured and compiled
linux, xorg hangs while probing card0. See provided logs.
yes, I can bisect.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2074 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-09-23 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 21:11 bugzilla-daemon [this message]
2019-09-23 21:11 ` [Bug 111792] [AMD tahiti xt] amd-staging-drm-next broken since linux 5.3.0-rc3 rebase bugzilla-daemon
2019-09-23 21:13 ` bugzilla-daemon
2019-09-25 2:24 ` bugzilla-daemon
2019-09-25 2:52 ` bugzilla-daemon
2019-09-25 12:04 ` bugzilla-daemon
2019-09-25 12:06 ` bugzilla-daemon
2019-09-25 14:04 ` bugzilla-daemon
2019-09-25 15:10 ` bugzilla-daemon
2019-09-25 15:14 ` bugzilla-daemon
2019-09-25 15:31 ` bugzilla-daemon
2019-09-25 15:52 ` bugzilla-daemon
2019-09-25 19:43 ` bugzilla-daemon
2019-09-25 19:54 ` bugzilla-daemon
2019-09-25 20:22 ` bugzilla-daemon
2019-11-19 9:52 ` 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-111792-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox