From owner-freebsd-stable@freebsd.org Fri Nov 17 14:25:05 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 12416DDB7DD for ; Fri, 17 Nov 2017 14:25:05 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 C380568768 for ; Fri, 17 Nov 2017 14:25:04 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pf0-x230.google.com with SMTP id 17so2043535pfn.12 for ; Fri, 17 Nov 2017 06:25:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=8yLNKYfrI2g9vIlFExF4fb4MMchZcOOoMvl8nbIwpBQ=; b=vhElmIpBBd4eNIFdnVnGGODUcbigGvxFZ7NI3mBnFQOtsjHeMJ0wYoGKqGGaG46tHc Ju8HBjyCVOJdqSkclqVKP6HPTG0Z3Jy0y0ytSPmdetmp6GVeFgWoZSbDX80WmhiJ6+Z5 P3Qmq9l7YBJk9WFV1CcpV2lH0zkeQSv7ERPyHaNOLOXFNh0AVqKUoKf643cv6RntVHfI OT9KKy2VZKw48xsTicgibM/hrbMmql1DaFMxvYw0FnmAR/mRrvzosTpMN3Ax55YXMzFG deIx9+JZTnSL8R6LRctNyjyvHfYeTtc1HR3sklMIC7fCFrX2gE7asCsnu16gxUZuEoxg Nxrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=8yLNKYfrI2g9vIlFExF4fb4MMchZcOOoMvl8nbIwpBQ=; b=XRRjimQ5sVhBoW8kBHuGQFpXfnspm+VFqnHKdl8xe7qaj16y2EP8L8y970Nua8dxXU kEHAiRoNSTAoz1EZCE+20dJvz4lnjdN/aQN2eWi1oBhW5BMmZmRroFCaKz50RqAv6K/u LHdsKlrHSHpP7An1u7kI4/VKD+MtLMPOJPwFuRvSvbzWNGFOi75BXD9Xx2oOPVKBrQgO qbhyy7yUxeFIaNVKTHXja00fJanNGLUSCIx0w2hYy7zf1T5be3Flw7dgS+ZEkGbVJ9U0 bxEr1xGs8UxxVLBiFokl/XLcVrwqSfsQLuSh1K1fKRsGOsP90aJWp3IugOYyN50bfAEC 3htw== X-Gm-Message-State: AJaThX5HhjjjmcVFJIgj4UKYH5JeZZX2trZYTZOycJSmK/j0mBUThq6Y DLSVDVMpxA54QRW4WsLZIOxrwQ== X-Google-Smtp-Source: AGs4zMbB7wnMMvY2pv+7pe7t4dkF7pMagWXlXAfUTOyBUwa9vZTAjZr0V021v/PdUboQwYYysivLWA== X-Received: by 10.84.198.35 with SMTP id o32mr5407184pld.214.1510928704190; Fri, 17 Nov 2017 06:25:04 -0800 (PST) Received: from localhost ([116.46.79.128]) by smtp.gmail.com with ESMTPSA id 3sm8590948pfo.17.2017.11.17.06.25.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 06:25:03 -0800 (PST) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Fri, 17 Nov 2017 23:25:00 +0900 Date: Fri, 17 Nov 2017 23:25:00 +0900 To: Mike Black Cc: freebsd-stable Subject: Re: D-Link DGE530T issue Message-ID: <20171117142500.GA1076@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com References: <20171117101954.GA1246@michelle.fasterthan.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=EUC-KR Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i 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 14:25:05 -0000 On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote: > Hello > > VPD is > none0@pci0:5:1:0: class=0x020000 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=0x020000 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. > >