From owner-freebsd-current@FreeBSD.ORG  Tue Jun 26 01:19:44 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 6B9CB16A41F
	for <freebsd-current@freebsd.org>; Tue, 26 Jun 2007 01:19:44 +0000 (UTC)
	(envelope-from sfpoof@gmail.com)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224])
	by mx1.freebsd.org (Postfix) with ESMTP id 17C1C13C480
	for <freebsd-current@freebsd.org>; Tue, 26 Jun 2007 01:19:43 +0000 (UTC)
	(envelope-from sfpoof@gmail.com)
Received: by wr-out-0506.google.com with SMTP id 70so1083643wra
	for <freebsd-current@freebsd.org>; Mon, 25 Jun 2007 18:19:42 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=n6th2j17tgmTpDO423J3IIED6jKTu2xFfjnKmRlF29/uHjEOdpemi0zapMQTmsC0kkYIEg5yWeH1hro+m5p+RK9wVS+uSuHC2+r0yl++ob9ArYUnlb6uKBmahaKjwGPUfzNn6y7PF8zQDA5OVJ1JqDKhPYTPPMKIcRxd/InC7YY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=N0ZVH7XfvZN/ycFnYB306Wvhd8AZb3JBhzp4hP16HmMaIYfeOATjUC5+gZHlrsTMjN+cItXQdLJCVoQt5m8y7nG2JCgxw9qpSJictCWmJtUsXdWXsxKcrlD71ZknMP9/sVKCm1S3Ql1xrHZ/Py7tySYyO5478GIU3oRnw+kVVNI=
Received: by 10.90.25.3 with SMTP id 3mr4881871agy.1182820781850;
	Mon, 25 Jun 2007 18:19:41 -0700 (PDT)
Received: by 10.90.70.9 with HTTP; Mon, 25 Jun 2007 18:19:41 -0700 (PDT)
Message-ID: <c027a39a0706251819y157a352fu292dc2533c6920b1@mail.gmail.com>
Date: Mon, 25 Jun 2007 18:19:41 -0700
From: "Kevin Gerry" <sfpoof@gmail.com>
To: freebsd-current@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Issues with 'xl0' keeping link
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2007 01:19:44 -0000

I've noticed that after a recent patch, that xl0 is having issues syncing
(Example from log/messages below) and wasn't sure how to 'debug' the
interface to find out what either physically or if the driver is causing it.
(I have attempted replacing the card with the same model)

/var/log/messages:
Jun 25 18:10:20 storage kernel: xl0: link state changed to DOWN
Jun 25 18:10:22 storage kernel: xl0: link state changed to UP
Jun 25 18:11:30 storage kernel: xl0: link state changed to DOWN
Jun 25 18:11:31 storage kernel: xl0: link state changed to UP
Jun 25 18:12:15 storage kernel: xl0: link state changed to DOWN
Jun 25 18:12:17 storage kernel: xl0: link state changed to UP
Jun 25 18:12:38 storage kernel: xl0: link state changed to DOWN
Jun 25 18:12:39 storage kernel: xl0: link state changed to UP

pciconf:
xl0@pci0:10:0:  class=0x020000 card=0x100010b7 chip=0x980510b7 rev=0x78
hdr=0x00
    vendor     = '3COM Corp, Networking Division'
    device     = '3C980-TX 10/100baseTX NIC [Python-T]'