Segfault problem in 9.1.0
Bill Larson
wllarso at swcp.com
Wed Jan 31 21:16:52 UTC 2001
A "sig-11" error on an Intel platform isn't unknown. This error is
possibly due to a hardware memory error on your system. See
<http://www.bitwizard.nl/sig11/> for more information about this.
Note, a sig-11 is commonly encountered when compiling a Linux kernel,
as initally talked about in the referenced site. This sig-11 has
nothing specifically to do with Linux, kernel, or compiling - it is
the result of interactions between the processor and RAM on an Intel
system.
Sig-11 errors are common when an Intel processor is working heavily, and
there is a communication problem (timing, etc.) with the RAM. It would
sound like bind-9 is causing your processor to work much harder than
previous versions of bind. Interesting!
Bill Larson
> I'm having problems running Bind 9.1.0 on OpenBSD 2.8. I've updated my
> conf and zone files to 9.1's liking and when I try to run named, it
> segfaults, signal 11:
>
> #0 0x401fac2f in _thread_macdep_switch ()
> #1 0x401fa992 in _thread_kern_sig_undefer ()
> #2 0x401f9ea7 in _thread_kern_sched_state_unlock ()
> #3 0x401fd7c9 in pthread_cond_wait ()
> #4 0x16a68c in dispatch (manager=0x1be0f0) at task.c:795
> #5 0x16aab5 in run (uap=0x1be0f0) at task.c:974
> #6 0x401b6854 in _thread_start ()
> #7 0x17 in ?? ()
> Cannot access memory at address 0xffffffff
>
> What might I have done wrong?
>
> Thanks,
> Trey Childs
> Sr. Network Administrator
>
>
>
>
More information about the bind-users
mailing list