No, if you take a look at the link I posted (that particular message, not the rest of the forum topic or related bug report), you will se that the same exact thing occurs on a system without this Intel driver.
Probably you're right. I think I missed this part of the log.
I now have a system without e1000, but it's still behaving the same way. In fact, it's currently using the bnxt driver. I'm ready to bet that if I use another NIC with a different driver, the same kernel traces will show up. I'm not saying xt_geoip is the culprit. I just need to get it out of the way for now so the kernel isn't tainted.
Nevertheless, I wish you luck and although it will probably be a miserable consolation for you, on Linux Slackware with the kernel series 5.4 I have no such errors and everything works perfectly fast. Cheers, Witek _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
