From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88481] Kernel oops leaves system without graphical output [radeon]
Date: Sat, 22 Nov 2014 00:54:32 +0000 [thread overview]
Message-ID: <bug-88481-2300-x4fr86y6nm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-88481-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=88481
Adam Williamson <adamw@happyassassin.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adamw@happyassassin.net
--- Comment #10 from Adam Williamson <adamw@happyassassin.net> ---
I'm not sure it's right to mark it as fixed until the patch goes to 3.17 - it's
fixed in mainline, sure, but not stable. The fix seems to have missed the boat
for 3.17.4. (I got burned by this with OpenELEC 5.0 beta 3, which happened to
get kernel 3.17.3, and is commonly used on systems with Radeon graphics
adapters and HDMI displays as it's an HTPC appliance distro...)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-22 0:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 1:33 [Bug 88481] New: Kernel oops leaves system without graphical output [radeon] bugzilla-daemon
2014-11-19 3:40 ` [Bug 88481] " bugzilla-daemon
2014-11-19 3:42 ` bugzilla-daemon
2014-11-19 3:48 ` bugzilla-daemon
2014-11-19 3:50 ` bugzilla-daemon
2014-11-19 7:34 ` bugzilla-daemon
2014-11-19 14:38 ` bugzilla-daemon
2014-11-19 15:52 ` bugzilla-daemon
2014-11-19 16:46 ` bugzilla-daemon
2014-11-19 21:06 ` bugzilla-daemon
2014-11-20 1:08 ` bugzilla-daemon
2014-11-22 0:54 ` bugzilla-daemon [this message]
2014-11-22 13:35 ` bugzilla-daemon
2014-11-27 1:33 ` bugzilla-daemon
2014-12-12 10:58 ` bugzilla-daemon
2014-12-12 14:14 ` 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-88481-2300-x4fr86y6nm@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.