Date: Fri, 17 Nov 2017 22:08:00 +0300 From: Mike Black <amdmiek@gmail.com> To: pyunyh@gmail.com Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: D-Link DGE530T issue Message-ID: <CA%2BAz77MtfZFx%2BbrXZTx7Cat6uZdyfd%2BhEjBsn7J1iN-9fgKq8Q@mail.gmail.com> In-Reply-To: <20171117142500.GA1076@michelle.fasterthan.co.kr> References: <CA%2BAz77M35U1L-XiNeC63stkO-NLhi-U5VW2p88BBF9sQN%2BHUYA@mail.gmail.com> <CA%2BAz77Oi75A_m2DbWcwOV9g15Mt8nJyuffEcjE=5%2Bv5U38bOHA@mail.gmail.com> <20171117101954.GA1246@michelle.fasterthan.co.kr> <CA%2BAz77OAc=bDK0iAx%2BuDyn8CE%2BphMewu_RSJwdFELmAgAeb5wQ@mail.gmail.com> <20171117142500.GA1076@michelle.fasterthan.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
Seems that it's a really HW issue.
I plugged it into windows PC and it was OK. After that I placed it in
FreeBSD box and it feels OK
So I will keep an eye on it
none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011186 chip=3D0x4b01118=
6
rev=3D0x11 hdr=3D0x00
vendor =3D 'D-Link System Inc'
device =3D 'DGE-530T Gigabit Ethernet Adapter (rev 11)'
class =3D network
subclass =3D ethernet
bar [10] =3D type Memory, range 32, base 0xfebec000, size 16384, enab=
led
bar [14] =3D type I/O Port, range 32, base 0xe800, size 256, enabled
cap 01[48] =3D powerspec 2 supports D0 D1 D2 D3 current D3
cap 03[50] =3D VPD
VPD ident =3D 'DGE-530T Gigabit Ethernet Adapter'
VPD ro PN =3D 'DGE-530T'
VPD ro EC =3D 'Rev. 1.1'
VPD ro MN =3D 'D-Link'
VPD ro SN =3D 'DGE530T863B53'
VPD ro CP =3D ID 01 in map 0x50[0x3cc]
17 =D0=BD=D0=BE=D1=8F=D0=B1. 2017 =D0=B3. 5:25 PM =D0=BF=D0=BE=D0=BB=D1=8C=
=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "YongHyeon PYUN" <pyunyh@g=
mail.com>
=D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote:
> Hello
>
> VPD is
> none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086 chip=3D0x4b011=
086
> rev=3D0x11 hdr=3D0x00
> vendor =3D 'J. Bond Computer Systems'
> class =3D network
> subclass =3D ethernet
> bar [10] =3D type Memory, range 32, base 0xfebec000, size 16384,
enabled
> bar [14] =3D type I/O Port, range 32, base 0xee00, size 512, enable=
d
> cap 01[48] =3D powerspec 2 supports D0 D1 D2 D3 current D3
> cap 03[50] =3D VPD
> VPD ident =3D 'DGD-530T Ghgabht Ethernet @dapte'
^ ^ ^
As Boris said there are bit flipping errors. I think it's better
to find other NIC. Even if it work after adding this device's
vendor ID to sk(4) you may encounter silent data corruption in near
future.
>
> But I see... it says some DGD-530T... Do not know why, because it's
> DGE-530T for sure.
>
> So you're saying this it hardware degradation?
> I will try to find some windows host and plug it in there to check it.
>
> 2017-11-17 13:19 GMT+03:00 YongHyeon PYUN <pyunyh@gmail.com>:
>
> > On Fri, Nov 17, 2017 at 09:55:03AM +0300, Mike Black wrote:
> > > Hello. I looked into svn code for 8.3R and 11.1R and there seems no
> > changes
> > > in descriptors/identifiers. So I think that NIC is being wrongly
> > identified
> > > during startup process - it is being recognized with a wrong PCI VID.
How
> > > can this be checked or fixed?
> > > I use a loadable kernel module after a startup, so there is no useful
> > > messages during boot process.
> > >
> >
> > It seems it's single bit error but if it's dying there would no way
> > to get fixed. Given that pciconf(8) says VPD capability, try to
> > read it(i.e. pciconf -lcbvV). Generally VPD contains a readable
> > product string so you may be able to know whether there are other
> > errors. If vendor ID is the only corrupted one, you can simply
> > patch the device ID in the driver.
> >
> > > 15 =D0=BD=D0=BE=D1=8F=D0=B1. 2017 =D0=B3. 11:00 PM =D0=BF=D0=BE=D0=BB=
=D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Mike Black" <amdmie=
k@gmail.com
>
> > > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
> > >
> > > > Hello
> > > >
> > > > I've got old PCI NIC D-Link DGE530T Rev 11 with SysKonnect chip on
it.
> > > > Years ago it worked in FreeBSD 8/9 Stable with if_sk driver.
> > > >
> > > > Now I'm runnig
> > > > 11.1-STABLE FreeBSD 11.1-STABLE #1 r323214: Sat Nov 11 19:06:20 MSK
> > 2017
> > > > amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64
amd64
> > > > 1101502 1101502
> > > >
> > > > But recently I plugged this card back and it's not being recognized
by
> > a
> > > > driver.
> > > >
> > > > pciconf says that is
> > > > none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086
chip=3D0x4b011086
> > > > rev=3D0x11 hdr=3D0x00
> > > > vendor =3D 'J. Bond Computer Systems'
> > > > class =3D network
> > > > subclass =3D ethernet
> > > > bar [10] =3D type Memory, range 32, base 0xfebec000, size 163=
84,
> > > > enabled
> > > > bar [14] =3D type I/O Port, range 32, base 0xee00, size 512,
> > enabled
> > > > cap 01[48] =3D powerspec 2 supports D0 D1 D2 D3 current D3
> > > > cap 03[50] =3D VPD
> > > >
> > > > According /usr/share/misc/pci_vendors this D-link should have
4b011186
> > not
> > > > 4b011086.
> > > > I looked into driver code (if_sk) and it expects 1186 card also.
> > > > I googled about this issue but found no one similar in a recent
years
> > > > So I'd like to know what's wrong - some changes in driver in a
recent
> > > > years or smth going wrong while OS detecting this NIC. But that's
> > > > confusing, because this exact NIC worked years ago...
> > > >
> > > > --
> > > > amd_miek
> > > > Think different.
> > > > Just superior.
> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BAz77MtfZFx%2BbrXZTx7Cat6uZdyfd%2BhEjBsn7J1iN-9fgKq8Q>