From owner-freebsd-i386@FreeBSD.ORG  Wed Jul 25 07:21:12 2007
Return-Path: <owner-freebsd-i386@FreeBSD.ORG>
Delivered-To: freebsd-i386@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4F0A416A419;
	Wed, 25 Jul 2007 07:21:12 +0000 (UTC)
	(envelope-from cerny@icomvision.com)
Received: from mohinder.icomvision.com (icom.casablanca.cz [81.0.254.115])
	by mx1.freebsd.org (Postfix) with ESMTP id 121A413C481;
	Wed, 25 Jul 2007 07:21:11 +0000 (UTC)
	(envelope-from cerny@icomvision.com)
Received: by mohinder.icomvision.com (Postfix, from userid 503)
	id 0BCCEF19E9; Wed, 25 Jul 2007 09:03:56 +0200 (CEST)
Date: Wed, 25 Jul 2007 09:03:56 +0200
From: Marian Cerny <jojo@matfyz.cz>
To: bug-followup@FreeBSD.org
Message-ID: <20070725070356.GA80507@icomvision.com>
References: <200706281720.l5SHK9hx098625@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200706281720.l5SHK9hx098625@freefall.freebsd.org>
User-Agent: Mutt/1.4.2.3i
Cc: Gavin Atkinson <gavin@FreeBSD.org>, freebsd-i386@FreeBSD.org
Subject: Re: i386/70832: [re] serious problems with RealTek NIC using re0
	driver on Evo N1015v
X-BeenThere: freebsd-i386@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2007 07:21:12 -0000

I tried to reproduce those problems on FreeBSD 6.2R.

1. I was not able to reproduce the first problem with sporadic hangs at
   boot. However I have not tested the laptop for long enough period.

2. I was not able to reproduce the panic on 'halt -p'. This problem
   seems to be fixed.

3. I WAS able to reproduce the last problem with cvsup & "re0: watchdog
   timeout". But there is a difference in the behaviour. Now when
   watchdog timeouts appear on the screen, the network is still usable.
   The cvsup does not finish successfully. When I tried csup, there also
   was a problem with watchdog timeouts, however the csup doesn't seem
   to block itself and it finishes its job successfully.

The problems are definitely less serious than in FreeBSD 5.2.1R.

Marian Cerny