From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77274] [drm:dce6_afmt_write_speaker_allocation] *ERROR* Couldn't read Speaker Allocation Data Block: 0
Date: Thu, 10 Apr 2014 20:00:59 +0000 [thread overview]
Message-ID: <bug-77274-502-db5GR9VfpC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77274-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 606 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=77274
--- Comment #5 from Daniele Peruzzi <amnesiac2001@gmail.com> ---
I'm sorry about having pointed to an external pastebin, I've attached dmesg and
Xorg.0.log to the discussion now.
I'm quite sure I'm experiencing the same issues of the bug 77002 so I'm going
to follow that discussion.
I don't know what you mean for bisecting but if needed I can try with different
kernels, the last one that worked for me was the 3.13.8. I can also try patches
or test on different hardwares.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1623 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-04-10 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 16:11 [Bug 77274] New: [drm:dce6_afmt_write_speaker_allocation] *ERROR* Couldn't read Speaker Allocation Data Block: 0 bugzilla-daemon
2014-04-10 16:29 ` [Bug 77274] " bugzilla-daemon
2014-04-10 16:30 ` bugzilla-daemon
2014-04-10 19:46 ` bugzilla-daemon
2014-04-10 19:47 ` bugzilla-daemon
2014-04-10 20:00 ` bugzilla-daemon [this message]
2014-04-10 20:27 ` bugzilla-daemon
2014-04-11 8:34 ` bugzilla-daemon
2014-04-11 8:35 ` bugzilla-daemon
2014-04-11 8:41 ` bugzilla-daemon
2014-04-11 13:06 ` bugzilla-daemon
2014-04-11 13: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-77274-502-db5GR9VfpC@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 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.