Re: D-Link DGE530T issue

[Mike Black]

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=0x02 card=0x4b011186 chip=0x4b011186
rev=0x11 hdr=0x00
vendor = 'D-Link System Inc'
device = 'DGE-530T Gigabit Ethernet Adapter (rev 11)'
class  = network
subclass   = ethernet
bar   [10] = type Memory, range 32, base 0xfebec000, size 16384, enabled
bar   [14] = type I/O Port, range 32, base 0xe800, size 256, enabled
cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
cap 03[50] = VPD
VPD ident  = 'DGE-530T Gigabit Ethernet Adapter'
VPD ro PN  = 'DGE-530T'
VPD ro EC  = 'Rev. 1.1'
VPD ro MN  = 'D-Link'
VPD ro SN  = 'DGE530T863B53'
VPD ro CP  = ID 01 in map 0x50[0x3cc]


17 нояб. 2017 г. 5:25 PM пользователь "YongHyeon PYUN" 
написал:

On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote:
> Hello
>
> VPD is
> none0@pci0:5:1:0:   class=0x02 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
> vendor = 'J. Bond Computer Systems'
> class  = network
> subclass   = ethernet
> bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
enabled
> bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
> cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> cap 03[50] = VPD
> VPD ident  = '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 :
>
> > 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 нояб. 2017 г. 11:00 PM пользователь "Mike Black" 
> > > написал:
> > >
> > > > 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=0x02 card=0x4b011086
chip=0x4b011086
> > > > rev=0x11 hdr=0x00
> > > > vendor = 'J. Bond Computer Systems'
> > > > class  = network
> > > > subclass   = ethernet
> > > > bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
> > > > enabled
> > > > bar   [14] = type I/O Port, range 32, base 0xee00, size 512,
> > enabled
> > > > cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> > > > cap 03[50] = 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.
> >
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: D-Link DGE530T issue

[YongHyeon PYUN]

On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote:
> Hello
> 
> VPD is
> none0@pci0:5:1:0:   class=0x02 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
> vendor = 'J. Bond Computer Systems'
> class  = network
> subclass   = ethernet
> bar   [10] = type Memory, range 32, base 0xfebec000, size 16384, enabled
> bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
> cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> cap 03[50] = VPD
> VPD ident  = '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 :
> 
> > 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 戟棘�뤢�. 2017 均. 11:00 PM 極棘剋�뚍론압꽥겉궿둔뿌� "Mike Black" 
> > > 戟逵極龜�곍겆�:
> > >
> > > > 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=0x02 card=0x4b011086 chip=0x4b011086
> > > > rev=0x11 hdr=0x00
> > > > vendor = 'J. Bond Computer Systems'
> > > > class  = network
> > > > subclass   = ethernet
> > > > bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
> > > > enabled
> > > > bar   [14] = type I/O Port, range 32, base 0xee00, size 512,
> > enabled
> > > > cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> > > > cap 03[50] = 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.
> >
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: D-Link DGE530T issue

[Arrigo Marchiori via freebsd-stable]

Hello,

On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote:

> Hello
> 
> VPD is
> none0@pci0:5:1:0:   class=0x02 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
> vendor = 'J. Bond Computer Systems'

IMHO this is either a joke, or a reference to a company in California
that seems to have not produced much for 10 years (I just googled its
name).

I would speculate it is a sort of inside joke from D-Link engineers,
for a chip intended for development, that was inadvertently mounted on
a board for resale.

This would explain the other strange bits.

> subclass   = ethernet
> bar   [10] = type Memory, range 32, base 0xfebec000, size 16384, enabled
> bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
> cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> cap 03[50] = VPD
> VPD ident  = '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 :
> 
> > 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 нояб. 2017 г. 11:00 PM пользователь "Mike Black" 
> > > написал:
> > >
> > > > 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=0x02 card=0x4b011086 chip=0x4b011086
> > > > rev=0x11 hdr=0x00
> > > > vendor = 'J. Bond Computer Systems'
> > > > class  = network
> > > > subclass   = ethernet
> > > > bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
> > > > enabled
> > > > bar   [14] = type I/O Port, range 32, base 0xee00, size 512,
> > enabled
> > > > cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> > > > cap 03[50] = 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.
> >
> 
> 
> 
> -- 
> amd_miek
> Think different.
> Just superior.

-- 
rigo

http://rigo.altervista.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: D-Link DGE530T issue

[Boris Samorodov]

17.11.2017 15:12, Mike Black пишет:

> VPD ident  = 'DGD-530T Ghgabht Ethernet @dapte'

So here we are (off by minus one errors):
---
D (44h) should be G (45h);
h (68h) -> i (69h);
@ (40h) -> A (41h).
---

And deltas in bytes between errors: 8, 4, 12.

Yep, looks like a hardware/power problem. Can you try to change
a power supply?

-- 
WBR, bsam
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: D-Link DGE530T issue

[Mike Black]

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:  on pcib3
pci1:  at device 0.0 (no driver attached)
skc0:  port 0xc800-0xc8ff mem
0xdfdfc000-0xdfdf irq 21 at device 1.0 on pci1
skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9)
sk0:  on skc0
sk0: Ethernet address: 00:19:5b:86:3b:53
miibus1:  on sk0
e1000phy0:  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  diablo kernel: pcib5:  at
device 30.0 on pci0
Nov 11 18:04:37  diablo kernel: pci5:  on pcib5
Nov 11 18:04:37  diablo kernel: pci5:  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=0x02 card=0x4b011186 chip=0x4b011186
rev=0x11 hdr=0x00
vendor = 'D-Link System Inc'
device = 'DGE-530T Gigabit Ethernet Adapter (rev 11)'
class  = network
subclass   = ethernet
bar   [10] = type Memory, range 32, base 0xdfdfc000, size 16384, enabled
bar   [14] = type I/O Port, range 32, base 0xc800, size 256, enabled
cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D0
cap 03[50] = 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 :

> Hello
>
> VPD is
> none0@pci0:5:1:0:   class=0x02 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
> vendor = 'J. Bond Computer Systems'
> class  = network
> subclass   = ethernet
> bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
> enabled
> bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
> cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> cap 03[50] = VPD
> VPD ident  = '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 :
>
>> 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 нояб. 2017 г. 11:00 PM пользователь "Mike Black" 
>> > написал:
>> >
>> > > 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=0x02 card=0x4b011086
>> chip=0x4b011086
>> > > rev=0x11 hdr=0x00
>> > > vendor = 'J. Bond Computer Systems'
>> > > class  = network
>> > > subclass   = ethernet
>> > > bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
>> > > enabled
>> > > bar   [14] = type I/O Port, range 32, base 0xee00, size 512,
>> enabled
>> > > cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
>> > > cap 03[50] = 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
>> > > 

Re: D-Link DGE530T issue

[Mike Black]

Hello

VPD is
none0@pci0:5:1:0:   class=0x02 card=0x4b011086 chip=0x4b011086
rev=0x11 hdr=0x00
vendor = 'J. Bond Computer Systems'
class  = network
subclass   = ethernet
bar   [10] = type Memory, range 32, base 0xfebec000, size 16384, enabled
bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
cap 03[50] = VPD
VPD ident  = '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 :

> 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 нояб. 2017 г. 11:00 PM пользователь "Mike Black" 
> > написал:
> >
> > > 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=0x02 card=0x4b011086 chip=0x4b011086
> > > rev=0x11 hdr=0x00
> > > vendor = 'J. Bond Computer Systems'
> > > class  = network
> > > subclass   = ethernet
> > > bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
> > > enabled
> > > bar   [14] = type I/O Port, range 32, base 0xee00, size 512,
> enabled
> > > cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> > > cap 03[50] = 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.
>



-- 
amd_miek
Think different.
Just superior.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: D-Link DGE530T issue

[YongHyeon PYUN]

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 戟棘�뤢�. 2017 均. 11:00 PM 極棘剋�뚍론압꽥겉궿둔뿌� "Mike Black" 
> 戟逵極龜�곍겆�:
> 
> > 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=0x02 card=0x4b011086 chip=0x4b011086
> > rev=0x11 hdr=0x00
> > vendor = 'J. Bond Computer Systems'
> > class  = network
> > subclass   = ethernet
> > bar   [10] = type Memory, range 32, base 0xfebec000, size 16384,
> > enabled
> > bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
> > cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
> > cap 03[50] = 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.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: iscsi target and VMware/esxi timeouts -- SOLVED

[Daniel Braniss]

> On 14 Nov 2017, at 11:28, Patrick M. Hausen  wrote:
> 
> Hello,
> 
>> Am 14.11.2017 um 10:08 schrieb Daniel Braniss :
>> 
>> Hi,
>> we are experimenting issues with several esxi’s servers that use freebsd 
>> 10.2 stable as a iscsi target.
>> ie:
>> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 
>> (iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 
>> seconds; dropping connection
>> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.201 
>> (iqn.1998-01.com.vmware:pe-02-2fa7cd9e): no ping reply (NOP-Out) after 5 
>> seconds; dropping connection
>> Nov 11 17:58:16 store-07 kernel: WARNING: 132.65.11.205 
>> (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 
>> seconds; dropping connection
>> Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.203 
>> (iqn.1998-01.com.vmware:pe-13-60e87d06): no ping reply (NOP-Out) after 5 
>> seconds; dropping connection
>> Nov 11 17:58:17 store-07 kernel: WARNING: 132.65.11.205 
>> (iqn.1998-01.com.vmware:pe-03-13e8b52d): no ping reply (NOP-Out) after 5 
>> seconds; dropping connection
>> 
>> these are 3 different esxis that almost at the same time the target looses 
>> connection to the initiators.
>> at the moment most ‘clients’  recover from the scsi error, but older 
>> freebsds don’t.
>> 
>> in any case, increasing the timeout is not helping.
>> 
>> any clues are welcome :-)
>> 
>> over the weekend i’m planning to upgrade the target to 11.1 and take for the 
>> hills.
> 
> Are you using istgt or ctld?
> 
> We have did experience similar occasional problems with the former
> but never with the latter.
> 
> Patrick

the iscsi initiator of the esxi’s (VMware) does answer to NOP’s once in a blue 
moon!
this was checked by sniffing the network.

setting kern.cam.ctl.iscsi.ping_timeout=0 solved this.

thanks,
danny


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"