From owner-freebsd-stable@FreeBSD.ORG Wed Mar 26 21:06:01 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 921B1106567D for ; Wed, 26 Mar 2008 21:06:01 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D422C8FC1A; Wed, 26 Mar 2008 21:05:59 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47EABABC.5010309@FreeBSD.org> Date: Wed, 26 Mar 2008 22:06:04 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Peter Much References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.ORG Subject: Re: "s/stable/broken/g" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2008 21:06:01 -0000 Peter Much wrote: > And the party continues... > When starting my usual environment, there is already the next pagefault > kernel panic! > > Tracking it down... it's the "type" keyword in devfs rules. According > to the manpage, support for this was _not_ withdrawn. > But actually, entering something like > devfs rule apply type tape WHATEVER > crashes the system. Software always has bugs, and it is a mistake to think that the "stable" designation does not mean "has no bugs". It's unfortunate that you have hit a couple of them, but please continue to work through the process of documenting them. With regards to your ethernet problems, old cards like ed do not get much testing thesedays because few people use them. Combined with the fact that ethernet problems are often specific to certain hardware models or revisions, you may be the only person to have tried this particular case in many years. By the same token, these problems are difficult to fix without a developer having access to the same problem hardware. You might consider offering to ship it to an interested developer if one can be found. Kris