From nobody@freefall.freebsd.org  Mon Dec 11 03:03:33 2000
Return-Path: <nobody@freefall.freebsd.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id EAD1537B404
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 11 Dec 2000 03:03:24 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id eBBAs1V55611;
	Mon, 11 Dec 2000 02:54:01 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200012111054.eBBAs1V55611@freefall.freebsd.org>
Date: Mon, 11 Dec 2000 02:54:01 -0800 (PST)
From: mark.rowlands@minmail.net
Sender: nobody@freefall.freebsd.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: profiing timer expired error
X-Send-Pr-Version: www-1.0

>Number:         23458
>Category:       misc
>Synopsis:       profiing timer expired error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec 11 03:10:01 PST 2000
>Closed-Date:    Sun Nov 18 08:41:52 PST 2001
>Last-Modified:  Sun Nov 18 08:43:53 PST 2001
>Originator:     Mark rowlands
>Release:        4.2R
>Organization:
none
>Environment:
FreeBSD marbsd.tninet.se 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000     jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC  i386
>Description:
seemingly random profile timer expired errors experienced after installing 4.2R on a previously functioning 4.1.1-Stable system.
This problem existed on 4.1R but disappeared after cvsup on 26-09-00
Other users had this problem...all had qlogic 1040 or 1080 scsi cards.
commenting out the psignal(p, SIGPROF); line in kern_clock.c seemed to help nsayer@quack.kfu.com. 
>How-To-Repeat:
install 4.1R or 4.2R and boot or try any long running process....delete a directory or cvsup or run  make buildworld...
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: iedowse 
State-Changed-When: Sun Nov 18 08:41:52 PST 2001 
State-Changed-Why:  

Most cases of unexpected SIGPROFs were caused by an overflow of 
the per-process kernel stack. The size of this stack was increases 
recently, so a recent -STABLE will not have this problem. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23458 
>Unformatted:
