From owner-freebsd-current@FreeBSD.ORG Mon Aug 2 11:29:21 2004 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 C921416A4CE; Mon, 2 Aug 2004 11:29:21 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D01E43D5D; Mon, 2 Aug 2004 11:29:18 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i72BTBDf007546; Mon, 2 Aug 2004 13:29:12 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <006001c47883$f20e9f70$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "John Baldwin" , "Robert Watson" References: <200407272318.46256.jhb@FreeBSD.org> Date: Mon, 2 Aug 2004 13:28:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 cc: bzeeb+freebsd+lor@zabbadoz.net cc: alc@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Fatal LOR: PV ENTRY (UMA zone) @ /home2/src/sys/vm/uma_core.c:2033 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Aug 2004 11:29:21 -0000 Well the Tyan board is finally in. Look like a quality PCB, althoug some of the connectors are somewhat far away for the large case I'm using.. First need to do some paid work, but then I'll start rebuilding the system. I guess we'll know more by tomorrow. :) --WjW ----- Original Message ----- From: "John Baldwin" To: "Robert Watson" Cc: "Willem Jan Withagen" ; ; ; Sent: Wednesday, July 28, 2004 5:18 AM Subject: Re: Fatal LOR: PV ENTRY (UMA zone) @ /home2/src/sys/vm/uma_core.c:2033 > On Tuesday 27 July 2004 06:51 pm, Robert Watson wrote: > > On Wed, 28 Jul 2004, Willem Jan Withagen wrote: > > > Running on amd64: > > > > > > > > > > > And right followed by.... > > > > > > panic: lock (sleep mutex) Giant not locked @ > > > /home2/src/sys/kern/vfs_syscalls.c: 959 > > > cpuid = 0; > > > KDB: stack backtrace: > > > kdb_backtrace() at kdb_backtrace+0x34 > > > panic() at panic+0x1d2 > > > witness_unlock() at witness_unlock+0xdd > > > _mtx_unlock_flags() at _mtx_unlock_flags+0x68 > > > kern_open() at kern_open+0x128 > > > open() at open+0x18 > > > syscall() at syscall+0x330 > > > Xfast_syscall() at Xfast_syscall+0xa8 > > > --- syscall (5, FreeBSD ELF64, open), rip = 0x76d75c, rsp = > > > 0x7fffffffe088, rbp = 0x7fffffffe0c0 --- > > > KDB: enter: panic > > > [thread 100316] > > > Stopped at kdb_enter+0x2e: nop > > > > I've seen several reports of "mysterious" panics where Giant isn't held on > > return from namei() or other points following a name lookup. Kris > > Kenneway reported this on the package build cluster, for example. I'm > > wondering if something handling a page fault hit by namei() during a > > string copy in from user space if resulting in Giant not being held where > > it should be. In Kris's case, we tried pushing around GIANT_REQUIRED some > > because I thought maybe the caller wasn't holding Giant when it should, > > but that turned out not to be it. So maybe we have some sort of > > preemption/VM/locking issue? > > The preemption case is very easy to test, just turn it off in machine/param.h > and see if it goes away. > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > >