From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39832] HDA ATI HDMI: no sound with 3.0 - 2.6.39.3 works
Date: Fri, 25 May 2012 06:21:20 +0000 (UTC) [thread overview]
Message-ID: <20120525062120.F355E11FD1D@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-39832-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=39832
Santiago Garcia Mantinan <manty@manty.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manty@manty.net
--- Comment #23 from Santiago Garcia Mantinan <manty@manty.net> 2012-05-25 06:21:20 ---
Hi, I'm the one that submitted the problem in Comment #19 From Jonathan Nieder,
I have now uploaded to alsa the alsa-info.sh collected data and tests include
3.3.6.
Here are the kernels for which I submitted the info and the link to the info
submitted.
ii linux-image-2.6.39-2-686-pae 2.6.39-3
ii linux-image-3.2.0-2-686-pae 3.2.17-1
ii linux-image-3.3.0-trunk-686-pae 3.3.6-1~experimental.1
3.2.17
http://www.alsa-project.org/db/?f=1065dc2b77cb999525747f08238309c2de1013c9
3.3.6
http://www.alsa-project.org/db/?f=499ea9e973c6119416e9356e23451250893048d5
2.6.39
http://www.alsa-project.org/db/?f=9c9b0c9e26c1bc570e15ed12b23d8b6ff1386ae5
I have previously tested 3.0 and 3.1 kernels and were also working, in I had to
go to 2.6.39 to find a working kernel.
I don't have access to the machine at anytime that is why it took so long to
report back, I hope I can test 3.4 soon but I don't think that will make any
change.
Hope this helps identify the bug, regards.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-05-25 6:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-39832-2300@https.bugzilla.kernel.org/>
2011-08-14 19:20 ` [Bug 39832] HDA ATI HDMI: no sound with 3.0 - 2.6.39.3 works bugzilla-daemon
2011-09-02 0:21 ` bugzilla-daemon
2011-09-02 9:47 ` bugzilla-daemon
2011-09-02 13:44 ` bugzilla-daemon
2011-09-02 14:19 ` bugzilla-daemon
2011-09-02 14:33 ` bugzilla-daemon
2011-09-03 11:00 ` bugzilla-daemon
2012-01-24 23:15 ` bugzilla-daemon
2012-02-17 5:38 ` bugzilla-daemon
2012-05-15 20:53 ` bugzilla-daemon
2012-05-17 7:14 ` bugzilla-daemon
2012-05-17 11:14 ` bugzilla-daemon
2012-05-25 6:21 ` bugzilla-daemon [this message]
2012-05-25 7:35 ` bugzilla-daemon
2012-07-16 6:54 ` bugzilla-daemon
2013-12-23 14:13 ` bugzilla-daemon
2016-11-09 19: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=20120525062120.F355E11FD1D@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 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).