From owner-freebsd-net@FreeBSD.ORG Thu Jan 24 21:50:20 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3E6278D6 for ; Thu, 24 Jan 2013 21:50:20 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id CA75D910 for ; Thu, 24 Jan 2013 21:50:19 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.5/8.14.5/ALCHEMY.FRANKEN.DE) with ESMTP id r0OLoIeD030826; Thu, 24 Jan 2013 22:50:18 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.5/8.14.5/Submit) id r0OLoHEp030825; Thu, 24 Jan 2013 22:50:17 +0100 (CET) (envelope-from marius) Date: Thu, 24 Jan 2013 22:50:17 +0100 From: Marius Strobl To: Paul Keusemann Subject: Re: Cas driver fails to load first time after boot. Message-ID: <20130124215017.GS85306@alchemy.franken.de> References: <50FEFAB8.1070006@visi.com> <20130124150904.GA27559@alchemy.franken.de> <51017FF0.5080001@visi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51017FF0.5080001@visi.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 21:50:20 -0000 On Thu, Jan 24, 2013 at 12:39:44PM -0600, Paul Keusemann wrote: > > On 01/24/13 09:09, Marius Strobl wrote: > > On Tue, Jan 22, 2013 at 02:46:48PM -0600, Paul Keusemann wrote: > >> Hi, > >> > >> I've got a Dell R200 which I'm trying to build into a gateway with a Sun > >> QGE (501-6738-10). The cas driver fails to load the first time I try to > >> load it but succeeds the second time. Is this a problem with the card, > >> the driver, my karma? > > Wrong phase of the moon, apparently :) > > The MII setup of these chips is a bit tricky and I'm not sure whether > > I've hit all code paths during development of the driver. I certainly > > didn't test with a 501-6738, these have been reported as working before, > > though. It also doesn't make much sense that attaching the devices > > succeeds on the second attempt. Could you please use a if_cas.ko built > > with the attached patch and report the debug output for one of the > > interfaces in both the working and the non-working case? > > I would love to give you output from the working and non-working case > but apparently the phase of the moon has changed, I can't get it to fail > now. The messages output from the working case is attached. > Thanks but unfortunately this doesn't make any sense either. In general, printf()s cause deays which can be relevant. In the locations I've put them they hardly can make such a difference though. If you haven't already done so, could you please power off the machine before doing the test with the patched module? Is the problem still gone if you revert to the original module? Marius