From owner-freebsd-current Mon Aug 25 23:22:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA12748 for current-outgoing; Mon, 25 Aug 1997 23:22:29 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA12731 for ; Mon, 25 Aug 1997 23:22:17 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27011; Tue, 26 Aug 1997 08:21:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA03455; Tue, 26 Aug 1997 08:09:50 +0200 (MET DST) Message-ID: <19970826080950.GF23680@uriah.heep.sax.de> Date: Tue, 26 Aug 1997 08:09:50 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@hub.freebsd.org Cc: mark@grondar.za Subject: Re: kern/4382: CURRENT kernel has a "free vnode isn't" panic References: <199708252100.OAA09409@hub.freebsd.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708252100.OAA09409@hub.freebsd.org>; from Steve Passe on Aug 25, 1997 14:00:01 -0700 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Steve Passe wrote: > The following reply was made to PR kern/4382; it has been noted by GNATS. > > From: Steve Passe > To: mark@grondar.za > Cc: FreeBSD-gnats-submit@FreeBSD.ORG > Subject: Re: kern/4382: CURRENT kernel has a "free vnode isn't" panic > Date: Mon, 25 Aug 1997 14:51:14 -0600 > > Hi, > > this is a know problem, John is working on it and says: This reminds me: i've just closed a number of PRs that were for -current. Folks, while we urge people to use send-pr for error reporting, please *don't* use this as the first method when reporting something for a brand-new -current system. Always watch the -current mailinglist, that's what you are expected to do. Only if you think there's danger that it might fall through the cracks (or it's really a long-standing problem affecting something else as well), report it with send-pr. PRs submitted for -current have proven to quickly become stale. And while the person who fixed the problem was often well aware of the problem itself, he wasn't of the PRs that were also file against it, so they never get closed. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)