Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #59592 > unrolled thread

Bug#883938: HP ProLiant DL360 Gen9

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#883938: HP ProLiant DL360 Gen9 Stephane Lapie <stephane.lapie@asahinet.com> - 2017-12-11 08:30 +0100
    Bug#883938: Workaround available Bernhard Schmidt <berni@birkenwald.de> - 2017-12-11 09:10 +0100

#59592 — Bug#883938: HP ProLiant DL360 Gen9

[Multipart message — attachments visible in raw view] — view raw

One more bit of info if it helps.

I noticed that I had some ProLiant DL360 Gen9 servers that booted fine with
that version.
The main difference between the ones that failed booting had more CPU cores
detected than the ones that succeeded.
For reference, the successful one had 20, the failed one had 32.
Given the kernel panic seems to be scheduler related, are there any chances
this is an edge case for servers with tons of CPUs?

Cheers,
-- 
ラピー ステファン Lapie Stephane
株式会社朝日ネット システム部
AsahiNet, Inc. - System Division

[toc] | [next] | [standalone]

#59597 — Bug#883938: Workaround available

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web