From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
linux-usb@vger.kernel.org, linux-sound@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: USB sound card issues
Date: Tue, 15 Jun 2021 02:14:20 -0400 [thread overview]
Message-ID: <27987.1623737660@turing-police> (raw)
In-Reply-To: <CAHhAz+goVhacpDPc-OaVuG151TS8QKYdsqdnK9UcAx+Hc07zSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Sat, 12 Jun 2021 16:45:00 +0530, Muni Sekhar said:
> > And if it's configurable for multiple formats, was it set for the correct one?
> Is there a way to verify was it set for the correct one or not?
arecord -v gives what it thinks the setup is.
> > Does the record die immediately, or hang for a few seconds and timeout?
> What is the difference between these two ways?
An immediate failure is usually related to a "Can't do it" situation where the
USB interaction to configure the device has failed, while a timeout usually
indicates that the configuration at least *claimed* to succeed, but is failing
to properly transfer valid data.
> For my hardware, I noticed that it hangs for a few seconds and gives EIO (arecord:
> pcm_read:2032: read error: Input/output error).
Given that the usbmon output ran to several megabytes, that's tending to
point at "the card was returning lots of packets, but they weren't actually the
format/data that arecord was expecting.
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
linux-usb@vger.kernel.org, linux-sound@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: USB sound card issues
Date: Tue, 15 Jun 2021 02:14:20 -0400 [thread overview]
Message-ID: <27987.1623737660@turing-police> (raw)
In-Reply-To: <CAHhAz+goVhacpDPc-OaVuG151TS8QKYdsqdnK9UcAx+Hc07zSg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]
On Sat, 12 Jun 2021 16:45:00 +0530, Muni Sekhar said:
> > And if it's configurable for multiple formats, was it set for the correct one?
> Is there a way to verify was it set for the correct one or not?
arecord -v gives what it thinks the setup is.
> > Does the record die immediately, or hang for a few seconds and timeout?
> What is the difference between these two ways?
An immediate failure is usually related to a "Can't do it" situation where the
USB interaction to configure the device has failed, while a timeout usually
indicates that the configuration at least *claimed* to succeed, but is failing
to properly transfer valid data.
> For my hardware, I noticed that it hangs for a few seconds and gives EIO (arecord:
> pcm_read:2032: read error: Input/output error).
Given that the usbmon output ran to several megabytes, that's tending to
point at "the card was returning lots of packets, but they weren't actually the
format/data that arecord was expecting.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: linux-sound@vger.kernel.org, linux-usb@vger.kernel.org,
alsa-devel <alsa-devel@alsa-project.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: USB sound card issues
Date: Tue, 15 Jun 2021 06:14:20 +0000 [thread overview]
Message-ID: <27987.1623737660@turing-police> (raw)
In-Reply-To: <CAHhAz+goVhacpDPc-OaVuG151TS8QKYdsqdnK9UcAx+Hc07zSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Sat, 12 Jun 2021 16:45:00 +0530, Muni Sekhar said:
> > And if it's configurable for multiple formats, was it set for the correct one?
> Is there a way to verify was it set for the correct one or not?
arecord -v gives what it thinks the setup is.
> > Does the record die immediately, or hang for a few seconds and timeout?
> What is the difference between these two ways?
An immediate failure is usually related to a "Can't do it" situation where the
USB interaction to configure the device has failed, while a timeout usually
indicates that the configuration at least *claimed* to succeed, but is failing
to properly transfer valid data.
> For my hardware, I noticed that it hangs for a few seconds and gives EIO (arecord:
> pcm_read:2032: read error: Input/output error).
Given that the usbmon output ran to several megabytes, that's tending to
point at "the card was returning lots of packets, but they weren't actually the
format/data that arecord was expecting.
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: linux-sound@vger.kernel.org, linux-usb@vger.kernel.org,
alsa-devel <alsa-devel@alsa-project.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: USB sound card issues
Date: Tue, 15 Jun 2021 02:14:20 -0400 [thread overview]
Message-ID: <27987.1623737660@turing-police> (raw)
In-Reply-To: <CAHhAz+goVhacpDPc-OaVuG151TS8QKYdsqdnK9UcAx+Hc07zSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Sat, 12 Jun 2021 16:45:00 +0530, Muni Sekhar said:
> > And if it's configurable for multiple formats, was it set for the correct one?
> Is there a way to verify was it set for the correct one or not?
arecord -v gives what it thinks the setup is.
> > Does the record die immediately, or hang for a few seconds and timeout?
> What is the difference between these two ways?
An immediate failure is usually related to a "Can't do it" situation where the
USB interaction to configure the device has failed, while a timeout usually
indicates that the configuration at least *claimed* to succeed, but is failing
to properly transfer valid data.
> For my hardware, I noticed that it hangs for a few seconds and gives EIO (arecord:
> pcm_read:2032: read error: Input/output error).
Given that the usbmon output ran to several megabytes, that's tending to
point at "the card was returning lots of packets, but they weren't actually the
format/data that arecord was expecting.
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2021-06-15 6:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 10:50 USB sound card issues Muni Sekhar
2021-06-08 10:51 ` Muni Sekhar
2021-06-08 10:50 ` Muni Sekhar
2021-06-08 11:14 ` Greg KH
2021-06-08 11:14 ` Greg KH
2021-06-08 11:14 ` Greg KH
2021-06-08 11:14 ` Greg KH
2021-06-08 12:14 ` Muni Sekhar
2021-06-08 12:14 ` Muni Sekhar
2021-06-08 12:31 ` Greg KH
2021-06-08 12:31 ` Greg KH
2021-06-08 12:31 ` Greg KH
2021-06-08 12:45 ` Muni Sekhar
2021-06-08 12:57 ` Muni Sekhar
2021-06-08 12:45 ` Muni Sekhar
2021-06-08 13:03 ` Greg KH
2021-06-08 13:03 ` Greg KH
2021-06-08 13:03 ` Greg KH
2021-06-11 23:46 ` Valdis Klētnieks
2021-06-11 23:46 ` Valdis Klētnieks
2021-06-11 23:46 ` Valdis Klētnieks
2021-06-11 23:46 ` Valdis Klētnieks
2021-06-12 11:15 ` Muni Sekhar
2021-06-12 11:27 ` Muni Sekhar
2021-06-12 11:15 ` Muni Sekhar
2021-06-12 11:15 ` Muni Sekhar
2021-06-15 6:14 ` Valdis Klētnieks [this message]
2021-06-15 6:14 ` Valdis Klētnieks
2021-06-15 6:14 ` Valdis Klētnieks
2021-06-15 6:14 ` Valdis Klētnieks
2021-06-15 7:00 ` Muni Sekhar
2021-06-15 7:12 ` Muni Sekhar
2021-06-15 7:00 ` Muni Sekhar
2021-06-15 7:00 ` Muni Sekhar
2021-06-14 11:03 ` Muni Sekhar
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=27987.1623737660@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=alsa-devel@alsa-project.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=munisekharrms@gmail.com \
/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.