CPU: 2 PID: 22 Comm: ksoftirqd/2 Not tainted 4.14.11 #3 BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 If helpful I could also run tests on HP ProLiant Gen9 which has different NICs I can, of course, provide further information (CPU, NIC, kernel config, more The bug is 100% reproducible on the Intel Atom machine from the log below andĪlso on a HP ProLiant Gen6 (also igb driver). * the top 6 entries of the call trace are the same every time the systemĬrashes, the other entries differ sometimes

* setting affinity of eth0 queues to CPU 1 and affinity of eth1 queues to CPUĢ is broken and seems to always trigger the bug on CPU 1 Work fine (running stable for more than 1 day now) * setting affinity for all queues of both interfaces to the same CPU seems to * all affinities set to default ff is broken * SMP Affinity for IRQs of the NICs Rx/Tx queues (/proc/irq/$IRQ/smp_affinity) Large file from the HTTP server, disconnect and after a random delay repeat eth0 connects to an infrastructure running anĭuring my tests these roadwarriors connect to the gateway, sometimes download a

The affected machine has 2 active ethernet interfaces (igb driver) and acts asĪ VPN gateway running strongswan. I tried 4.14.3 initially which did not workĪnyone has an idea what is happening here?

I'm running into a NULL pointer dereference after updating from Linux 4.1.6 toĤ.14.11 (see kernel log below). ` (2 more replies) 0 siblings, 3 replies 31+ messages in threadįrom: Tobias Hommel 21:13 UTC ( / raw) BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup All of help / color / mirror / Atom feed * BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup 21:13 Tobias Hommel

Komplete keyboard a61