kern/96391: [nve] [patch] Device timeouts on nve(4)
Daniel Rich
drich at pdi.com
Mon Jan 22 21:10:18 UTC 2007
The following reply was made to PR kern/96391; it has been noted by GNATS.
From: Daniel Rich <drich at pdi.com>
To: bug-followup at FreeBSD.org, nathanw at uchicago.edu
Cc:
Subject: Re: kern/96391: [nve] [patch] Device timeouts on nve(4)
Date: Mon, 22 Jan 2007 11:40:03 -0800
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig3806569C1A2B03E94EE66C35
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I realize this PR has been closed for over 6 months, but I'm seeing
similar symptoms in 6.2REL with my nve0 interface.
In looking at the current code in if_nve.c, it looks like things have
changed a little bit since the patch in this PR, but most of the patch
still exists. The major difference I see is that it now uses
sc->pending_txs to see if there are any pending packets instead of just
checking for it =3D=3D 0. Without knowing more about the hardware, would=
it
make more sense for the "pending_txs_start =3D sc->pending_txs;" line to
be *after* the driver is kicked by tweaking the interrupts?
For the specifics of my system:
6.2-RELEASE amd64
Motherboard: ASUS M2NPV-VM (integrated NVIDIA nForce=AE 430 built-in
Gigabit MAC)
=20
It looks like it is only having problems when passing lots of traffic.=20
Also, I do go through two switches at the moment, that will change when
I get home tonight.
--=20
Dan Rich <drich at pdi.com>
PDI Dreamworks | "Step up to red alert!" "Are you sure, sir?
(650)562-9018 | It means changing the bulb in the sign..."
--------------enig3806569C1A2B03E94EE66C35
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFFtRMUBqBGo55TfQcRAhWCAJ434fsqjJ86G8vJh8ewN3zPEvffnQCfXcnZ
NCttmz7zcz7pJCaM2MLcGFc=
=+0tY
-----END PGP SIGNATURE-----
--------------enig3806569C1A2B03E94EE66C35--
More information about the freebsd-bugs
mailing list