From owner-freebsd-current Tue Apr 21 23:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05645 for freebsd-current-outgoing; Tue, 21 Apr 1998 23:48:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pc-21490.bc.rogers.wave.ca (pc-21490.bc.rogers.wave.ca [24.113.51.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05545 for ; Wed, 22 Apr 1998 06:47:56 GMT (envelope-from jh@pc-21490.bc.rogers.wave.ca) Received: (from jh@localhost) by pc-21490.bc.rogers.wave.ca (8.8.8/8.8.7) id XAA00313; Tue, 21 Apr 1998 23:46:36 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 21 Apr 1998 23:46:36 -0700 (PDT) Reply-To: Jonathan Hanna Organization: Pangolin Systems From: Jonathan Hanna To: Andrzej Bialecki Subject: RE: Ouch... (DEVFS) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Apr-98 Andrzej Bialecki wrote: > Hi! > > I have two problems with DEVFS (sources are from yesterday). > > 1. Running multiuser, as soon as I try to umount the DOS partition, > machine panics with something like: > > _panic > _wdcontrol > _wdintr > Xresume14() > --- interrupt > vec14 > _pmap_enter > _vm_fault > _trap_pfault > calltrap > --- trap > >>cont > > syncing disks 19 19 19 19 [...] .... giving up > rebooting > > This is 100% repeatable. Same here. It happens when I mount both an msdos and an ffs slice from the same disk. I tracked it a little in an earlier version of DEVFS/SLICE: I don't know how things are supposed to work but it seems that msdos_unmount is calling wdsclose via VOP_CLOSE, setting the du->dk_state to CLOSE. Later an ffs_unmout is done, which tries an operation on the now closed disk and panics. I am mounting msdos on wd1s1 and ufs on wd1s2a,e,f,g. Jonathan Hanna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message