From owner-freebsd-bugs Wed Jul 19 5:20: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1EE0937BB57 for ; Wed, 19 Jul 2000 05:20:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA50414; Wed, 19 Jul 2000 05:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 19 Jul 2000 05:20:02 -0700 (PDT) Message-Id: <200007191220.FAA50414@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Joakim Henriksson Subject: Re: misc/20031: kernel randomly panics with ffs_clusteralloc: map mismatch Reply-To: Joakim Henriksson Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/20031; it has been noted by GNATS. From: Joakim Henriksson To: Sheldon Hearn Cc: Joakim Henriksson , freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/20031: kernel randomly panics with ffs_clusteralloc: map mismatch Date: Wed, 19 Jul 2000 14:14:05 +0200 > > I've been getting consistant crashes while accessing a msdos drive since i > > filed the 16740 PR. Do you perchance have a VIA MVP3 based mother board? > > Perhaps you could send the chipset related info from a "boot -v"? > > Msdos, you say? I saw a fix go into msdosfs_vnops.c recently, which > is presumed to have fixed this panic: > > panic: vrele: negative ref cnt I will try it. But the fact remains that the ffs_cluster alloc bug still exists... > However, I seem to remember that you're using 3.4-RELEASE. The fix has > only been applied to the development branch and to RELENG_4. You can > try to come up with a patch for yourself based on: I'm running 4.1-RC two days too early for this patch. > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/msdosfs/msdosfs_vnops.c.diff?r1=1.95&r2=1.95.2.1 -- regards/ Joakim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message