Hide Forgot
Description of problem: I saw this fault couple times when I had running both ldattach and latest gpsd from rawhide which supports PPS (and creates the device by the TIOCSETD ioctl). Version-Release number of selected component (if applicable): kernel-2.6.40.3-0.fc15.x86_64 gpsd-3.1-1.fc17.x86_64 How reproducible: seems to be reproducible Steps to Reproduce: 1. run latest gpsd from rawhide which creates /dev/pps0 2. run ldattach /dev/ttyS0 3. kill gpsd Additional info: dmesg attached Please let me know if you need more information.
Created attachment 521636 [details] dmesg
Are you still seeing this with 2.6.43/3.3?
Fedora 15 has reached it's end of life as of June 26, 2012. As a result, we will not be fixing any remaining bugs found in Fedora 15. In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set 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. Thank you for taking the time to file a report. We hope newer versions of Fedora suit your needs.
This still seems to be happening, at least with kernel-3.4.9-2.fc16.x86_64.
Created attachment 623448 [details] kernel backtrace This happened when ldattach 18 /dev/ttyS0 was running and systemctl restart gpsd.service was called.
# 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.