From owner-freebsd-stable@freebsd.org Mon Nov 6 22:51:15 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 9E277E68D15 for ; Mon, 6 Nov 2017 22:51:15 +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 83A52638E1 for ; Mon, 6 Nov 2017 22:51:15 +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 vA6MpDjj040660 for ; Mon, 6 Nov 2017 22:51:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221146] [LAGG] Problem with second laggport Date: Mon, 06 Nov 2017 22:51:14 +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: jeffrey.e.pieper@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.23 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, 06 Nov 2017 22:51:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 Jeff Pieper changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffrey.e.pieper@intel.com --- Comment #16 from Jeff Pieper --- We are unable to reproduce this over 10 reboots: FreeBSD u1015 11.1-STABLE FreeBSD 11.1-STABLE #0 d89b4f5935a(stable/11): Sat Nov 4 04:15:08 UTC 2017 [root@u1015 ~]# sysctl dev.ix|grep Version dev.ix.1.%desc: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k dev.ix.0.%desc: Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k Relevant rc.conf entries: ifconfig_ix0=3D"up" ifconfig_ix1=3D"up" cloned_interfaces=3D"lagg0" ifconfig_lagg0=3D"laggproto lacp laggport ix0 laggport ix1 190.2.10.15 netm= ask 255.255.0.0" [root@u1015 ~]# ifconfig -vvvv lagg0 lagg0: flags=3D8843 metric 0 mtu 15= 00 =20=20=20=20=20=20=20 options=3De407bb ether 90:e2:ba:d5:bf:40 inet 190.2.10.15 netmask 0xffff0000 broadcast 190.2.255.255 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg laggproto lacp lagghash l2,l3,l4 lagg options: flags=3D11 flowid_shift: 16 lagg statistics: active ports: 2 flapping: 0 lag id: [(8000,90-E2-BA-D5-BF-40,00D2,0000,0000), (0000,00-04-96-9B-9B-35,03E9,0000,0000)] laggport: ix0 flags=3D1c state=3D3d [(8000,90-E2-BA-D5-BF-40,00D2,8000,0003), (0000,00-04-96-9B-9B-35,03E9,0000,03E9)] laggport: ix1 flags=3D1c state=3D3d [(8000,90-E2-BA-D5-BF-40,00D2,8000,0004), (0000,00-04-96-9B-9B-35,03E9,0000,03EA)] [root@u1015 ~]# ifconfig -vvvvv ix1 ix1: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3De407bb ether 90:e2:ba:d5:bf:40 hwaddr 90:e2:ba:d5:bf:41 nd6 options=3D29 media: Ethernet autoselect (10Gbase-LR ) status: active plugged: SFP/SFP+/SFP28 10G Base-LR (LC) vendor: Intel Corp PN: FTLX1471D3BCV-I3 SN: ATS0LVZ DATE: 2015-07-06 module temperature: 42.12 C Voltage: 3.30 Volts RX: 0.43 mW (-3.64 dBm) TX: 0.76 mW (-1.17 dBm) SFF8472 DUMP (0xA0 0..127 range): 03 04 07 20 00 00 02 00 00 00 00 06 67 02 0A 64 00 00 00 00 49 6E 74 65 6C 20 43 6F 72 70 20 20 20 20 20 20 00 00 1B 21 46 54 4C 58 31 34 37 31 44 33 42 43 56 2D 49 33 41 20 20 20 05 1E 00 83 00 3A 00 00 41 54 53 30 4C 56 5A 20 20 20 20 20 20 20 20 20 31 35 30 37 30 36 20 20 68 FA 02 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [root@u1015 ~]# ifconfig -vvvvv ix0 ix0: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 options=3De407bb ether 90:e2:ba:d5:bf:40 hwaddr 90:e2:ba:d5:bf:40 nd6 options=3D29 media: Ethernet autoselect (10Gbase-LR ) status: active plugged: SFP/SFP+/SFP28 10G Base-LR (LC) vendor: Intel Corp PN: FTLX1471D3BCV-I3 SN: AU20U3K DATE: 2015-07-15 module temperature: 41.68 C Voltage: 3.30 Volts RX: 0.34 mW (-4.64 dBm) TX: 0.72 mW (-1.37 dBm) SFF8472 DUMP (0xA0 0..127 range): 03 04 07 20 00 00 02 00 00 00 00 06 67 02 0A 64 00 00 00 00 49 6E 74 65 6C 20 43 6F 72 70 20 20 20 20 20 20 00 00 1B 21 46 54 4C 58 31 34 37 31 44 33 42 43 56 2D 49 33 41 20 20 20 05 1E 00 83 00 3A 00 00 41 55 32 30 55 33 4B 20 20 20 20 20 20 20 20 20 31 35 30 37 31 35 20 20 68 FA 02 FC 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Can you give us the ifconfig -vvvvv output for each ix interface? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Tue Nov 7 06:36:16 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 8150AE50451 for ; Tue, 7 Nov 2017 06:36:16 +0000 (UTC) (envelope-from op-mp-ojs-notification@publications.europa.eu) Received: from out.mail.ec.europa.eu (out.mail.ec.europa.eu [147.67.11.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "out.mail.ec.europa.eu", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 533FD65945 for ; Tue, 7 Nov 2017 06:36:14 +0000 (UTC) (envelope-from op-mp-ojs-notification@publications.europa.eu) Received: from S-DC-EMP020-I.net1.cec.eu.int (158.166.6.142) by S-DC-EDG038-Z.rcnet.cec.eu.int (147.67.11.10) with Microsoft SMTP Server (TLS) id 14.3.352.0; Tue, 7 Nov 2017 07:35:13 +0100 Received: from opvmwsehtx4.publications.win (158.167.96.63) by SMTPMAIL.cec.eu.int (158.166.6.142) with Microsoft SMTP Server (TLS) id 14.3.352.0; Tue, 7 Nov 2017 07:35:00 +0100 Received: from localhost.localdomain (158.167.96.8) by opvmwsehtx4.publications.win (158.167.96.63) with Microsoft SMTP Server id 14.3.352.0; Tue, 7 Nov 2017 07:35:00 +0100 Content-Disposition: inline X-Mailer: MIME::Lite 3.01 (F2.74; A1.77; B3.07; Q3.07) Date: Tue, 7 Nov 2017 06:35:00 +0000 From: OPOCE MP-OJS Notification To: Subject: hi Message-ID: <945a2b11-5e50-4161-80fa-d7505eaf5b77@OPVMWSEHTX4.publications.win> MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Nov 2017 06:36:16 -0000 From owner-freebsd-stable@freebsd.org Tue Nov 7 16:04:50 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 3D096E5C958; Tue, 7 Nov 2017 16:04:50 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::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 DF999722FB; Tue, 7 Nov 2017 16:04:49 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x233.google.com with SMTP id x195so10257959qkb.12; Tue, 07 Nov 2017 08:04:49 -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=mpSZgR/BlqIslQ7DXUyswSNMDZVgaWhzmX6xUwUUXdo=; b=Ik3HNNAUHaCD+xolpN9lSrycOQTEwFRJP7o4ZSov7hozYPoGpYt7xg83k8UBbds5Lc 1MuLRQsGVqRWSWHvxWWwyleRGGv2gsLDkg8K+qJ9b0ZG+tupzbhQa9xXWyGYNp9En4k2 N34Fxy4+EKAApKr6oq28Uv7rngAr04JvtX/BqcwKAnvUZeRLgmQGwmohV+L9EkcGBaG6 wQiooCZk9aqkiegQE5DydLtFovQqeYGcV7aK0eoL6vypatB3s8ijDcoVRywLG8LoHBRR RIspfABuNWHUlhc1VYukTfw562f3AA9IqcTxIJAxkrG3kkCOFrrK2tkdNqTMZOHvel6Y 1g/g== 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=mpSZgR/BlqIslQ7DXUyswSNMDZVgaWhzmX6xUwUUXdo=; b=SvuRwMcmHC55Mx0/RVV0W5YLWs/qFIY18qdo7Z7Dn2YHYoyC4p5PcHoiHXf3djsCw6 AG0FwGO/Cnx2qHf3tSTg162j+CyBkmDMovCSjGkHVLIuVpG4YGm8XkGbj1MJRMiam/Ww 4srz5S1sLv4zH3ISmc6sTfSY4rkhCzRas8hlUkCNU+QnTQO533s9xV+RrlCFzcvZdU9X 7XYnhEXrKOaRvm/aevbjoGThFHzwgR0WyGWpXX4Bx8LkMROviIcWs3bBOyilHVY29Sx5 VstSvKk0axRuDwmhfhJzTtmQIjJGM17J71om3DPskGHyT/m+/mAaTLzZ2j2vpGiwr3Sr yciw== X-Gm-Message-State: AJaThX7RfypjKXlzuyv/k9DB/638a2HP9WWfOBh7oCw0yGhl6mAqdhBg OZ2OKLjXhT3qtvF2qHtw+dmxTSu99qsGH6onF7k= X-Google-Smtp-Source: ABhQp+R1LNdCXWfJCZm/sIYfg84q5/RXZK9QGCMwuZJqGN4oo5ApqL6uUDMi0Jv8TSavOczwPPzvhzuF84UfNaBsBLA= X-Received: by 10.55.134.1 with SMTP id i1mr26628388qkd.195.1510070688804; Tue, 07 Nov 2017 08:04:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.53.23 with HTTP; Tue, 7 Nov 2017 08:04:48 -0800 (PST) In-Reply-To: References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830125950.mcp34sddcp6c757t@ivaldir.net> <20170830143426.r53pztrybmmvfy6c@ivaldir.net> From: Cassiano Peixoto Date: Tue, 7 Nov 2017 14:04:48 -0200 Message-ID: Subject: Re: pkg issue after FreeBSD 11 upgrade To: Baptiste Daroussin Cc: Matthew Seaman , "freebsd-stable@freebsd.org" , "freebsd-ports@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Nov 2017 16:04:50 -0000 Hi Baptiste, Sorry to bother you. Did you have some time to work on this thread? Thanks. On Wed, Aug 30, 2017 at 12:46 PM, Cassiano Peixoto < peixotocassiano@gmail.com> wrote: > Thank you for your support Baptiste, I really appreciate that. > > As same as HANDLE_RC_SCRIPTS option the new one should be handled > carefully. > > Please keep us posted when it's ready. > > > On Wednesday, August 30, 2017, Baptiste Daroussin > wrote: > >> On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote: >> > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal >> > with when I need to restart a service without upgrading? Reaper >> > functionnality is a trouble for many administrators who made meta ports >> to >> > manage their servers. I really think it could be a option to be >> > enabled/disabled. Can you see this possibility? >> > >> >> Yes I could add an option to disable the reaper functionnality (and will >> probably to unblock such use case as soon as I have time to do it.) >> >> However I still think this is not the right idea :) and a better one >> could be >> found >> >> Bapt >> > From owner-freebsd-stable@freebsd.org Tue Nov 7 16:12:21 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 43721E5CB98; Tue, 7 Nov 2017 16:12:21 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::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 F068A72CA2; Tue, 7 Nov 2017 16:12:20 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x22e.google.com with SMTP id y23so15882286qkb.10; Tue, 07 Nov 2017 08:12:20 -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=GJNLEddcRFzrokh03suWc3rVP5qnw4hw47yHCOqeu+I=; b=qubb0kSLfe8rdm2evZ5DvesfH9enLwnlbv9IMtKyf1fLbI/bxrMR5kPjzy66TY/pK/ mG7xHCcJsTUjCqgUXrW8jT+ZJw7XQ0nNLGHUJ/WsavJKj+b/qH04n0v7YrrNXJAZeWyh EaCx9UEpzPtSD+iasVug5/3xv6vT4iI1CfJJP9U0q83TWh4CjUQ5t48qFJooTm4UawR6 +Es3mQUPfzUhngPxdMQoClT0zpv8cM1WWHkjTXajykXhNtqgpL4XH76soQq0VA/fqEQu xAb+FfMnQN9GJRlnVjNf1oR2CoHCHkqBBS+FQ7Z0NgILb+1o2+h33Sjc+oOaoOYc9XNw ZeLA== 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=GJNLEddcRFzrokh03suWc3rVP5qnw4hw47yHCOqeu+I=; b=qCXT3TWlCqQhKGzTo2BgqD2DLmM0y5mPFHTzFkMwhPsm/1E/220fBy+jUcBCU8SVe9 nTS4YGzq2pwU35U/WO0sO1DOq7s3azW0S5dHH+nCSFelbIM/dQN5gyb3Vff8X98aRlaM sxjhuxRZglx2Oq/rG6u27snXnlDRSJ20naXC13vFFu52K3MUXj35IMMpbTqXXpkOJKWs pXBHMd3ba2/QQpSvTIDIqw5TLA95t8LXTpBkMkY5urAu2+qh/WdSP30mcNBEwHnY8YhK mu22d5Nxp2suiCEdZiDmM3TJQbB9skUFI6VOtaDyNBB7h51oEeaeDjN1r1+HxG+DpIbX YJLA== X-Gm-Message-State: AMCzsaVoBiVj/mfMPb4UqNmbOqnsJTlXUBrzzloE/uCZ8lSzo8njAwwd y4FMWT8h3c5NJSRcBUZ4obZCfbbDDBV+YNiP8860Mg== X-Google-Smtp-Source: ABhQp+SPeSMesonJ+oWzkq1gVWL/u0OMCE+6tuendeDlEfY1/OC5ZnX8XZlpDX7z+jVqxni+6HW1xjY172vXe49L38Q= X-Received: by 10.55.127.66 with SMTP id a63mr26807670qkd.90.1510071139810; Tue, 07 Nov 2017 08:12:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.53.23 with HTTP; Tue, 7 Nov 2017 08:12:19 -0800 (PST) In-Reply-To: References: From: Cassiano Peixoto Date: Tue, 7 Nov 2017 14:12:19 -0200 Message-ID: Subject: Re: Denverton CPU on FreeBSD To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Nov 2017 16:12:21 -0000 Hi guys, I'm backing to this thread because I had no success yet. There is an issue with console boot on Intel Denverton. I've followed the instruction bellow: https://www.freebsd.org/doc/handbook/serialconsole-setup.html I tried using an IPMI card and worked fine. I don't know who is the maintainer for console code to get in touch. Can some developer work on this issue? I can help making any test needed. Thank you. On Wed, Aug 16, 2017 at 5:32 PM, Cassiano Peixoto wrote: > Hi there, > > Is someone playing with Denverton CPU On FreeBSD? > > I'm trying to use serial console on FreeBSD with Denverton CPU but doesn't > work. > > I can see the boot process but it stops and I do not have the login > prompt. My keyboard doesn't answer as well. > > I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is > working with Rangeley CPU. > > Any help is welcome. > > Thanks. > From owner-freebsd-stable@freebsd.org Tue Nov 7 16:30:34 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 816A1E5D2E8; Tue, 7 Nov 2017 16:30:34 +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 26C5B73ED5; Tue, 7 Nov 2017 16:30:33 +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 vA7GSsX2067635; Tue, 7 Nov 2017 16:28:54 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: Denverton CPU on FreeBSD From: Bob Bishop In-Reply-To: Date: Tue, 7 Nov 2017 16:28:54 +0000 Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Cassiano Peixoto X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Nov 2017 16:30:34 -0000 Hi, > On 7 Nov 2017, at 16:12, Cassiano Peixoto = wrote: >=20 > Hi guys, >=20 > I'm backing to this thread because I had no success yet. There is an = issue > with console boot on Intel Denverton. I've followed the instruction = bellow: >=20 > https://www.freebsd.org/doc/handbook/serialconsole-setup.html >=20 > I tried using an IPMI card and worked fine. >=20 > I don't know who is the maintainer for console code to get in touch. = Can > some developer work on this issue? I can help making any test needed. >=20 > Thank you. >=20 > On Wed, Aug 16, 2017 at 5:32 PM, Cassiano Peixoto = > wrote: >=20 >> Hi there, >>=20 >> Is someone playing with Denverton CPU On FreeBSD? >>=20 >> I'm trying to use serial console on FreeBSD with Denverton CPU but = doesn't >> work. >>=20 >> I can see the boot process but it stops and I do not have the login >> prompt. My keyboard doesn't answer as well. Have you set /etc/ttys entry for the serial port appropriately? = https://www.freebsd.org/doc/handbook/term.html#term-config >> I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is >> working with Rangeley CPU. Maybe BIOS initialises the serial port differently? >> Any help is welcome. >>=20 >> Thanks. >>=20 > _______________________________________________ > 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 t: +44 (0)118 940 1243 rb@gid.co.uk m: +44 (0)783 626 4518 From owner-freebsd-stable@freebsd.org Tue Nov 7 17:27:42 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 AB204E5EA9D; Tue, 7 Nov 2017 17:27:42 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::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 6D02378D5B; Tue, 7 Nov 2017 17:27:42 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id y23so16221338qkb.10; Tue, 07 Nov 2017 09:27:42 -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=p2QACPKg2J4SR7NmzHtMyjq8Jngojrm7QOh1w8Gf0rw=; b=mhsHpxE5oEhmQMe6Jm8fznx4qA5bX9mswyOqatENDzytAjpsWG1rJp/13rbZ2sXI3l 7+24P3JhH1dfxWXhY69VC79lB3ogdqE6YJXuVtvKNhVJrF6E3MgQJru6UBBpXwb1w8vh qOg/JBLqWVqzZVfLtdDftuAKqvs6i3fXpljiY0EXjx+5yxeH761nqvvuWmUBEPBrsxm2 XkLMxDGtI10Jb0bVgUukcPwiOTTRUNfdYjIiHzJbK7sBxtdJz99XdMtjAywWGe5AWl0i 7pP1jpLQU3gvM8St0OVnIT04NwMXe/BCpEYeACyA0akYbkMlDf6w3B/qEr/66W8sy305 UjXw== 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=p2QACPKg2J4SR7NmzHtMyjq8Jngojrm7QOh1w8Gf0rw=; b=ovQgDKAaDsax0u5qRLLEy+KmfdBhMtPU642RalgAb6JhWvfVw3Q/7Q+4Jqt6WPZ/2j +rRqVZGb+iS8vKsQDF4THHG2Tkr4RwMdP06xZ4Q+//x4cmjcXV78Ncpc0ZKIMJ369hDF PtPI0nleYdisBYpwx0lK7VF1lVU12lp3zEj5w5F7V3fV6PIMTdHguWaoT8+EX5MeIf3h wYmgoLll/EsmaSGGe3kVm6Xq75h68Wn01miBuGuaGcHc3ZYSzlGNX60p8SULyj3HFOlP CRgH/0JBavdjVGq48WzD/7mNxa/RAXtxJXJaJvM+LQdg5cKM2BzeuyalRA0MbbuJODst ghGQ== X-Gm-Message-State: AMCzsaV3bp7gjHsn7xXljbLtKqA/3I8PExLYkDHPqcwTKZZpbK750kXO ZIk/EbNakZRWhtkisDODcE7aXWCU5rua5WtWSqw= X-Google-Smtp-Source: ABhQp+Qp0q8ziTTLVqjvNmrTzdDcKChFwYBLxHC4h9+lwIHhjNQchc6+KQlvo9O9JXYDUJ3E0lhhNSVNNtnkg6eCF3I= X-Received: by 10.55.127.66 with SMTP id a63mr27186033qkd.90.1510075661483; Tue, 07 Nov 2017 09:27:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.53.23 with HTTP; Tue, 7 Nov 2017 09:27:41 -0800 (PST) In-Reply-To: References: From: Cassiano Peixoto Date: Tue, 7 Nov 2017 15:27:41 -0200 Message-ID: Subject: Re: Denverton CPU on FreeBSD To: Bob Bishop Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Nov 2017 17:27:42 -0000 Hi Bob, Yes I've tried this configuration with no success as well. :( On Tue, Nov 7, 2017 at 2:28 PM, Bob Bishop wrote: > Hi, > > > On 7 Nov 2017, at 16:12, Cassiano Peixoto > wrote: > > > > Hi guys, > > > > I'm backing to this thread because I had no success yet. There is an > issue > > with console boot on Intel Denverton. I've followed the instruction > bellow: > > > > https://www.freebsd.org/doc/handbook/serialconsole-setup.html > > > > I tried using an IPMI card and worked fine. > > > > I don't know who is the maintainer for console code to get in touch. Can > > some developer work on this issue? I can help making any test needed. > > > > Thank you. > > > > On Wed, Aug 16, 2017 at 5:32 PM, Cassiano Peixoto < > peixotocassiano@gmail.com > >> wrote: > > > >> Hi there, > >> > >> Is someone playing with Denverton CPU On FreeBSD? > >> > >> I'm trying to use serial console on FreeBSD with Denverton CPU but > doesn't > >> work. > >> > >> I can see the boot process but it stops and I do not have the login > >> prompt. My keyboard doesn't answer as well. > > Have you set /etc/ttys entry for the serial port appropriately? > https://www.freebsd.org/doc/handbook/term.html#term-config > > >> I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is > >> working with Rangeley CPU. > > Maybe BIOS initialises the serial port differently? > > >> Any help is welcome. > >> > >> Thanks. > >> > > _______________________________________________ > > 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 > " > > > > > -- > Bob Bishop t: +44 (0)118 940 1243 > rb@gid.co.uk m: +44 (0)783 626 4518 > > > > > > From owner-freebsd-stable@freebsd.org Thu Nov 9 08:58: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 E7455E6F447 for ; Thu, 9 Nov 2017 08:58:43 +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 ABBC97DE25 for ; Thu, 9 Nov 2017 08:58:43 +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=1510217922; h=Content-Type: Cc: To: Subject: Message-ID: Date: From: MIME-Version: Sender; bh=4EZCWQZR8ozUq/HN40SLRzUefyJ65m8o3aiXlyeCuFw=; b=VW9gIACv4zLXxNY9I7Ym8FCXK1yk3NIivH1DDkGb+M/PWZhz73PXXW6ZELxpoB1cyoku75sm DnlC//Ab30u0DDIuwoXb1kY2H7wsShk6iFnW2e3fnMoW7y6a7M3S23Th4X991224VKtFLhub FB2NiVTZ6+3wCETzft3n3P2UTQE= Sender: zy@miator.net X-Mailgun-Sending-Ip: 184.173.153.196 X-Mailgun-Sid: WyJkZjBjNyIsICJmcmVlYnNkLXN0YWJsZUBmcmVlYnNkLm9yZyIsICI2OTExMCJd Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) by mxa.mailgun.org with ESMTP id 5a04178f.7f02541c8b30-smtp-out-n02; Thu, 09 Nov 2017 08:53:35 -0000 (UTC) Received: by mail-qk0-f181.google.com with SMTP id x195so6713493qkb.12; Thu, 09 Nov 2017 00:53:35 -0800 (PST) X-Gm-Message-State: AJaThX7XDnCwAwK+i1QZa5mVynJz8PSJCtf8TIOEzxfN68GYD5h9GYrW vur3PH9y/olZaOr4Ar4hvDvwlcmOz8p8B5U3YGY= X-Google-Smtp-Source: AGs4zMbfvPNIq6mnIha+hr6ia6sinERu6SDTsZ0b4uD7ppHgzKcXV03g0yGCCjD6SuFsZ73OWurvODXn0r9wlm45whA= X-Received: by 10.55.26.90 with SMTP id a87mr4812896qka.184.1510217615573; Thu, 09 Nov 2017 00:53:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.50.38 with HTTP; Thu, 9 Nov 2017 00:53:34 -0800 (PST) From: Zhihao Yuan Date: Thu, 9 Nov 2017 02:53:34 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: iwn crashing on 11n network To: FreeBSD-STABLE Mailing List , freebsd-wireless@freebsd.org Cc: avos@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 09 Nov 2017 08:58:44 -0000 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. This card used to work in FreeBSD, where 11n is not supported, so it connects to an 11a network instead. Now it connects to nothing, even after -ht -- which will causes the whole system to reboot after lots of disconnects. -- Zhihao Yuan, ID lichray The best way to predict the future is to invent it. _______________________________________________ From owner-freebsd-stable@freebsd.org Thu Nov 9 20:17:55 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 D0345E5AB9D; Thu, 9 Nov 2017 20:17:55 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 6629B76B9D; Thu, 9 Nov 2017 20:17:54 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.19.110] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 833AA8E1; Thu, 9 Nov 2017 23:17:48 +0300 (MSK) To: "freebsd-net@freebsd.org" , freebsd-stable Reply-To: lev@FreeBSD.org From: Lev Serebryakov Subject: =?UTF-8?Q?Intel_I210_=28igb=29_sometimes_consume_all_CPU_on_not-so-?= =?UTF-8?Q?big_traffic_=e2=80=94_need_help!?= Organization: FreeBSD Message-ID: <8590fa5d-fd06-90c6-8d3e-34c155423720@FreeBSD.org> Date: Thu, 9 Nov 2017 23:17:43 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="5an80dmX23Xem9Cn9rD5b6lv1DxQnFTNJ" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 09 Nov 2017 20:17:55 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5an80dmX23Xem9Cn9rD5b6lv1DxQnFTNJ Content-Type: multipart/mixed; boundary="lSrC2sueveAJMard5bJ9FL02Uqoib6CAM"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: "freebsd-net@freebsd.org" , freebsd-stable Message-ID: <8590fa5d-fd06-90c6-8d3e-34c155423720@FreeBSD.org> Subject: =?UTF-8?Q?Intel_I210_=28igb=29_sometimes_consume_all_CPU_on_not-so-?= =?UTF-8?Q?big_traffic_=e2=80=94_need_help!?= --lSrC2sueveAJMard5bJ9FL02Uqoib6CAM Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable I still have problems with my E-1220v3 server equipped with Intel I210 adapter. It can not be loaded more than 100Mbit/s because it is connection to internet. But sometimes four interrupt threads "intr{irqXXX: igb0:que Y}" consume 100% CPU. Interrupt rate is very modest: % vmstat -i interrupt total rate =2E.. irq276: igb0:que 0 851899713 1193 irq277: igb0:que 1 907338150 1271 irq278: igb0:que 2 907538207 1271 irq279: igb0:que 3 768217584 1076 irq280: igb0:link 2 0 % But CPU consumption is 90-100% per thread: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root -92 - 0K 544K CPU2 2 146:22 98.30% intr{irq278: igb0:que 2} 11 root -92 - 0K 544K WAIT 0 178:18 81.55% intr{irq276: igb0:que 0} 11 root -92 - 0K 544K WAIT 1 135:34 77.77% intr{irq277: igb0:que 1} 11 root -92 - 0K 544K CPU3 3 138:57 67.50% intr{irq279: igb0:que 3} procstat -ak looks suspicious: % sudo procstat -ak | grep igb0:que 11 100056 intr irq276: igb0:que 0 vm_page_scan_contig vm_phys_scan_contig vm_page_reclaim_contig kmem_alloc_contig mbuf_jumbo_alloc keg_alloc_slab keg_fetch_slab zone_fetch_slab zone_import zone_alloc_item uma_zalloc_arg m_getjcl igb_refresh_mbufs igb_rxeof igb_msix_que intr_event_execute_handlers ithread_loop fork_exit= 11 100058 intr irq277: igb0:que 1 mi_switch ithread_loop fork_exit fork_trampoline 11 100060 intr irq278: igb0:que 2 mi_switch ithread_loop fork_exit fork_trampoline 11 100062 intr irq279: igb0:que 3 mi_switch ithread_loop fork_exit fork_trampoline % --=20 // Lev Serebryakov --lSrC2sueveAJMard5bJ9FL02Uqoib6CAM-- --5an80dmX23Xem9Cn9rD5b6lv1DxQnFTNJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAloEt+dfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R48OQhAAldC1+7npWwVeT2eDrZnfO3RP5mcfww5x7RNBj2UR8GPEBN++esw6/jlk 1fVDu0uNcrlZPu6UTdS6Xl+3T99YcFGzolGWOKIYk4ZFvsigDmX2yYE9L+QCNk4a FyEo483MSGDy/o48BU4AcfpeI0vTtEA2lA5VWE8rPJbTVrZ65V0vB34lZQ3++gvT is0ETrU3UbpEdyTtSeygUSARsJ+OXqwO8uMU+KAxe12nCKy9yd2KeDsCSmRu49Kj c1N22VIeQbMEaNVFc+12VC7ZG2YADZPhqbnxFEck4y/u8eeKDp8R0dGuBe/4JwFD eF/vHxF61rIczujd3CiTskW78KR2wmLdIRUgv1YcR61Ud6ZWUTU8mJF1YAIT0vEy QXm9rxvNlAcb+yisG4XXHjdzYyVfGo3AWpIXW5uvWoC5gSh025KTvn8JUv3N7YUT sex+8+1y/ejMWsU/ZWpjh6ooaTKhcUQSAnx7lX3HxesmGFxdJOO40ld+acpowdbk vbnik4ycQODFe8+/KT7fdQngutotJ7ifFKhr2ivFlw9VXqE18X08hrJgA247J3mW fwiTTi9gPzaGy+QjZ29kZKp9/c6QpDjV1cISrdZ6XzzYTpS7s2YB3RnIGvThqOQI 4cTNCOKnZ4qn2Ml6Xq483OiKStFTN3aGd+Pd4GihWg6IozGkpIE= =RYSJ -----END PGP SIGNATURE----- --5an80dmX23Xem9Cn9rD5b6lv1DxQnFTNJ-- From owner-freebsd-stable@freebsd.org Thu Nov 9 20:23:49 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 D4487E5AFD8 for ; Thu, 9 Nov 2017 20:23:49 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 8C89677151 for ; Thu, 9 Nov 2017 20:23:49 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: by mail-qt0-x234.google.com with SMTP id f8so9298502qta.5 for ; Thu, 09 Nov 2017 12:23:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tenebras-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3FBvZ0Wl9BtcsBvEuS59W0QcpO9WfhJ1hXAPGSVcBEA=; b=ChwD1vSsgnp38x/baIRF9ErS9U+8OrMpN+ohKSDdv6fudtebkBw6sMgfPTU2uzavoe zA+LplQ3nX131L2+uetSA3qF94tTLfMveIFu1MaHVTWOWaVLTBhmCgUQZwZrelXteJKe cMcxRCKeXVrj1QCsEYXFIEGxIwWk1FEb2GFQcbytLRcf55CiQFiwlaxoN7ctZ/qglwb4 VVxVXBAOBX9tIPwTX/HXiK0G97UBmjUX6cR98Y0qT1SoPqFwK8Owzo0HqWDPTmLB8wy5 WRgLMcdaQd2FeYkl696cfHTrT5j/to5Dr4X5cb6wjAm2ZOR6gNY3z4ZNB+vWqAl1BRbI /cyg== 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=3FBvZ0Wl9BtcsBvEuS59W0QcpO9WfhJ1hXAPGSVcBEA=; b=WYIZWPDEwt0qB6yU1d75UM6jNrw7PmhHKt5u7HFxkdukInzTM/HEbK0RqkoqTUAC+s 1G5OJJdWmHs2BjlVQ0P9ZQjjTJ5gq6cqSeBQXBU3clJ+c/XrDfvom8GshSm1xPBOtnw2 OX1wdyf7JYFvyaUw+OsoRj0EVPmVr4GKVBwoUmtbM/pmQV3Uvk/pkHm/nuSAReXoviSr muX+fSVdYYTiCxyN8Kw/1QhUAdVG+Pybsf+d+Ml5iVVZsJRvFAz7YdoU/+Y4Cxvxy6XS rL1zHz9OtzdTVm7Y4rgyk00y9mp+ir200Dy7XSjKi4xEMaKPtnKpE7u0llAJx07KeGmx +v5A== X-Gm-Message-State: AJaThX6xoXc63n1uzhxxi0TVSeHf9ntYmV7PCqcTiyWmVE2HWuMH4SE4 S6S0lzez6hs/KnMJiARFosnoBaDmOkAoVU8JBumGIQ== X-Google-Smtp-Source: AGs4zMaT5GtZcDtVH3bY4o84XU6BQad3lm9pOcQK9jihXQCGyNEBqWzo5PAQli11iDc/xdwZhqgyVMeOZORk6sbOlko= X-Received: by 10.200.9.73 with SMTP id z9mr2788548qth.43.1510259028373; Thu, 09 Nov 2017 12:23:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.46.131 with HTTP; Thu, 9 Nov 2017 12:23:47 -0800 (PST) In-Reply-To: <8590fa5d-fd06-90c6-8d3e-34c155423720@FreeBSD.org> References: <8590fa5d-fd06-90c6-8d3e-34c155423720@FreeBSD.org> From: Michael Sierchio Date: Thu, 9 Nov 2017 12:23:47 -0800 Message-ID: Subject: =?UTF-8?Q?Re=3A_Intel_I210_=28igb=29_sometimes_consume_all_CPU_on_no?= =?UTF-8?Q?t=2Dso=2Dbig_traffic_=E2=80=94_need_help=21?= To: lev@freebsd.org Cc: "freebsd-net@freebsd.org" , freebsd-stable Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 09 Nov 2017 20:23:49 -0000 Is device polling enabled? - M On Thu, Nov 9, 2017 at 12:17 PM, Lev Serebryakov wrote: > > I still have problems with my E-1220v3 server equipped with Intel I210 > adapter. It can not be loaded more than 100Mbit/s because it is > connection to internet. > > But sometimes four interrupt threads "intr{irqXXX: igb0:que Y}" consume > 100% CPU. Interrupt rate is very modest: > > % vmstat -i > interrupt total rate > ... > irq276: igb0:que 0 851899713 1193 > irq277: igb0:que 1 907338150 1271 > irq278: igb0:que 2 907538207 1271 > irq279: igb0:que 3 768217584 1076 > irq280: igb0:link 2 0 > % > > But CPU consumption is 90-100% per thread: > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 11 root -92 - 0K 544K CPU2 2 146:22 98.30% intr{irq278: > igb0:que 2} > 11 root -92 - 0K 544K WAIT 0 178:18 81.55% intr{irq276: > igb0:que 0} > 11 root -92 - 0K 544K WAIT 1 135:34 77.77% intr{irq277: > igb0:que 1} > 11 root -92 - 0K 544K CPU3 3 138:57 67.50% intr{irq279: > igb0:que 3} > > procstat -ak looks suspicious: > > % sudo procstat -ak | grep igb0:que > 11 100056 intr irq276: igb0:que 0 vm_page_scan_contig > vm_phys_scan_contig vm_page_reclaim_contig kmem_alloc_contig > mbuf_jumbo_alloc keg_alloc_slab keg_fetch_slab zone_fetch_slab > zone_import zone_alloc_item uma_zalloc_arg m_getjcl igb_refresh_mbufs > igb_rxeof igb_msix_que intr_event_execute_handlers ithread_loop fork_exit > 11 100058 intr irq277: igb0:que 1 mi_switch ithread_loop fork_exit > fork_trampoline > 11 100060 intr irq278: igb0:que 2 mi_switch ithread_loop fork_exit > fork_trampoline > 11 100062 intr irq279: igb0:que 3 mi_switch ithread_loop fork_exit > fork_trampoline > % > > -- > // Lev Serebryakov > > --=20 "Well," Brahma said, "even after ten thousand explanations, a fool is no wiser, but an intelligent person requires only two thousand five hundred." - The Mah=C4=81bh=C4=81rata From owner-freebsd-stable@freebsd.org Thu Nov 9 20:33: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 562C1E5BA48; Thu, 9 Nov 2017 20:33:45 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [148.251.9.81]) by mx1.freebsd.org (Postfix) with ESMTP id 0336777B0D; Thu, 9 Nov 2017 20:33:44 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.19.110] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 5D99F8ED; Thu, 9 Nov 2017 23:33:43 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: =?UTF-8?Q?Re:_Intel_I210_=28igb=29_sometimes_consume_all_CPU_on_not?= =?UTF-8?Q?-so-big_traffic_=e2=80=94_need_help!?= To: Michael Sierchio Cc: "freebsd-net@freebsd.org" , freebsd-stable References: <8590fa5d-fd06-90c6-8d3e-34c155423720@FreeBSD.org> From: Lev Serebryakov Organization: FreeBSD Message-ID: <913d5386-9d53-3c32-e109-f7b687b54262@FreeBSD.org> Date: Thu, 9 Nov 2017 23:33:42 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ckvwnbsg6XMXlPJw98fXgpDhRiwL7U90m" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 09 Nov 2017 20:33:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ckvwnbsg6XMXlPJw98fXgpDhRiwL7U90m Content-Type: multipart/mixed; boundary="AWjBJl8C2hfgvwGi9cwl7DAOCw8fDiaeS"; protected-headers="v1" From: Lev Serebryakov Reply-To: lev@FreeBSD.org To: Michael Sierchio Cc: "freebsd-net@freebsd.org" , freebsd-stable Message-ID: <913d5386-9d53-3c32-e109-f7b687b54262@FreeBSD.org> Subject: =?UTF-8?Q?Re:_Intel_I210_=28igb=29_sometimes_consume_all_CPU_on_not?= =?UTF-8?Q?-so-big_traffic_=e2=80=94_need_help!?= References: <8590fa5d-fd06-90c6-8d3e-34c155423720@FreeBSD.org> In-Reply-To: --AWjBJl8C2hfgvwGi9cwl7DAOCw8fDiaeS Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 09.11.2017 23:23, Michael Sierchio wrote: Nope. > Is device polling enabled? >=20 > - M >=20 > On Thu, Nov 9, 2017 at 12:17 PM, Lev Serebryakov wrot= e: >=20 >> >> I still have problems with my E-1220v3 server equipped with Intel I21= 0 >> adapter. It can not be loaded more than 100Mbit/s because it is >> connection to internet. >> >> But sometimes four interrupt threads "intr{irqXXX: igb0:que Y}" consu= me >> 100% CPU. Interrupt rate is very modest: >> >> % vmstat -i >> interrupt total rate >> ... >> irq276: igb0:que 0 851899713 1193 >> irq277: igb0:que 1 907338150 1271 >> irq278: igb0:que 2 907538207 1271 >> irq279: igb0:que 3 768217584 1076 >> irq280: igb0:link 2 0 >> % >> >> But CPU consumption is 90-100% per thread: >> >> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND >> 11 root -92 - 0K 544K CPU2 2 146:22 98.30% intr{irq278: >> igb0:que 2} >> 11 root -92 - 0K 544K WAIT 0 178:18 81.55% intr{irq276: >> igb0:que 0} >> 11 root -92 - 0K 544K WAIT 1 135:34 77.77% intr{irq277: >> igb0:que 1} >> 11 root -92 - 0K 544K CPU3 3 138:57 67.50% intr{irq279: >> igb0:que 3} >> >> procstat -ak looks suspicious: >> >> % sudo procstat -ak | grep igb0:que >> 11 100056 intr irq276: igb0:que 0 vm_page_scan_contig >> vm_phys_scan_contig vm_page_reclaim_contig kmem_alloc_contig >> mbuf_jumbo_alloc keg_alloc_slab keg_fetch_slab zone_fetch_slab >> zone_import zone_alloc_item uma_zalloc_arg m_getjcl igb_refresh_mbufs >> igb_rxeof igb_msix_que intr_event_execute_handlers ithread_loop fork_e= xit >> 11 100058 intr irq277: igb0:que 1 mi_switch ithread_loop fork_ex= it >> fork_trampoline >> 11 100060 intr irq278: igb0:que 2 mi_switch ithread_loop fork_ex= it >> fork_trampoline >> 11 100062 intr irq279: igb0:que 3 mi_switch ithread_loop fork_ex= it >> fork_trampoline >> % >> >> -- >> // Lev Serebryakov >> >> >=20 >=20 --=20 // Lev Serebryakov --AWjBJl8C2hfgvwGi9cwl7DAOCw8fDiaeS-- --Ckvwnbsg6XMXlPJw98fXgpDhRiwL7U90m Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAloEu6ZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R4+VKRAAuVsXugJfn2BnorxxnydtIceFNinThHn1MD6OB6l8wAnU+OE+JKg3IhWg 255OWWAgyUyYPVhmpUj596JhT98VjjjAcMrYFGJ9BYO0Eb8vRhX+B4Jcp8ZI3Wtn PT+FUSWRhsQOhSdZ6wopabI2v7JwcLdidpwu1l3uy9ZPQfFHzPQphaguv1YtHUL7 8JH9wd5BqR/llCgYxRDVdd9uMTg81QGvaf6AW0tcUrIvE4t5EkeyJ0CZIuGtEtSw Sjeso00KvJk66Xo9vVCDA4yVMMr14RdwXZQlRfcTKqA3XC/ISJgm0RrkHCGQ/+k1 340zyYqZyy07vssz4BVegMFZajB+nSz5XbO1qDeISlh+AvAVwBSVibGMHgLcxHIW AUkRSL2lcRDNFrbr0oXLqkz03aLfyW9DsYjJOg3ZnXlNfWqepdsUCpjSgdUXKMya 2qUtxeGIVl8j4jWYUZAuyhaMlytfcE93pcbigq5bAEGz3PTR54ScJxroW2Ob0wP9 UJZw4MzimQYg7W/m+fBiAE5czuSdTq4RLVzqhHEAKZZkilsIH1E0J1b7cXg3CB0b Zqe5N6CMEDr92lFgeMHHY6xf52kvEsZt5dhK+SArEUwQKOH5bfDN4PIM1iRnhfW3 2wXLmmKJE6kzJ/WZ2E3RX8PTXdrfEj/Y2BVSofXjdbQDsYFfFj8= =isX7 -----END PGP SIGNATURE----- --Ckvwnbsg6XMXlPJw98fXgpDhRiwL7U90m-- From owner-freebsd-stable@freebsd.org Fri Nov 10 15:44:37 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 0A759E7086A for ; Fri, 10 Nov 2017 15:44:37 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]) (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 A19EA78756 for ; Fri, 10 Nov 2017 15:44:36 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from www.verweg.com (www@erg.verweg.com [IPv6:2a02:898:96:0:0:0:5e8e:f508]) by erg.verweg.com (8.15.2/8.15.2) with ESMTP id vAAFiNcw021237 for ; Fri, 10 Nov 2017 15:44:29 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host www@erg.verweg.com [IPv6:2a02:898:96:0:0:0:5e8e:f508] claimed to be www.verweg.com MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_bc8651b7469c654406285b0280c53d05"; micalg=pgp-sha1 Date: Fri, 10 Nov 2017 16:44:22 +0100 From: Ruben van Staveren To: freebsd-stable@freebsd.org Subject: ZFS arc behaviour different after upgrading to 10.4 Organization: Verweg dot Com Message-ID: X-Sender: ruben@verweg.com User-Agent: Roundcube Webmail/1.3.1 X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on erg.verweg.com X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.6.2 (erg.verweg.com [0.0.0.0]); Fri, 10 Nov 2017 15:44:32 +0000 (UTC) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Nov 2017 15:44:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_bc8651b7469c654406285b0280c53d05 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi list, I noticed that the ZFS ARC is behaving differently with 10.4, giving me a much worser cache effeciency as with 10.3 The following grafana/telefraph graph illustrates this as follows. https://snapshot.raintank.io/dashboard/snapshot/X18wHgmqFnMccEYlnbwgQtYgLIZ4oQLU?panelId=65061&fullscreen&orgId=2 Left I'm still running 10.3, Started some maintenance (binary update with freebsd-update) at 12:36 and booted into 10.4 at 14:34. Since then the ARC hits/misses are much more irregular. Disabling compression (apparently also introduced in 10.4) didn't help that much with regards to the pattern although it did shave off some load of the system. Any thoughts on the changed behaviour? Cheers, Ruben --=_bc8651b7469c654406285b0280c53d05 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=801 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJaBclWAAoJEIhva+zUd6k/vx4P/AypEQMZagypVQjUoefM3cKg oUDTTJD+VbifuFENNjLo9lCXtaCw/dDKz17K+1ES/QgIdpifIMeGbLuKHjAot644 9waZGrHrz2hcH0FZJDDTGWeX14oOvWc6NuhyTiM+8DyRjz1ubd1mSZzn25RFWiuG R5J2c83ciy1/VeLSh4wsLEYKbu9VsBaZehwOdVcV4tGqqao4ji4dFcqp9Heupu0h Rof7EBOkguaNm/ArrFjqWPig/w2Yys2c7WbXy453zE49Je9LGN3JhjehZb0008JG XrBk3Pyc0FicLDAwTx/4joFVzlFVOBdoI9m5ETfemlaFMMaKG9ci18w7xrZeA7On yQZsgn7yVY/yCAI8hhXQ9TYLnlMLkkTJcsj9avnMCXt6IgRBhHkGJXluNBeV2Ofp sWhwraBeA2ECqbG2JRe1TrhlRk+mw+NgUVw89PI0vcMtlxShQ/tLAxDsO5vBn3GA 971JRDD0SDnByGg1VLLoOODEpIXOh5f+1WciaFHFrPail3Ri7N09hJveFT/bktVv RtZe3LO6x6ICpxVJsKse5xKXYbtp07GgZ2dzNxNC9L7xzEjJPdV529Vp6MFyV15q /BsCvvlZR6g+23mMIbBDzgJdWf9K1dFPHPmCWU3i+rhV4QA8rX7tQGgH6kLCLXO4 l0XyG8Zows/RskkXGNuZ =Yewv -----END PGP SIGNATURE----- --=_bc8651b7469c654406285b0280c53d05-- From owner-freebsd-stable@freebsd.org Fri Nov 10 21:16:07 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 A59B1E50590 for ; Fri, 10 Nov 2017 21:16:07 +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 9413F3ADB for ; Fri, 10 Nov 2017 21:16:07 +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 vAALG7EJ066348 for ; Fri, 10 Nov 2017 21:16:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221146] [LAGG] Problem with second laggport Date: Fri, 10 Nov 2017 21:16:07 +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: attachments.created 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.23 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, 10 Nov 2017 21:16:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 --- Comment #17 from Sean Bruno --- Created attachment 187911 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187911&action= =3Dedit Move hardware notification of driver readiness to end of attach. Current. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Fri Nov 10 21:16:49 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 E13A5E50701 for ; Fri, 10 Nov 2017 21:16:49 +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 CEEE83DAB for ; Fri, 10 Nov 2017 21:16:49 +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 vAALGni5067197 for ; Fri, 10 Nov 2017 21:16:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221146] [LAGG] Problem with second laggport Date: Fri, 10 Nov 2017 21:16:49 +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: attachments.created 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.23 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, 10 Nov 2017 21:16:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 --- Comment #18 from Sean Bruno --- Created attachment 187912 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187912&action= =3Dedit Move hardware notification of driver readiness to end of attach. Stable/11. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Fri Nov 10 21:18: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 25622E508C9 for ; Fri, 10 Nov 2017 21:18:01 +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 0AFEE632A7 for ; Fri, 10 Nov 2017 21:17:59 +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 vAALHwiR068706 for ; Fri, 10 Nov 2017 21:17:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221146] [LAGG] Problem with second laggport Date: Fri, 10 Nov 2017 21:17:59 +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.23 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, 10 Nov 2017 21:18:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 --- Comment #19 from Sean Bruno --- I'm having a heck of a time reproducing this bug, as it seems like a race in the attach startup. If you are seeing this problem on Current or Stable/11, I've attached an attempt to fix this, please report back if it helps or does nothing. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Fri Nov 10 21:18:37 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 8FCA1E509CC for ; Fri, 10 Nov 2017 21:18:37 +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 6D533633EA for ; Fri, 10 Nov 2017 21:18:37 +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 vAALIZB5069481 for ; Fri, 10 Nov 2017 21:18:37 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: Fri, 10 Nov 2017 21:18:36 +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: short_desc 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.23 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, 10 Nov 2017 21:18:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221146 Sean Bruno changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[LAGG] Problem with second |[ixgbe] Problem with second |laggport |laggport --=20 You are receiving this mail because: You are on the CC list for the bug.=