I saw spurious reboots as well, but I thought it was fixed. I can't remember when it was fixed (earlier this year?) but you should be able to find it in the archives.
On Fri, 29 Nov 2013, Emmanuel Dreyfus wrote:
Hi I move thisthread to tech-kern@ since I suspect a kernel bug. Perhaps port-i386 would be better, someone tells me if it is. I have a two new machines that exhibit spurious reboots without panics. The problem arise on both, hence I suspected memory to fit badly with the chipset. But memtest ran 16 passes without finding anything wrong. Moreover, I have been able to acheive stability by using an amd64 kernel or a -current i386 kernel, which suggests a kernel bug, or a hardware problem worked around by a kernel fix. The machine has 2 DIMMs of 4 GB of RAM. NetBSD-6.0/i386 GENERIC only sees 2 GB. Using PAE or amd64, all memory is seen. Here are my findings so far: NetBSD-6.0/i386 GENERIC spurious reboots, sees only 2 GB NetBSD-6.0/i386 GENERIC+PAE spurious reboots, sees all memory latest netbsd-6/i386 GENERIC+PAE spurious reboots, sees all memory NetBSD-6.0/amd64 GENERIC stable, works fine latest netbsd-current/i386 GENERIC+PAE stable, works fine. Does that rings a bell to someone? Is there some fixes in -current i386 that could be puled upto netbsd-6 ?
-- Hisashi T Fujinaka - ht...@twofifty.com BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte