Hide Forgot
Description of problem: Using irda almost hangs the machine. The machine doesn't lock solid, but becomes totally unusable (as if there's a busywait somewhere that sucks up all CPU). I'm using plptools to connect to an Ericsson MC218, on a Thinkpad T40p, using either the built-in irda (module: nsc_ircc) or an external USB irda dongle (module mcs7780). This used to work ages ago, now it hangs the machine. Sometimes the machine recovers, which means it is not a total lockup/crash, but the machine becomes totally unresponsive. I've tried debugging the applications involved, but it is difficult to do when the machine grinds to a halt. I don't think the fault lies with plptools, it is the same version that I've used for many years now. Version-Release number of selected component (if applicable): kernel-3.2.6-3.fc16.i686 How reproducible: Steps to Reproduce: 1. service irda start 2. service psion start 3. move the machine out of range Actual results: the machine becomes totally unuseable until the irda reconnects Expected results: the machine should still respond while irda waits to reconnect Additional info:
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Still hangs :-( 1. service irda start 2. service psion start 3. with no irda device in sight of the laptop, the loptop now freezes
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.