(In reply to comment #2 above) I do not recall that this was seen immediately after an update. The machine has been running 14.04 (upgraded from 12.04) almost since 14.04 was released.
The anomaly was noticed only by chance; I was browsing the logs for other information and simply happened to get curious about that particular line, then discovered just how curious the line was on its own. I can not run alternate configurations or test kernels on this installation without destabilizing the system configuration beyond my risk tolerance. However, what I might be able to do is set up another VM and install another instance of 14.04 and then test it with the Mainline kernel. But I don't know enough about selecting versions to know if I'm getting the 14.04 that should exhibit the problem (is there only one rev of 14.04? if not, which should I start with to best replicate what I have now? to what level of update? Is that determinable from the data I've already uploaded?). Could you take a look and post a link to the proper Ubuntu config that I can use as a baseline in a clean VM, and then I'll see if the bug is there, and if it is, then I'll use the link you have provided to check the mainline kernel also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581890 Title: Boot registers protocol family 40, which is not in configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581890/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
