dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70439] Mobility 4570: System freezes after ~5s of enabling audio via xrandr
Date: Mon, 14 Oct 2013 19:34:14 +0000	[thread overview]
Message-ID: <bug-70439-502-Upu61BXHa3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70439-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 941 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=70439

--- Comment #12 from Mohammad AlSaleh <CE.Mohammad.AlSaleh@gmail.com> ---
(In reply to comment #10)
> (In reply to comment #6)
> > (In reply to comment #2)
> > > Did you started audio before enabling it with "xrandr --output HDMI-0 --set
> > > audio auto" ?
> 
> Had you started audio playback in the application before enabling it with
> xrandr?  If so, do you still get the hang if you enable audio with xrandr
> first, and then start playback in the application?
> 
> > 
> > radeon.audio=1 seems to have no effect!
> > 
> 
> radeon.audio=1 is the default now.

Upgraded to 3.12rc5.

I get the hang in all cases. Even if I don't use an application at all.

The hang sometimes happens so fast before xrandr exiting. And sometimes it
takes ~90s. But I always get a hang at the end.

I'll test with the patch now.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1989 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

  parent reply	other threads:[~2013-10-14 19:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13 23:40 [Bug 70439] New: Mobility 4570: System freezes after ~5s of enabling audio via xrandr bugzilla-daemon
2013-10-14  2:20 ` [Bug 70439] " bugzilla-daemon
2013-10-14  7:58 ` bugzilla-daemon
2013-10-14 11:22 ` bugzilla-daemon
2013-10-14 11:32 ` bugzilla-daemon
2013-10-14 11:38 ` bugzilla-daemon
2013-10-14 11:59 ` bugzilla-daemon
2013-10-14 12:00 ` bugzilla-daemon
2013-10-14 12:01 ` bugzilla-daemon
2013-10-14 12:07 ` bugzilla-daemon
2013-10-14 16:19 ` bugzilla-daemon
2013-10-14 17:22 ` bugzilla-daemon
2013-10-14 19:34 ` bugzilla-daemon [this message]
2013-10-14 22:39 ` bugzilla-daemon
2013-10-14 22:50 ` bugzilla-daemon
2013-10-15 10:52 ` bugzilla-daemon
2013-10-16 21:58 ` bugzilla-daemon
2013-10-17 20:13 ` bugzilla-daemon
2013-10-18 13:41 ` bugzilla-daemon
2013-10-22 14:21 ` 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-70439-502-Upu61BXHa3@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;
as well as URLs for NNTP newsgroup(s).