From owner-freebsd-current Fri Feb 9 8:23:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id B8A4C37B6B3 for ; Fri, 9 Feb 2001 07:24:20 -0800 (PST) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.22 #1) id 14RFPH-0006AF-00; Fri, 09 Feb 2001 16:24:19 +0100 Received: from b8422.pppool.de ([213.7.132.34] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.22 #1) id 14RFPG-0000Jp-00; Fri, 09 Feb 2001 16:24:18 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.2/8.11.2) with ESMTP id f19D52T02449; Fri, 9 Feb 2001 14:05:03 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200102091305.f19D52T02449@Magelan.Leidinger.net> Date: Fri, 9 Feb 2001 14:05:01 +0100 (CET) From: Alexander Leidinger Subject: Re: kernel trap 12 with interrupts disabled To: bde@zeta.org.au Cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Feb, Bruce Evans wrote: > Pagefaults occur in copyin() (called from addupc_task() which is called > from ast()) while sched_lock is held. This is not good. Incrementing > the profiling counters is supposed to be pushed to ordinary process > context so that things like copyin() can work (they have to be able > to fault in pages, so they have to be able to sleep...), so using > sched_lock to lock things here is wrong. Are we talking about /sys/kern/kern_clock.c: statclock()? I'm not familiar with the kernel and that's the only place I find something related to profiling if I grep for "profil" and look at the results. If yes, what is to to? >> If I run it withhin X11, the machine deadlocks hard (no response from >> the numlock led on the keyboard), withhin a virtual console I get a lot >> of "kernel trap ..." and the program runs fine. > > It's surprising that it doesn't always deadlock. First I thought I have a hardware problem, I was able to profile the program 4-5 times withhin X11 at a day before. Without changing anything except the options to the program I wasn't able to profile it later. Bye, Alexander. -- Loose bits sink chips. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message