> Ciao Elisabetta,
>
Ciao Gennaro! :)
>
> On Tue, Jan 09, 2018 at 01:40:19PM +0100, Elisabetta Falivene wrote:
> > The new kernel was installed during an upgrade from Debian 7 Wheezy to
> > Debian 8 Jessie. The upgrade went ok on the 8 nodes of the cluster, but
> not
> > on the master. Btw, on t
>
>
> 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?
>
Nope. On the nodes the version is 3.16.43-2, and on the master dpkg points
that the unloaded kernel is 3.16.43-2+deb8u5
> There seems to be an issue with
Ciao Elisabetta,
On Tue, Jan 09, 2018 at 01:40:19PM +0100, Elisabetta Falivene wrote:
> The new kernel was installed during an upgrade from Debian 7 Wheezy to
> Debian 8 Jessie. The upgrade went ok on the 8 nodes of the cluster, but not
> on the master. Btw, on the nodes kernel 3.16 is working ok.
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 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
Interesting. Going to try!
The new kernel was installed during an upgrade from Debian 7 Wheezy to
Debian 8 Jessie. The upgrade went ok on the 8 nodes of the cluster, but not
on the master. Btw, on the nodes kernel 3.16 is working ok.
Stupid question: It's worth trying to make the new kernel work,
Elisabetta, I am not an expert on Debian systems.
I think to solve your problem with the kernels, you need to recreate the
initial ramdisk and make sure it has the modules you need.
So boot the system in kernel 3.2 and then run:
mkinitrd 3.16.0-4-amd64
How was the kernel version 3.16.0-4-amd64
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.
Anyway, rebooting with kernel 3.2, slurm (now updated to 14.03.
On Monday, 8 January 2018 11:39:32 CET Elisabetta Falivene wrote:
> Here I am again.
> In the end, I did the upgrade from debian 7 wheezy to debian 8 jessie in
> order to update Slurm and solve some issues with it. It seemed it all went
> well. Even slurm problem seemed solved. Then I rebooted the
Here I am again.
In the end, I did the upgrade from debian 7 wheezy to debian 8 jessie in
order to update Slurm and solve some issues with it. It seemed it all went
well. Even slurm problem seemed solved. Then I rebooted the machine and the
problems began. I can't boot the master anymore returning
10 matches
Mail list logo
