From: "Dâniel Fraga" <fragabr@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Realtek ACL892: audio gap ~ each 10 seconds? [SOLVED]
Date: Fri, 11 May 2012 11:53:09 -0300 [thread overview]
Message-ID: <4fad27d8.6974340a.5e07.6c22@mx.google.com> (raw)
In-Reply-To: <s5h3976akpa.wl%tiwai@suse.de>
On Fri, 11 May 2012 15:52:49 +0200
Takashi Iwai <tiwai@suse.de> wrote:
> Could you check which unsolicited events are triggered on your
> machine? When you build your kernel with the tracing support
> (CONFIG_TRACEPOINTS=y), you can enable the tracing via
>
> % echo 1 > /sys/kernel/debug/tracing/events/hda/hda_unsol_event/enable
> .....
>
> Check whether the events come up frequently even without
> plugging/unplugging any jacks. Usually this shouldn't happen. But in
> the case of problematic hardware with the auto-mute, many bogus unsol
> events are triggered.
Takashi, I got the following:
# tracer: nop
#
# entries-in-buffer/entries-written: 12/12 #P:8
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
<idle>-0 [000] d.h3 449.885014: hda_unsol_event: [0] res=40000c1, res_ex=10
<idle>-0 [000] d.h3 449.906339: hda_unsol_event: [0] res=4000041, res_ex=10
<idle>-0 [000] d.h3 472.269431: hda_unsol_event: [0] res=40000c1, res_ex=10
<idle>-0 [000] d.h3 472.290721: hda_unsol_event: [0] res=4000041, res_ex=10
<idle>-0 [000] d.h3 478.262018: hda_unsol_event: [0] res=40000c1, res_ex=10
<idle>-0 [000] d.h3 478.283319: hda_unsol_event: [0] res=4000041, res_ex=10
<idle>-0 [000] d.h3 482.934742: hda_unsol_event: [0] res=40000c1, res_ex=10
<idle>-0 [000] d.h3 482.956033: hda_unsol_event: [0] res=4000041, res_ex=10
<idle>-0 [000] d.h3 584.308420: hda_unsol_event: [0] res=40000c1, res_ex=10
<idle>-0 [000] d.h3 584.329693: hda_unsol_event: [0] res=4000041, res_ex=10
<idle>-0 [000] d.h3 593.781622: hda_unsol_event: [0] res=40000c1, res_ex=10
<idle>-0 [000] d.h3 593.802890: hda_unsol_event: [0] res=4000041, res_ex=10
***
But I couldn't notice it happening exactly during the click and
pop... When click and pop happens, nothing happens in this file... So I
don't know if it will be useful to you.
Anyway, I'm confortable with auto-mute off... If you need more
testing, just ask. I'll be glad to help.
Thank you.
--
Linux 3.4.0-rc6: Saber-toothed Squirrel
http://www.youtube.com/DanielFragaBR
next prev parent reply other threads:[~2012-05-11 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:11 Realtek ACL892: audio gap ~ each 10 seconds? Dâniel Fraga
2012-05-06 5:51 ` Alexander E. Patrakov
2012-05-08 15:11 ` Dâniel Fraga
2012-05-11 1:39 ` Realtek ACL892: audio gap ~ each 10 seconds? [SOLVED] Dâniel Fraga
2012-05-11 5:39 ` Takashi Iwai
2012-05-11 7:01 ` Dâniel Fraga
2012-05-11 7:43 ` Takashi Iwai
2012-05-11 13:45 ` David Henningsson
2012-05-11 13:55 ` Takashi Iwai
2012-05-11 14:25 ` David Henningsson
2012-05-11 14:29 ` Takashi Iwai
2012-05-11 15:20 ` David Henningsson
[not found] ` <4fad162b.07b3340a.14cb.5a06@mx.google.com>
2012-05-11 13:52 ` Takashi Iwai
2012-05-11 14:53 ` Dâniel Fraga [this message]
2012-05-11 15:05 ` Takashi Iwai
2012-05-11 15:51 ` Dâniel Fraga
2012-05-11 15:54 ` Takashi Iwai
2012-05-11 16:11 ` Dâniel Fraga
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=4fad27d8.6974340a.5e07.6c22@mx.google.com \
--to=fragabr@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.