On 2007/03/03 14:01, Paul Pruett wrote: > Umm, it frooze/hung up again at 5:08 am. about > 23 hours after rebooting with the current 4.1 kernel > on the i386 4.0 userland.... (not recommended...I'm sure you know that already though)
> I was remote so I did not see the monitor for any > panics, but reset using the apc power switch. If you set ddb.panic=0 you'll _sometimes_ get something useful in syslog. Try and arrange serial console access if possible though. Was it definitely not running, or is there a chance you just lost the network? (you could check for newsyslog's hourly entries in /var/cron/log if there's nothing else that would be logging without network input). > ... My personal experience is that going forward > I would strongly recommend to readers to use OpenBSD amd64 > (not i386) on the AMD K8 platforms (athlon64). there are definitely times when you want to use i386. (don't rule out defective hardware too soon, either).
