Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59592
| From | Stephane Lapie <stephane.lapie@asahinet.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#883938: HP ProLiant DL360 Gen9 |
| Date | 2017-12-11 08:30 +0100 |
| Message-ID | <uVqHf-2bh-1@gated-at.bofh.it> (permalink) |
| References | <uVpBv-1wK-1@gated-at.bofh.it> <uURgt-4GB-7@gated-at.bofh.it> <uVpBv-1wK-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[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
Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
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
csiph-web