From owner-freebsd-net@FreeBSD.ORG  Tue Oct 28 03:44:48 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 8ABFC71F
 for <freebsd-net@freebsd.org>; Tue, 28 Oct 2014 03:44:48 +0000 (UTC)
Received: from phlegethon.blisses.org (phlegethon.blisses.org [50.56.97.101])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6B21A377
 for <freebsd-net@freebsd.org>; Tue, 28 Oct 2014 03:44:48 +0000 (UTC)
Received: from blisses.org (cocytus.blisses.org [23.25.209.73])
 by phlegethon.blisses.org (Postfix) with ESMTPSA id 2590D1F02FF;
 Mon, 27 Oct 2014 23:44:47 -0400 (EDT)
Date: Mon, 27 Oct 2014 23:44:45 -0400
From: Mason Loring Bliss <mason@blisses.org>
To: Yonghyeon PYUN <pyunyh@gmail.com>
Subject: Re: Very bad Realtek problems
Message-ID: <20141028034445.GR17150@blisses.org>
References: <20141027195124.GI17150@blisses.org>
 <20141028015020.GB1054@michelle.fasterthan.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20141028015020.GB1054@michelle.fasterthan.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: freebsd-net@freebsd.org
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Oct 2014 03:44:48 -0000

On Tue, Oct 28, 2014 at 10:50:20AM +0900, Yonghyeon PYUN wrote:

> Currently re(4) heavily relies on power on default settings since no
> detailed register configuration is not available. Some register
> configurations made in Windows can survive from warm boot.

Alright, a cold boot doesn't help. I froze up on an rsync, and observed these
stats:

re0 statistics:
Tx frames : 209681
Rx frames : 27559
Tx errors : 0
Rx errors : 0
Rx missed frames : 0
Rx frame alignment errs : 0
Tx single collisions : 0
Tx multiple collisions : 0
Rx unicast frames : 27548
Rx broadcast frames : 9
Rx multicast frames : 2
Tx aborts : 0
Tx underruns : 0

I rebooted with MSI and MSI-X disabled, and it broke again on an rsync. I
observed:

re0 statistics:
Tx frames : 416065
Rx frames : 47783
Tx errors : 0
Rx errors : 0
Rx missed frames : 0
Rx frame alignment errs : 0
Tx single collisions : 0
Tx multiple collisions : 0
Rx unicast frames : 47757
Rx broadcast frames : 24
Rx multicast frames : 2
Tx aborts : 0
Tx underruns : 0

The multicast frames seem to coincide with interface lock-ups.

This time to correct I said ifconfig re0 down; ifconfig re0 up. It came back
but the rsync died.

I'll be happy to provide further debugging information once I know how to
collect it.

-- 
Mason Loring Bliss          mason@blisses.org          Ewige Blumenkraft!
awake ? sleep : random() & 2 ? dream : sleep; -- Hamlet, Act III, Scene I