[slurm-users] Cluster not booting after upgrade to debian jessie

John Hearns hearnsj at googlemail.com
Tue Jan 9 06:54:47 MST 2018

Elisabetta, I will not answer your question directly.
However I think that everyone has heard of the Meltdown bug by now, and
there are updated kernels being made available for this.
You should have a look on the Debian pages to see what they are saying
about this, and choose which kernel you need on your head node.

On 9 January 2018 at 14:17, Steffen Grunewald <steffen.grunewald at aei.mpg.de>

> On Tue, 2018-01-09 at 13:16:12 +0100, Elisabetta Falivene wrote:
> > Root file system is on the master. I'm being able to boot the machine
> > changing kernel. Grub allow to boot from two kernel:
> >
> >
> > kernel 3.2.0-4-amd64
> >
> > kernel 3.16.0-4-amd64
> >
> >
> > The problem is with kernel 3.16, but boots correctly with 3.2.
> Let me guess: you're running multi-socket systems, and the kernel
> version behind that "3.16.0-4" label is 3.16.51-2, not 3.16.43-2?
> There seems to be an issue with that latest kernel update in Debian
> Jessie, mainly affecting multi-socket machines, but since Dec 4
> when this kernel package (set) was released I haven't seen any
> updates or fixes.
> Would using the jessie-backports kernel (4.9.x) be an option for you?
> Cheers,
>  S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20180109/99e5b7f7/attachment.html>

More information about the slurm-users mailing list