[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
*** This bug is a duplicate of bug 320875 *** https://bugs.launchpad.net/bugs/320875 On Ubuntu 12.04.3, I'm seeing [alsa-source] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read! [alsa-source] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. [alsa-source] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value min_avail. in the syslog. It also seems I have no access to the usual alsamixer volume controls on running alsamixer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/329620 Title: ALSA woke us up to write new data to the device, but there was actually nothing to write. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/329620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
*** This bug is a duplicate of bug 320875 *** https://bugs.launchpad.net/bugs/320875 Hi This bug is there in Ubuntu 11.04 . So let's celebrate 2 year Anniversary Regards, Vipin Balakrishnan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/329620 Title: ALSA woke us up to write new data to the device, but there was actually nothing to write. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
*** This bug is a duplicate of bug 320875 *** https://bugs.launchpad.net/bugs/320875 Hi All, This Bug is there very badly in Ubuntu 10.04 LTS. I dont know why nobody is intereseted to fix. Regards, Vipin Balakrishnan. -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
*** This bug is a duplicate of bug 320875 *** https://bugs.launchpad.net/bugs/320875 I am also receiving these mesages in syslog. My alsa-info.sh output is locate at http://www.alsa- project.org/db/?f=3cc84abd1b4be1ec90a385aa93c4c010cccf43fc . I already have load-module module-hal-detect tsched=0in /etc/pulse/default.pa. I upgraded from Intrepid to Jaunty a couple of months ago, and didn't start getting this error until recently. I installed ftpsfv located at http://www.bunker-werk.net/proftpd/ which changed the boot order of some services (snort is booted before mysql). -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
*** This bug is a duplicate of bug 320875 *** https://bugs.launchpad.net/bugs/320875 ** This bug has been marked a duplicate of bug 320875 pulseaudio produces lots of log messages -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
This appeared in my pc after upgrading to 9.04 alpha 5. LOTS of identical entries in my syslog. Is there some progress? Can I help somehow? My result of alsa debugging script: http://tinyurl.com/asc8mz -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
I'm getting the same problem in 9.04 and floods of logs about it. ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is a Linux bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. I also get skipping and stuttering in totem. I'm not sure if it's at all related. So far, I can't correlate the two at all. -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Try adding tsched = 0 to /etc/pulse/default.pa under the hal-detect module. More info at the end of this article: http://fedoraproject.org/wiki/Features/GlitchFreeAudio It fixed my audio problems and the messages. Clearly it's exposing a bug somewhere. -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
** Attachment added: user.log http://launchpadlibrarian.net/22640876/user.log ** Description changed: Hello everyone, I was going over my log messages and found out this entry appears a few times in the user.log file: Feb 14 19:08:05 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. Feb 14 19:10:23 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 40.41 ms Feb 14 20:35:07 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 80.82 ms You can find the complete log file attached. Let me know if you guys need more info. + + By the way I am running Jaunty. ** Description changed: Hello everyone, I was going over my log messages and found out this entry appears a few times in the user.log file: Feb 14 19:08:05 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. Feb 14 19:10:23 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 40.41 ms Feb 14 20:35:07 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 80.82 ms You can find the complete log file attached. Let me know if you guys need more info. - By the way I am running Jaunty. + By the way I am running Jaunty x86_64 with 2.6.28-7-generic kernel. -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
** Description changed: Hello everyone, I was going over my log messages and found out this entry appears a few times in the user.log file: Feb 14 19:08:05 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. Feb 14 19:10:23 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 40.41 ms Feb 14 20:35:07 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 80.82 ms You can find the complete log file attached. Let me know if you guys need more info. By the way I am running Jaunty x86_64 with 2.6.28-7-generic kernel. + + kerm...@laptoplinux:~$ aplay -l + List of PLAYBACK Hardware Devices + card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 + card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI] + Subdevices: 1/1 + Subdevice #0: subdevice #0 ** Description changed: Hello everyone, I was going over my log messages and found out this entry appears a few times in the user.log file: Feb 14 19:08:05 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. Feb 14 19:10:23 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 40.41 ms Feb 14 20:35:07 LaptopLinux pulseaudio[21013]: module-alsa-sink.c: Increasing wakeup watermark to 80.82 ms You can find the complete log file attached. Let me know if you guys need more info. By the way I am running Jaunty x86_64 with 2.6.28-7-generic kernel. kerm...@laptoplinux:~$ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 + + kerm...@laptoplinux:~$ lsmod | grep snd + snd_seq_dummy 11524 0 + snd_hda_intel 545588 3 + snd_seq_oss41856 0 + snd_pcm_oss52224 0 + snd_seq_midi 15744 0 + snd_mixer_oss 24960 1 snd_pcm_oss + snd_pcm98952 2 snd_hda_intel,snd_pcm_oss + snd_rawmidi33920 1 snd_seq_midi + snd_seq_midi_event 16512 2 snd_seq_oss,snd_seq_midi + snd_seq66144 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event + snd_timer 34064 2 snd_pcm,snd_seq + snd_seq_device 16276 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq + snd78792 15 snd_hda_intel,snd_seq_oss,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device + soundcore 16800 1 snd + snd_page_alloc 18704 2 snd_hda_intel,snd_pcm -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Please run the alsa-info.sh debugging script from http://www.alsa- project.org/alsa-info.sh ** Changed in: linux (Ubuntu) Sourcepackagename: alsa-driver = linux Status: New = Incomplete -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Here it is ** Attachment added: alsa-info.txt http://launchpadlibrarian.net/22641238/alsa-info.txt -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
I think I am hittingBug #326693 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/326693). I too realized that I can not get sound when glxgears is running. -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329620] Re: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Forget what I just said about glxgears -- ALSA woke us up to write new data to the device, but there was actually nothing to write. https://bugs.launchpad.net/bugs/329620 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
