Red Hat Bugzilla – Bug 113037
ciped crashes with kxchg: read(r): Interrupted system call error
Last modified: 2008-08-02 19:40:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b)
Description of problem:
The cipe client daemon dies every few days after logging the message
"kxchg: read(r): Interrupted system call". This began only after
upgrading from RedHat 9 to Fedora Core 1.
I patched the source code to retry the read() in case of an EINTR
error return or a successful return of fewer than the requested number
of bytes. I have been using the patched code for a month now and it
seems to have fixed this problem. I will attach the patch.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run cipe client under the 2.4.22 kernel.
2. Wait a few days until cipe daemon dies.
Actual Results: /var/log/messages contains lines like:
Nov 26 11:50:56 daphne ciped-cb: kxchg: read(r): Interrupted
Nov 26 11:50:56 daphne ciped-cb: Interface stats 1780808
7285 22 0 0 22
0 0 1347332 6289 0 0 0 0 0 0
Nov 26 11:50:56 daphne ciped-cb: KX stats: rreq=1, req=643,
ind=640, indb=0, ack=640, ack
Nov 26 11:50:57 daphne ciped-cb: cipcb0: daemon exiting
Expected Results: Should continue working.
Created attachment 96807 [details]
Patch file that apparently fixes reported problem
Fedora Core 1 is maintained by the Fedora Legacy project for security updates
only. If this problem is a security issue, please reopen and reassign to the
Fedora Legacy product. If it is not a security issue and hasn't been resolved in
the current FC5 updates or in the FC6 test release, reopen and change the
version to match.
NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy
project. After Fedora Core 6 Test 2 is released (currently scheduled for July
26th), there will be no more security updates for FC1. Please use these next two
weeks to upgrade any remaining FC1 systems to a current release.
Closing per lack of response. Also note that FC1 and FC2 are no longer
supported even by Fedora Legacy. If this still occurs on FC3 or FC4, please
assign to that version and Fedora Legacy. If it still occurs on FC5 or FC6,
please reopen and assign to the correct version.