From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196117] amdgpu - RX 480 (polaris) - freeze during boot
Date: Mon, 19 Jun 2017 20:23:59 +0000 [thread overview]
Message-ID: <bug-196117-2300-BIHRmsQGhD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196117-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196117
--- Comment #4 from Paul K. Gerke (paulkgerke@craftware.nl) ---
Hmm... I quickly checked the kernel codebase but do not really have a clue what
is going on. When cross-correlating my issues with other issues, I guess it all
starts to go wrong at the line "Something is broken"... which I found is just a
result of a statecheck.
I think I will try to follow this lead next:
https://bugzilla.kernel.org/show_bug.cgi?id=193651#c8
It seems sensible to me that my issues are of similar nature with regards to
"Stock distribution kernels do not have stable amdgpu code".
--
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 prev parent reply other threads:[~2017-06-19 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 20:08 [Bug 196117] New: amdgpu RC 480 (polaris) freeze after initramfs, before kernel load bugzilla-daemon
2017-06-18 20:33 ` [Bug 196117] " bugzilla-daemon
2017-06-18 20:35 ` [Bug 196117] amdgpu - RX 480 (polaris) - freeze during boot bugzilla-daemon
2017-06-19 2:17 ` bugzilla-daemon
2017-06-19 8:17 ` bugzilla-daemon
2017-06-19 20:23 ` bugzilla-daemon [this message]
2017-06-22 23:22 ` bugzilla-daemon
2017-06-23 23:48 ` bugzilla-daemon
2017-06-23 23:50 ` bugzilla-daemon
2017-06-23 23:51 ` 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-196117-2300-BIHRmsQGhD@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.