Created attachment 524784 [details] dmesg output Description of problem: xawtv causes pcm overrun and seems to hang system. Can't CTRL-ALT-DEL, or CTRL-ALT-Fn to get out, after CTRL-C wat recognized in starting terminal window. Version-Release number of selected component (if applicable): xawtv-3.101-1.fc16.x86_64 aalib-libs-1.4.0-0.19.rc5.fc15.x86_64 gpm-libs-1.20.6-18.fc16.x86_64 libXaw-1.0.8-1.fc15.x86_64 xorg-x11-fonts-misc-7.5-4.fc15.noarch zvbi-0.2.33-9.fc16.x86_64 How reproducible: Every time Steps to Reproduce: 1. Boot Fedora Live Desktop Beta RC2 2. Install above components 3. Open terminal window 4. Invoke xawtv Actual results: I get pcm overrun errors. I'm trying to figure out how to save the actual error messages I get. After a few seconds, the system freezes, preventing me from saving my terminal session. Expected results: Normal xawtv operaton Additional info: Will attach dmesg to show hardware configuration. I notice some suspicious messages: "... fedora-readonly[518]: /etc/init.d/functions: line 58: /dev/stderr: No such device or address" (may not be relevant to this bug [
Created attachment 524786 [details] typescript output with trailing CR's deleted Found I could recover typescript output on reboot.
This is likely due to a bug at cx231xx alsa kernel driver. The previous versions of xawtv weren't starting an alsa thread to output the audio. With the new version, if the driver has a problem at the alsa start stream logic, the machine will hang. We've fixed some similar bugs on tm6000 and em28xx drivers: what happened there is that some USB URB's are needed to start audio. The alsa driver seems to call the start/stop streaming code during interrupt time, but the kernel call to send an URB can't be send at interrupt time, as it can block, causing the machine to die.
Hi, Fedora 16 is EOL, closing this. Hopefully it is fixed in a newer version of the kernel and/or xawtv. I've just released a new xawtv upstream version and build it for Fedora: http://koji.fedoraproject.org/koji/taskinfo?taskID=5198439 If you still see this with Fedora with the latest kernel update (3.8.x) and xawtv (3.103) please open a new bug. Regards, Hans