Hi Robert, Since the uptime of that machine is important, this might be kind of tricky, but we can still collect logs on the troublesome kernel with an extra step. Once you've booted into the kernel where networking doesn't work, the report can be generated and saved locally. Then you can boot back into the 4.18 kernel and submit the report to this bug [1].
My hope is that the logs might contain some clues which will help us zero in on the regression without too much kernel testing churn. If that's not the case, bisection to find the commit that introduced this regression looks like it could take around 15 steps to bisect and drill down on the regression. [1] See step #2 here: https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_when_offline_or_using_a_headless_setup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828666 Title: Kernels 5.0.0 and later networking does not work on i7-6850k on Asus X99A motherboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828666/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
