Hi Ben, Sorry, was trying to squeeze in a quick reply in between classes.
Yes, I did a dist-upgrade, and a new kernel was installed, and DKMS did run. I will try purging and reinstalling the client tonight, that should address any mismatches, yes? I'll also remove any other kernels and headers at the same time, just to be sure. Thanks, Richard On August 9, 2017 4:09:27 PM PDT, Benjamin Kaduk <ka...@mit.edu> wrote: >Hi Richard, > >Sure, but there were two other questions in my mail; could you answer >those as well? > >-Ben > >On Wed, Aug 09, 2017 at 04:08:07PM -0700, Richard Feltstykket wrote: >> Hi Ben, >> >> Yes, I have rebooted quite a few times after the upgrade, as the >machine >> becomes unresponsive to ssh logins after the kernel panic. >> >> Thanks, >> Richard >> >> On Wed, Aug 09, 2017 at 05:59:40PM -0500, Benjamin Kaduk wrote: >> > On Wed, Aug 09, 2017 at 12:46:25PM -0700, Richard Feltstykket >wrote: >> > > Hello list, >> > > >> > > We have for the past few years been running openafs under lxc on >ubuntu >> > > 14.04 using bind mounts like this: >> > > >> > > lxc.mount.entry = /afs /lxc/containers/cafe/rootfs/afs none bind >0 0 >> > > >> > > I have just patched one of the hosts. After starting some of the >> > > containers, a few minutes later I get a kernel panic with: >> > >> > When you say "patched", you mean like "apt-get dist-upgrade"? >> > I assume that a new kernel was part of it; did the update take >multiple >> > minutes (as is needed for DKMS to rebuild the openafs kernel >module)? >> > Have you rebooted since the update? >> > >> > A possibly plausible cause of this behavior would be a mismatch >between >> > the kernel and kernel module, which is why I ask. >> > >> > -Ben >> >>
