From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73848] [Radeon] Blank screen after boot with kernel 3.12.x, xorg 1.15
Date: Mon, 03 Feb 2014 20:29:51 +0000 [thread overview]
Message-ID: <bug-73848-502-YSCKU5WDf4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73848-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1088 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73848
--- Comment #15 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #14)
> (In reply to comment #13)
> > Also, the fact that disabling audio on a newer kernel doesn't break things
>
> If I disable audio, shouldn't the Radeon HDMI ALSA device disappear? That
> didn't happen for me when I set radeon.audio=0. Am I doing something wrong?
>
No. disabling audio in the radeon driver just disables the audio stream in the
hdmi stream. The audio device itself can't be disabled.
> > The audio hardware doesn't interact with the memory controller (or 3D engine
> > for that matter) so I don't really see how it could cause a GPU page fault.
>
> Could it be a timing issue? Audio init delays startup enough that it doesn't
> hit some races anymore?
If you disable acceleration (add Option "NoAccel" "true" to the device section
of your xorg config) do you still get the problems? It's most likely some
issue related to the 3D engine set up in mesa.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2082 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-02-03 20:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 21:10 [Bug 73848] New: [Radeon] Blank screen after boot with kernel 3.12.x, xorg 1.15 bugzilla-daemon
2014-01-20 21:11 ` [Bug 73848] " bugzilla-daemon
2014-01-20 21:11 ` bugzilla-daemon
2014-01-20 23:28 ` bugzilla-daemon
2014-01-20 23:45 ` bugzilla-daemon
2014-01-22 22:49 ` bugzilla-daemon
2014-01-22 22:59 ` bugzilla-daemon
2014-01-22 23:03 ` bugzilla-daemon
2014-01-23 16:09 ` bugzilla-daemon
2014-01-23 18:21 ` bugzilla-daemon
2014-01-26 11:56 ` bugzilla-daemon
2014-01-28 22:46 ` bugzilla-daemon
2014-02-03 19:06 ` bugzilla-daemon
2014-02-03 19:57 ` bugzilla-daemon
2014-02-03 20:18 ` bugzilla-daemon
2014-02-03 20:29 ` bugzilla-daemon [this message]
2014-02-04 18:38 ` bugzilla-daemon
2019-11-19 8:42 ` 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-73848-502-YSCKU5WDf4@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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