I encountered this kind of situation before. From what I experienced, it was some sort of a thing that the memory suddenly freezes all the running processes. I can even remember that I saw something like "db>...". I did tried changing a different machine with the same hard disk still there was a point in time that the machine just suddenly halted. To sort it out, I migrated to 4.3 and I got an OpenBSD running seamlessly.
> Hi, > > I have an openbsd 4.2 pf firewall using a generic, multiprocessor kernel > that has been running with no issues for 101 days. Yesterday it stopped > forwarding traffic and stopped allowing me to log on via ssh. > Unfortunately, although it stopped forwarding traffic, it didn't fail > over to its CARP standby node. We forced a failover by shutting down one > of its switch ports. Now when I try to log on over the serial port I get > the following message: 'internal resource failure'. > > First question: We have the machine left in its failed state at the > moment. Is there a signal I can send it over the serial port to get the > machine to panic before rebooting it (to give us as much information as > possible)? > > (More questions to follow no doubt!) > > Thanks in advance, > > Cliff.
