Subject: Re: possible causes for read(2) to return EFAULT?
To: None <current-users@NetBSD.ORG>
From: None <email@example.com>
Date: 04/29/2003 23:40:59
>I've just been doing some benchmarks and tests on a new server with the
>NetBSD snapshot from releng.netbsd.org/NetBSD-daily/current/200304250000/i386
>You'll see why I'm testing with -current when you see which devices are
>in the system from the dmesg output below.
>Running bonnie (after patching some off_t bugs), and not on the first
>run but rather after a half-dozen successful runs, I see it return an
>EFAULT from read():
> Bonnie: drastic I/O error (rewrite read): Bad address
This sounds very similar to a problem we have with apache and write().
Under 1.6, it always returns EFAULT when trying to write the access log.
The same binary works fine under 1.5.x.
We've reported this to Perry, but he hasn't had time to look at it yet.