From owner-freebsd-current@FreeBSD.ORG Mon Jun 2 23:10:43 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8218C1065685 for ; Mon, 2 Jun 2008 23:10:43 +0000 (UTC) (envelope-from flo@kasimir.com) Received: from kasimir.com (kasimir.com [85.214.51.166]) by mx1.freebsd.org (Postfix) with ESMTP id 0257A8FC19 for ; Mon, 2 Jun 2008 23:10:42 +0000 (UTC) (envelope-from flo@kasimir.com) Received: (qmail 90278 invoked from network); 3 Jun 2008 01:10:42 +0200 Received: from i53874f42.versanet.de (HELO nibbler-osx.local) (83.135.79.66) by kasimir.com with SMTP; 3 Jun 2008 01:10:41 +0200 Message-ID: <48447DD3.8030700@kasimir.com> Date: Tue, 03 Jun 2008 01:10:11 +0200 From: Florian Smeets User-Agent: Thunderbird 2.0.0.15pre (Macintosh/20080602) MIME-Version: 1.0 To: John Baldwin References: <200805302339.33935.jhb@freebsd.org> <484461A5.1010003@kasimir.com> <200806021749.06765.jhb@freebsd.org> <48447BF4.4000808@kasimir.com> In-Reply-To: <48447BF4.4000808@kasimir.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: tx(4) MPSAFE patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2008 23:10:43 -0000 Florian Smeets wrote: > John Baldwin wrote: >> On Monday 02 June 2008 05:09:57 pm Florian Smeets wrote: >>> John Baldwin wrote: >>>> I have a patch to make tx(4) MPSAFE. I do not have the hardware to >>>> test >> this >>>> however. Unlike many of the previous patches, though, this driver >>>> appears >> to >>>> be for hardware that is not entirely ancient, so there is hopefully a >> decent >>>> chance someone can test this. >>>> >>>> http://www.FreeBSD.org/~jhb/patches/tx.patch >>>> >>> Hi John, >>> >>> sorry does not work, do you need anything else than the backtrace? >>> FWIW, this is an SMP system with 2 CPUs. >> >> Ok, I've updated the patch to fix this (and to fix a few other minor >> nits with the driver). Please refetch the patch from the URL above >> and try again. Thanks. >> > > > > It goes on like that forever sometimes the zone varies between "16" "32" > and "64". The system does not boot further, or i was just to impatient... > In fact i was too impatient, it did boot. After the last witness warning these messages appear: tx0: Ethernet address: 00:e0:29:6c:2e:47 tx0: [ITHREAD] tx0: flags=8843 metric 0 mtu 1500 options=8 ether 00:e0:29:6c:2e:47 inet 172.30.1.100 netmask 0xffff0000 broadcast 172.30.255.255 media: Ethernet autoselect (100baseTX ) status: active And it does work flo@fw-pri:~ 1 > ping 172.30.1.100 PING 172.30.1.100 (172.30.1.100): 56 data bytes 64 bytes from 172.30.1.100: icmp_seq=0 ttl=64 time=1.780 ms 64 bytes from 172.30.1.100: icmp_seq=1 ttl=64 time=0.969 ms 64 bytes from 172.30.1.100: icmp_seq=2 ttl=64 time=0.974 ms Cheers, Florian