From owner-freebsd-net@freebsd.org Fri Jan 19 09:02:09 2018 Return-Path: Delivered-To: freebsd-net@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 815A8ECBE0E; Fri, 19 Jan 2018 09:02:09 +0000 (UTC) (envelope-from bhughes@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 5359279039; Fri, 19 Jan 2018 09:02:08 +0000 (UTC) (envelope-from bhughes@freebsd.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4D7D420DED; Fri, 19 Jan 2018 04:02:07 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 19 Jan 2018 04:02:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=pNoaOH 8hCvQoGbe7JmXmMmbbCzAZZSqzVbnbuH1aVDE=; b=cZLpojnRblSMiXtqWDoMnM evAPVy22JciSlMvmb/rApwKsQig8P5ylOoBPQjGQnIr1gRED2vB76YK+tGE2ILMx qSmO0go1bLvRJndXtetJdhsF1A6TJmYi/4PK2gjlFiTmscCJC9pdDfbWVrXfUQZP cwJ6MjDgKtXSw+ver7drUjkhro/CaZW5KM4DYvWByLM/BM+W6QKV5TzrUTVOr3Ol UkNoew7P4dJI92RzaHsUsz3kUf412Zki2vcrcFfOG3/FdOMA4jV4GydGFMWY/D0Q Ks8fuDPY6ALZJnmDp5m1NZA1vFXeTfB8uX74Eq2L4q4UY9gqCyDZa6/TCQVDEd7w == X-ME-Sender: Received: from hayseed.lan (90.89-11-136.nextgentel.com [89.11.136.90]) by mail.messagingengine.com (Postfix) with ESMTPA id E519C2449D; Fri, 19 Jan 2018 04:02:05 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Panic with recent -CURRENT kernel in EC2 From: "Bradley T. Hughes" In-Reply-To: <01000160ec74f91e-2181241b-7d3f-4740-88d5-3b0559cecd09-000000@email.amazonses.com> Date: Fri, 19 Jan 2018 10:02:04 +0100 Cc: "Pieper, Jeffrey E" , "freebsd-cloud@freebsd.org" , "freebsd-net@freebsd.org" , Eric Joyner Content-Transfer-Encoding: quoted-printable Message-Id: <551A3441-609F-49BA-841B-2040E14D411C@freebsd.org> References: <01000160e9f7ae62-92937548-d46c-4687-87c0-2205119d5132-000000@email.amazonses.com> <191060CB-F1F8-4E34-8191-99EB7B28597C@intel.com> <01000160ec74f91e-2181241b-7d3f-4740-88d5-3b0559cecd09-000000@email.amazonses.com> To: Colin Percival X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 09:02:09 -0000 > On 12 Jan 2018, at 23:19, Colin Percival wrote: >=20 > On 01/12/18 08:16, Pieper, Jeffrey E wrote: >> Hrm=E2=80=A6 >>=20 >>> taskqgroup_attach_cpu: setaffinity failed: 22 >>> taskqgroup_attach_cpu: setaffinity failed: 22 >>=20 >> Is this a fresh snapshot? That should have been fixed in >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D327013 . = Can you >> please file a bug on this? This looks like an iflib issue. >=20 > I can confirm that this happens with the 12.0-CURRENT r327524 snasphot = (on a > c4.8xlarge EC2 instance, in case it matters). Indeed. I still get this with r328126 as well. I will file a PR about = it. -- Bradley T. Hughes bradleythughes@fastmail.fm