Bug 741109 - xawtv hangs in Fedora 16 Beta RC2 64-bit
Summary: xawtv hangs in Fedora 16 Beta RC2 64-bit
Alias: None
Product: Fedora
Classification: Fedora
Component: xawtv
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dmitry Butskoy
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-25 13:34 UTC by Peter H. Jones
Modified: 2013-04-02 14:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-04-02 14:06:00 UTC

Attachments (Terms of Use)
dmesg output (82.13 KB, text/plain)
2011-09-25 13:34 UTC, Peter H. Jones
no flags Details
typescript output with trailing CR's deleted (35.40 KB, text/plain)
2011-09-25 13:51 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2011-09-25 13:34:57 UTC
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):


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


Comment 1 Peter H. Jones 2011-09-25 13:51:26 UTC
Created attachment 524786 [details]
typescript output with trailing CR's deleted

Found I could recover typescript output on reboot.

Comment 2 Mauro Carvalho Chehab 2011-09-25 19:52:21 UTC
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.

Comment 3 Hans de Goede 2013-04-02 14:06:00 UTC

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.



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