Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Justus Winter writes: > Steve McIntyre writes: > >> OK, this is not looking good. I'll ask some of the Arm folks to have a >> look here in case they can help. > > Thanks! Any news from Arm? Justus signature.asc Description: PGP signature
Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Steve McIntyre writes: > On Mon, Aug 16, 2021 at 01:24:14PM +0200, Justus Winter wrote: >>Steve McIntyre writes: >>> >>> OK, and my upgrade worked just fine. The key difference that I'm >>> seeing is that on my system ACPI is *not* used: >>> >>> root@mustang4:/home/steve# grep ACPI /var/log/syslog >>> Aug 16 11:20:27 mustang4 kernel: [0.00] efi: ACPI=0x43fa70 ACPI >>> 2.0=0x43fa700014 SMBIOS 3.0=0x43fa9db000 ESRT=0x43ff006d18 >>> MOKvar=0x43fd2b2000 MEMRESERVE=0x43fa5e0718 >>> Aug 16 11:20:27 mustang4 kernel: [1.293700] ACPI: Interpreter disabled. >>> Aug 16 11:20:27 mustang4 kernel: [1.322457] pnp: PnP ACPI: disabled >>> >>> Basically, the firmware on these older machines is too old for ACPI to >>> work well. This brings back memories of X-Gene 1 oddities - the way >>> they boot the extra CPU cores depends on specific setup in the DTB. My >>> machine is working that way, but I'm guessing that maybe whatever in >>> the kernel determines this is *not* automatically disabling ACPI on >>> your machine. >>> >>> Pondering: do things work better for you if you add "acpi=off" to the >>> kernel command line? >> >>Interesting. Yeah, I actually tried that last week, but it failed: > > :-( Argh. > > Oh wow, just noticed: > >>U-Boot 2013.04 (Oct 02 2015 - 14:44:51) > > I moved all my Mustangs over to UEFI (edk2) rather than U-Boot, but I > honestly don't know if that's an option for the m400. I put the cartridge in UEFI mode. AIUI, it starts using U-Boot, then chainloads UEFI. >>[0.00] Kernel command line: BOOT_IMAGE=/debian-installer/arm64/linux >>--- console=ttyS0,115200 earlycon=uart,mmio32,0x1c021000 initcall_debug >>keep_bootcon efi=debug debug earlyprintk=efi,keep acpi=off >>[0.00] Dentry cache hash table entries: 8388608 (order: 14, 67108864 >>bytes, linear) >>[0.00] Inode-cache hash table entries: 4194304 (order: 13, 33554432 >>bytes, linear) >>[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off >>[0.00] software IO TLB: mapped [mem >>0x0040f800-0x0040fc00] (64MB) >>[0.00] Memory: 5107712K/67104768K available (11776K kernel code, >>2436K rwdata, 7008K rodata, 5440K init, 598K bss, 1407976K reserved, 65536K >>cma-reserved) >>[0.00] random: get_random_u64 called from >>__kmem_cache_create+0x38/0x560 with crng_init=0 >>[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 >>[0.00] ftrace: allocating 38533 entries in 151 pages >>[0.00] ftrace: allocated 151 pages with 5 groups >>[0.00] rcu: Hierarchical RCU implementation. >>[0.00] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=1. >>[0.00] Rude variant of Tasks RCU enabled. >>[0.00] Tracing variant of Tasks RCU enabled. >>[0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 >>jiffies. >>[0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 >>[0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 >>[0.00] Kernel panic - not syncing: No interrupt controller found. >>[0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.0-8-arm64 #1 >>Debian 5.10.46-3 >>[0.00] Call trace: >>[0.00] dump_backtrace+0x0/0x1e4 >>[0.00] show_stack+0x24/0x30 >>[0.00] dump_stack+0xd0/0x12c >>[0.00] panic+0x168/0x370 >>[0.00] init_IRQ+0xe8/0x104 >>[0.00] start_kernel+0x3a8/0x5ac >>[0.00] ---[ end Kernel panic - not syncing: No interrupt controller >>found. ]--- > > OK, this is not looking good. I'll ask some of the Arm folks to have a > look here in case they can help. Thanks! Justus signature.asc Description: PGP signature
Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
On Mon, Aug 16, 2021 at 01:24:14PM +0200, Justus Winter wrote: >Steve McIntyre writes: >> >> OK, and my upgrade worked just fine. The key difference that I'm >> seeing is that on my system ACPI is *not* used: >> >> root@mustang4:/home/steve# grep ACPI /var/log/syslog >> Aug 16 11:20:27 mustang4 kernel: [0.00] efi: ACPI=0x43fa70 ACPI >> 2.0=0x43fa700014 SMBIOS 3.0=0x43fa9db000 ESRT=0x43ff006d18 >> MOKvar=0x43fd2b2000 MEMRESERVE=0x43fa5e0718 >> Aug 16 11:20:27 mustang4 kernel: [1.293700] ACPI: Interpreter disabled. >> Aug 16 11:20:27 mustang4 kernel: [1.322457] pnp: PnP ACPI: disabled >> >> Basically, the firmware on these older machines is too old for ACPI to >> work well. This brings back memories of X-Gene 1 oddities - the way >> they boot the extra CPU cores depends on specific setup in the DTB. My >> machine is working that way, but I'm guessing that maybe whatever in >> the kernel determines this is *not* automatically disabling ACPI on >> your machine. >> >> Pondering: do things work better for you if you add "acpi=off" to the >> kernel command line? > >Interesting. Yeah, I actually tried that last week, but it failed: :-( Argh. Oh wow, just noticed: >U-Boot 2013.04 (Oct 02 2015 - 14:44:51) I moved all my Mustangs over to UEFI (edk2) rather than U-Boot, but I honestly don't know if that's an option for the m400. ... >[0.00] Kernel command line: BOOT_IMAGE=/debian-installer/arm64/linux >--- console=ttyS0,115200 earlycon=uart,mmio32,0x1c021000 initcall_debug >keep_bootcon efi=debug debug earlyprintk=efi,keep acpi=off >[0.00] Dentry cache hash table entries: 8388608 (order: 14, 67108864 >bytes, linear) >[0.00] Inode-cache hash table entries: 4194304 (order: 13, 33554432 >bytes, linear) >[0.00] mem auto-init: stack:off, heap alloc:on, heap free:off >[0.00] software IO TLB: mapped [mem >0x0040f800-0x0040fc00] (64MB) >[0.00] Memory: 5107712K/67104768K available (11776K kernel code, 2436K >rwdata, 7008K rodata, 5440K init, 598K bss, 1407976K reserved, 65536K >cma-reserved) >[0.00] random: get_random_u64 called from >__kmem_cache_create+0x38/0x560 with crng_init=0 >[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 >[0.00] ftrace: allocating 38533 entries in 151 pages >[0.00] ftrace: allocated 151 pages with 5 groups >[0.00] rcu: Hierarchical RCU implementation. >[0.00] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=1. >[0.00] Rude variant of Tasks RCU enabled. >[0.00] Tracing variant of Tasks RCU enabled. >[0.00] rcu: RCU calculated value of scheduler-enlistment delay is 25 >jiffies. >[0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 >[0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 >[0.00] Kernel panic - not syncing: No interrupt controller found. >[0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.0-8-arm64 #1 >Debian 5.10.46-3 >[0.00] Call trace: >[0.00] dump_backtrace+0x0/0x1e4 >[0.00] show_stack+0x24/0x30 >[0.00] dump_stack+0xd0/0x12c >[0.00] panic+0x168/0x370 >[0.00] init_IRQ+0xe8/0x104 >[0.00] start_kernel+0x3a8/0x5ac >[0.00] ---[ end Kernel panic - not syncing: No interrupt controller >found. ]--- OK, this is not looking good. I'll ask some of the Arm folks to have a look here in case they can help. -- Steve McIntyre, Cambridge, UK.st...@einval.com Dance like no one's watching. Encrypt like everyone is. - @torproject
Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Steve McIntyre writes: > On Mon, Aug 16, 2021 at 12:54:47PM +0200, Justus Winter wrote: >>Steve McIntyre writes: >>> On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote: Package: debian-installer Version: 20210731 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, I'm trying to install Debian Bullseye on a ProLiant m400 Server Cartridge. The cartridge is in EFI mode, we boot the EFI shim, GRUB, the kernel, and the netboot initrd via PXE and tftp. We added the necessary kernel command line flags to redirect the kernel log to the serial console early on, and various debugging flags. Reading the log we believe that there are two problems. First, while bringing up additional CPU cores, we see them crash immediately. Adding nosmp to the kernel command line avoids this, but doesn't make the second problem go away. Second, the kernel calls acpi_init, which does not seem to return. >>> I've got some Mustang (X-Gene 1) machines here, which are the same >>> core APM hardware but packaged on standard motherboard (mini-itx I >>> think?). I'm just trying a bullseye update on one now. >> >>Thanks. > > OK, and my upgrade worked just fine. The key difference that I'm > seeing is that on my system ACPI is *not* used: > > root@mustang4:/home/steve# grep ACPI /var/log/syslog > Aug 16 11:20:27 mustang4 kernel: [0.00] efi: ACPI=0x43fa70 ACPI > 2.0=0x43fa700014 SMBIOS 3.0=0x43fa9db000 ESRT=0x43ff006d18 > MOKvar=0x43fd2b2000 MEMRESERVE=0x43fa5e0718 > Aug 16 11:20:27 mustang4 kernel: [1.293700] ACPI: Interpreter disabled. > Aug 16 11:20:27 mustang4 kernel: [1.322457] pnp: PnP ACPI: disabled > > Basically, the firmware on these older machines is too old for ACPI to > work well. This brings back memories of X-Gene 1 oddities - the way > they boot the extra CPU cores depends on specific setup in the DTB. My > machine is working that way, but I'm guessing that maybe whatever in > the kernel determines this is *not* automatically disabling ACPI on > your machine. > > Pondering: do things work better for you if you add "acpi=off" to the > kernel command line? Interesting. Yeah, I actually tried that last week, but it failed: U-Boot 2013.04 (Oct 02 2015 - 14:44:51) ProLiant m400 Server Cartridge - U02 (10/02/2015) Copyright 2013 - 2015 Hewlett-Packard Development Company, L.P. Copyright 2000 - 2012 Wolfgang Denk, DENX Software Engineering, w...@denx.de CPU0: APM ARM 64-bit Potenza Rev B0 2400MHz PCP 2400MHz 32 KB ICACHE, 32 KB DCACHE SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz Boot from SPI-NOR Slimpro FW: Ver: 2.3 (build 2015/03/16) PMD: 960 mV SOC: 950 mV I2C: ready DRAM: ECC 64 GiB @ 1333MHz Using default environment API sig @ 0x004ffdf13170 In:serial Out: serial Err: serial CPUs: CPLD: 0B SF: Detected MX25L12805D with page size 64 KiB, total 16 MiB SF: 16384 KiB MX25L12805D at 0:0 is now current device SF: flash read success (17417 bytes @ 0xe) . SF: flash read success (65568 bytes @ 0xc) SF: flash read success (1477 bytes @ 0x10) Node Boot Start Time: 2021-08-16T13:38:11 Node Serial Number: CN7447V0BK Cartridge Chassis Slot ID: 26 Cartridge Serial Number: CN7447V0BK Chassis Serial Number: CZ3450K3J5 Chassis Asset Tag: Node UUID: 4445FA0A-122C-52F2-8764-A549A7928A4B Product ID: 721717-B21 Timezone Name: Europe/London Loading UEFI ... SF: flash read success (3604480 bytes @ 0x20) ## Starting application at 0x400200 ... ProLiant System BIOS U02 v1.01 (10/02/2015) (C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P. Early system initialization, please wait... Processor Root Ports Initialization BIOS Configuration Initialization Early PCI Initialization - Start Early PCI Initialization - Complete Switching console output to Primary Video. Please wait... (C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P. HP ProLiant m400 Server BIOS Version: U02 v1.01 (10/02/2015) Serial Number: CN7447V0BK System Memory: 64 GB 1 Processor(s) detected, 8 total cores enabled, Proc 1: X-Gene HP Power Profile Mode: Balanced Power and Performance Boot Mode: UEFI For access via BIOS Serial Console: Press 'ESC+9' for System Utilities Press 'ESC+@' for Network Boot >> Booting Embedded LOM 1 Port 1 : Port 1 - Mellanox Network Adapter (PXE IPv4) >> Booting PXE over IPv4. Station IP address is 192.168.103.26 Server IP address is 192.168.103.253 NBP filename is debian-stable/debian-installer/arm64/bootnetaa64.efi NBP filesize is 856064 Bytes Downloading NBP file... NBP file downloaded successfully. Fetching Netboot Image Welcome to GRUB! GNU GRUB version 2.04-20 /\ |*Install
Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
On Mon, Aug 16, 2021 at 12:54:47PM +0200, Justus Winter wrote: >Steve McIntyre writes: >> On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote: >>>Package: debian-installer >>>Version: 20210731 >>>Severity: critical >>>Tags: d-i >>>Justification: breaks the whole system >>> >>>Dear Maintainer, >>> >>>I'm trying to install Debian Bullseye on a ProLiant m400 Server >>>Cartridge. The cartridge is in EFI mode, we boot the EFI shim, GRUB, >>>the kernel, and the netboot initrd via PXE and tftp. We added the >>>necessary kernel command line flags to redirect the kernel log to the >>>serial console early on, and various debugging flags. >>> >>>Reading the log we believe that there are two problems. First, while >>>bringing up additional CPU cores, we see them crash immediately. >>>Adding nosmp to the kernel command line avoids this, but doesn't make >>>the second problem go away. Second, the kernel calls acpi_init, which >>>does not seem to return. >> >> Hmmm. The m400 sleds are getting quite old, and AIUI they're basically >> EOL in terms of firmware support etc. > >Well, I'm also getting quite old, yet, I'd like to use Debian :) Sure. :-) >> I've got some Mustang (X-Gene 1) machines here, which are the same >> core APM hardware but packaged on standard motherboard (mini-itx I >> think?). I'm just trying a bullseye update on one now. > >Thanks. OK, and my upgrade worked just fine. The key difference that I'm seeing is that on my system ACPI is *not* used: root@mustang4:/home/steve# grep ACPI /var/log/syslog Aug 16 11:20:27 mustang4 kernel: [0.00] efi: ACPI=0x43fa70 ACPI 2.0=0x43fa700014 SMBIOS 3.0=0x43fa9db000 ESRT=0x43ff006d18 MOKvar=0x43fd2b2000 MEMRESERVE=0x43fa5e0718 Aug 16 11:20:27 mustang4 kernel: [1.293700] ACPI: Interpreter disabled. Aug 16 11:20:27 mustang4 kernel: [1.322457] pnp: PnP ACPI: disabled Basically, the firmware on these older machines is too old for ACPI to work well. This brings back memories of X-Gene 1 oddities - the way they boot the extra CPU cores depends on specific setup in the DTB. My machine is working that way, but I'm guessing that maybe whatever in the kernel determines this is *not* automatically disabling ACPI on your machine. Pondering: do things work better for you if you add "acpi=off" to the kernel command line? -- Steve McIntyre, Cambridge, UK.st...@einval.com "Yes, of course duct tape works in a near-vacuum. Duct tape works anywhere. Duct tape is magic and should be worshipped." -― Andy Weir, "The Martian"
Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Hi Steve :) Steve McIntyre writes: > Reassigning to the right package. While you're seeing this during d-i, > the problem is clearly coming from the Linux kernel. Thanks! > On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote: >>Package: debian-installer >>Version: 20210731 >>Severity: critical >>Tags: d-i >>Justification: breaks the whole system >> >>Dear Maintainer, >> >>I'm trying to install Debian Bullseye on a ProLiant m400 Server >>Cartridge. The cartridge is in EFI mode, we boot the EFI shim, GRUB, >>the kernel, and the netboot initrd via PXE and tftp. We added the >>necessary kernel command line flags to redirect the kernel log to the >>serial console early on, and various debugging flags. >> >>Reading the log we believe that there are two problems. First, while >>bringing up additional CPU cores, we see them crash immediately. >>Adding nosmp to the kernel command line avoids this, but doesn't make >>the second problem go away. Second, the kernel calls acpi_init, which >>does not seem to return. > > Hmmm. The m400 sleds are getting quite old, and AIUI they're basically > EOL in terms of firmware support etc. Well, I'm also getting quite old, yet, I'd like to use Debian :) > I've got some Mustang (X-Gene 1) machines here, which are the same > core APM hardware but packaged on standard motherboard (mini-itx I > think?). I'm just trying a bullseye update on one now. Thanks. > Out of curiosity: how does an equivalent boot work with buster d-i on > your system? No. It fails the same way, see log. Note that I used bullseye's shim and GRUB, I couldn't get buster's to work. Justus ~~~ snip ~~~ U-Boot 2013.04 (Oct 02 2015 - 14:44:51) ProLiant m400 Server Cartridge - U02 (10/02/2015) Copyright 2013 - 2015 Hewlett-Packard Development Company, L.P. Copyright 2000 - 2012 Wolfgang Denk, DENX Software Engineering, w...@denx.de CPU0: APM ARM 64-bit Potenza Rev B0 2400MHz PCP 2400MHz 32 KB ICACHE, 32 KB DCACHE SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz Boot from SPI-NOR Slimpro FW: Ver: 2.3 (build 2015/03/16) PMD: 960 mV SOC: 950 mV I2C: ready DRAM: ECC 64 GiB @ 1333MHz Using default environment API sig @ 0x004ffdf13170 In:serial Out: serial Err: serial CPUs: CPLD: 0B SF: Detected MX25L12805D with page size 64 KiB, total 16 MiB SF: 16384 KiB MX25L12805D at 0:0 is now current device SF: flash read success (17417 bytes @ 0xe) . SF: flash read success (65568 bytes @ 0xc) SF: flash read success (1477 bytes @ 0x10) Node Boot Start Time: 2021-08-16T13:04:15 Node Serial Number: CN7447V0BK Cartridge Chassis Slot ID: 26 Cartridge Serial Number: CN7447V0BK Chassis Serial Number: CZ3450K3J5 Chassis Asset Tag: Node UUID: 4445FA0A-122C-52F2-8764-A549A7928A4B Product ID: 721717-B21 Timezone Name: Europe/London Loading UEFI ... SF: flash read success (3604480 bytes @ 0x20) ## Starting application at 0x400200 ... ProLiant System BIOS U02 v1.01 (10/02/2015) (C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P. Early system initialization, please wait... Processor Root Ports Initialization BIOS Configuration Initialization Early PCI Initialization - Start Early PCI Initialization - Complete Switching console output to Primary Video. Please wait... (C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P. HP ProLiant m400 Server BIOS Version: U02 v1.01 (10/02/2015) Serial Number: CN7447V0BK System Memory: 64 GB 1 Processor(s) detected, 8 total cores enabled, Proc 1: X-Gene HP Power Profile Mode: Balanced Power and Performance Boot Mode: UEFI For access via BIOS Serial Console: Press 'ESC+9' for System Utilities Press 'ESC+@' for Network Boot >> Booting Embedded LOM 1 Port 1 : Port 1 - Mellanox Network Adapter (PXE IPv4) >> Booting PXE over IPv4. Station IP address is 192.168.103.26 Server IP address is 192.168.103.253 NBP filename is debian-stable/debian-installer/arm64/bootnetaa64.efi NBP filesize is 856064 Bytes Downloading NBP file... NBP file downloaded successfully. Fetching Netboot Image Welcome to GRUB! GNU GRUB version 2.04-20 /\ | Install| |*Install oldstable | | Graphical install | | Advanced options ... | | Dark theme option... | | Install with speech synthesis | || || |
Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Control: severity -1 important Control: reassign -1 src:linux Hi Justus! Reassigning to the right package. While you're seeing this during d-i, the problem is clearly coming from the Linux kernel. On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote: >Package: debian-installer >Version: 20210731 >Severity: critical >Tags: d-i >Justification: breaks the whole system > >Dear Maintainer, > >I'm trying to install Debian Bullseye on a ProLiant m400 Server >Cartridge. The cartridge is in EFI mode, we boot the EFI shim, GRUB, >the kernel, and the netboot initrd via PXE and tftp. We added the >necessary kernel command line flags to redirect the kernel log to the >serial console early on, and various debugging flags. > >Reading the log we believe that there are two problems. First, while >bringing up additional CPU cores, we see them crash immediately. >Adding nosmp to the kernel command line avoids this, but doesn't make >the second problem go away. Second, the kernel calls acpi_init, which >does not seem to return. Hmmm. The m400 sleds are getting quite old, and AIUI they're basically EOL in terms of firmware support etc. I've got some Mustang (X-Gene 1) machines here, which are the same core APM hardware but packaged on standard motherboard (mini-itx I think?). I'm just trying a bullseye update on one now. Out of curiosity: how does an equivalent boot work with buster d-i on your system? -- Steve McIntyre, Cambridge, UK.st...@einval.com "I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop" -- Vivek Das Mohapatra
Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init
Package: debian-installer Version: 20210731 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, I'm trying to install Debian Bullseye on a ProLiant m400 Server Cartridge. The cartridge is in EFI mode, we boot the EFI shim, GRUB, the kernel, and the netboot initrd via PXE and tftp. We added the necessary kernel command line flags to redirect the kernel log to the serial console early on, and various debugging flags. Reading the log we believe that there are two problems. First, while bringing up additional CPU cores, we see them crash immediately. Adding nosmp to the kernel command line avoids this, but doesn't make the second problem go away. Second, the kernel calls acpi_init, which does not seem to return. ~~~ boot log ~~~ U-Boot 2013.04 (Oct 02 2015 - 14:44:51) ProLiant m400 Server Cartridge - U02 (10/02/2015) Copyright 2013 - 2015 Hewlett-Packard Development Company, L.P. Copyright 2000 - 2012 Wolfgang Denk, DENX Software Engineering, w...@denx.de CPU0: APM ARM 64-bit Potenza Rev B0 2400MHz PCP 2400MHz 32 KB ICACHE, 32 KB DCACHE SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz Boot from SPI-NOR Slimpro FW: Ver: 2.3 (build 2015/03/16) PMD: 960 mV SOC: 950 mV I2C: ready DRAM: ECC 64 GiB @ 1333MHz Using default environment API sig @ 0x004ffdf13170 In:serial Out: serial Err: serial CPUs: CPLD: 0B SF: Detected MX25L12805D with page size 64 KiB, total 16 MiB SF: 16384 KiB MX25L12805D at 0:0 is now current device SF: flash read success (17417 bytes @ 0xe) . SF: flash read success (65568 bytes @ 0xc) SF: flash read success (1477 bytes @ 0x10) Node Boot Start Time: 2021-08-16T09:56:54 Node Serial Number: CN7447V0BK Cartridge Chassis Slot ID: 26 Cartridge Serial Number: CN7447V0BK Chassis Serial Number: CZ3450K3J5 Chassis Asset Tag: Node UUID: 4445FA0A-122C-52F2-8764-A549A7928A4B Product ID: 721717-B21 Timezone Name: Europe/London Loading UEFI ... SF: flash read success (3604480 bytes @ 0x20) ## Starting application at 0x400200 ... ProLiant System BIOS U02 v1.01 (10/02/2015) (C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P. Early system initialization, please wait... Processor Root Ports Initialization BIOS Configuration Initialization Early PCI Initialization - Start Early PCI Initialization - Complete Switching console output to Primary Video. Please wait... (C) Copyright 1982 - 2015 Hewlett-Packard Development Company, L.P. HP ProLiant m400 Server BIOS Version: U02 v1.01 (10/02/2015) Serial Number: CN7447V0BK System Memory: 64 GB 1 Processor(s) detected, 8 total cores enabled, Proc 1: X-Gene HP Power Profile Mode: Balanced Power and Performance Boot Mode: UEFI For access via BIOS Serial Console: Press 'ESC+9' for System Utilities Press 'ESC+@' for Network Boot >> Booting Embedded LOM 1 Port 1 : Port 1 - Mellanox Network Adapter (PXE IPv4) >> Booting PXE over IPv4. Station IP address is 192.168.103.26 Server IP address is 192.168.103.253 NBP filename is debian-stable/debian-installer/arm64/bootnetaa64.efi NBP filesize is 856064 Bytes Downloading NBP file... NBP file downloaded successfully. Fetching Netboot Image Welcome to GRUB! GNU GRUB version 2.04-20 /\ |*Install| | Graphical install | | Advanced options ... | | Dark theme option... | | Install with speech synthesis | || || || || || || || || \/ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. GNU GRUB version 2.04-20 /\ |setparams 'Install' | |
