Using HPE Servers Gen10 Installation Kit Version 2. Booting from this CD to initiate install of SLES11 SP4 on HP ML350 Gen10 in Legacy BIOS mode.
If leave default Video Mode, install stops right after loading the kernel - screen is blank.
If set video mode to 1024x768, at least the screen isn’t blank when it fails. Now is shows Kernel Panic, hard LOCKUP on cpu0. Then a call trace.
This server has 2 Intel 6133 (8-core) processors and 128 GB memory.
Anybody have any success with V2 of the SuSE Gen10 Install Kit?
Installs SLES12 SP3 in UEFI mode on this server fine.
processor is wrong - it is Intel 6134 3.2Ghz
Same problem in UEFI mode
On 09/11/17 14:54, sdrake1 wrote:
[color=blue]
Looks like too much memory - SLES11 supports 64GB max[/color]
I don’t think so, though it depends on whether you’re installing 32- or
64-bit SLES11 (x86 or x86_64).
From
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/11/#rnotes-technical
SLES11 x86 was certified with 16GiB (64GiB theoretical) whilst x86_64 is
512GiB (64TiB certified).
Please can you post output from “cat /etc/*release”.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
Working on DL380 Gen10 1P 5122 3.6Ghz 4-core, 64GB memory, Legacy Bios
Not working on ML350 Gen10 2p 6134 3.2Ghz 8-core, 64GB memory, Legacy Bios
Works (meaning G10 Install Kit CD-Rom boots) when restricting each CPU to 4 cores in HP System settings. Each 6134 has 8-cores.
Note: Hyperthreading is on so to kernel number of cores is doubled.
Is there some restriction with SLES11 SP4 and the number of cores?
My bad. This is x86_64. Restricting the number of cores allowed this G10 Install Kit to boot and install SLES11 SP4. Intel Gold 6134 has 8 cores, I have 2 processors and hyperthreading is on - so 32 virtual cores. In HP System Settings I restricted each processor to 4 cores (so 16 virtual cores) and it boots and installs OS.
Suspect SLES11 SP4 might have # of cores limit (16 is my guess).
After running the G10 Install Kit (with only 4 cores per processor enabled) and installing SLES11 SP4, I rebooted, re-enabled all cores (8 per Intel Xeon Gold 6134) and tried booting the OS. It fails with Kernel NULL pointer dereference at 0000000000000010
Stack:
ffff88a80ee97bc8 ffff88180ee97b18 ffff88183ffdad08 0000000000010b08
0000000000010b00 0000000000010b08 ffff88a80ee97cb0 0000001900000000
Call Trace:
load_balance+0xa5/0x480
idle_balance+0x110/0x1a0
thread_return+0x263/0x2a7
do_wait+0x21c/0x250
sys_wait4+0x97/0x100
system_call_fastpath+0x16/0x1b
0x7f379f9a0b14
Last line is:
4.82662] RSP
From what I can read 32 cores should not be a problem for x86_64 SLES11 SP4 but clearly not working on HP ML350 Gen10
sdrake1 wrote:
[color=blue]
Suspect SLES11 SP4 might have # of cores limit (16 is my guess).[/color]
The release notes state max. # Logical CPUs is 4096
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/11-SP4/#TechInfo.Kernel
There has to be another explanation!
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
sdrake1 wrote:
[color=blue]
From what I can read 32 cores should not be a problem for x86_64
SLES11 SP4 but clearly not working on HP ML350 Gen10[/color]
Have you installed the latest BIOS and firmware?
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
Yes, installed updates from HP Service Pack 2017.10.01 released yesterday
Yes, that is what I read too.
On 09/11/17 19:14, sdrake1 wrote:
[color=blue]
Yes, that is what I read too.[/color]
Do you have the Sub NUMA Clustering (SNC) option enabled? I’ve found
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00019612en_us
which references TID 7018835[1] and says Sub NUMA Clustering is not
supported with SLES11 SP4 (but is supported with SLES12 SP2 and later).
HTH.
[1] https://www.suse.com/support/kb/doc/?id=7018835
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
[QUOTE=smflood;40155]On 09/11/17 19:14, sdrake1 wrote:
[color=blue]
Yes, that is what I read too.[/color]
Do you have the Sub NUMA Clustering (SNC) option enabled? I’ve found
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00019612en_us
which references TID 7018835[1] and says Sub NUMA Clustering is not
supported with SLES11 SP4 (but is supported with SLES12 SP2 and later).
HTH.
[1] https://www.suse.com/support/kb/doc/?id=7018835
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]
Thank you. Setting of Sub-NUMA Clustering is the trouble.
On the Gen10, this setting is part of the Workload Profile (and displayed in the Power and Performance Options).
I was using an alternate profile, General Throughput Compute which sets Sub-NUMA Clustering to enabled.
The other available profiles all have Sub-NUMA Clustering disabled: Dynamic Power Savings, General Peak Frequency, Virtualization - Power Efficient.
Changing the Workload Profile resolved the trouble.
On 10/11/17 14:24, sdrake1 wrote:
[color=blue]
Thank you. Setting of Sub-NUMA Clustering is the trouble.
On the Gen10, this setting is part of the Workload Profile (and
displayed in the Power and Performance Options).
I was using an alternate profile, General Throughput Compute which sets
Sub-NUMA Clustering to enabled.
The other available profiles all have Sub-NUMA Clustering disabled:
Dynamic Power Savings, General Peak Frequency, Virtualization - Power
Efficient.
Changing the Workload Profile resolved the trouble.[/color]
Glad to hear it’s now working and thanks for providing the profile
information.
Simon
SUSE Knowledge Partner