From owner-freebsd-current@FreeBSD.ORG Tue Aug 12 12:43:03 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 9801D37B401 for ; Tue, 12 Aug 2003 12:43:03 -0700 (PDT) Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B08043FAF for ; Tue, 12 Aug 2003 12:42:58 -0700 (PDT) (envelope-from ler@lerctr.org) Received: from lerlaptop.iadfw.net (lerlaptop.iadfw.net [206.66.13.21]) (authenticated bits=0)h7CJgnfg010522; Tue, 12 Aug 2003 14:42:50 -0500 (CDT) Date: Tue, 12 Aug 2003 14:42:49 -0500 From: Larry Rosenman To: Poul-Henning Kamp , Eivind Olsen Message-ID: <268510000.1060717369@lerlaptop.iadfw.net> In-Reply-To: <770.1060717174@critter.freebsd.dk> References: <770.1060717174@critter.freebsd.dk> X-Mailer: Mulberry/3.1.0b5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-milter (http://amavis.org/) cc: freebsd-current@freebsd.org Subject: Re: Crash in g_dev_strategy / CURRENT as of yesterday. 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: Tue, 12 Aug 2003 19:43:03 -0000 --On Tuesday, August 12, 2003 21:39:34 +0200 Poul-Henning Kamp wrote: > In message <12117531.1060724252@[192.168.0.2]>, Eivind Olsen writes: >> --On 12. august 2003 21:26 +0200 Poul-Henning Kamp >> wrote: >>> In message <10206765.1060722342@[192.168.0.2]>, Eivind Olsen writes: >>>> Hello. Some of you might have seen my previous mailings regarding >>>> crashes in g_dev_strategy under FreeBSD 5.1 (RELENG_5_1). I have now >>>> upgraded to CURRENT (cvsupped, compiled and installed yesterday) and I >>>> still see similar crashes (but not identical crashes, I can't see any >>>> mention of Vinum here). >>>># 12 0xc030697e in spec_xstrategy (vp=0xc1fa9cc0, bp=0x0) at >>>> /usr/src/sys/fs/specfs/spec_vnops.c:512 >>> This is the call into the device driver. Do you have any idea which >>> driver this might be ? Can you try to print out the bp->b_dev structure >>> if you still have the dump ? >> >> I still have the dump. Please tell me exactly which commands I should >> use and I'll take a look. I'm not a kernel hacker so I don't know how >> to get at that information all by myself. > > I'm not of a gdb wizard either, but I think you type "up" or "down" until > you are at stack frame #12, and the simply say "print *bp->b_dev" fr 12 will get to that stack frame. FWIW. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749