
At Fri, 11 May 2012 11:53:09 -0300, Dâniel Fraga wrote:
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.
Did you get any unsol events while you don't plug anything? The output about indicates that it's an unsol event from the headphone pin (tag=1).
Takashi