On Tue, Nov 26, 2013 at 08:24:33AM +0100, Manuel Bouyer wrote: > The only way for software to cause this would be triple-fault AFAIK. > Or a watchdog ... > But maybe you should try to replace RAM too ...
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 NetBSD-6.0/amd64 GENERIC stable, works fine latest netbsd-6/i386 GENERIC+PAE spurious reboots, sees all memory latest netbsd-current/i386 GENERIC+PAE stable, works fine. Hence IMO this is not a hardware problem, but a bug in NetBSD/i386 that has been fixed. Or if it is a hardxare problem, -current has a workaround. It would be worth identifying the relevant change, and pull it up to netbsd-6 if possible. -- Emmanuel Dreyfus m...@netbsd.org
