i386/61705: Random "bus errors".

[Paul-Andrew Joseph Miseiko]

>Number:         61705
>Category:       i386
>Synopsis:       Random "bus errors".
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 21 20:50:13 PST 2004
>Closed-Date:
>Last-Modified:
>Originator:     Paul-Andrew Joseph Miseiko
>Release:        FreeBSD 5.2R
>Organization:
>Environment:
FreeBSD teardrop.ca 5.2-RELEASE FreeBSD 5.2-RELEASE #9: Wed Jan 21 21:10:58 EST 2004     esoteric at teardrop.ca:/usr/src/sys/i386/compile/TEARDROP  i386
>Description:
I have noticed that after loading NTP (4.2) on FreeBSD 5.2R I will get occasional, completely random, bus errors (i.e. a program will die with a signal 10).  It only appears to happen to programs executed after the loading of the NTP daemon (I have not witnessed any applications die from a signal 10 if they had been operational before the NTP daemon was loaded).  On a twist of events I have noticed the bus errors slowly disappear as the system progresses away from the loading of the NTP daemon (though it is still resident and operational); reloading it will once again present the problem in full force.
>How-To-Repeat:
Kill your NTP Daemon after booting up then reload it.  Perform several operations relatively fast and an occasional "bus error (core dumped)" will occur.  I used "host" and looked up the same domain relatively fast however I have had "tail", "cat", "ntpq", "ntpdc", and "ee" crash with the same aforementioned signal.

This problem is reproducable with the NTP shipped with the operating system (though in any event no NTP version should be capable of doing this).
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted: