From owner-freebsd-sparc64@FreeBSD.ORG Thu May 21 14:50:07 2009 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94EA61065674 for ; Thu, 21 May 2009 14:50:07 +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 0EB748FC17 for ; Thu, 21 May 2009 14:50:06 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id n4LEo5Pj097825; Thu, 21 May 2009 16:50:05 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id n4LEo53V097824; Thu, 21 May 2009 16:50:05 +0200 (CEST) (envelope-from marius) Date: Thu, 21 May 2009 16:50:05 +0200 From: Marius Strobl To: Mauro Calderara Message-ID: <20090521145005.GB89774@alchemy.franken.de> References: <21C7712A-2C48-4D95-91B9-536361CA04EA@lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21C7712A-2C48-4D95-91B9-536361CA04EA@lbl.gov> User-Agent: Mutt/1.4.2.3i Cc: freebsd-sparc64@freebsd.org Subject: Re: tap-driver on sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2009 14:50:07 -0000 On Wed, May 20, 2009 at 01:14:06PM -0700, Mauro Calderara wrote: > Hi Marius > > I just ran into an issue with the tap-driver on FreeBSD resulting in a > kernel panic. Googling yielded this bug report (the poster did exactly > what I'm trying to do, run OpenVPN on a tap-interface): > http://lists.freebsd.org/pipermail/freebsd-sparc64/2006-May/004132.html > > You provided a patch but it seems the person never responded. I still > see the issue on 7.0 and am currently recompiling to see whether it is > still there with 7.2. Did that patch go into the official repo somewhen? > > In case not, what would you need to create one? I'm pretty sure I can > provide instructions detailed enough to reproduce the issue. > Hi, that patch went it into the repository prior to FreeBSD 7.0, so what you are seeing is likely to be a different problem. If it still persists with 7.2 it would be great if you could also provide a backtrace. Marius