From owner-freebsd-stable@FreeBSD.ORG Thu May 19 02:25:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09E9F16A4CE for ; Thu, 19 May 2005 02:25:56 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0CB943D95 for ; Thu, 19 May 2005 02:25:53 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j4J2TARs090971; Wed, 18 May 2005 20:29:10 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <428C152A.2020706@samsco.org> Date: Wed, 18 May 2005 22:25:14 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Burden References: <200505162358.j4GNwFjg033775@sullivan.realtime.net> <20050518160240.Q87264@carver.gumbysoft.com> <20050519022029.GB16642@tigerfish2.my.domain> In-Reply-To: <20050519022029.GB16642@tigerfish2.my.domain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: stable@freebsd.org Subject: Re: problems with ASR card/5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2005 02:25:56 -0000 Bruce Burden wrote: > > > Hi Doug, > > well, pulling cards demonstrated where the problem lie, but it > was not a hardware problem. By chance, I happened upon the "options > ASR_COMPAT" directive, and that solved my problem. However, the > GENERIC kernel configuration for i386 does NOT have this option, but > it does have the "asr" driver configured. > > Having one but not the other causes problems, as I discovered. > > Bruce > Thanks for the report. The ASR_COMPAT option should be self-contained, so if its abscence is causing problems then it needs to be fixed. I'll try to look at it soon. Scott