Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E)
ethernet
Pyun YongHyeon
pyunyh at gmail.com
Fri Dec 19 16:25:18 PST 2008
On Fri, Dec 19, 2008 at 04:19:31PM +0100, albri wrote:
> On Wed, Dec 03, 2008 at 06:05:40PM +0900, Pyun YongHyeon wrote:
> > On Mon, Nov 24, 2008 at 01:58:46PM +0900, To albri wrote:
> > > On Mon, Nov 17, 2008 at 07:14:12PM +0100, albri wrote:
> > > > hello,
> > > >
> > > > On 11/17/08, Pyun YongHyeon <pyunyh at gmail.com> wrote:
> > > > > On Sun, Nov 16, 2008 at 03:42:16PM +0100, albri wrote:
> > > > > > hello,
> > > > > >
> > > > > > I have issues transfering big or many files over ethernet on 1000H, also.
> > > > > > Using yongari's ale(4) driver
> > > > > > http://people.freebsd.org/~yongari/ale/ale.20081114.tar.gz I did not
> > > > > > have any problems while I surf or download 37MB sourcecode from inet.
> > > > > > Then scp(1)'ing source from 1000H to desktop PC showed a transfer rate
> > > > > > with maximum 86kB/s regardless to which direction is copied. The
> > > > > > ethernet NIC, while copying, is switched off regularily then. No
> > > > > > copies possible after three megabytes.
> > > > >
> > > > > Try turning off TSO and let me know how it goes.
> > > > > ("#ifconfig ale0 -tso" will do the job.)
> > > > >
> > > >
> > > > this helps a little bit with two effects.
> > > > Copying source-tree with scp(1):
> > > > Now I can see transfers with up to approx. 500kB/s - inaccurate
> > > > measured with scp(1),
> > > > but relation counts.
> > > > Transfer stalles after different data volumes with DMA-error on tty0,
> > > > but networking
> > > > port is not turned off. This happens after 30-80MB data transfers.
> > > > You can restart the whole copy at once again.
> > > >
> > > > Copying source-tree with nc(1) tar-gzipped:
> > > > Transfer stops and starts with DMA-error every approx. 7MB with turning off NIC.
> > >
> > > I still can't reproduce this and I have no idea how to solve it
> > > even if I can reproduce that on my box. :-(
> > > There could be a wrong in DMA configuration or some mis-programmed
> > > registers but I still see no errors in these area.
> > >
> >
> > FYI: Fix committed to HEAD(r185577).
> >
> > --
> > Regards,
> > Pyun YongHyeon
>
> hello,
>
> with a fresh csup(1) from 19th of December nc(1) is working without any
> errors, now.
Thanks for testing.
> Thank you very much for your work.
You're welcome.
> BTW: Do you have any reading hints about developing FBSD drivers?
>
FreeBSD developers' handbook has valuable information for starters
but it lacks how to write a network device driver. Personally I
used to read other driver sources in tree and asked questions to
other developers.
--
Regards,
Pyun YongHyeon
More information about the freebsd-current
mailing list