From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: 'Raymond Yau' <superquad.vortex2@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA
Date: Fri, 30 May 2014 04:40:55 -0400 [thread overview]
Message-ID: <001201cf7be2$dfbb1980$9f314c80$@lucidpixels.com> (raw)
In-Reply-To: <CAN8cciZwbNVu7LO_muaynfbudxTB8qRS0aPyxwnd28yupCxSEA@mail.gmail.com>
Hello,
As requested—
http://home.comcast.net/~jpiszcz/20140530/lsusb-vvvv.txt
http://home.comcast.net/~jpiszcz/20140530/full-pulse-audio-log.txt
http://home.comcast.net/~jpiszcz/20140530/alsa-info.txt
Ø step to reproduce your problem when you report the bug
I often SSH to my machine or use X remotely and not locally— this is the first time I have seen this in logs that I can remember and I’ve not changed anything locally.
Justin.
From: Raymond Yau [mailto:superquad.vortex2@gmail.com]
Sent: Thursday, May 29, 2014 10:15 PM
To: Justin Piszcz
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA
>
>
>
> Bug report:
>
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers
You have to provide pulseaudio verbose log, output of alsa-info.sh , lsusb -vvvv and step to reproduce your problem when you report the bug
>
>
> ==> /var/log/user.log <==
>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
> ALSA woke us up to write new data to the device, but there was actually
> nothing to write!
>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c:
> Most likely this is a bug in the ALSA driver '(null)'. Please report this
> issue to the ALSA developers.
Name of alsa sink seem changed from USB-audio to null, did you find any unplug event if USB audio device in system log
Any error message related to USB controllers and your audio card
>
> May 25 06:38:06 atom pulseaudio[6754]: [alsa-sink-USB Audio] alsa-sink.c: We
> were woken up with POLLOUT set -- however a subsequent snd_pcm_avail()
> returned 0 or another value < min_avail.
>
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2014-05-30 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 12:53 Bug report: [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA Justin Piszcz
2014-05-30 2:15 ` Raymond Yau
2014-05-30 8:40 ` Justin Piszcz [this message]
2014-05-30 12:17 ` Raymond Yau
2014-05-31 4:58 ` [alsa-devel] " Raymond Yau
2014-05-31 10:48 ` Justin Piszcz
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='001201cf7be2$dfbb1980$9f314c80$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox