From owner-freebsd-current@FreeBSD.ORG  Thu Apr  3 13:10:11 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 4422537B41A
	for <current@freebsd.org>; Thu,  3 Apr 2003 13:10:11 -0800 (PST)
Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1B9B843F3F
	for <current@freebsd.org>; Thu,  3 Apr 2003 13:10:10 -0800 (PST)
	(envelope-from Robin.Blanchard@gactr.uga.edu)
Received: (qmail 82409 invoked from network); 3 Apr 2003 21:10:04 -0000
Received: from unknown (HELO ex.gactr.uga.edu) ([10.10.11.21])
	(envelope-sender <Robin.Blanchard@gactr.uga.edu>)
	by mail.servers.gactr.gc.nat (qmail-ldap-1.03) with SMTP
	for <current@freebsd.org>; 3 Apr 2003 21:10:04 -0000
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Thu, 3 Apr 2003 16:10:04 -0500
Message-ID: <EE3D3FBAFFCAED448C21C398FDAD91AC044284@EBE1.gc.nat>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Panic on fxp
Thread-Index: AcL6JOl10Fh/a24ETviqEHwZETl6aQAABcbw
From: "Robin P. Blanchard" <Robin.Blanchard@gactr.uga.edu>
To: <current@freebsd.org>
Subject: RE: Panic on fxp
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Thu, 03 Apr 2003 21:10:11 -0000

I'm seeing the same thing. A kernel from first thing this morning =
paniced the
kernel whilst attempting to probe the device. I saw a commit go in =
shortly
after 15.00 and rebuilt the kernel. Kernel built on that commit allows =
the
box to boot, but the device simply doesn't pass (or see) any
traffic...Reverted back to a working kernel from 10March.


# ls -ltr /usr/src/sys/dev/fxp/
total 116
-rw-r--r--  1 root  wheel  21318 Oct 25  2001 rcvbundl.h
-rw-r--r--  1 root  wheel   8190 Apr  2 13:00 if_fxpvar.h
-rw-r--r--  1 root  wheel  73326 Apr  3 11:46 if_fxp.c
-rw-r--r--  1 root  wheel  12975 Apr  3 15:14 if_fxpreg.h


Peter Wemm wrote:
> "Daniel C. Sobral" wrote:
>=20
>>It seems recent current doesn't like my fxp. A current from some 10
>>hours ago keeps complaining about device timeout and dma timeout. I=20
>>don't *know* it's fxp fault (for one thing, because it says =
"unknown"),=20
>>but...
>>
>>So, two hours ago, I cvsupped and tried a new world. This one panics=20
>>on
>>boot, while doing something with fxp (attaching, I think), and doesn't =

>>even get me a core dump.
>>
>>I'll try a new world tomorrow. People tweaking fxp, do please try to=20
>>get
>>it fixed?
>=20
>=20
> Some details would be useful.  Pencil and paper perhaps?  Serial cable =

> to another machine and boot -h?