Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-31 Thread ผู้หญิง ธรรมดา 
On Mon, 11 Dec 2017 19:07:05 +0100 Karsten Heiken <
hei...@luis.uni-hannover.de> wrote:
> Bernhard Schmidt wrote:
> >Can you check whether numa=off on the kernel command line fixes this as
well?
>
> Indeed it does. Appending numa=off to the kernel command line fixes
> the bug in my KVM virtual machines as well as my physical servers (at
> least the ones I've tested so far).
>
> So this might be a viable workaround for the people that already
> patched their systems.
>
>
>

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-11 Thread Heiko Schlittermann 
The provided work-around (setting numa=off) worked here.
Do you need further information about the system in use?

BTW: Thank you for the NUMA advice, it was about 21.00 CET when
I started a search engine and found the bug entry and the suggested
work-around, so, your advice came just in time.

Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
-- 
 SCHLITTERMANN.de  internet & unix support -
 Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
 gnupg encrypted messages are welcome --- key ID: F69376CE -
 ! key id 7CBF764A and 972EAC9F are revoked since 2015-01  -


signature.asc
Description: PGP signature

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-11 Thread Karsten Heiken 

Bernhard Schmidt wrote:

Can you check whether numa=off on the kernel command line fixes this as well?


Indeed it does. Appending numa=off to the kernel command line fixes
the bug in my KVM virtual machines as well as my physical servers (at
least the ones I've tested so far).

So this might be a viable workaround for the people that already
patched their systems.

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-11 Thread Bernhard Schmidt 
Hi Karsten,

Thanks for the test. Can you check whether numa=off on the kernel command line 
fixes this as well?

Bernhard
-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-11 Thread Karsten Heiken 

I can reproduce the bug on multiple (physical) servers running in our
data center.

When booting my virtual servers with the new kernel, the issue did not
arise...

...until I enabled NUMA.

Booting a virtual machine with 2 sockets and 16 cores each works fine
when NUMA is disabled in KVM.

With NUMA enabled the machine boots only if I set the number of
sockets to "1". When I set the number of sockets to two, the machine
crashes.

Bug#883938: Bug #883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

2017-12-11 Thread Christoph Martin 
Just as a note:

Upgrading to jessie-backports version 4.9.51-1~bpo8+1 is also an option,
which works.

Christoph
<>

signature.asc
Description: OpenPGP digital signature