Date: Thu, 1 Jun 1995 18:40:01 -0700 From: Stephen McKay <syssgm@devetir.qld.gov.au> To: freebsd-bugs Subject: kern/472: bad mount causes panic: ufs_lock Message-ID: <199506020140.SAA21624@freefall.cdrom.com> In-Reply-To: Your message of Fri, 2 Jun 1995 11:06:11 %2B1000 <199506020106.LAA00224@stupid.devetir.qld.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
>Number: 472 >Category: kern >Synopsis: 'mount /foo /foo' causes panic: ufs_lock >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 1 18:40:00 1995 >Originator: Stephen McKay >Organization: >Release: FreeBSD 2.0-BUILT-19950510 i386 >Environment: 386SX16 4Mb ram, IDE 80Mb, 10Mb swap FreeBSD-current CTM src-cur 681 (1995-05-31 01:19:48) Perhaps you think of this as 2.0.5-ALPHA. >Description: One hazy afternoon, I mistyped a floppy mount command and got: mount -t msdos /fd0 /fd0 Result: panic: ufs_lock: recursive lock not expected, pid: 267 To be sure of this, I rebooted and tried: mount /fd0 /fd0 Result: panic: ufs_lock: recursive lock not expected, pid: 11 >How-To-Repeat: 'mount /mnt /mnt' should do the trick. >Fix: Unknown. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506020140.SAA21624>