[TOPICADJUST:] if_lagg(4)+if_vlan(4) panic: sleeping in an epoch section (igb, e1000_82575, actiall 82576 in use)

[Harry Schmalzbauer]

Am 08.05.2018 um 11:52 schrieb Kevin Bowling:
> On Tue, May 8, 2018 at 2:43 AM, Harry Schmalzbauer <freebsd at omnilan.de> wrote:
>> Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:26 (localtime):
>>> iflib in stable/11 only affects bnxt at this time.
>>>
>>> You should try out HEAD and let us know for the rest of your questions.
>>
>> Ic, sorry for the noise – should have read the commits before wasting
>> others' time :-(
>>
>> Thanks for your help, but I can only briefly test hartwell and kawela
>> (82574, Desktop 1gE and 82576, ET2 dual Server 1gE) and see how much
>> queues they use, since I don't run -current on anything productive and
>> spare time is even much more limited than spare machines ;-)
>> Will find out who many queues i217 should provide as soon as possible
>> and if it's more than one, I'll file a PR.
>>
>> But if the simple iflib/hw-support test with kawela+hartwell helps I'm
>> happy to do.
> 
> At this point it would be helpful, we think e1000 is nearing pretty
> good shape and I need to become familiar with any outstanding bugs.

Still refering your old reply:
Please see new bug report related to e1000 and iflib, while this one 
might have it's roots in if_lagg(4)...
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232362

Thanks,

-harry