On 6/23/05, Matt Juszczak [EMAIL PROTECTED] wrote:
Personally, I would update to RELENG_5 as of today. There are a lot of
bug fixes and its quite solid..
Did the upgrade earlier to two of five machines (the ones that were
crashing). We'll see what happens :) Thanks!
Any planned date
-Original Message-
From: Matt Juszczak [mailto:[EMAIL PROTECTED]
Sent: Monday, June 20, 2005 10:49 AM
To: Ted Mittelstaedt
Cc: freebsd-questions@freebsd.org
Subject: RE: FreeBSD Machines dieing, we've tried so much
On Mon, 20 Jun 2005, Ted Mittelstaedt wrote:
Please post
On Jun 22, 2005, at 3:07 AM, Ted Mittelstaedt wrote:
-Original Message-
From: Matt Juszczak [mailto:[EMAIL PROTECTED]
Sent: Monday, June 20, 2005 10:49 AM
To: Ted Mittelstaedt
Cc: freebsd-questions@freebsd.org
Subject: RE: FreeBSD Machines dieing, we've tried so much
On Mon
The vast majority of panics are hardware-related. It is rare nowadays
for a usermode program to make the system panic. In particular you said
the problem happens more under load. That really points even more to a
hardware problem - bad CPU cache ram, bad ram, scsi termination, that
sort of
Hello, Matt.
The vast majority of panics are hardware-related. It is rare nowadays
for a usermode program to make the system panic. In particular you said
the problem happens more under load. That really points even more to a
hardware problem - bad CPU cache ram, bad ram, scsi termination,
On Jun 22, 2005, at 9:59 AM, Matt Juszczak wrote:
The vast majority of panics are hardware-related. It is rare
nowadays
for a usermode program to make the system panic. In particular
you said
the problem happens more under load. That really points even more
to a
hardware problem -
I had same situation with to different high loaded servers (both SMP, with 8Gb
of
ram, and HT enabled,), with 5.4 Release, after disabeling HT and cvsup
OS to 5.4-stable all working fine without any problems, last reboot was 28
days ago.
That's exactly our config. SMP, 4 gb RAM, HT was
On Wed, 22 Jun 2005 13:14:52 -0400, in sentex.lists.freebsd.questions
you wrote:
That's exactly our config. SMP, 4 gb RAM, HT was enabled, no longer.
Should I upgrade to 5.4-STABLE? Is there a bug ? Is 5.4-STABLE
stable enough? :) Also, if I cvsup to 5.4-STABLE right now, would I
be able
Personally, I would update to RELENG_5 as of today. There are a lot of
bug fixes and its quite solid..
Did the upgrade earlier to two of five machines (the ones that were
crashing). We'll see what happens :) Thanks!
Any planned date for 5.5-RELEASE?
Hi all,
OK, we're still having the FreeBSD machines die on us. Its two specific
machines we've noticed, both FreeBSD 5.4, different hardware, different
purposes.
Originally, orion, our mail server, started getting kernel traps and
dieing. Then, our primary ldap server, a week later,
Please post dmesg output from both systems.
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Matt Juszczak
Sent: Monday, June 20, 2005 1:56 AM
To: freebsd-questions@freebsd.org
Subject: FreeBSD Machines dieing, we've tried so much
Hi all,
OK
On Mon, 20 Jun 2005, Ted Mittelstaedt wrote:
Please post dmesg output from both systems.
The systems end up crashing so I can't do a dmesg or do you mean a
general dmesg when they are stable?
Here is the output from Caliban: http://paste.atopia.net/126.
The machine crashed
On Jun 20, 2005, at 11:48 AM, Matt Juszczak wrote:
On Mon, 20 Jun 2005, Ted Mittelstaedt wrote:
Please post dmesg output from both systems.
The systems end up crashing so I can't do a dmesg or do you
mean a general dmesg when they are stable?
Probably just a standard one so
Attached is the dmesg as requested
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.4-RELEASE-p1 #0: Mon May 16 21:25:42 EDT 2005
I would start by disabling Hyperthreading in the BIOS. It doesnt
really have much benefit with the default scheduler (might make some
things slower), and seems to cause problems.
---Mike
But I have hyperthreading disabled in the sysctl variable for
hyperthreading (can't remember
15 matches
Mail list logo
