From owner-freebsd-current@FreeBSD.ORG Sat Apr 5 07:58:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FE8937B401 for ; Sat, 5 Apr 2003 07:58:34 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D877C43F3F for ; Sat, 5 Apr 2003 07:58:33 -0800 (PST) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id C097F2ED410; Sat, 5 Apr 2003 07:58:33 -0800 (PST) Date: Sat, 5 Apr 2003 17:58:33 +0200 From: Maxime Henrion To: current@freebsd.org Message-ID: <20030405155833.GV1750@elvis.mu.org> References: <20030405002444.GR1750@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030405002444.GR1750@elvis.mu.org> User-Agent: Mutt/1.4.1i Subject: Re: HEADS UP: fxp breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 05 Apr 2003 15:58:34 -0000 Hi all, I was finally able to reproduce the problems people have been reporting. That is, the fxp(4) card works but there are many odd "unknown: DMA timeout" and "unknown: device timeout" messages. This was due to a bug in fxp(4) which was harmless unless you used DEVICE_POLLING. These problems go away when using the 1.156 revision of if_fxp.c. Please note that other people have been reporting different symptoms, ie the card sees no traffic at all. I'm not sure the latest sources fix these cases too, but I'm fairly confident they do, because one person who has been reporting me such symptoms was using DEVICE_POLLING too. Of course, if it's still broken for you, please let me know. Cheers, Maxime