USN-3405-1 kernel cause kernel panic when using mandos

[KayNettle]

When mandos is installed, kernel panics and doesn't get password from mandos server. Since it happens so early in the boot, the panic isn't in the logs. On machine that don't have mandos installed, kernel boots fine. The linux-image-4.4.0-92-generic kernel works fine.

sorry, I had to say I didn't know which package is was in order to submit the bug report, it's linux-image-4.4.0-93-generic.

[KayNettle (pkn)]

I grabbed the newest mandos sources, 1.7.16, and the client doesn't kernel panic, but I get no response from the server. I'll see if I can find a spare machine to set up as a mandos 1.7.16 server. I'd rather not have to build .debs for the newer version, but we can't stay 4.4.0-92 kernel forever and we LOTS of machines that we are required to encrypt.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1713770/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1713770

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.84

[KayNettle (pkn)]

Sorry everyone, this is a mandos problem and it's in universe, so I shouldn't have reported the problem here. Building a 1.7.16 mandos-client package fixed my issue.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.]