From nobody@FreeBSD.ORG Thu Apr 15 18:40:43 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 3549614D07; Thu, 15 Apr 1999 18:40:43 -0700 (PDT)
Message-Id: <19990416014043.3549614D07@hub.freebsd.org>
Date: Thu, 15 Apr 1999 18:40:43 -0700 (PDT)
From: robk@empire.net
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: system slows down and freezes in a dual cpu kernel running on comaq 1600r server
X-Send-Pr-Version: www-1.0

>Number:         11161
>Category:       i386
>Synopsis:       system slows down and freezes in a dual cpu kernel running on comaq 1600r server
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 15 18:40:01 PDT 1999
>Closed-Date:    Sun Apr 18 20:46:16 PDT 1999
>Last-Modified:  Sun Apr 18 20:46:50 PDT 1999
>Originator:     Robert Kirkpatrick
>Release:        3.1
>Organization:
Empire.Net
>Environment:
FreeBSD num2.empire.net 3.1-RELEASE FreeBSD 3.1-RELEASE #0: Mon Apr 12 08:56:48 GMT 1999     bena@num2.empire.net:/usr/src/sys/compile/EMPIRE  i386
>Description:
if I run in the dual cpu mode I will eventually loose the machine even the console, requireing a reboot. Single cpu kernel seems to work however..
The machine is a compaq 1600r 2 400 512 meg dpt smartraid4 4 9 gig drives compaq and 3com network cards
running radius, sendmail webmin dns..
Im stumped and not that good at bsd yet


>How-To-Repeat:
see above, eventually it will freeze locking you out completely even from console. Requres a reboot
>Fix:
no known fix

>Release-Note:
>Audit-Trail:

From: "Rob Kirkpatrick" <robk@empire.net>
To: <freebsd-gnats-submit@freebsd.org>, <robk@empire.net>
Cc:  
Subject: Re: i386/11161: system slows down and freezes in a dual cpu kernel running on comaq 1600r server
Date: Fri, 16 Apr 1999 23:58:02 -0400

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_002E_01BE8864.F6701400
 Content-Type: text/plain;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 the issue with this seems to be fixed now.
 The problem was the kernel was only seeing 16meg out of 512 meg. During =
 non busy times the system would respond fairly but under load was not =
 able to swap out fast enough to keep up with the load.
 
 I found the answer for this in the linux group because linux has this =
 same problem under certian configs.
 
 whats the syntax to fix this ? I dont know, a unix motor head did it for =
 me but Im sure serious users will know how to fix this..
 
 
 
 ------=_NextPart_000_002E_01BE8864.F6701400
 Content-Type: text/html;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META content=3D"text/html; charset=3Diso-8859-1" =
 http-equiv=3DContent-Type>
 <META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
 <STYLE></STYLE>
 </HEAD>
 <BODY bgColor=3D#ffffff>
 <DIV><FONT face=3DArial size=3D2>the issue with this seems to be fixed=20
 now.</FONT></DIV>
 <DIV><FONT face=3DArial size=3D2>The problem was the kernel was only =
 seeing 16meg=20
 out of 512 meg. During non busy times the system would respond fairly =
 but under=20
 load was not able to swap out fast enough to keep up with the =
 load.</FONT></DIV>
 <DIV>&nbsp;</DIV>
 <DIV><FONT face=3DArial size=3D2>I found the answer for this in the =
 linux group=20
 because linux has this same problem under certian configs.</FONT></DIV>
 <DIV>&nbsp;</DIV>
 <DIV><FONT face=3DArial size=3D2>whats the syntax to fix this ? I dont =
 know, a unix=20
 motor head did it for me but Im sure serious users will know how to fix=20
 this..</FONT></DIV>
 <DIV>&nbsp;</DIV>
 <DIV>&nbsp;</DIV></BODY></HTML>
 
 ------=_NextPart_000_002E_01BE8864.F6701400--
 
 
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun Apr 18 20:46:16 PDT 1999 
State-Changed-Why:  
Orginator notes that the problem seems to be fixed now. 
>Unformatted:
