-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 03 August 2004 02:07, Chuck Rock wrote:
I had a similar problem with this release running on any Dell 2550 Rack
server I had. I tried three different servers with the same config, and I
had kernel panics at various times. All of them had
On Sunday 01 August 2004 09:08 am, Hugo Silva wrote:
I am running a Dual Xeon 2.8ghz w/ SMP, SCHED_ULE on FreeBSD
5.2.1-RELEASE-p9.
Whenever I load the server a bit more (let [EMAIL PROTECTED] run, compile stuff in
multiple jails, etc), it will simple go offline. I confirmed with the
I had a similar problem with this release running on any Dell 2550 Rack
server I had. I tried three different servers with the same config, and I
had kernel panics at various times. All of them had different information
on the screen at each panic.
I had several people tel lme they had no such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 01 August 2004 15:08, Hugo Silva wrote:
I am running a Dual Xeon 2.8ghz w/ SMP, SCHED_ULE on FreeBSD
5.2.1-RELEASE-p9.
Why aren't you running FreeBSD 4.10 on a machine like that? 5.2.1 is simply
NOT ready for production enviroments. Why
4.10 won't work with the current hardware on the server, and I wanted to
try 5.2.1 because of the improved SMP.
I know there is a solution for this by adding a kernel option, but i'm
completely CLUELESS.
Can anyone give a hint?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 01
it was said:
4.10 won't work with the current hardware on the
server, and I wanted to
try 5.2.1 because of the improved SMP.
I know there is a solution for this by adding a
kernel option, but i'm
completely CLUELESS.
Can anyone give a hint?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On
Damn.
And any clue on the magic kernel option that stopped the panics? Perhaps
it wasn't *that* magic and just decreased the odds of a panic hapenning
under high load, but that would do for me. I just lost the server 10
minutes ago doing a portupgrade -a with 4 jails running. :x
Regards,
Hugo
