From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69301] no screen on update from 3.12.0
Date: Sun, 26 Jan 2014 15:48:51 +0000 [thread overview]
Message-ID: <bug-69301-2300-1ZutVjuTiY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-69301-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=69301
--- Comment #7 from Jan Outhuis <jouthuis@dds.nl> ---
No. Same happens as before: radeon.dpm enabled gives a deadstop early in
the bootprocess (hardware reboot required); radeon.dpm=0 finishes the
bootprocess, but no screen on tty7.
On Fri, 2014-01-24 at 15:08 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=69301
>
> --- Comment #6 from Alex Deucher <alexdeucher@gmail.com> ---
> Does reverting:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4573388c92ee60b4ed72b8d95b73df861189988c
> help?
>
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-01-26 15:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 14:44 [Bug 69301] New: no screen on update from 3.12.0 bugzilla-daemon
2014-01-23 14:45 ` [Bug 69301] " bugzilla-daemon
2014-01-23 15:22 ` bugzilla-daemon
2014-01-23 15:27 ` bugzilla-daemon
2014-01-23 17:14 ` bugzilla-daemon
2014-01-23 20:50 ` bugzilla-daemon
2014-01-23 23:04 ` bugzilla-daemon
2014-01-24 15:08 ` bugzilla-daemon
2014-01-26 15:48 ` bugzilla-daemon [this message]
2014-01-28 18:45 ` bugzilla-daemon
2014-01-30 13:39 ` bugzilla-daemon
2014-01-30 17:18 ` bugzilla-daemon
2014-01-31 14:48 ` bugzilla-daemon
2014-02-02 18:38 ` bugzilla-daemon
2014-02-03 15:18 ` bugzilla-daemon
2014-02-03 15:25 ` bugzilla-daemon
2014-02-06 17:03 ` bugzilla-daemon
2014-02-06 17:10 ` bugzilla-daemon
2014-02-07 2:02 ` bugzilla-daemon
2014-02-07 13:44 ` bugzilla-daemon
2014-02-16 12:51 ` bugzilla-daemon
2015-04-25 16:37 ` bugzilla-daemon
2015-04-30 12:06 ` 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-69301-2300-1ZutVjuTiY@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.