From owner-freebsd-stable@freebsd.org Fri Nov 17 19:08:02 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C683DE11C0 for ; Fri, 17 Nov 2017 19:08:02 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E714971994 for ; Fri, 17 Nov 2017 19:08:01 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: by mail-io0-x233.google.com with SMTP id v21so9797856ioi.4 for ; Fri, 17 Nov 2017 11:08:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UArEmCT6kpTEkAqMl1OtKP5aloZWaOqmxBwbwdN/2UQ=; b=m5Esw+uWjscel6cevw+VB9CzOY9UEMM0nAhvaiMb5ZpgIAtd5REirIxNNCrhONoD/u B2GV1Kpk1D7Kvhuv1SxP9Tb1hFl0gklBBpVPnaNVkSJjMrqEhkL1GEO9p2Obx46u3jeJ 5QG9g0GabpYMA/ztQ/55a7ClzeMTxdO0/pEzsv1bvtt+MlltrpI97RNTbEdvJDhqScwi RcHZE21Rmn/fKR4kXPhpbM19j5ihyedDeE7XXnURdBIXMSDU1iv7wxXly0ie3aRhdmPZ VQWtQI8NENKhTsxns2TI4GN56tFj7HicvrVAjem79at1aoFlL3B6nwKbCgxajWCkKion KVig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UArEmCT6kpTEkAqMl1OtKP5aloZWaOqmxBwbwdN/2UQ=; b=r4k8z3rm8sr3X94sHUlEsSV/n5DNE8i/7CwYYFo+V01qrtgcJBozLgAx2NuDbwpjZo H9l/vyOF5ageQujzj3V9cEypsq1v0mnlOTcZekHBLDXKgkoV0viIDdWP08kHiWC27ZzL 0GEZ7AZ1pmWin5+k5v5EdEyGuBKQULOgzasOjNe/Wx2ycx/wEnf28wQN5mEsaN2e3JoJ mQ/TLqGeQUHKVCo4snERItz87wR2fdPbEmw+pi7Ce1At/EyJyRyGENpyfwONaTE2DKlt uzEVN/xFUarnLMLUqJ4IFNRPftaqsHzM7oNPPKpW01I+JPkulUH0x2jyD0h6X1C/aorR Oodg== X-Gm-Message-State: AJaThX5N+j3dbHY/KXYD5VuaBxQb/CIiejq4VF2Z68uHXDMN7qD/CH2G 5tFwwwXHpsbg0QYIbGvccCNtEZsLgmkcmxkjWFYO8A== X-Google-Smtp-Source: AGs4zMZEaM9ZBGBnjOuSpHq40AIbV6KiXquiZWllw9/FSri8k53uCWT/+cHa9yYxW5ATb7AY7Kf92dkgNn6oqvy/yWM= X-Received: by 10.107.107.21 with SMTP id g21mr3950623ioc.101.1510945680517; Fri, 17 Nov 2017 11:08:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.9.200 with HTTP; Fri, 17 Nov 2017 11:08:00 -0800 (PST) In-Reply-To: <20171117142500.GA1076@michelle.fasterthan.co.kr> References: <20171117101954.GA1246@michelle.fasterthan.co.kr> <20171117142500.GA1076@michelle.fasterthan.co.kr> From: Mike Black Date: Fri, 17 Nov 2017 22:08:00 +0300 Message-ID: Subject: Re: D-Link DGE530T issue To: pyunyh@gmail.com Cc: freebsd-stable Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2017 19:08:02 -0000 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" =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 : > > > 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" > > > =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. > >