Date: Mon, 30 Oct 2006 08:50:31 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: pyunyh@gmail.com Cc: freebsd-current@FreeBSD.org, Philip Paeps <philip@FreeBSD.org> Subject: Re: Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers. Message-ID: <4545AEC7.2080205@zedat.fu-berlin.de> In-Reply-To: <20061030044121.GB51632@cdnetworks.co.kr> References: <20060926002916.GA5975@cdnetworks.co.kr> <4833C999-9C20-4C40-814F-214BCE90494E@tamu.edu> <20061029213433.GB1106@fasolt.home.paeps.cx> <20061030044121.GB51632@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
Pyun YongHyeon wrote: > On Sun, Oct 29, 2006 at 10:34:33PM +0100, Philip Paeps wrote: > > The driver seems to work for me, but only when I put it in the kernel proper. > > If I try to load it as a module, it gives ENOMEM when trying bus_dmamem_alloc() > > for the jumbo buf (line 2177 of if_msk.c). > > > > If there is no cotiguous DMA memory requried by the driver you have > to reboot to get it. Alternatively, you can put the driver in the > kernel instead of using kernel module as you mentioned. > > > Two things I'm curious about: > > > > msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > options=9a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> > > inet6 fe80::211:11ff:fe59:1333%msk0 prefixlen 64 scopeid 0x1 > > inet 172.16.1.2 netmask 0xffffff00 broadcast 172.16.1.255 > > inet6 2001:6f8:32f:10:211:11ff:fe59:1333 prefixlen 64 autoconf > > ether 00:11:11:59:13:33 > > media: Ethernet autoselect (100baseTX <full-duplex,flag0,flag1>) > > status: active > > > > What are flag0 and flag1 in the media: line? > > > > AFAIK there is no official way to indicate negotiated Rx/Tx > flow-control status in ifconfig(8). So I used flag0 to indicate > Rx flow-control and flag1 to denote Tx flow-control. It just means > the driver will flow-control(Rx, Tx) with its link-partner(usually > switch). > > > The kernel also prints "mskc0: Uncorrectable PCI Express error" after bringing > > the interface up. It doesn't seem to cause any harm, but it feels fishy. I > > haven't looked at the source for this. > > > > You can safely ignore the error message unless the error shows > endlessly. > Is this driver also gonna be used in STABLE/6.2? Regards, Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4545AEC7.2080205>