From: "P.W. Pulto" <pwpulto@studiopulto.org>
To: alsa-devel@alsa-project.org
Subject: journalctl suggests I report Bug to ALSA developers
Date: Sat, 21 May 2016 10:45:47 +0200 [thread overview]
Message-ID: <5740203B.70701@studiopulto.org> (raw)
Dear ALSA developers,
Having a problem with my Sennheiser DW Pro 2 Dect Headset, I looked in
the journalctl. It suggested I report a bug to the ALSA developers.
I have no idea if this would be a "kernel driver bug" or an "other ALSA
bug". Hopefully I'm at the right address.
The problem occurs when I take the headset off the base station and a
connection between base station and headset is established.
My ALSA-info:
-------------------
http://www.alsa-project.org/db/?f=2eaeea040fef7cc2476c239e1fec90dd2bf4eea8
The journalctl output:
-----------------------------
journalctl --no-pager --since "25 min ago"
May 20 09:05:34 studiopulto-ubuntu-1 pulseaudio[2098]: [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 20 09:05:34 studiopulto-ubuntu-1 pulseaudio[2098]: [alsa-sink-USB
Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver
'snd_usb_audio'. Please report this issue to the ALSA developers.
May 20 09:05:34 studiopulto-ubuntu-1 pulseaudio[2098]: [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.
Hopefully this is sufficient information. Obviously you welcome to ask
for missing info!
Kind regards,
P.W. Pulto
--
Like us on Facebook <https://www.facebook.com/studiopulto>
dhr. P.W. Pulto
Studio Pulto vzw
Jef Vandermeulenstraat 37
9050 Gentbrugge
Bélgica
tel: 0032 9 220 73 40
e-mail: pwpulto@studiopulto.org
http://www.studiopulto.org
IBAN.: BE03 4487 6576 5184
BIC: KREDBEBB
ondern nr.: BE 0470 427 828
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
reply other threads:[~2016-05-21 8:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5740203B.70701@studiopulto.org \
--to=pwpulto@studiopulto.org \
--cc=alsa-devel@alsa-project.org \
/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.