From: "S. Christian Collins" <s.chriscollins@gmail.com>
To: Mark Hills <mark@xwax.org>, Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: "alsactl store" fails to save Echo Gina3G mixer
Date: Thu, 14 Sep 2017 08:40:35 -0500 [thread overview]
Message-ID: <d4b1b2e2-687a-a9fc-4244-9ca54d709f60@gmail.com> (raw)
In-Reply-To: <1709042113040.5915@beth.localdomain>
Takashi, is there anything else you would like me to do to help with
this issue? Should it perhaps be filed on the bug tracker so it doesn't
get lost in this list?
-~Chris
On 09/04/2017 03:23 PM, Mark Hills wrote:
> On Thu, 31 Aug 2017, Takashi Sakamoto wrote:
>
>> On Aug 29 2017 12:46, S. Christian Collins wrote:
>>> On 08/28/2017 10:33 PM, Takashi Sakamoto wrote:
>>>> Would you get output from below command line for your Gina 3G?
>>>>
>>>> $ amixer scontrols
>>> The output of "amixer -c 1 scontrols" is attached to this e-mail as
>>> "scontrols.txt".
>>>
>>>> And typically state data is stored into '/var/lib/alsa/asound.state' as a
>>>> default. For my information, could you disclose it if possible?
>>> Yes, it is also attached to this e-mail. The asound.state file was last
>>> modified on March 26th. I remember that I used to not get the error when
>>> using "alsactl store", so perhaps an update caused this issue to appear
>>> around that time?
>> $ alsactl -f ~/asound1.state store 1
>> (alsa-utils:alsactl/alsactl.c)
>> main()
>> (alsa-utils:alsactl/state.c)
>> ->save_state()
>> ->get_controls()
>> ->get_control()
>> snd_ctl_elem_info(info)
>> count = snd_ctl_elem_info_get_count(info)
>> for (i = 0; i < count; i++)
>> snd_ctl_elem_value_get_integer(ctl, i)
>>
>> I guess that 'snd-echo3g.ko' returns value greater than 128 in a call graph of
>> 'snd_ctl_elem_info_get_count()', then a call of
>> 'snd_ctl_elem_value_get_integer()' hits an assertion in the function.
> This sounds familiar -- would you like to compare to my post earlier in
> the year (for Layla):
>
> http://mailman.alsa-project.org/pipermail/alsa-devel/2017-March/119125.html
>
> In this post I made a misdiagnosis that it was related to my move to a
> 64-bit userland. When I found I could revert a patch it looks like it was
> coincidence.
>
>> A patch mentioned by Mark Hills (a commit 275353bb684e 'ALSA: echoaudio: purge
>> contradictions between dimension matrix members and total number of members')
>> is fairly valid in a logical design of ALSA control protocol/interface. In
>> detail, please refer to my post[1].
>>
>> Some of ALSA drivers for PCI cards produced by Echo Audio potentially have
>> problems which I mentioned in the post. They can cause buffer-over-run over
>> 'struct snd_ctl_elem_value.value' in user space. The drivers should be going
>> to fix.
>>
>> I wrote a small program to validate dimension information for your card[2].
>> Would you please execute it? Like:
>>
>> $ gcc -o ./test ./alsa-ctl-dimen-check.c
>> $ ./test /dev/snd/controlC[0-9]
> In case it's useful, I've also attached the output for my Layla 3G.
>
> This is with the patch reverted as that's the kernel currently in use.
> If it would be helpful for me to build another kernel, I can do that.
>
next prev parent reply other threads:[~2017-09-14 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 15:34 "alsactl store" fails to save Echo Gina3G mixer S. Christian Collins
2017-08-29 3:33 ` Takashi Sakamoto
2017-08-29 3:46 ` S. Christian Collins
2017-08-31 3:50 ` Takashi Sakamoto
2017-08-31 20:25 ` S. Christian Collins
2017-09-04 20:23 ` Mark Hills
2017-09-14 13:40 ` S. Christian Collins [this message]
2017-09-15 5:21 ` Takashi Sakamoto
2017-10-03 1:53 ` Takashi Sakamoto
2017-10-03 18:05 ` S. Christian Collins
2017-08-29 20:36 ` Mark Hills
2017-08-30 14:17 ` S. Christian Collins
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=d4b1b2e2-687a-a9fc-4244-9ca54d709f60@gmail.com \
--to=s.chriscollins@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=mark@xwax.org \
--cc=o-takashi@sakamocchi.jp \
/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).