Date: Fri, 19 Jan 2018 10:02:04 +0100 From: "Bradley T. Hughes" <bhughes@freebsd.org> To: Colin Percival <cperciva@tarsnap.com> Cc: "Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com>, "freebsd-cloud@freebsd.org" <freebsd-cloud@freebsd.org>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Eric Joyner <erj@FreeBSD.org> Subject: Re: Panic with recent -CURRENT kernel in EC2 Message-ID: <551A3441-609F-49BA-841B-2040E14D411C@freebsd.org> In-Reply-To: <01000160ec74f91e-2181241b-7d3f-4740-88d5-3b0559cecd09-000000@email.amazonses.com> References: <E708396E-B987-4B1A-A373-101B2B62CB64@freebsd.org> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 12 Jan 2018, at 23:19, Colin Percival <cperciva@tarsnap.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551A3441-609F-49BA-841B-2040E14D411C>