Date: Sun, 6 Jun 2004 06:25:25 -0700 (PDT) From: Tom Stanik <stanik@alumni.princeton.edu> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/67627: gbde kernel panic Message-ID: <200406061325.i56DPPN4035828@www.freebsd.org> Resent-Message-ID: <200406061330.i56DUKXW090015@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 67627 >Category: i386 >Synopsis: gbde kernel panic >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jun 06 06:30:19 PDT 2004 >Closed-Date: >Last-Modified: >Originator: Tom Stanik >Release: 5.2.1-RELEASE >Organization: >Environment: FreeBSD barr.wi-on.one 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #1: Fri Jun 4 16:11:00 EST 2004 root@barr.wi-on.one:/usr/src/sys/i386/compile/barr1 i386 >Description: gbde panic's kernel if two attach commands are issued; otherwise it works normally. On my system if I enter: -su-2.05b# gbde attach ad1s1c -l /etc/gbde/ad1s1c.lock -su-2.05b# gbde attach ad1s1c -l /etc/gbde/ad1s1c.lock Aside, I know the second attach should have been a 'mount' command and should have failed but it shouldn't panic the kernel >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406061325.i56DPPN4035828>