From owner-freebsd-i386@FreeBSD.ORG Tue Oct 5 18:10:21 2004 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69ACD16A4CE for ; Tue, 5 Oct 2004 18:10:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EE5243D31 for ; Tue, 5 Oct 2004 18:10:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i95IALB5005991 for ; Tue, 5 Oct 2004 18:10:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i95IALmr005990; Tue, 5 Oct 2004 18:10:21 GMT (envelope-from gnats) Date: Tue, 5 Oct 2004 18:10:21 GMT Message-Id: <200410051810.i95IALmr005990@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Russell Jackson Subject: Re: i386/70832: Serious problems with RealTek NIC using re0 on Evo N1015v X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Russell Jackson List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2004 18:10:21 -0000 The following reply was made to PR i386/70832; it has been noted by GNATS. From: Russell Jackson To: freebsd-gnats-submit@freebsd.org, jojo@matfyz.cz Cc: Subject: Re: i386/70832: Serious problems with RealTek NIC using re0 on Evo N1015v Date: Tue, 5 Oct 2004 10:57:47 -0700 (PDT) We're on 5.3BETA7 now, and this problem persists. The internal RT8139C+ on my Compaq Presario 900 is complete unusable. Not only do I get the watchog timeouts and random panics at shutdown, but often the loopback test fails and the driver doesn't attach.Obviously, I'm not on a 64bit bus, so this test should not fail. Turning off ACPI does not seem to correct the problem, but I'm not certain that it rules it out as a source. I know many others have also reported this problem on freebsd-current. I have personally sent several messages to Bill Paul (maintainer) about the issue, but have never recieved a response.