> A disturbing thought, since I recently added more RAM to the machine.
> Memtest found no problems in a single pass; maybe I'll run it longer
> overnight.

I had a similar problem and used memtest. Here are two tips:
- Use memtest from http://www.memtest.org/ and NOT from
http://www.memtest86.com/.
- In Test selections use "all" instead of the "standard" default
selection, this one saved me! The "standard" test did fine, the "all"
test revealed timing problems with one of the memory chips (no
overclocking) on the module. Underclocking my memory solved my
problem.

Good luck hunting,
Onno


On 9/8/05, Steven M. Bellovin <smb@cs.columbia.edu> wrote:
> In message <20050908123731.5c911f43.segv@netctl.net>, segv writes:
> >On Thu, 08 Sep 2005 07:30:23 -0400
> >"Steven M. Bellovin" <smb@cs.columbia.edu> wrote:
> >
> >> Last night, probably during the daily job, my laptop appears to have
> >> rebooted.  There's no core dump and nothing in dmesg.  I'm running
> >> -current from about 4 or 5 days ago.  Has anyone seen anything like
> >> this?
> >>
> >>              --Steven M. Bellovin, http://www.cs.columbia.edu/~smb
> >
> >Yeah, I've seen it happen occasionally (i.e. more than just once) on my =
AMD
> >Athlon PC. The reboots were quite random, so I assumed it was buggy hard=
ware,
> >because it didn't happen to any other machines that were running NetBSD.=
 This
> >was NetBSD-3.0_BETA
> >
> A disturbing thought, since I recently added more RAM to the machine.
> Memtest found no problems in a single pass; maybe I'll run it longer
> overnight.
>=20
> Thanks.
>=20
>                --Steven M. Bellovin, http://www.cs.columbia.edu/~smb
>=20
>=20
>