Date: Fri, 17 Nov 2017 16:00:30 +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%2BAz77MfWq1_Um5w=jO==Vmi2zsWa0ZqAryFyC%2BefH7KGcjHBA@mail.gmail.com> In-Reply-To: <CA%2BAz77OAc=bDK0iAx%2BuDyn8CE%2BphMewu_RSJwdFELmAgAeb5wQ@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello again
PCI slot is 100% working, I just got another D-LINK PCI card (different
Chip, different driver) out of there that was working OK.
I spend some time and found this - some bootlog with exact this card. But I
think it does not really contain any useful information.
It was FreeBSD 9.1-STABLE #0 r246597M: Sun Feb 10 00:10:59 MSK 2013
pci1: <ACPI PCI bus> on pcib3
pci1: <network, ethernet> at device 0.0 (no driver attached)
skc0: <D-Link DGE-530T Gigabit Ethernet> port 0xc800-0xc8ff mem
0xdfdfc000-0xdfdfffff irq 21 at device 1.0 on pci1
skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:19:5b:86:3b:53
miibus1: <MII bus> on sk0
e1000phy0: <Marvell 88E1011 Gigabit PHY> PHY 0 on miibus1
e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
There was a different hardware, but NIC is the same, it was lying for years
until now.
Now in boot log there's only
Nov 11 18:04:37 <kern.crit> diablo kernel: pcib5: <ACPI PCI-PCI bridge> at
device 30.0 on pci0
Nov 11 18:04:37 <kern.crit> diablo kernel: pci5: <ACPI PCI bus> on pcib5
Nov 11 18:04:37 <kern.crit> diablo kernel: pci5: <network, ethernet> at
device 1.0 (no driver attached)
And that's not really helping.
And finally I found a pciconf from this exact NIC
skc0@pci0:1: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 0xdfdfc000, size 16384, enab=
led
bar [14] =3D type I/O Port, range 32, base 0xc800, size 256, enabled
cap 01[48] =3D powerspec 2 supports D0 D1 D2 D3 current D0
cap 03[50] =3D VPD
Do not know what version of FreeBSD is always was stable and the date was
02.2013, no VPD
2017-11-17 15:12 GMT+03:00 Mike Black <amdmiek@gmail.com>:
> 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'
>
> 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 i=
t.
>> > > 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 amd6=
4
>> > > 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 1638=
4,
>> > > 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 year=
s
>> > > So I'd like to know what's wrong - some changes in driver in a recen=
t
>> > > 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.
>>
>
>
>
> --
> amd_miek
> Think different.
> Just superior.
>
--=20
amd_miek
Think different.
Just superior.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BAz77MfWq1_Um5w=jO==Vmi2zsWa0ZqAryFyC%2BefH7KGcjHBA>