1. The "cx22702 no longer works"-issue where cx22702_{readreg|writereg} is failing.
According to the info in another bug this is because a gpio is mis-configured accidently.
2. snd_pcm_proc_info_read+0x34/0x180 [snd_pcm] to crash with an uninitialized pointer.
Maybe this happens due to incomplete error handling for 1.?
and finally
3. Locking issue in sound/core/devices.c where a list is destroyed when it is not locked.
I am of the opinion that 3. is not related to the other two, because the patch for 3. just solved issue 3 for me.
Problem 1. and 2. do still exist on my system. I have found the time to test the gpio fix yet.
Hi Leann,
I think that I see three issues on my box:
1. The "cx22702 no longer works"-issue where cx22702_ {readreg| writereg} is failing.
According to the info in another bug this is because a gpio is mis-configured accidently.
2. snd_pcm_ proc_info_ read+0x34/ 0x180 [snd_pcm] to crash with an uninitialized pointer.
Maybe this happens due to incomplete error handling for 1.?
and finally devices. c where a list is destroyed when it is not locked.
3. Locking issue in sound/core/
I am of the opinion that 3. is not related to the other two, because the patch for 3. just solved issue 3 for me.
Problem 1. and 2. do still exist on my system. I have found the time to test the gpio fix yet.
Frank