
3 Oct
2011
3 Oct
'11
11:36 a.m.
'Twas brillig, and Arun Raghavan at 01/10/11 09:49 did gyre and gimble:
I'm going to try to handle this by just stopping PA from listening on these fds when I get a (POLLERR|POLLNVAL), but it seems to me that this is a bug in the driver somewhere. Any ideas w.r.t. what might be going wrong or where I should be looking to debug further?
Also a question to ask. Would a POLLERR|POLLNVAL be received any time when normal operations will continue afterwards? e.g. should we use this error as an indicator to ignore it forever or, e.g., just for a finite period of time like 1s.
Although if the underlying cause of the flood of errors can be addressed, that would be nicer!
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited http://www.tribalogic.net/
Open Source:
Mageia Contributor http://www.mageia.org/
PulseAudio Hacker http://www.pulseaudio.org/
Trac Hacker http://trac.edgewall.org/