Bug 1036917 - E: [alsa-sink] alsa-sink.c: ALSA woke us
Summary: E: [alsa-sink] alsa-sink.c: ALSA woke us
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-02 21:56 UTC by George R. Goffe
Modified: 2014-01-06 10:56 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-06 10:56:18 UTC
Type: Bug

Attachments (Terms of Use)
gzip'd tar file of requested info. (7.86 KB, application/x-gzip)
2014-01-05 06:35 UTC, George R. Goffe 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description George R. Goffe 2013-12-02 21:56:42 UTC 
Description of problem:

messages from/during pulseaudio

Version-Release number of selected component (if applicable):

pulseaudio-3.0-10.fc19.x86_64

How reproducible:

Frequently but not every time

Steps to Reproduce:
1.run pulseaudio as root
2.view "movies" (MAY be related to filetype)
3.

Actual results:

Everything seems to work properly but this message does appear.

Expected results:

NO messages.

Additional info:

E: [alsa-sink] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
E: [alsa-sink] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers.
E: [alsa-sink] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Comment 1 Justin M. Forbes 2014-01-03 22:05:37 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.
Comment 2 Michele Baldessari 2014-01-04 12:47:09 UTC 
Beyond trying the 3.12.6 can we also get lspci -nvvv please and dmidecode attached to this BZ?
Comment 3 George R. Goffe 2014-01-05 06:35:23 UTC 
Created attachment 845699 [details]
gzip'd tar file of requested info.

Michele,

Thank you for your attention to this bug report.

I haven't seen this in a while. I've been running FC19x86_64 for about 3 months.

Here's the info you've requested.

George...

HAPPY NEW YEAR!
Comment 4 George R. Goffe 2014-01-05 06:36:43 UTC 
Michele,

I'm still running a kernel at 3.12.5-200.fc19.x86_64.

George...
Comment 5 Michele Baldessari 2014-01-05 10:19:53 UTC 
Hi George,

thanks for the feedback. Given that 3 months have passed without the issue,
I'd say we can close it? 

Happy new year to you as well,
Michele
Comment 6 George R. Goffe 2014-01-06 10:40:20 UTC 
Michele,

I agree, let's close this one.

If if happens again I'll open a new one.

Thanks for your help.

George...
Comment 7 Michele Baldessari 2014-01-06 10:56:18 UTC 
Hi George,

thanks for the feedback. Ok, let's close it. If it happens again we can reopen

regards,
Michele
Note You need to log in before you can comment on or make changes to this bug.