From owner-freebsd-current@FreeBSD.ORG Wed Aug 13 00:00:34 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 B4F1637B405 for ; Wed, 13 Aug 2003 00:00:34 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF21543FBF for ; Wed, 13 Aug 2003 00:00:33 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc156.dialup.mindspring.com ([209.86.4.166] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19mpcK-00074F-00; Wed, 13 Aug 2003 00:00:21 -0700 Message-ID: <3F39E1CC.7292B6C1@mindspring.com> Date: Tue, 12 Aug 2003 23:59:24 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Eivind Olsen References: <770.1060717174@critter.freebsd.dk> <15173625.1060727308@[192.168.0.2]> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a485a1e8575fd33b60bf7822442acc4c51667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: Poul-Henning Kamp 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: Wed, 13 Aug 2003 07:00:35 -0000 Eivind Olsen wrote: > (kgdb) fr 12 > #12 0xc030697e in spec_xstrategy (vp=0xc1fa9cc0, bp=0x0) at > /usr/src/sys/fs/specfs/spec_vnops.c:512 > 512 DEV_STRATEGY(bp); > (kgdb) print *bp->b_dev > There is no member named b_dev. Uh, bp is 0 (NULL). Even if there were a member, you're not going to find out its value, since there isn't one. A couple of things you might want to try is to chase down the vnode, instead, e.g.: print *vp (look for v_type) print *(dn_p)vp->v_data (if it's a devfs vnode) print *((dn_p)vp->v_data)->linklist->name (name of the device with the problem, if this is a devfs vp) etc. -- Terry