From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77671] New: radeon system does not boot with 3.14.6 (bisect -> 4740d5c1c89c152ef847e4a479a87a25e763b286)
Date: Wed, 11 Jun 2014 17:23:06 +0000 [thread overview]
Message-ID: <bug-77671-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=77671
Bug ID: 77671
Summary: radeon system does not boot with 3.14.6 (bisect ->
4740d5c1c89c152ef847e4a479a87a25e763b286)
Product: Drivers
Version: 2.5
Kernel Version: 3.14.6
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: renerietz@gmx.net
Regression: No
My system does not boot anymore (blank screen, no response, no journal entries
after restart) with kernel 3.14.6. I did a bisect on the linux-stable tree
(3.14.y branch). The last non-working commit was:
commit 4740d5c1c89c152ef847e4a479a87a25e763b286
Author: Alex Deucher <alexdeucher@gmail.com>
Date: Fri Apr 11 11:21:50 2014 -0400
drm/radeon: add support for newer mc ucode on CI (v2)
commit 277babc374f6ecab6af182554f5d9f35a7768755 upstream.
Fixes mclk stability on certain asics.
v2: print out mc firmware version used and size
bug:
https://bugs.freedesktop.org/show_bug.cgi?id=75992
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Chipset info from Xorg: RADEON(0): Chipset: "VERDE" (ChipID = 0x683d)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-06-11 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 17:23 bugzilla-daemon [this message]
2014-06-11 17:31 ` [Bug 77671] radeon system does not boot with 3.14.6 (bisect -> 4740d5c1c89c152ef847e4a479a87a25e763b286) bugzilla-daemon
2014-06-11 19:48 ` 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@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.