From owner-freebsd-stable@FreeBSD.ORG Wed May 24 18:19:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 EDC0916AB84 for ; Wed, 24 May 2006 18:19:25 +0000 (UTC) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAACF43D70 for ; Wed, 24 May 2006 18:19:18 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [192.168.1.128] (e178025128.adsl.alicedsl.de [85.178.25.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 0FE213000C7E; Wed, 24 May 2006 20:19:17 +0200 (CEST) Message-ID: <4474A3DA.7040409@mail.uni-mainz.de> Date: Wed, 24 May 2006 20:20:10 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.2 (X11/20060517) MIME-Version: 1.0 To: Damian Gerow , freebsd-stable@freebsd.org References: <4472551C.5020803@mail.uni-mainz.de> <20060524002323.GF61179@afflictions.org> In-Reply-To: <20060524002323.GF61179@afflictions.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: Subject: Re: nve0: device timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 18:19:30 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Damian Gerow wrote: > Thus spake O. Hartmann (ohartman@mail.uni-mainz.de) [22/05/06 20:23]: > : Is there a solution on its way? What is about the Berkeley native nfe-code? > > As someone already pointed out, the fix is already in -CURRENT. A patch for > -STABLE has been posted recently, but I don't remember if it was to stable@ > or amd64@. > > FWIW, I'd recommend if_nfe. It's proven a little more stable for me, and I > haven't had any issues with device timeouts at all. > > All right, I did as recommended an now: Voila, I have a usable computersystem! Without any patch or the new nfe driver a system based on the ASUS A8N32-SLI is unusable! The box get stuck every few minutes for a second a loose keyboard input and corrupt DVD/DVD+-RW or CD-R/CD-RW while burning. Hope the nfe driver will find it's way into stable as fast as possible ... oh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdKPY9PZHcThI6nsRAivbAJ0UE9sbLeL+0sLlRcti3jA3m4iP0wCfXNdG OmlR2KW1bSxhrDrYiw1dYjE= =Elyt -----END PGP SIGNATURE-----