From owner-freebsd-stable@freebsd.org Mon Nov 13 04:59:59 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 10BBCCFF0BC for ; Mon, 13 Nov 2017 04:59:59 +0000 (UTC) (envelope-from walterp@gmail.com) Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 B4B091AC6 for ; Mon, 13 Nov 2017 04:59:58 +0000 (UTC) (envelope-from walterp@gmail.com) Received: by mail-qt0-x22a.google.com with SMTP id p44so7701072qtj.6 for ; Sun, 12 Nov 2017 20:59:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=eog5UpIDOiYBpuLdIEsX6I8PAYtSUVIE9IEtsPTc2nE=; b=hoQEYbR4jFFsDJRhs2Xw6/YV1lD6N6MEfJzAYg+CSpnCoNR9R4fCvcNB43NOjZDFqn kMDSPAmGAfveBJExNEDJs4fKe6hlAYUIOHe6AkMPB67GdnNnbUB+QUbFmdMSZPzekALM gdrNoeSqGTwh1eRw05aMnT/1118/dN/Q242UAsupg42+HY64tsoCiAdwW16GxYtvYvAQ UYUVAo2U0o4o1HkbTsf6HKN1BGQJ8qpv6pekt6Ln1fZZ/5VNGJ8NPpFgwC0hVh2RMTEy YCRPohp1H1+8XOKxTpsKVFRe3OdnVEYAvuXHqjlT/IbsESaB52mQjeM4jkPmKKcedr1Y 9fiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=eog5UpIDOiYBpuLdIEsX6I8PAYtSUVIE9IEtsPTc2nE=; b=lqVmXUmgSq6oR7ETb2r9FaY8aa3k8FiP3ugy+NeMV8A7HE4PJnjNGBrN00y5q5DrGJ IUv5Cc9LxzibObrYGtRwMEb1RHq8409LoykdPVeJGNQM7fIgdwypqqM4Jj4HtujX28vy yqCdWDFUREFhkN6j2t5SXcV0Ps1tB8ydLhZgK5SOdRnmQgEQLlkEtisukVTtS6Ldnh2Q JMOWTeG9nDhLfy5bAJWxZjrBXG/CgGgIv3YgwyWDWWjx4sxZqlyDhL8dffnYILXaCztJ GTh5TSg1iwPj3uVqMKiS+Uo835+YrsbcaD4WrAeIXNsfhrgUz+Oa9yxnXn32inLdophH zHEw== X-Gm-Message-State: AJaThX4XY8d4Qd51IpggP9LjCMric3f10BBn2M99gXRLuiUZEvbeccka bHNNKF8LI/XMq7n6RFIgKS0VHC/ZRkjRoNngixA= X-Google-Smtp-Source: AGs4zMaBWzu+MjHlADCpFcEiGGseF2iqt9MAimi7BQ4lwpaM2MZVK4jx4Q8qdH9XtU/cZUMlEGHiKSaszKc31qzqFa8= X-Received: by 10.200.22.209 with SMTP id y17mr7864502qtk.284.1510549197685; Sun, 12 Nov 2017 20:59:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.154.68 with HTTP; Sun, 12 Nov 2017 20:59:57 -0800 (PST) From: Walter Parker Date: Sun, 12 Nov 2017 20:59:57 -0800 Message-ID: Subject: GPT partition gets erased on boot To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Mon, 13 Nov 2017 04:59:59 -0000 Hi, I'm setting up an old Sunfire X4140 system with 4 SAS drives plugged into the SUN STK controller. Each drive is configured as a separate device. I ran the FreeBSD 11.1 installer and picked guided ZFS install where I selected RAID10 (2 2way mirrors) using aacd0, aacd1, aacd2, and aacd3. It installed the system and rebooted. When the new system came up, zpool status complained that aacd0p3 was unavailable. Looking at /dev, I noticed that the only dev file was aacd0 (aacd0p* were all missing). Using gpart on aacd0 it said there was no geom. I was able to run gpart create to recreate the drive geom and then gpart add to readd all of the partitions. After recreating aacd0p3, I was even able to run zpool replace -f zroot /dev/aacd0p3 and the pool resilvered and stopped complaining. On the next boot, aacd0 was missing all of its partitions. What would cause the partitions on a ZFS drive to disappear? Thank you, Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis From owner-freebsd-stable@freebsd.org Mon Nov 13 10:31:43 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 28157D7F77A for ; Mon, 13 Nov 2017 10:31:43 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C692D68CC4 for ; Mon, 13 Nov 2017 10:31:41 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [194.32.164.27] ([194.32.164.27]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id vADAVYj2085940; Mon, 13 Nov 2017 10:31:34 GMT (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: GPT partition gets erased on boot From: Bob Bishop In-Reply-To: Date: Mon, 13 Nov 2017 10:31:32 +0000 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4DBDE77E-3847-4966-BDBD-53CD8C6A7754@gid.co.uk> References: To: Walter Parker X-Mailer: Apple Mail (2.3273) 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: Mon, 13 Nov 2017 10:31:43 -0000 Hi, > On 13 Nov 2017, at 04:59, Walter Parker wrote: >=20 > Hi, >=20 > I'm setting up an old Sunfire X4140 system with 4 SAS drives plugged = into > the SUN STK controller. Each drive is configured as a separate device. >=20 > I ran the FreeBSD 11.1 installer and picked guided ZFS install where I > selected RAID10 (2 2way mirrors) using aacd0, aacd1, aacd2, and aacd3. = It > installed the system and rebooted. >=20 > When the new system came up, zpool status complained that aacd0p3 was > unavailable. Looking at /dev, I noticed that the only dev file was = aacd0 > (aacd0p* were all missing). Using gpart on aacd0 it said there was no = geom. > I was able to run gpart create to recreate the drive geom and then = gpart > add to readd all of the partitions. After recreating aacd0p3, I was = even > able to run zpool replace -f zroot /dev/aacd0p3 and the pool = resilvered and > stopped complaining. >=20 > On the next boot, aacd0 was missing all of its partitions. >=20 > What would cause the partitions on a ZFS drive to disappear? At a guess, the controller is writing its metadata to the disk and = trampling on the gpart data. > Thank you, >=20 >=20 > Walter >=20 > --=20 > The greatest dangers to liberty lurk in insidious encroachment by men = of > zeal, well-meaning but without understanding. -- Justice Louis D. = Brandeis > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >=20 -- Bob Bishop rb@gid.co.uk From owner-freebsd-stable@freebsd.org Mon Nov 13 16:55: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 451E8DBF190 for ; Mon, 13 Nov 2017 16:55:02 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from oceanview.tundraware.com (oceanview.tundraware.com [45.55.60.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailman.tundraware.com", Issuer "mailman.tundraware.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A1A174DEA for ; Mon, 13 Nov 2017 16:55:01 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (ozzie.tundraware.com [75.145.138.73]) (authenticated bits=0) by oceanview.tundraware.com (8.15.2/8.15.2) with ESMTPSA id vADGspFT026340 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 13 Nov 2017 10:54:52 -0600 (CST) (envelope-from tundra@tundraware.com) Subject: Re: GPT partition gets erased on boot To: Walter Parker , freebsd-stable@freebsd.org References: From: Tim Daneliuk Message-ID: <270670c0-d632-7488-6e16-5f9a11834191@tundraware.com> Date: Mon, 13 Nov 2017 10:54:46 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (oceanview.tundraware.com [45.55.60.57]); Mon, 13 Nov 2017 10:54:52 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: vADGspFT026340 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-0.894, required 1, autolearn=not spam, ALL_TRUSTED -1.00, AWL 0.11, RP_MATCHES_RCVD -0.00) X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No 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: Mon, 13 Nov 2017 16:55:02 -0000 On 11/12/2017 10:59 PM, Walter Parker wrote: > What would cause the partitions on a ZFS drive to disappear? In no particular order, these leap to mind: - A bad drive - A misconfigured controller - A dead backup battery on the controller -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-stable@freebsd.org Mon Nov 13 17:29:04 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 BDACADBFC91 for ; Mon, 13 Nov 2017 17:29:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ABD7175F2F for ; Mon, 13 Nov 2017 17:29:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vADHT2do071142 for ; Mon, 13 Nov 2017 17:29:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221146] [ixgbe] Problem with second laggport Date: Mon, 13 Nov 2017 17:29:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cramerj@intel.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Mon, 13 Nov 2017 17:29:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 Jeb Cramer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cramerj@intel.com --- Comment #20 from Jeb Cramer --- (In reply to Sean Bruno from comment #19) I'm not saying it won't help, but it also opens the door for the reasons we moved it to the beginning of attach() in the first place. The firmware ten= ds to not honor the synchronization bits until the driver has taken over (via = the DRV_LOAD bit). --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Mon Nov 13 18:49:45 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 44AB1DC13F5 for ; Mon, 13 Nov 2017 18:49:45 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 F0D88785F6 for ; Mon, 13 Nov 2017 18:49:44 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-qk0-x22d.google.com with SMTP id p7so21002709qkd.7 for ; Mon, 13 Nov 2017 10:49:44 -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=fTMtX4Thj1CDfYNsdIZQF60N4/dOgvE4TozmGMufwBU=; b=R0179afSxyCqE6gaoGEentyr0L2Tnd9C2KU3HnxwG3F7bCNoCcWKLtHl79r1BaIWGU VFDu7liv7qY6b4O067l9CU87rZ8tJQ2VaGqECxXdymFjAPeIkRhIo/f5699dt/UsrYhL ubf8CKrWtmCqtNty20eDa8ZB5+1mFFoKTGq+RnTMsufROFrVb/S7Ik2wDcQUc64Cqvj3 Qgvz7NZCqRphdZNI7EUNdiIJYVTIcIHbfkZyRINqanh/5lpCFE81cWy80an3fHUGnw8/ ilmexfO3//gLEtZ8SGHJIP4NTBKcKP3g0TUeJVILTXzfZPT/zt+u/e2Q10WhVHdrd6++ XUAw== 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=fTMtX4Thj1CDfYNsdIZQF60N4/dOgvE4TozmGMufwBU=; b=ENENmK05uPEQsq9eavuMUC6RzyPwPnj5SHq5ENzA5Ou5OJkzpV7Uqx6PyG5CTydkYt g8XycIhTZ1R7P8xIZVGup00r6QRDFA2fqmZf6Hh+cbrlFPOj2DsUjlIaQIddINta7a7x mB3l6uf3FdN0sQOevm8yI/6myGJzfUj08QwITixdmUN4jLsljohn49mIXSyVipT4A7nK ZQjH0fQ7BdZWDLkrrdfrQY2HAv4aI4dT7arrZYL3y4lEvf2Xsj40NLxAoZeuylGl8Vxh BjZojTjjKmHjZGa4Vcx2RA14QIu1X97sddiRznxuUQYsNyZ7bub33uPmJyQfnMV5Aapo gEOA== X-Gm-Message-State: AJaThX6JBXOw2td5jr9p3FVTyQ9XZfQfSDzlnF22HYklnp2puD0irN+0 dN8Gf7MF3y7jM48RiGp37WznO7UgbKPl9etEfOE= X-Google-Smtp-Source: AGs4zMZCyWcXlcflsywD8qKpNadZs9IkV0XR8TpuQKzqX6kx0yc3MS8ukWNEyzVOFCUMf57ItFXl1NGzUK4Yl0X/JDo= X-Received: by 10.55.94.65 with SMTP id s62mr14698310qkb.282.1510598984126; Mon, 13 Nov 2017 10:49:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.20.65 with HTTP; Mon, 13 Nov 2017 10:49:43 -0800 (PST) Received: by 10.140.20.65 with HTTP; Mon, 13 Nov 2017 10:49:43 -0800 (PST) In-Reply-To: <270670c0-d632-7488-6e16-5f9a11834191@tundraware.com> References: <270670c0-d632-7488-6e16-5f9a11834191@tundraware.com> From: krad Date: Mon, 13 Nov 2017 18:49:43 +0000 Message-ID: Subject: Re: GPT partition gets erased on boot To: Tim Daneliuk Cc: Walter Parker , freebsd-stable Content-Type: text/plain; charset="UTF-8" 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: Mon, 13 Nov 2017 18:49:45 -0000 I have a vague memory of these controllers doing something odd with the end of the volume but can't remember where or when, but I know I would generally avoid them. It looks like you are using them in jbod mode, but if you aren't do so. If you can reflash them to hba mode even better. If you are stuck it as it is, it's probably with trying to partition them with a Linux live CD or illumiinos to eliminate freebsd issues. On 13 Nov 2017 16:55, "Tim Daneliuk" wrote: > On 11/12/2017 10:59 PM, Walter Parker wrote: > > What would cause the partitions on a ZFS drive to disappear? > > In no particular order, these leap to mind: > > - A bad drive > - A misconfigured controller > - A dead backup battery on the controller > > -- > ------------------------------------------------------------ > ---------------- > Tim Daneliuk tundra@tundraware.com > PGP Key: http://www.tundraware.com/PGP/ > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Mon Nov 13 18:58:22 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 F0EF2DC17D9 for ; Mon, 13 Nov 2017 18:58:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DEE4E78C94 for ; Mon, 13 Nov 2017 18:58:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vADIwMFu018531 for ; Mon, 13 Nov 2017 18:58:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221146] [ixgbe] Problem with second laggport Date: Mon, 13 Nov 2017 18:58:23 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sbruno@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Mon, 13 Nov 2017 18:58:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 --- Comment #21 from Sean Bruno --- (In reply to Jeb Cramer from comment #20) Until I get confirmation from a failure case, I'm not going to do anything = with this at this time. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Tue Nov 14 01:46:29 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 70B20C7C12A for ; Tue, 14 Nov 2017 01:46:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57DB066CB1 for ; Tue, 14 Nov 2017 01:46:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAE1kRlt073297 for ; Tue, 14 Nov 2017 01:46:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221146] [ixgbe] Problem with second laggport Date: Tue, 14 Nov 2017 01:46:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: IntelNetworking, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Tue, 14 Nov 2017 01:46:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |IntelNetworking --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Tue Nov 14 09:09:08 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 2565DDB8980 for ; Tue, 14 Nov 2017 09:09:08 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 131C276190 for ; Tue, 14 Nov 2017 09:09:08 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 125AFDB897F; Tue, 14 Nov 2017 09:09:08 +0000 (UTC) Delivered-To: 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 10167DB897E; Tue, 14 Nov 2017 09:09:08 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C05137618F; Tue, 14 Nov 2017 09:09:07 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1eEXDD-000O9b-U4; Tue, 14 Nov 2017 11:08:55 +0200 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: iscsi target and VMware/esxi timeouts Message-Id: <7779629C-A1E5-4E96-B660-A0FAD231468C@cs.huji.ac.il> Date: Tue, 14 Nov 2017 11:08:55 +0200 Cc: stable@freebsd.org To: Freebsd hackers list , =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-Mailer: Apple Mail (2.3445.4.7) 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: Tue, 14 Nov 2017 09:09:08 -0000 Hi, we are experimenting issues with several esxi=E2=80=99s 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 =E2=80=98clients=E2=80=99 recover from the scsi = error, but older freebsds don=E2=80=99t. in any case, increasing the timeout is not helping. any clues are welcome :-) over the weekend i=E2=80=99m planning to upgrade the target to 11.1 and = take for the hills. danny From owner-freebsd-stable@freebsd.org Tue Nov 14 09:28:35 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 67DCADB90A2 for ; Tue, 14 Nov 2017 09:28:35 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 529E376ADD for ; Tue, 14 Nov 2017 09:28:35 +0000 (UTC) (envelope-from hausen@punkt.de) Received: by mailman.ysv.freebsd.org (Postfix) id 51EADDB90A1; Tue, 14 Nov 2017 09:28:35 +0000 (UTC) Delivered-To: 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 4F8F1DB90A0; Tue, 14 Nov 2017 09:28:35 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD38C76ADC; Tue, 14 Nov 2017 09:28:34 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id vAE9S8pt030303; Tue, 14 Nov 2017 10:28:08 +0100 (CET) Received: from [217.29.44.234] ([217.29.44.234]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id vAE9S8LS059259; Tue, 14 Nov 2017 10:28:08 +0100 (CET) (envelope-from hausen@punkt.de) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: iscsi target and VMware/esxi timeouts From: "Patrick M. Hausen" In-Reply-To: <7779629C-A1E5-4E96-B660-A0FAD231468C@cs.huji.ac.il> Date: Tue, 14 Nov 2017 10:28:07 +0100 Cc: Freebsd hackers list , =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= , stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6B1A4A67-D0E9-4A73-B690-60A52D144F81@punkt.de> References: <7779629C-A1E5-4E96-B660-A0FAD231468C@cs.huji.ac.il> To: Daniel Braniss X-Mailer: Apple Mail (2.3273) 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: Tue, 14 Nov 2017 09:28:35 -0000 Hello, > Am 14.11.2017 um 10:08 schrieb Daniel Braniss : >=20 > Hi, > we are experimenting issues with several esxi=E2=80=99s 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 >=20 > these are 3 different esxis that almost at the same time the target = looses connection to the initiators. > at the moment most =E2=80=98clients=E2=80=99 recover from the scsi = error, but older freebsds don=E2=80=99t. >=20 > in any case, increasing the timeout is not helping. >=20 > any clues are welcome :-) >=20 > over the weekend i=E2=80=99m 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 --=20 punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling From owner-freebsd-stable@freebsd.org Wed Nov 15 01:53: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 7548FDBC394 for ; Wed, 15 Nov 2017 01:53:02 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id EB8E279231 for ; Wed, 15 Nov 2017 01:53:01 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 38076 invoked by uid 907); 15 Nov 2017 01:53:00 -0000 Received: from Unknown (HELO jmmacpro.tmst.com.au) (203.14.245.130) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA; Wed, 15 Nov 2017 12:53:00 +1100 From: Jan Mikkelsen Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: Panic in unionfs "it is not a unionfs-vnode" Date: Wed, 15 Nov 2017 12:52:58 +1100 References: <06DF69C5-884F-4483-8AF7-2013F4E868D1@transactionware.com> To: FreeBSD Stable Maling List In-Reply-To: <06DF69C5-884F-4483-8AF7-2013F4E868D1@transactionware.com> Message-Id: <1F01FF1D-AC5E-41B5-9134-7E81ED8E60D7@transactionware.com> X-Mailer: Apple Mail (2.3445.4.7) 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: Wed, 15 Nov 2017 01:53:02 -0000 Oops, wrong list. I just resent to freebsd-current. > On 15 Nov 2017, at 12:48, Jan Mikkelsen = wrote: >=20 > Hi, >=20 > I got the panic below in unionfs. Head as at 325569, 2017-11-09 = 12:41:00 +1100 (Thu, 09 Nov 2017). >=20 > This is a ufs filesystem union mounted on top of a read-only ufs /etc. = I know unionfs has "architecture issues=E2=80=9D. Is this resolvable?=20 >=20 > panic: unionfs: it is not unionfs-vnode > cpuid =3D 5 > time =3D 1510678800 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame = 0xfffffe02c418c280 > vpanic() at vpanic+0x19c/frame 0xfffffe02c418c300 > kassert_panic() at kassert_panic+0x126/frame 0xfffffe02c418c370 > unionfs_lock() at unionfs_lock+0x635/frame 0xfffffe02c418c400 > VOP_LOCK1_APV() at VOP_LOCK1_APV+0xd9/frame 0xfffffe02c418c430 > _vn_lock() at _vn_lock+0x66/frame 0xfffffe02c418c4a0 > vget() at vget+0x82/frame 0xfffffe02c418c4e0 > cache_lookup() at cache_lookup+0x787/frame 0xfffffe02c418c5c0 > vfs_cache_lookup() at vfs_cache_lookup+0xac/frame 0xfffffe02c418c620 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xd3/frame 0xfffffe02c418c650 > lookup() at lookup+0x682/frame 0xfffffe02c418c6f0 > namei() at namei+0x51a/frame 0xfffffe02c418c7b0 > kern_statat() at kern_statat+0x98/frame 0xfffffe02c418c9c0 > sys_fstatat() at sys_fstatat+0x2f/frame 0xfffffe02c418cac0 > amd64_syscall() at amd64_syscall+0x79b/frame 0xfffffe02c418cbf0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe02c418cbf0 > --- syscall (552, FreeBSD ELF64, sys_fstatat), rip =3D 0x800dd48da, = rsp =3D 0x7fffffffddc8, rbp =3D 0x7fffffffde70 =E2=80=94 >=20 >=20 > Thanks, >=20 > Jan Mikkelsen >=20 >=20 From owner-freebsd-stable@freebsd.org Wed Nov 15 01:55:14 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 993CCDBC67E for ; Wed, 15 Nov 2017 01:55:14 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 00A7B793E6 for ; Wed, 15 Nov 2017 01:55:13 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 36991 invoked by uid 907); 15 Nov 2017 01:48:31 -0000 Received: from Unknown (HELO jmmacpro.tmst.com.au) (203.14.245.130) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA; Wed, 15 Nov 2017 12:48:31 +1100 From: Jan Mikkelsen Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Panic in unionfs "it is not a unionfs-vnode" Message-Id: <06DF69C5-884F-4483-8AF7-2013F4E868D1@transactionware.com> Date: Wed, 15 Nov 2017 12:48:28 +1100 To: FreeBSD Stable Maling List X-Mailer: Apple Mail (2.3445.4.7) 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: Wed, 15 Nov 2017 01:55:14 -0000 Hi, I got the panic below in unionfs. Head as at 325569, 2017-11-09 12:41:00 = +1100 (Thu, 09 Nov 2017). This is a ufs filesystem union mounted on top of a read-only ufs /etc. I = know unionfs has "architecture issues=E2=80=9D. Is this resolvable?=20 panic: unionfs: it is not unionfs-vnode cpuid =3D 5 time =3D 1510678800 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame = 0xfffffe02c418c280 vpanic() at vpanic+0x19c/frame 0xfffffe02c418c300 kassert_panic() at kassert_panic+0x126/frame 0xfffffe02c418c370 unionfs_lock() at unionfs_lock+0x635/frame 0xfffffe02c418c400 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xd9/frame 0xfffffe02c418c430 _vn_lock() at _vn_lock+0x66/frame 0xfffffe02c418c4a0 vget() at vget+0x82/frame 0xfffffe02c418c4e0 cache_lookup() at cache_lookup+0x787/frame 0xfffffe02c418c5c0 vfs_cache_lookup() at vfs_cache_lookup+0xac/frame 0xfffffe02c418c620 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xd3/frame 0xfffffe02c418c650 lookup() at lookup+0x682/frame 0xfffffe02c418c6f0 namei() at namei+0x51a/frame 0xfffffe02c418c7b0 kern_statat() at kern_statat+0x98/frame 0xfffffe02c418c9c0 sys_fstatat() at sys_fstatat+0x2f/frame 0xfffffe02c418cac0 amd64_syscall() at amd64_syscall+0x79b/frame 0xfffffe02c418cbf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe02c418cbf0 --- syscall (552, FreeBSD ELF64, sys_fstatat), rip =3D 0x800dd48da, rsp = =3D 0x7fffffffddc8, rbp =3D 0x7fffffffde70 =E2=80=94 Thanks, Jan Mikkelsen From owner-freebsd-stable@freebsd.org Wed Nov 15 20:00:36 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 40112DE5DD6 for ; Wed, 15 Nov 2017 20:00:36 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 11B28796E3 for ; Wed, 15 Nov 2017 20:00:35 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id 189so2800731iow.10 for ; Wed, 15 Nov 2017 12:00:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=vLTAZaY/ab98zB51yJMsEnegtKhNlcYugq0PbHUBjgY=; b=jC0+z8C2USV/Aa5O8qgzv7srrGxa6j/Sl41mteguE1/1knDz5ULCqNIrjZtWKF2Bdg 5evagLyba/qDFHo/x+TPB378S8NnIgcyk+neuSJtMSp6jN4oNP3N01fHFvyAqfHtr49W JVyxIpe2moInhHuMeelBKUW1dCctSA4d0w55W5uKDoUesQuITT5eG9zpOBjNJPrCW4WQ 8zxy613oAqGWMpFLv2tH8y6GyD6ygn+BGw82C7boIaqay1/FZtzXPG46CDvXZTs1T2JX n9zYf/YnRL1QtefQROTVqPuQR5MQndZ/PGvQN5M6tyXa81iv0jUOTvoY6nAakadkPhq+ qrDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=vLTAZaY/ab98zB51yJMsEnegtKhNlcYugq0PbHUBjgY=; b=dEGJeqFP5wyiWSlTv+AApO7DMp/wZrorSETxz9ylHMarJ/WbNBeMq33QL7sL9yDh5b RgyClc1m8LvUPerpW4Hgzct5XxEdeL1atLEQd/RpdfwKAshuUqapC6TeeaQfRpYUJ+th bakvUn1sM1Vp614t2Urf3MotR4xlt4R/XayQUJ8+5DHqtj9nDxNxVgABj3DLGU4nLuk8 zqW70JzOThn964AeeNz1AwqXmwy25Jh/ymdAhB4fqti9Io2LZmOV7NoL1b6L7l8GZeoC Ha1GMGh5Uh6pgd6Ss9NqKEYLxzuYb4yHgVZgPbF/R7GaT7HFIqtovM3aanrBRpNfNUsA Pq1Q== X-Gm-Message-State: AJaThX6ccO9ryzFUmOw4qqezjAMTKVe1ey2+lZsOQJ7zVK/GgxizX6Fq nZEM7FofBetQQUOiWJZ6unb13MI9Ne+ugBG2V9AJuw== X-Google-Smtp-Source: AGs4zMZEF83dFOw0tBgNwmjG6Vk3bYoVa2cDr28HaDCfdOW3ZmVSLhSVJE1MfYy2jXik5kd7+2qgq25p4OldtkI9OIU= X-Received: by 10.107.183.77 with SMTP id h74mr17779977iof.0.1510776033492; Wed, 15 Nov 2017 12:00:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.9.200 with HTTP; Wed, 15 Nov 2017 12:00:33 -0800 (PST) From: Mike Black Date: Wed, 15 Nov 2017 23:00:33 +0300 Message-ID: Subject: D-Link DGE530T issue To: 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: Wed, 15 Nov 2017 20:00:36 -0000 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=3D0x4b01108= 6 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, enab= led 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... --=20 amd_miek Think different. Just superior. =D0=91=D0=B5=D0=B7 =D0=B2=D0=B8=D1=80=D1=83=D1=81=D0=BE=D0=B2. www.avast.ru <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> From owner-freebsd-stable@freebsd.org Thu Nov 16 02:10:36 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 AC211DB83F6 for ; Thu, 16 Nov 2017 02:10:36 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8601D676CE for ; Thu, 16 Nov 2017 02:10:35 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vAG2ARj6008548 for ; Wed, 15 Nov 2017 18:10:34 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: From: "Chris H" Subject: Re: D-Link DGE530T issue Date: Wed, 15 Nov 2017 18:10:34 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit 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: Thu, 16 Nov 2017 02:10:36 -0000 On Wed, 15 Nov 2017 23:00:33 +0300 Mike Black wrote > 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. Just a hunch; But maybe it was simply a typo? You can probably omit the additional "1" on your local copy of the source, and try to build it again. My guess is you'll have success. NOTE: I'm not an authority on this driver. I'm only attempting to provide a possible solution. :) If you *are* successful. I would advise opening a PR for this. :) --Chris > 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. > > n=sig-email&utm_content=webmail> Без > вирусов. www.avast.ru > n=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Fri Nov 17 06:55: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 870B0DBC376 for ; Fri, 17 Nov 2017 06:55:05 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 4B8D87CE4E for ; Fri, 17 Nov 2017 06:55:05 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: by mail-io0-x235.google.com with SMTP id t11so7764673iof.13 for ; Thu, 16 Nov 2017 22:55:05 -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; bh=1QAJLynHRUxx+SX71lnXjs22UhJQpgpq9NlKymAJTt4=; b=put8p9/rI09nCGE0+NhoTomqPIG5g6t3Q5/6yZum/p6nHNFk6Ln+I8s7TidSXRFIDd pKszrl3mB8oQMqYQfvcutpjaaOS3+VfcN3UUSNC1EeTM7rj3+vVbwRO59/1VXHLjQ5S9 y4BZcWpv21FUpi8S/GvbO0GDSrBlI3KR4heLpojqhAXtMWsy/kdRvhTw6/oCAptf84mW o42AFIKrPMtrXC5wmCS4Pw+pJ0+Io5ff83Ont8f6MOmwtm7zC1M7w2mnXoiN85Sy9LQw 2wbWy839+Wbu/YvHzICVpxR1HlCTaDm9WztxOCn1MHLesn5pgJd6IAZz23+zFECKFxHB ApVw== 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; bh=1QAJLynHRUxx+SX71lnXjs22UhJQpgpq9NlKymAJTt4=; b=jxo1CtwmNLJDuWZ5Tt0E+kDNiFDqRKAHDMCNXqXO+Dwff1gaH11nBnuk/cUJIkF9Sg j+ndOik6gO2uopTX4pi1+7NrBZ46cJp7AaLJ2XSHQUYMDxk4mDC6C+v3ycaFbK2YmBOj 2h1YbADdXzimlZmfGz+7Y4dS9BttAOUaigIoezE/NAZpL0fUtbimogIigzVGNAHsoGNP 9VXde/biwOnm6sCVrJokFOoA5RcdhmeAhdmMyfGVFPjBDI+KQW+RwFeuFuIDm4wZNkFK L7c5v4g/7OSZBWq/y5DjNTULAIch8U4/SxgaOzwlYR+WQP+t/gn10B9y393UTBRPWm2+ U+Iw== X-Gm-Message-State: AJaThX4xZ2uI5SsBizpAYykhhaXPYCsE/KYgRkXdzO7GMwZ6GZ/tO3j1 Rbu6S2WxBNGPWNNwodh5Q1lRpSdGw9rOWi9d28o= X-Google-Smtp-Source: AGs4zMYL/tqxEGsyINP82RQRackOWLxUdOmOidwQF+uhYmMBfBH8wVyMSGL44K4jIQwSeF69fke9ozXjgD/8ruMul4s= X-Received: by 10.107.3.170 with SMTP id e42mr1772327ioi.88.1510901704267; Thu, 16 Nov 2017 22:55:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.9.200 with HTTP; Thu, 16 Nov 2017 22:55:03 -0800 (PST) Received: by 10.2.9.200 with HTTP; Thu, 16 Nov 2017 22:55:03 -0800 (PST) In-Reply-To: References: From: Mike Black Date: Fri, 17 Nov 2017 09:55:03 +0300 Message-ID: Subject: Re: D-Link DGE530T issue To: 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 06:55:05 -0000 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. 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=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 > > According /usr/share/misc/pci_vendors this D-link should have 4b011186 no= t > 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. > > > =D0=91=D0=B5=D0=B7 > =D0=B2=D0=B8=D1=80=D1=83=D1=81=D0=BE=D0=B2. www.avast.ru > > <#m_6570072101733768544_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > From owner-freebsd-stable@freebsd.org Fri Nov 17 08:30:26 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 AADADDBE0DA for ; Fri, 17 Nov 2017 08:30:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 947367F21B for ; Fri, 17 Nov 2017 08:30:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 8FD68DBE0D8; Fri, 17 Nov 2017 08:30:26 +0000 (UTC) Delivered-To: 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 8DA7DDBE0D7; Fri, 17 Nov 2017 08:30:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 40FD27F219; Fri, 17 Nov 2017 08:30:25 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1eFc2O-000GuK-5i; Fri, 17 Nov 2017 10:30:12 +0200 From: Daniel Braniss Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: iscsi target and VMware/esxi timeouts -- SOLVED Date: Fri, 17 Nov 2017 10:30:11 +0200 In-Reply-To: <6B1A4A67-D0E9-4A73-B690-60A52D144F81@punkt.de> Cc: Freebsd hackers list , =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= , stable@freebsd.org To: "Patrick M. Hausen" References: <7779629C-A1E5-4E96-B660-A0FAD231468C@cs.huji.ac.il> <6B1A4A67-D0E9-4A73-B690-60A52D144F81@punkt.de> X-Mailer: Apple Mail (2.3445.4.7) 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 08:30:26 -0000 > On 14 Nov 2017, at 11:28, Patrick M. Hausen wrote: >=20 > Hello, >=20 >> Am 14.11.2017 um 10:08 schrieb Daniel Braniss : >>=20 >> Hi, >> we are experimenting issues with several esxi=E2=80=99s 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 >>=20 >> these are 3 different esxis that almost at the same time the target = looses connection to the initiators. >> at the moment most =E2=80=98clients=E2=80=99 recover from the scsi = error, but older freebsds don=E2=80=99t. >>=20 >> in any case, increasing the timeout is not helping. >>=20 >> any clues are welcome :-) >>=20 >> over the weekend i=E2=80=99m planning to upgrade the target to 11.1 = and take for the hills. >=20 > Are you using istgt or ctld? >=20 > We have did experience similar occasional problems with the former > but never with the latter. >=20 > Patrick the iscsi initiator of the esxi=E2=80=99s (VMware) does answer to = NOP=E2=80=99s once in a blue moon! this was checked by sniffing the network. setting kern.cam.ctl.iscsi.ping_timeout=3D0 solved this. thanks, danny From owner-freebsd-stable@freebsd.org Fri Nov 17 10:20:00 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 0DAFCDC0658 for ; Fri, 17 Nov 2017 10:20:00 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 CA80426C5 for ; Fri, 17 Nov 2017 10:19:59 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pf0-x22c.google.com with SMTP id a84so1650626pfl.0 for ; Fri, 17 Nov 2017 02:19:59 -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=MvSvYj3UYYAF9opPn/vOgipvBypgpdjzfvrfeot+p4o=; b=NQeOeMgtDpyCGwkGumtFg1Ps2jCDNH6CfA8tvnsg6bNhRQHZchV0vcuPr9TRF7Vwfa xYrdCkotg4odoUQUqi7evRtKGDrRPNFOXSQImLLTmDaSlPC8K7/GpdyeShADfrnUk7Qk zVtaOH7XxIMrUtEInw9CjaPFqycW75DZijScucGdjm6u0u4B9fiGhmmhCtb4QOSdwg94 fKah6qsBIiJJbiHXPQ11wHP9b2oJdchcqdxC/RyMyjExzNpgHBSr+wDl4TKxZR5LfRkP qV/DnZGh7ry9DMMbaiX2Wa3BYmPjC28LT5b5mBXf0l0sj1GEPmDasbGRZRpxAvvwNTas 82aw== 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=MvSvYj3UYYAF9opPn/vOgipvBypgpdjzfvrfeot+p4o=; b=Tv+z8Z75vdtsIroE46gVFu4uiKzKQmAkB16itPkqlwTB2j3c/rcl3/XNWThh4FQzaf zJIuh15rmM7udpyHOemR7lWxVGyqKb/jFR4PeumrJF+lExGSfbU1Ytl4nTe2zrKjOdZG xHm7kLgh6nsJd13sER0GCJULDY5Ip+1EitLCMNInUTS/NU2X7AmKTPt1YIYZPogFubN1 pAv+ohVZxMVuiZvwVeXOgquw8lOkDOnnB7EMPDO/yugB4RFSidSf/B5cBEQJQUY6kB/N PkOfbxipSgkU6q7INUlATWCiKyBnCAbIX96hTOXnXg8Sq++e5bkzvTGXXeYPjH0NiOKq uuvQ== X-Gm-Message-State: AJaThX5VuSkwnNU49xui12ie4HQHPh6HyONp6n/WwpYew4ZFaAOsRuuQ kqjtYc/JwubcyIYXpXw9Bg0OGg== X-Google-Smtp-Source: AGs4zMYS5pIn7ueVKGNJ1YLCPtu1zbCPRFjk/gVcMjYv2L/p6d5CB+Wn1S2y7Q+c2HA7K+Za/tjU7g== X-Received: by 10.98.64.141 with SMTP id f13mr1535683pfd.213.1510913999262; Fri, 17 Nov 2017 02:19:59 -0800 (PST) Received: from localhost ([116.46.79.128]) by smtp.gmail.com with ESMTPSA id s71sm7330703pfa.147.2017.11.17.02.19.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 02:19:58 -0800 (PST) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Fri, 17 Nov 2017 19:19:55 +0900 Date: Fri, 17 Nov 2017 19:19:55 +0900 To: Mike Black Cc: freebsd-stable Subject: Re: D-Link DGE530T issue Message-ID: <20171117101954.GA1246@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com References: 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 10:20:00 -0000 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. From owner-freebsd-stable@freebsd.org Fri Nov 17 12:13:00 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 5248CDD81D5 for ; Fri, 17 Nov 2017 12:13:00 +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 17833649D6 for ; Fri, 17 Nov 2017 12:13:00 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: by mail-io0-x233.google.com with SMTP id v21so8549488ioi.4 for ; Fri, 17 Nov 2017 04:13:00 -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=2ohnU91TReYMCABYopMBZ1s3KwGGxSab8w6tfKFCDf4=; b=AD7XcQb9BNB8JE9hseZ12rYDYOdcK4E/Rm6bQCTG5qdfsTSDGsUHspiHICGQ9nmDX2 Ehb9DJNz0b+nZ0Pu9t4HuTZa1hyDRRqd7usu1pIdhjOc1HWZAWM8FU/BU9I6fvHfvuL2 8+1eqgJol8mrdE9mpMMOnv8WN6A6zT4OAOSBJzfUjkONeMyiZXFSM1OZIJpzP0o9AWtQ VZeShTvijfYMgGAI0Sue3WIbbDrn2YFhj/85hespy/JR99/XbcvjkzB7VqosA3UngUlO gsIo2Tf+z3Gga0vOFpiyFiAMy679OeRrqiXPYu9CDbMvkrHdplST/QOGjqlcQAI/leLp spfA== 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=2ohnU91TReYMCABYopMBZ1s3KwGGxSab8w6tfKFCDf4=; b=YwQ7dWCDfm20JEw+CYGPFV3YbgbseOTyrdXjf+G16WXB05cQaWJUfHMuI6npWvyFzv XM5Avy0SfxL+xeVux6XG/0kNTQOEinhZAeKxkFhL/1UEs+zoEEUUrw00pylNr52qg6Jc tpWj4+8vI13eJQ2thxFvLKi6ZGcQWa49qhFU61JrAI0ritk7UVdfJrvA2F8z8QZe0JZR bKX4ZBwbrinqXeVOjjQOp1mM3eAPg0stkHIEINrV247EpMsksx46jgPLRQQIVMRFAlNb KbCaZuG+lEAg1yhpPEO4s9Ra0C41HVg8yIDOm+5MbFw5iA8j5oF0WhpFq87UQedu8Bpb 0qtw== X-Gm-Message-State: AJaThX4zIQ1a/uGGnpInhIFzCIp49AYbXe5HjMJeQ+GLTaQFZgA/X1Ir ZQekhGRQX/7LLr6QBAzipkxzAHK/cZMT6Npcnts= X-Google-Smtp-Source: AGs4zMbw3HBREXeV+04XQn8o3zpg5zBi2aJh8Y5hiD2jrjYv+WxL7FnI/Z2pwhB+hC0PpZjq75iaq6y0eG3Q/45MM5I= X-Received: by 10.107.102.13 with SMTP id a13mr2475872ioc.185.1510920779323; Fri, 17 Nov 2017 04:12:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.9.200 with HTTP; Fri, 17 Nov 2017 04:12:58 -0800 (PST) In-Reply-To: <20171117101954.GA1246@michelle.fasterthan.co.kr> References: <20171117101954.GA1246@michelle.fasterthan.co.kr> From: Mike Black Date: Fri, 17 Nov 2017 15:12:58 +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 12:13:00 -0000 Hello VPD is none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086 chip=3D0x4b01108= 6 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, enab= led 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 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 : > 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. H= ow > > 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 b= y > a > > > driver. > > > > > > pciconf says that is > > > none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086 chip=3D0x4= b011086 > > > 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, > 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 4b01118= 6 > 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. > --=20 amd_miek Think different. Just superior. From owner-freebsd-stable@freebsd.org Fri Nov 17 13:00:31 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 C5296DD9797 for ; Fri, 17 Nov 2017 13:00:31 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (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 890D765CED for ; Fri, 17 Nov 2017 13:00:31 +0000 (UTC) (envelope-from amdmiek@gmail.com) Received: by mail-it0-x235.google.com with SMTP id x28so3948463ita.0 for ; Fri, 17 Nov 2017 05:00:31 -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=vgyTcg5w1Pi5v883v2QLcUqJxqpioqiElYRBZAS2YsM=; b=M3KQAnJgeZ4y/q3UVFm3wiTDkjOeB+BAoc7Ukq1rWAzcJCVktU32KZxVKTishEtXHe 5G7HdoXgiPST/aEPtQZs+FWwXX7omdwdXo234zrVEUJwUBlg4UgaO8vde4gDkG3+Uq51 8lGynOzl0hGNfkmYu6N8kbyKugPPcm5ANS2nCW3fJIZbLedSlJkZO85EQrkocztnlSSU PmCFbJUYk8mjEgcnEanQUCGeP3XJIDZ7kORRGUvpiZGt90KUK/OaZx0GzHp3Waed7fAW gbfP6tAg0xCZrVNsdzkutngD32pUq3Gx2pOPXIlVkWmxL++/l6Uii7lCXb583VzIavxy Q4Tw== 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=vgyTcg5w1Pi5v883v2QLcUqJxqpioqiElYRBZAS2YsM=; b=NYNgmHq3LdW3K956F+PmA5OdoBur8ZgK+plWQVW1CcI8YxKV+vvzMvqO2I+lutIpSa UgTf1Ug/v5qZfBc+FBhlDBF9iOTyotZXyEzvR7es/PX2U1hpq3MCq5ud32e931s+XnuT 0HPWlhQs4hOCNT+XWFEATf/G76cUGEZarx9yISe2/gCZ/veSzqQtZggWRhEWCyb3ALnm ctF+TxjF45bL9xEBA6eWuuxo4KrzjSIzJDhdVLFGXhKom/MgazxVOpvU6n8YRcs52Jhi rK1z6topYqt+R/ywFi3g9/o8SkGMbgnoKJPrw5M/wMbtwIIucr5aLt39eCvhNVkFuLzk Zxbw== X-Gm-Message-State: AJaThX4QFgG+AvgTmZvqBuxIX7bjR05BYODAvVBMnKb+BMCnGN4sOHWl 7fXgKt8Pt/BAl2mtFPw4Ifm1ztZTQLjTjU8+D7A= X-Google-Smtp-Source: AGs4zMZVaFFY+0dIjsub1N+iQpNlO/IUp2lZcRbLRwZjU/tx8YbrVRJKc5D/fsDs4rNm0kdu6eM9otUabUFgq6UxXWI= X-Received: by 10.36.196.85 with SMTP id v82mr6994030itf.136.1510923630687; Fri, 17 Nov 2017 05:00:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.9.200 with HTTP; Fri, 17 Nov 2017 05:00:30 -0800 (PST) In-Reply-To: References: <20171117101954.GA1246@michelle.fasterthan.co.kr> From: Mike Black Date: Fri, 17 Nov 2017 16:00:30 +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 13:00:31 -0000 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-0xdfdfffff 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=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 : > 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 : > >> 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 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. From owner-freebsd-stable@freebsd.org Fri Nov 17 13:10:35 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 45E4ADD9C6E for ; Fri, 17 Nov 2017 13:10:35 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward101o.mail.yandex.net (forward101o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::601]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA95C663B2 for ; Fri, 17 Nov 2017 13:10:34 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback14j.mail.yandex.net (mxback14j.mail.yandex.net [IPv6:2a02:6b8:0:1619::90]) by forward101o.mail.yandex.net (Yandex) with ESMTP id BF2D51343262 for ; Fri, 17 Nov 2017 16:10:16 +0300 (MSK) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [2a02:6b8:0:801::ab]) by mxback14j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id QECXxnoafO-AFB0DhYm; Fri, 17 Nov 2017 16:10:16 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1510924216; bh=qDznO4eXKK/D94mX4qJ1U4Fy8rS+2nqSZicLR9pNdQA=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=Mz8Pdow/DQZRiAtnan3toAk+fTsQPq4Kh1KuaAk2nmiErwTS57zgz1Tzt1QTgp/VU DDb4HltFMPzaP0gSBvdbT6IUIHXMiqouXawBKs2SaHhWF85WpAB7fpR4Vm2bvkY5jl Ft7DcN2ZiR1uo0i8hGcdqdDvcxi5jjR7tW8Lxa8o= Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 14PJ7SgqLx-AFJqJMmr; Fri, 17 Nov 2017 16:10:15 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1510924215; bh=qDznO4eXKK/D94mX4qJ1U4Fy8rS+2nqSZicLR9pNdQA=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=LDxWw2LPbsWSwHwKQRlJ3pouH2sO+dCgQm69qNRY4SMkkzb5IbcuTIF0YmNGJ2fhT QimNb3uoa3vbDML36aOQNC6hZMf1hRU61JxEksvB+MADm9nwtwaPQLGy4Cc1iJpO0b NDlKwuK+rlRsjvcTvkLGTZyJGtRYzmaA6vZZGBZQ= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: D-Link DGE530T issue To: freebsd-stable@freebsd.org References: <20171117101954.GA1246@michelle.fasterthan.co.kr> From: Boris Samorodov Message-ID: <52fed579-6430-37d0-e859-86f62b74a181@passap.ru> Date: Fri, 17 Nov 2017 16:10:15 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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 13:10:35 -0000 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 From owner-freebsd-stable@freebsd.org Fri Nov 17 13:51:22 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 1D3D1DDAD85 for ; Fri, 17 Nov 2017 13:51:22 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from sonic304-22.consmr.mail.ir2.yahoo.com (sonic304-22.consmr.mail.ir2.yahoo.com [77.238.179.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A725967657 for ; Fri, 17 Nov 2017 13:51:20 +0000 (UTC) (envelope-from ardovm@yahoo.it) X-YMail-OSG: tQr70uUVM1k7lUwFmZbV1dYsqLHL7A3xjYJS1OqSRtoAx2OWKAI4eSJ3d3CpNRa E9ECoLCk.mHd2yxxy5qg_TVVn8m9hiMglKIpb3qyRlxQKYHbvAzLEYqfdL4OEid0eHsQSqOXA5C. 4fFeQHKnDsULmATD5glV4Ih.2lLKaMHMZ_Q9pHuqr32PDQckwwaQSDePWt1tGnn1WduPXewWTkMS _4ncjpxlDD0CdbD.HzkRmTGlu7FdEhJcGG7oGiTCsI58aIntIZ9zzMoTn6hSiqrMUVLb7SQhaQHn UgDRT.Rq0ZXCuaR2LDwV3QE.z.JL4hfuMr8hnDSiqSyOqHeCIlHE4zlNMHC.L8q1H2iPVTkjC.a7 6vyrkf5DdamvAotgdRKii3oVn8KYHPbteKGlkBTFHLPWv30.oaN75DJnG_38vUsfL8eTm9CNwQVC 87Y4gwLANX2ay6Bw_e_EWoVWeIxi.gc.sIzcnrMV8rja8bZymOLXC9lM1jYu7a7SpG2eW0ty6_xv tJqBtsafhwf5.WGqUQywx9HcNnYGRaKMH5pKcU0_q_uk- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ir2.yahoo.com with HTTP; Fri, 17 Nov 2017 13:51:12 +0000 Received: from [127.0.0.1] by smtp124.mail.ir2.yahoo.com with NNFMP; 17 Nov 2017 13:51:09 -0000 X-Yahoo-Newman-Id: 116651.13917.bm@smtp124.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: tQr70uUVM1k7lUwFmZbV1dYsqLHL7A3xjYJS1OqSRtoAx2O WKAI4eSJ3d3CpNRaE9ECoLCk.mHd2yxxy5qg_TVVn8m9hiMglKIpb3qyRlxQ KYHbvAzLEYqfdL4OEid0eHsQSqOXA5C.4fFeQHKnDsULmATD5glV4Ih.2lLK aMHMZ_Q9pHuqr32PDQckwwaQSDePWt1tGnn1WduPXewWTkMS_4ncjpxlDD0C dbD.HzkRmTGlu7FdEhJcGG7oGiTCsI58aIntIZ9zzMoTn6hSiqrMUVLb7SQh aQHnUgDRT.Rq0ZXCuaR2LDwV3QE.z.JL4hfuMr8hnDSiqSyOqHeCIlHE4zlN MHC.L8q1H2iPVTkjC.a76vyrkf5DdamvAotgdRKii3oVn8KYHPbteKGlkBTF HLPWv30.oaN75DJnG_38vUsfL8eTm9CNwQVC87Y4gwLANX2ay6Bw_e_EWoVW eIxi.gc.sIzcnrMV8rja8bZymOLXC9lM1jYu7a7SpG2eW0ty6_xvtJqBtsaf hwf5.WGqUQywx9HcNnYGRaKMH5pKcU0_q_uk- X-Yahoo-SMTP: WU.IBxeswBAAnLcBZV3tEZIK0A-- Received: by nuvolo.localdomain (Postfix, from userid 1001) id 2A52A1B08C0; Fri, 17 Nov 2017 14:51:07 +0100 (CET) Date: Fri, 17 Nov 2017 14:51:07 +0100 From: Arrigo Marchiori To: freebsd-stable@freebsd.org Subject: Re: D-Link DGE530T issue Message-ID: <20171117135107.GA70004@nuvolo> References: <20171117101954.GA1246@michelle.fasterthan.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Content-Transfer-Encoding: quoted-printable 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 13:51:22 -0000 Hello, On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote: > Hello >=20 > VPD is > none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086 chip=3D0x4b0= 11086 > rev=3D0x11 hdr=3D0x00 > vendor =3D '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 =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, enab= led > 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' >=20 > But I see... it says some DGD-530T... Do not know why, because it's > DGE-530T for sure. >=20 > So you're saying this it hardware degradation? > I will try to find some windows host and plug it in there to check it. >=20 > 2017-11-17 13:19 GMT+03:00 YongHyeon PYUN : >=20 > > 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 VI= D. How > > > can this be checked or fixed? > > > I use a loadable kernel module after a startup, so there is no usef= ul > > > 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 o= n 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 M= SK > > 2017 > > > > amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 a= md64 > > > > 1101502 1101502 > > > > > > > > But recently I plugged this card back and it's not being recogniz= ed by > > a > > > > driver. > > > > > > > > pciconf says that is > > > > none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086 chip=3D= 0x4b011086 > > > > 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 1= 6384, > > > > 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 4b0= 11186 > > 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 y= ears > > > > So I'd like to know what's wrong - some changes in driver in a re= cent > > > > 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. > > >=20 >=20 >=20 > --=20 > amd_miek > Think different. > Just superior. --=20 rigo http://rigo.altervista.org 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. > > 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. > > From owner-freebsd-stable@freebsd.org Sat Nov 18 08:07:51 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 86EFADF16D0 for ; Sat, 18 Nov 2017 08:07:51 +0000 (UTC) (envelope-from bounce+b1b547.69110-freebsd-stable=freebsd.org@miator.net) Received: from mail-s68.mailgun.info (mail-s68.mailgun.info [184.173.153.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F949675F8 for ; Sat, 18 Nov 2017 08:07:50 +0000 (UTC) (envelope-from bounce+b1b547.69110-freebsd-stable=freebsd.org@miator.net) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=miator.net; q=dns/txt; s=krs; t=1510992464; h=Content-Type: Cc: To: Subject: Message-ID: Date: From: References: In-Reply-To: MIME-Version: Sender; bh=O696Sczd93hoJz6OQsyeqbevKyeGM03Uvdj9f5dfZJQ=; b=G2pbWaociGUg8X0AexUKxuGI0Uk7G/Gu99GJO72rswzFMLEuq5x82PlWfQNaEENd0qafecM6 iZh5Ejs8bB4OGWuWUmJFU1ydVXFHMZ2B59ctNs6o4fZ3pp1iHKQOlxDO72wvX688TU24PMdK uIjVUkcpC8Jfnrtaj2OhC55ioZo= Sender: zy@miator.net X-Mailgun-Sending-Ip: 184.173.153.196 X-Mailgun-Sid: WyJkZjBjNyIsICJmcmVlYnNkLXN0YWJsZUBmcmVlYnNkLm9yZyIsICI2OTExMCJd Received: from mail-qt0-f171.google.com (mail-qt0-f171.google.com [209.85.216.171]) by mxa.mailgun.org with ESMTP id 5a0fea50.7f4c342071b0-smtp-out-n02; Sat, 18 Nov 2017 08:07:44 -0000 (UTC) Received: by mail-qt0-f171.google.com with SMTP id n32so9587891qtb.2; Sat, 18 Nov 2017 00:07:44 -0800 (PST) X-Gm-Message-State: AJaThX65WywW8iMYISv2KLjthq1EkKjZtvCfCbTmLGX+Ae1+X+dmCT9l Mc3G2JHgCeFHk78H/HAXkdLwfSLJi26ImT25vog= X-Google-Smtp-Source: AGs4zMYAHmk1LAHPbEwlaozg4XIieAiYHvt/Ae9ee/PU7NG292Z0ig7AdQ+Xezfk1qhrxsw2at+CQDXPDRLLkaItQiQ= X-Received: by 10.200.54.236 with SMTP id b41mr13132515qtc.280.1510992464246; Sat, 18 Nov 2017 00:07:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.41.106 with HTTP; Sat, 18 Nov 2017 00:07:43 -0800 (PST) In-Reply-To: References: From: Zhihao Yuan Date: Sat, 18 Nov 2017 02:07:43 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: iwn crashing on 11n network To: Zhihao Yuan Cc: FreeBSD-STABLE Mailing List , freebsd-wireless@freebsd.org, avos@freebsd.org Content-Type: text/plain; charset="UTF-8" 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: Sat, 18 Nov 2017 08:07:51 -0000 On Thu, Nov 9, 2017 at 2:53 AM, Zhihao Yuan wrote: > > The issues is here: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214435 > > We observed same error from two cards, > > Intel Centrino Wireless-N 1000 > > and > > Intel Centrino Ultimate-N 6300 > > both on 11. > Ping? Is iwn driver still maintained? -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. _______________________________________________ From owner-freebsd-stable@freebsd.org Sat Nov 18 08:58:32 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 BAE14DF2332; Sat, 18 Nov 2017 08:58:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (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 4F95268855; Sat, 18 Nov 2017 08:58:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id u40so3984618wrf.10; Sat, 18 Nov 2017 00:58:32 -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=oa+YNyzOsRmSucrFhnM3KyF016CplqftP1uH15s00vY=; b=cQ3QweeLWBgO2Qm0GSnh4Q7WVOzTrlUdIakji+QA/3MYmhChMtAiZNw9mR88vNEveI zS7aEzDa1ulcS/cV87xN4EfJ5jam/VF3Dywr8fWtN2wdJnzuMrtTjeFnYBo1YNbSyPLU 5grWrQepIzhhnXJMSTYoP3AdAPKYgprtj7Xb3Nvm5hksfWYP+amzBuhGeElmUe70qxbs rbA02v2ItdAW/HVZ7yCCOtahdXJvUkMlOUmoORKamufRChjJ8zE1PTPtrYaysQ8Due8k +POLIps6K/JfKwcW64VubILENPnUm0Q5GaARBSSA7DoVZ2eRRJdlCI+l1yIMcrYka24A rjuQ== 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=oa+YNyzOsRmSucrFhnM3KyF016CplqftP1uH15s00vY=; b=g0FWlc9HgDIIVsY7vpSxSvUKalWHSCGHohRV+xj8dKBwjd7WQHCNZz7yjxI1ioKInD XcQeA/4U8QnocUQA8tEx4AnRfEOrH5yiDuak5T6xyLO2DTPou2KkVZGkQjoHlvVHh6c2 IK0JcZLJ/j+jskXuARvibbHk8swLNoy82s17QopMxSRb2uDzFZZAKV/8K+DtGXR/xVrs c7Jn4Elol4RaqDM2nYzNZzmdAsmdCOvkW2fcGAUrU8leSaykQi+JfGt4/LBD5+yvHe9U +0OijH0RxSCjURmvht/3JlqYDIsu9SFsldTNd7d66Vuak+BG2cSZEfcPy6XyKdUAhlev 5DBA== X-Gm-Message-State: AJaThX79rhpwxWu/e+dfaGIfkroniCjguBy835AlAX7kiY4A5tCuYW4r XrOLmDSge2CZj/6wfhvSrOq+naqH4rLIAEfQHeY= X-Google-Smtp-Source: AGs4zMYiG819SW/8g8O8I/y3KHtz9n5SbALX78Q1VMMshOLb3NETbKzY34z1wZKM8fdGSOcDIZgyEL5n/sBuPFxIPZU= X-Received: by 10.223.179.194 with SMTP id x2mr6609319wrd.266.1510995509149; Sat, 18 Nov 2017 00:58:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.213.131 with HTTP; Sat, 18 Nov 2017 00:58:28 -0800 (PST) In-Reply-To: References: From: Adrian Chadd Date: Sat, 18 Nov 2017 00:58:28 -0800 Message-ID: Subject: Re: iwn crashing on 11n network To: Zhihao Yuan Cc: "freebsd-wireless@freebsd.org" , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" 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: Sat, 18 Nov 2017 08:58:32 -0000 hi, I'm busy and there isn't a specific maintainer! Bug me in a couple days; we need to figure out how to enable the right command to enable debugging the firmware messages. Hopefully we can narrow down which firmware message its erroring out on! -a