Bug#883938: Workaround available

To: Stephane Lapie <stephane.lapie@asahinet.com>, 883938@bugs.debian.org
Subject: Bug#883938: Workaround available
From: Bernhard Schmidt <berni@birkenwald.de>
Date: Mon, 11 Dec 2017 09:03:04 +0100
Message-id: <[🔎] 20171211080303.3knykh4q3ir2op52@fliwatuet.svr02.mucip.net>
Reply-to: Bernhard Schmidt <berni@birkenwald.de>, 883938@bugs.debian.org
In-reply-to: <[🔎] CAJ3gHgvw-imUbwgyyVxDVLR4+5hu1c4R7ZsGrM3n34ZGeuMN=w@mail.gmail.com>
References: <[🔎] CAJ3gHguoUesMW_AKVyW+LFSW4V5r6yshfkZCL=msEFBHEiLekQ@mail.gmail.com> <[🔎] 20171209172304.GA2110@noloop.net> <[🔎] CAJ3gHgvw-imUbwgyyVxDVLR4+5hu1c4R7ZsGrM3n34ZGeuMN=w@mail.gmail.com> <[🔎] 20171209172304.GA2110@noloop.net>

Control: summary -1 Seems two affect machines with more than one socket. Workaround: set maxcpus=1 on the kernel command line

Hi,

this seems to affect two-socket boxes.

Workaround is to set maxcpus=1 on the kernel command line.

Bernhard

Reply to:

References:
- Bug#883938: HP ProLiant DL360 Gen9
  - From: Stephane Lapie <stephane.lapie@asahinet.com>
- Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
  - From: debbug <debbug.linuximage.debian810@sub.noloop.net>
- Bug#883938: HP ProLiant DL360 Gen9
  - From: Stephane Lapie <stephane.lapie@asahinet.com>

Prev by Date: Bug#884069: Kernel crash on boot on IBM BladeCenter HS22
Next by Date: Processed: Re: Bug#883938: Workaround available
Previous by thread: Bug#883938: HP ProLiant DL360 Gen9
Next by thread: Processed: Re: Bug#883938: Workaround available
Index(es):
- Date
- Thread