From owner-freebsd-arch@FreeBSD.ORG  Mon May 26 18:58:02 2008
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AEC211065730
	for <arch@freebsd.org>; Mon, 26 May 2008 18:58:02 +0000 (UTC)
	(envelope-from gary.jennejohn@freenet.de)
Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4])
	by mx1.freebsd.org (Postfix) with ESMTP id 188B18FC17
	for <arch@freebsd.org>; Mon, 26 May 2008 18:58:02 +0000 (UTC)
	(envelope-from gary.jennejohn@freenet.de)
Received: from [195.4.92.20] (helo=10.mx.freenet.de)
	by mout2.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
	25) (Exim 4.69 #19)
	id 1K0htQ-00019M-52; Mon, 26 May 2008 20:58:00 +0200
Received: from r9ea7.r.pppool.de ([89.54.158.167]:39991
	helo=peedub.jennejohn.org)
	by 10.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
	25) (Exim 4.69 #12)
	id 1K0htP-0002Eq-F8; Mon, 26 May 2008 20:58:00 +0200
Date: Mon, 26 May 2008 20:57:57 +0200
From: Gary Jennejohn <gary.jennejohn@freenet.de>
To: arch@freebsd.org
Message-ID: <20080526205757.6e49abba@peedub.jennejohn.org>
In-Reply-To: <483AF194.2020002@digiware.nl>
References: <20080524111715.T64552@fledge.watson.org>
	<1211640498.1510.8.camel@localhost>
	<20080524165519.K9809@fledge.watson.org>
	<e7db6d980805241656q30193933hcd983b6322d02df8@mail.gmail.com>
	<20080525105726.O39741@fledge.watson.org>
	<5D4AF8D7-88A7-4197-A0FE-7CA992EE5F96@FreeBSD.org>
	<20080526163844.GA37636@troutmask.apl.washington.edu>
	<483AF194.2020002@digiware.nl>
X-Mailer: Claws Mail 3.4.0 (GTK+ 2.10.14; amd64-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Willem Jan Withagen <wjw@digiware.nl>,
	Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gary.jennejohn@freenet.de
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 May 2008 18:58:02 -0000

On Mon, 26 May 2008 19:21:24 +0200
Willem Jan Withagen <wjw@digiware.nl> wrote:

> Steve Kargl wrote:
> > On Mon, May 26, 2008 at 05:34:09AM -0700, Ade Lovett wrote:
> >> idiosyncratic situations (yes, ahc(4), I'm looking at you) for 5+  
> > 
> > What's the problem with ahc(4)?  My ahc controller is one of
> > the most reliable pieces of hardware that I've purchased.
> > It's also the only interface available to my external DLT
> > tape drive.
> 
> Not to forget the large amount of embedded ahc's that got implemented on 
> all kinds of serverbords. I still have quite a large set of customers 
> with such ASUS boards I sold to them over the years. Up 'till now I've 
> been able to keep 'm running with the pace of FreeBSD.
> Removing this driver would "leave them behind".
> 
> I can force them to upgrade, but thus far there has been little reason 
> for that (hardware wise).
> 

[pruned the over-zealous CCs]

Well, one problem with ahc is that it doesn't play nicely with >= 4GB
of memory on AMD64.

I have ahc and 4GB of memory and have to set hw.physmem="3500m" in
/boot/loader.conf to keep it from dumping its cookies at boot time.

Otherwise I'm more than happy with my 29160N.

---
Gary Jennejohn