Date: Mon, 11 Dec 2000 00:46:41 -0800 (PST) From: mark.rowlands@minmail.net To: freebsd-gnats-submit@FreeBSD.org Subject: misc/23460: profiing timer expired error Message-ID: <200012110846.eBB8kf840785@freefall.freebsd.org> Resent-Message-ID: <200012111110.eBBBA2g59941@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 23460 >Category: misc >Synopsis: profiing timer expired error >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 11 03:10:02 PST 2000 >Closed-Date: >Last-Modified: >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 profiling timer expired errors received after installing 4.2R on a previously working 4.1.1-stable system. system is a pentium 233 / qlogic 1040 scsi / 3com 3c3509b / 96mb Problem first occurred with 4.1-release and was experience by a few other people...common thread was qlogic card. Problem went away after sep 26 cvsup. Commenting out psignal(p, SIGPROF); line in kern_clock.c helped...if you could build afterwards without getting profiling timer errors :-). >How-To-Repeat: install 4.2R >Fix: install 4.1.1R maybe >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012110846.eBB8kf840785>