> On 19 Jan 2018, at 10:02, Bradley T. Hughes wrote:
>
>> On 12 Jan 2018, at 23:19, Colin Percival wrote:
>>
>> On 01/12/18 08:16, Pieper, Jeffrey E wrote:
>>> Hrm…
>>>
taskqgroup_attach_cpu: setaffinity failed: 22
taskqgroup_attach_cpu: setaffinity failed: 22
>>>
>>> Is this a fre
> On 12 Jan 2018, at 23:19, Colin Percival wrote:
>
> On 01/12/18 08:16, Pieper, Jeffrey E wrote:
>> Hrm…
>>
>>> taskqgroup_attach_cpu: setaffinity failed: 22
>>> taskqgroup_attach_cpu: setaffinity failed: 22
>>
>> Is this a fresh snapshot? That should have been fixed in
>> https://svnweb.fre
On 01/12/18 08:16, Pieper, Jeffrey E wrote:
> Hrm…
>
>> taskqgroup_attach_cpu: setaffinity failed: 22
>> taskqgroup_attach_cpu: setaffinity failed: 22
>
> Is this a fresh snapshot? That should have been fixed in
> https://svnweb.freebsd.org/base?view=revision&revision=327013 . Can you
> please fi
Hrm…
> taskqgroup_attach_cpu: setaffinity failed: 22
> taskqgroup_attach_cpu: setaffinity failed: 22
Is this a fresh snapshot? That should have been fixed in
https://svnweb.freebsd.org/base?view=revision&revision=327013 . Can you please
file a bug on this? This looks like an iflib issue.
Than
This sounds like it may be related to r327031, which make ixgbe (and thus ixv)
use iflib... maybe erj@ will have some ideas here?
In case it helps, dhclient sets the MTU, which in the past has caused
problems due to drivers resetting -- the fact that sys_ioctl is ending
up in iflib_init_locked mak
(Cross-posting to -net, but I'm not subscribed there... yet)
I was wondering if anyone else has experienced this panic when dhclient tries
to get an IP address after booting a recent 12.0-CURRENT kernel? Using the
12.0-CURRENT AMI from early November works, but with the latest snapshot or
when
