Date: 22 Jul 1999 08:59:22 -0000 From: Jos Backus <Jos.Backus@nl.origin-it.com> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/12758: idprio-related panic in -stable and -current Message-ID: <19990722085922.750.qmail@hal.mpn.cp.philips.com>
index | next in thread | raw e-mail
>Number: 12758
>Category: kern
>Synopsis: Adjusting the idle priority of a process causes panic
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jul 22 02:10:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Jos Backus
>Release: FreeBSD 4.0-CURRENT i386
>Organization:
Origin B.V.
>Environment:
-current as of today, -stable as of 19 July 1999
>Description:
See below.
>How-To-Repeat:
% primes 3 > /dev/null &
[1] 306
% primes 3 > /dev/null &
[2] 307
% su
# idprio 31 -306
# idprio -t -306
# panic: remrq
Debugger("panic") at ...
db> trace
Debugger(c01dba5b) at Debugger+0x38
panic(c01c21fe,c012e00b2,c832a8c0,0,c012dfa4) at panic+0x74
rem1(0,40000000,280ef774,bfbfd940,a) at rem1
softclock(0,2f,2f,2f,a) at softclock+0xde
doreti_swi() at doreti_swi+0xf
Apparently this only happens when the CPU load is above normal, hence
two instances of the primes program had to be started.
>Fix:
No idea.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990722085922.750.qmail>