From owner-freebsd-current@FreeBSD.ORG Wed Jun 25 10:37:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0430537B404 for ; Wed, 25 Jun 2003 10:37:24 -0700 (PDT) Received: from MX3.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80B8943F75 for ; Wed, 25 Jun 2003 10:37:22 -0700 (PDT) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-39-98-dsl.mus.estpak.ee [80.235.39.98]) by MX3.estpak.ee (Postfix) with ESMTP id 29A8023C016; Wed, 25 Jun 2003 20:37:20 +0300 (EEST) Received: by kevad.internal (Postfix, from userid 1000) id 6E7C18232; Wed, 25 Jun 2003 13:38:25 +0300 (EEST) Date: Wed, 25 Jun 2003 13:38:25 +0300 From: Vallo Kallaste To: Ian Freislich Message-ID: <20030625103825.GA4818@kevad.internal> References: <7075.1056558033@mci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7075.1056558033@mci.com> User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org Subject: Re: ULE crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2003 17:37:24 -0000 On Wed, Jun 25, 2003 at 06:20:33PM +0200, Ian Freislich wrote: > About 4.5 minutes after rebooting with a SCHED_ULE kernel (I give > ULE a go every few months), top started looking really wierd (the > CPU % just kept on accumulating for each process). Before dnetc > started, httpd showed 17% CPU, but the system was supposedly 100% > idle at the time according to top. Then dnetc started and things > got wierd. > > panic: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > cpuid = 1; lapic.id = 01000000 > fault virtual address = 0x38 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc01e094d > stack pointer = 0x10:0xce772be4 > frame pointer = 0x10:0xce772bf4 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 603 (dnetc) > trap number = 12 > panic: page fault > cpuid = 1; lapic.id = 01000000 > Stack backtrace: > boot() called on cpu#1 > > syncing disks, buffers remaining... panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled > cpuid = 1; lapic.id = 01000000 > boot() called on cpu#1 > Uptime: 4m15s > Dumping 191 MB > ata0: resetting devices .. > done > 16 32 48 64 80 96 112 128 144 160 176 > --- I had the same panic last week after updating and had to disable seti@home to get up in hurry. The last kernel (4BSD) ran fine for a month with two seti processes running. -- Vallo Kallaste