Bus access fault usually means that a program tried to address memory
that has either failed (a chip failed), or is not plugged into the PC.
What happens is that memory usually provides a ready line back to the
processor. The processor will time out waiting for this ready line from
non-existant memory and give you a "bus access fault."
Under Linux, about the only reason for this is that your memory has some
bad spots in it, unless the communicator code programmed around this and
set the gdt or ldt itself. (In brief, gdt and ldt are arrays that map
physical memory to arbitrary address values.)
wade
On Wed, 16 Jun 1999, Tom Berger wrote:
> Hi!
> Crashes on fvwm2, too. BTW: what does 'bus access fault' mean anyway? Which
> bus?
>
> Frustrated
>
> tom
>
