From owner-freebsd-current@FreeBSD.ORG Tue Jul 21 13:59:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F166106566B; Tue, 21 Jul 2009 13:59:52 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from fujibayashi.jp (karas.fujibayashi.jp [77.221.159.4]) by mx1.freebsd.org (Postfix) with ESMTP id 3CBFB8FC25; Tue, 21 Jul 2009 13:59:51 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from [192.168.0.10] (datacenter.telecombusinessconsulting.net [77.221.137.211]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by fujibayashi.jp (Postfix) with ESMTPSA id 8733A78F50; Tue, 21 Jul 2009 17:59:50 +0400 (MSD) Message-ID: <4A65C9D1.6080902@haruhiism.net> Date: Tue, 21 Jul 2009 17:59:45 +0400 From: Kamigishi Rei User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: John Baldwin References: <4A659F98.2060007@haruhiism.net> <200907210857.01690.jhb@freebsd.org> In-Reply-To: <200907210857.01690.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Lawrence Stewart , freebsd-current@freebsd.org Subject: Re: [follow-up] Fatal trap 12 in r195146+ in netisr_queue_internal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 21 Jul 2009 13:59:52 -0000 John Baldwin wrote: > On Tuesday 21 July 2009 6:59:36 am Kamigishi Rei wrote: > >> Everything goes fine until - under heavy load on an interface, usually - >> we reach a point where: >> 1. m->mtx_lock is 4 (== MTX_UNOWNED). >> 2. v is assigned mtx_lock's value (4 == MTX_UNOWNED). >> 3. condition (v == MTX_UNOWNED) fails. >> > This will not happen. If you look at the disassembly you will see this can't > happen either. Do you have a crashdump from a crash? > I've got about 40 crash dumps on unmodded (without debug code) kernel, and 3 or 4 with debug stuff (KASSERTs added by me). I can reproduce this on my test server (Core2 Duo 3.0, 4GB RAM), on my home PC (Core2 Quad 2.5), and in VMWare with 2 CPUs in VT-x mode on my laptop. It can't be reproduced on single-CPU single-core (including hyperthreaded) systems. Quoting, (kgdb) fr 6 #6 0xffffffff80586255 in _mtx_lock_sleep (m=0xffffffff80e60823, tid=18446742977255365296, opts=Variable "opts" is not available. ) at /usr/src/sys/kern/kern_mutex.c:407 407 owner = (struct thread *)(v & ~MTX_FLAGMASK); (kgdb) print m->mtx_lock $14 = 4 (kgdb) print v $15 = 21946368 -- Kamigishi Rei KREI-RIPE