From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77671] radeon system does not boot with 3.14.6 (bisect -> 4740d5c1c89c152ef847e4a479a87a25e763b286)
Date: Wed, 11 Jun 2014 17:31:53 +0000 [thread overview]
Message-ID: <bug-77671-2300-EVyKjXtiW7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-77671-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=77671
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
This commit requires new microcode in the driver. You are probably seeing the
firmware loader waiting for a long time for the new microcode to become
available. Grab the latest radeon microcode from the linux-firmware tree.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-06-11 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 17:23 [Bug 77671] New: radeon system does not boot with 3.14.6 (bisect -> 4740d5c1c89c152ef847e4a479a87a25e763b286) bugzilla-daemon
2014-06-11 17:31 ` bugzilla-daemon [this message]
2014-06-11 19:48 ` [Bug 77671] " 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-77671-2300-EVyKjXtiW7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox