Date: Tue, 12 Aug 2003 21:39:34 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Eivind Olsen <eivind@aminor.no> Cc: freebsd-current@freebsd.org Subject: Re: Crash in g_dev_strategy / CURRENT as of yesterday. Message-ID: <770.1060717174@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 12 Aug 2003 21:37:32 %2B0200." <12117531.1060724252@[192.168.0.2]>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <12117531.1060724252@[192.168.0.2]>, Eivind Olsen writes: >--On 12. august 2003 21:26 +0200 Poul-Henning Kamp <phk@phk.freebsd.dk> >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" -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?770.1060717174>