Subject: Re: fxp issues
To: HITOSHI Osada <QFH02545@nifty.com>
From: Daniel Carosone <dan@geek.com.au>
List: current-users
Date: 09/20/2004 12:34:27
--RDS4xtyBfx+7DiaI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 17, 2004 at 12:27:31AM +0900, HITOSHI Osada wrote:
>=20
> > So, as stated before, the only workaround I know of is to keep some tra=
ffic
> > on the interface.. but whether or not that works for everyone, it is
> > obviously still a driver problem. If I had the time, I'd try to debug i=
t..
> > but it's (obviously) not causing a kernel panic, nor any messages to
> > console, so I wouldn't know where in the code to start looking.
>=20
> Yes, this problem is really our driver's limitation.=20
> See /sys/dev/ic/i82557.c line:1472.

I'm not entirely convinced.  At least, I don't understand why this has
only now started happening, when the code has been like this since
1999. (rev 1.8)

Something else is afoot.

--
Dan.
--RDS4xtyBfx+7DiaI
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iD8DBQFBTkGzEAVxvV4N66cRAmF5AJwJEB+Cvn6RX5Xw2lke34rX4dyQlACdHVnJ
tCfXDl3HP/DWcPqh9i0vKpA=
=/qn4
-----END PGP SIGNATURE-----

--RDS4xtyBfx+7DiaI--