E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
-
Topic author - Active Contributor
- Posts: 31
- Joined: Sat Apr 22, 2023 3:56 am
- Reputation: 0
- Status: Offline
E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
Starting a thread here for hardware that's been tried and hasn't worked for various reasons, if I can, I'll edit and add to the top post as people add on to this thread over time.
List of known failures here, down in the thread will be details and specifics of each:
Known failures:
Gigabyte X299 UD4 - E9.2-1, V9.2
Asus PRIME X299 UD4 - E9.2-1, V9.2
Supermicro X9DR3-LN4F+ - E9.2-1 (installed pre-sysgen/first boot image only, install DVD boot not tested)
HP Z240 - Successful boot to installation environment, onboard SATA non-functional/compatible.
Non-working HBAs:
LSI SAS-3041
LSI SAS-9212
Dell SAS 5/E (LSI 1068 - NOT the 1068E) with stock bios from Dell, unknown version. This is the PCI-X version of the 1068, with a PCIe to PCI-X bridge chip on the card.
List of known failures here, down in the thread will be details and specifics of each:
Known failures:
Gigabyte X299 UD4 - E9.2-1, V9.2
Asus PRIME X299 UD4 - E9.2-1, V9.2
Supermicro X9DR3-LN4F+ - E9.2-1 (installed pre-sysgen/first boot image only, install DVD boot not tested)
HP Z240 - Successful boot to installation environment, onboard SATA non-functional/compatible.
Non-working HBAs:
LSI SAS-3041
LSI SAS-9212
Dell SAS 5/E (LSI 1068 - NOT the 1068E) with stock bios from Dell, unknown version. This is the PCI-X version of the 1068, with a PCIe to PCI-X bridge chip on the card.
Last edited by gdwnldsksc on Mon May 01, 2023 3:41 am, edited 12 times in total.
-
Topic author - Active Contributor
- Posts: 31
- Joined: Sat Apr 22, 2023 3:56 am
- Reputation: 0
- Status: Offline
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
Failing system:
OS Version: E9.2-1
Motherboard: Gigabyte X299 UD4 (non-Pro version) - onboard NIC is an intel i219, which I do not expect to work (have separate NICs that I was going to use after a successful boot).
CPU: i7-7800X (HTT disabled)
Ram: 2x8GB DDR4-3200 (running at 2400 - XMP disabled)
GPU: MSI GeForce 210
ODD: LG GH24NSC0B DVD-RW
Storage: None (Test system).
PCIe serial cards: StarTech PEX2S553 (ASIX MCS9922CV-AA) and LinksTek PCIE-SE2 (ASIX AX99100 )
Failure: Failure to boot installer(E9.2-1)/serial console out from bootloader(V9.2 and E9.2-1).
Symptoms: Bootloader can't see either PCIe serial card on hand as serial ports, but do show up in SMBIOS listing as SERIAL devices. Bootloader only presents COM 1 (or 0 to disable) as available options, but the COM1 shown is shown as J2A2A - which is intel chipset provided serial port and isn't wired out on the board (no UEFI options to control/disable either).
RAMDISK image successfully loads to boot, and briefly the "GRAPHICAL OUTPUT HAS BEEN SUSPENDED" screen displays (less than a second) before the machine resets itself. Unfortunately, given the target market of this motherboard, there's not much in the way of configurable options. CSM disabled, HTT disabled, Turbo Boost disabled, tried with some C state limitations/disabled and with defaults.
V9.2 (non-field test) however, does boot successfully and does NOT reset, remaining at the GRAPHICAL OUTPUT... screen, however no COM port on either card responds. No serial port shows in boot manager via DEVC either on V9.2's 113 bootloader as well - identical symptoms to E9.2-1 including showing as SERIAL in SMBIOS listing.
Second system:
Asus PRIME X299-A II, otherwise same hardware as last system.
Onboard serial port has good output.
VMS boot:
OS Version: E9.2-1
Motherboard: Gigabyte X299 UD4 (non-Pro version) - onboard NIC is an intel i219, which I do not expect to work (have separate NICs that I was going to use after a successful boot).
CPU: i7-7800X (HTT disabled)
Ram: 2x8GB DDR4-3200 (running at 2400 - XMP disabled)
GPU: MSI GeForce 210
ODD: LG GH24NSC0B DVD-RW
Storage: None (Test system).
PCIe serial cards: StarTech PEX2S553 (ASIX MCS9922CV-AA) and LinksTek PCIE-SE2 (ASIX AX99100 )
Failure: Failure to boot installer(E9.2-1)/serial console out from bootloader(V9.2 and E9.2-1).
Symptoms: Bootloader can't see either PCIe serial card on hand as serial ports, but do show up in SMBIOS listing as SERIAL devices. Bootloader only presents COM 1 (or 0 to disable) as available options, but the COM1 shown is shown as J2A2A - which is intel chipset provided serial port and isn't wired out on the board (no UEFI options to control/disable either).
RAMDISK image successfully loads to boot, and briefly the "GRAPHICAL OUTPUT HAS BEEN SUSPENDED" screen displays (less than a second) before the machine resets itself. Unfortunately, given the target market of this motherboard, there's not much in the way of configurable options. CSM disabled, HTT disabled, Turbo Boost disabled, tried with some C state limitations/disabled and with defaults.
V9.2 (non-field test) however, does boot successfully and does NOT reset, remaining at the GRAPHICAL OUTPUT... screen, however no COM port on either card responds. No serial port shows in boot manager via DEVC either on V9.2's 113 bootloader as well - identical symptoms to E9.2-1 including showing as SERIAL in SMBIOS listing.
Second system:
Asus PRIME X299-A II, otherwise same hardware as last system.
Onboard serial port has good output.
VMS boot:
Code: Select all
BOOTMGR> BOOT FS0
Booting...
%VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
100%
%%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
_______________________________________________
GRAPHICAL OUTPUT HAS BEEN SUSPENDED
USE A TERMINAL UTILITY FOR ACCESS
_______________________________________________
VSI Primary Kernel SYSBOOT Jan 23 2023 14:03:45
%SYSBOOT-F-NOPXML, The PXML database could not be initialized
%SYSBOOT-F-NOINITMMMG, Unable to initialize SYSBOOT memory managment, status = 00000124
Then instant machine reset.
V9.2 exhibits the same behavior, including not instantly resetting. With serial output, the output/error messages is exactly the same.
E9.2-1 on disk (before first boot/autogen) -
BOOTMGR> BOOT FS0
Booting...
%VMS_BOOTMGR-I-MAIN, Updating the environment store.
%VMS_BOOTMGR-I-MAIN, Allocating Kernel Memory.
%VMS_BOOTMGR-I-SMP, Enumerating Processors.
%VMS_BOOTMGR-I-MEMDISK, [BLOCKIO] Booting a local system disk image.
%VMS_BOOTMGR-I-MEMDISK, Loading DMM0...
%VMS_BOOTMGR-I-MEMDISK, Extracting SYSBOOT from DMM0...
%VMS_BOOTMGR-I-HWRPB, Initializing Kernel Data Structures.
%VMS_BOOTMGR-I-HWRPB, Initializing HWRPB for Primary Kernel.
%VMS_BOOTMGR-I-HWRPB, Configuring System Clocks... (~3 second delay)
%VMS_BOOTMGR-I-HWRPB, Initializing HWRPB for Dump Kernel.
%VMS_BOOTMGR-I-TRANSFER: Starting VSI OpenVMS
%%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
%SYSBOOT-I-CONSOLE, initializing Serial Port: 0x3F8
: 0x3F8
al Port
Current date and time: 04-23-2023 13:37:03
Welcome to VSI OpenVMS SYSBOOT, Baselevel XGF4, built on Jan 23 2023 14:03:45
HWRPB address 00000000.00600000, SWRPB address 00000000.00412400
SYSBOOT message flags address 0x00412418 value 0x00000000
_______________________________________________
GRAPHICAL OUTPUT HAS BEEN SUSPENDED
USE A TERMINAL UTILITY FOR ACCESS
_______________________________________________
%SYSBOOT-I-HPETTIMER, This system is using the HPET as the hardware timer
VSI Primary Kernel SYSBOOT Jan 23 2023 14:03:45
%SYSBOOT-I-ONEGB, 1-GB pages ARE available on this system
%SYSBOOT-I-MOUNT, Mounting the boot memory disk
%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
%SYSBOOT-I-LOADPARAM, Loading parameter file X86_64VMSSYS.PAR
%SYSBOOT-I-LOADFILE, Loaded file [SYS0.SYSEXE]X86_64VMSSYS.PAR
boo$usefile: startup file SYS$SYSTEM:INS_STARTUP.COM
%SYSBOOT-I-DISMOUNT, Dismounting the boot memory disk
%SYSBOOT-I-MEMDISKDISMNT, Boot memory disk dismounted
%SYSBOOT-F-NOPXML, The PXML database could not be initialized
%SYSBOOT-F-NOINITMMMG, Unable to initialize SYSBOOT memory managment, status = 00000124
Last edited by gdwnldsksc on Wed Apr 26, 2023 1:15 am, edited 3 times in total.
Re: OpenVMS 9.2-1 on real hardware success.
I was able to get the installer to boot on an HP Z240 but the installer can't find a hard drive to install on. I've tried the onboard SATA controller, onboard NVME and a HP P420i SAS controller from a DL360 Gen8.
Code: Select all
-----------
This procedure installs the OpenVMS X86-64 operating system.
All software and data files that were previously on the
target disk will be removed.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE] initialize
You must enter the device name for the target disk on which
OpenVMS X86-64 will be installed.
Enter device name for target disk: (? for choices) ?
Device Name Device Type Name Volume Label Size (blocks/xB)
------------ ------------------------- -------------- --------------------
No devices named * found
Enter device name for target disk: (? for choices) ?
Device Name Device Type Name Volume Label Size (blocks/xB)
------------ ------------------------- -------------- --------------------
No devices named * found
Enter device name for target disk: (? for choices)
$$$ sho dev
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DMM0: Offline 0
DMM1: Mounted wrtlck 0 X86E921OE 98160 13 1
LDM0: Online 0
LDM7528: Mounted wrtlck 0 MD23045A0DAA 25664 13 1
Device Device Error
Name Status Count
OPA0: Online 0
FTA0: Offline 0
Device Device Error
Name Status Count
SRA0: Online 0
MPA0: Online 0
$$$
-
- Valued Contributor
- Posts: 77
- Joined: Sat Apr 15, 2023 11:53 pm
- Reputation: 0
- Status: Offline
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
The only bare metal storage device that I had work successfully is a plain LSI SAS controller. Maybe a controller that was supported on Itanium will work, but my p222 didn't get recognized either.
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
I've got an LSI SAS 9240-4i controller but I think it's over 10 years old. The firmware is from 2014 and I don't think it's UEFI compatible. I'll see if I can dig out something more modern.
-
Topic author - Active Contributor
- Posts: 31
- Joined: Sat Apr 22, 2023 3:56 am
- Reputation: 0
- Status: Offline
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
The controller doesn't need to have UEFI firmware to work, UEFI will still enumerate it just fine like any other PCIe card. UEFI firmware is really only required for configuration/management of it if you can't launch BIOS based option roms for things like configuration, etc. I use reflashed H310's all the time (which is an LSI SAS 2008 based card - even older, i'd wager) for other purposes in UEFI only systems for boot volumes. (You can flash them with UEFI configuration capable firmware, but otherwise, just reflashing to IT mode and booting "just works" usually)
Last edited by gdwnldsksc on Wed Apr 26, 2023 1:13 am, edited 1 time in total.
-
Topic author - Active Contributor
- Posts: 31
- Joined: Sat Apr 22, 2023 3:56 am
- Reputation: 0
- Status: Offline
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
Supermicro X9DR3-LN4F+ boot failure due to ACPI issue
Configuration: 64GB SSD onboard SATA port. 2x E5-2697v2, 16GB memory, 1 stick.
VMS version: E9.2-1
Bios settings: Default, except serial port 2 disabled and hyperthreading disabled
:
Configuration: 64GB SSD onboard SATA port. 2x E5-2697v2, 16GB memory, 1 stick.
VMS version: E9.2-1
Bios settings: Default, except serial port 2 disabled and hyperthreading disabled
:
Code: Select all
%VMS_BOOTMGR-I-DEVICE, Using USB Keyboard.
Selected USB Keyboard Boot Protocol. Endpoint: 0x81, Interval: 10, PacketSize: 8
%VMS_BOOTMGR-I-DEVICE, Using USB Keyboard.
Selected USB Keyboard Boot Protocol. Endpoint: 0x81, Interval: 10, PacketSize: 8
VSI OpenVMS Boot Manager: V9.2-1, Build 122
ENABLED: Symmetric Multi-Processing
ENABLED: Boot Manager interaction
ENABLED: Crash Dump Processing
ENABLED: Console output to Legacy COM 1 Port
Checking Required Processor Features:
PASSED
Mapping UEFI Devices through Emulated Shell.
%VMS_BOOTMGR-I-MAP, Mapping Boot Devices.
Found 1 FS Handles
MAPPED UEFI DEVICES:
+ FS0: + BLK0: SATA HD (0x2, 0x1) HD0a65535a1:
PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,9CFABBBC-E0D1-11ED-B7F7-AA000400FEFF,0x2C7D00,0x3E800)
%VMS_BOOTMGR-I-DEVICE, Identifying System Devices.
SYSTEM DEVICES IDENTIFIED:
+ 2 Root Bridges
+ 1 Disk Devices or Partitions
+ 4 Simple Text Devices
+ 1 Serial Devices
+ 165 PCI Devices
%VMS_BOOTMGR-I-DEVICE, Scanning PCI/e Busses...
BOOT MANAGER DEVICE: DKB0
DEFAULT BOOT COMMAND: BOOT FS0 0 810031F3
CONNECT A REMOTE TERMINAL SESSION NOW.
BOOTMGR>
BOOTMGR>
BOOTMGR> BOOT FS0
BOOT MANAGER DEVICE: DKB0:
BOOT SOURCE DEVICE: FS0:
Compare BootDev: FS0, against TargetDev: FS0
MATCHED FS0 - E9_2_1
Booting...
%VMS_BOOTMGR-I-MAIN, Updating the environment store.
BOOT SOURCE PATH: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,9CFABBBC-E0D1-11ED-B7F7-AA000400FEFF,0x2C7D00,0x3E800)
%VMS_BOOTMGR-I-MAIN, Allocating Kernel Memory.
%VMS_BOOTMGR-I-SMP, Enumerating Processors.
CPU ENUMERATION:
CBB Summary Bitmask: <63:00> 00000000.00000001
CBB Unit Bitmasks (Bit Set = Enumerate this CPU ID):
00: <0063:0000> FFFFFFFF.FFFFFFFF
+ BSP_LAPIC_Address: 0xFEE00000
+ Enabled X2APIC Mode. Base MSR value: 0xFEE00D00
+ CPU(BP): PhysID:00 APIC_ID:00, UID:0x0000 (S:00 C:00 T:0) xAPIC
+ CPU(AP): PhysID:01 APIC_ID:02, UID:0x0001 (S:00 C:01 T:0) xAPIC
+ CPU(AP): PhysID:02 APIC_ID:04, UID:0x0002 (S:00 C:02 T:0) xAPIC
+ CPU(AP): PhysID:03 APIC_ID:06, UID:0x0003 (S:00 C:03 T:0) xAPIC
+ CPU(AP): PhysID:04 APIC_ID:08, UID:0x0004 (S:00 C:04 T:0) xAPIC
+ CPU(AP): PhysID:05 APIC_ID:10, UID:0x0005 (S:00 C:05 T:0) xAPIC
+ CPU(AP): PhysID:06 APIC_ID:16, UID:0x0006 (S:00 C:08 T:0) xAPIC
+ CPU(AP): PhysID:07 APIC_ID:18, UID:0x0007 (S:00 C:09 T:0) xAPIC
+ CPU(AP): PhysID:08 APIC_ID:20, UID:0x0008 (S:00 C:10 T:0) xAPIC
+ CPU(AP): PhysID:09 APIC_ID:22, UID:0x0009 (S:00 C:11 T:0) xAPIC
+ CPU(AP): PhysID:10 APIC_ID:24, UID:0x000A (S:00 C:12 T:0) xAPIC
+ CPU(AP): PhysID:11 APIC_ID:26, UID:0x000B (S:00 C:13 T:0) xAPIC
+ CPU(AP): PhysID:12 APIC_ID:32, UID:0x000C (S:01 C:00 T:0) xAPIC
+ CPU(AP): PhysID:13 APIC_ID:34, UID:0x000D (S:01 C:01 T:0) xAPIC
+ CPU(AP): PhysID:14 APIC_ID:36, UID:0x000E (S:01 C:02 T:0) xAPIC
+ CPU(AP): PhysID:15 APIC_ID:38, UID:0x000F (S:01 C:03 T:0) xAPIC
+ CPU(AP): PhysID:16 APIC_ID:40, UID:0x0010 (S:01 C:04 T:0) xAPIC
+ CPU(AP): PhysID:17 APIC_ID:42, UID:0x0011 (S:01 C:05 T:0) xAPIC
+ CPU(AP): PhysID:18 APIC_ID:48, UID:0x0012 (S:01 C:08 T:0) xAPIC
+ CPU(AP): PhysID:19 APIC_ID:50, UID:0x0013 (S:01 C:09 T:0) xAPIC
+ CPU(AP): PhysID:20 APIC_ID:52, UID:0x0014 (S:01 C:10 T:0) xAPIC
+ CPU(AP): PhysID:21 APIC_ID:54, UID:0x0015 (S:01 C:11 T:0) xAPIC
+ CPU(AP): PhysID:22 APIC_ID:56, UID:0x0016 (S:01 C:12 T:0) xAPIC
+ CPU(AP): PhysID:23 APIC_ID:58, UID:0x0017 (S:01 C:13 T:0) xAPIC
ACTUAL_CPUS: 24, MAX_CPUS: 64
MEMORY ALLOCATION SUMMARY:
KERNEL BASE: PA Floor: 0x00100000, Ceiling: 0x003FFFFF, WHAMI:0x00140000, PK_BAP:0x00100000, DK_BAP:0x00200000, BAP_SIZE:0x100000
MAIN KERNEL SYSBOOT: PA Floor: 0x00400000, Ceiling: 0x005FFFFF, Size: 0x00200000 (2MB)
MAIN KERNEL HWRPB: PA Floor: 0x00600000, Ceiling: 0x006FFFFF, Size: 0x00100000 (1MB)
DUMP KERNEL SYSBOOT: PA Floor: 0x00800000, Ceiling: 0x009FFFFF, Size: 0x00200000 (2MB)
DUMP KERNEL HWRPB: PA Floor: 0x00A00000, Ceiling: 0x00AFFFFF, Size: 0x00100000 (1MB)
DUMP KERNEL SYSTEM: PA Floor: 0x00000000.62211000, Ceiling: 0x00000000.72210FFF (256MB)
SELECTED BOOT DEVICE (Index 107):
Device Path: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,9CFABBBC-E0D1-11ED-B7F7-AA000400FEFF,0x2C7D00,0x3E800)
UEFI Details:
+ iCtrlType: PCI
+ iDeviceType: SATA
+ iMediaType: HD
+ UEFI Consistent Name: HD0a65535a1:
+ UEFI Mapped Name: FS0:
+ UEFI Label: E9_2_1
VMS Details:
+ VMS Device Name: DKB0: VMS: X86SYS , MemDisk: MD2311252F3A
+ IsFsDevice: YES - FS0:
+ IsBlkDevice: YES
+ IsBootableDeviceType: YES
+ IsBootableVmsDevice: YES
+ DeviceInfo: SATA Disk
+ PartitionType: GPT
+ PartitionNumber: 1
+ PartitionStart (LBN): 0x00000000.002C7D00
+ PartitionSize(Blocks): 0x00000000.0003E800
+ Size in MegaBytes: Volume: 60416 MB, Partition: 124 MB
+ PartitionGUID: 9CFABBBC-E0D1-11ED-B7F7-AA0000000000
+ Boot Source Path: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,9CFABBBC-E0D1-11ED-B7F7-AA000400FEFF,0x2C7D00,0x3E800)
+ Boot Source Root: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)
+ Overrode BlockIo with Root-BlockIo, Device Type: 1
**** Boot Path #1 - Local HD Boot ****
%VMS_BOOTMGR-I-MEMDISK, [BLOCKIO] Booting a local system disk image.
+ Reading GPT at LBN: 1 using 512 Byte Block Size
+ Reading GPTE Partition Array at LBN: 2 (Decimal)
+ Reading X86_EFI partition BootBlock at LBN: 2915584 (Decimal)
+ MDBOOT Signature and Checksum are good
+ Requested buffer for DMM0: 94265344 bytes (89 MB)
+ Allocated 4MB-aligned DMM0: 96468992 bytes (92 MB)
BOOT MEMORYDISK (DMM0): PA Floor: 0x00000000.04400000, Ceiling: 0x00000000.09FFFFFF, Bytes: 96468992 (92MB)
%VMS_BOOTMGR-I-MEMDISK, Loading DMM0...
+ Checksum of DMM0 after extraction: 0xD5F9FCE2
%VMS_BOOTMGR-I-MEMDISK, Extracting SYSBOOT from DMM0...
+ DMM0 PA: 0x00000000.04400000, SYSBOOT LBN (in DMM0): 1123 (0x463), PA (Src): 0x00000000.0448C600
+ SYSBOOT PA - PK: 0x00000000.00400000, DK: 0x00000000.00800000
%VMS_BOOTMGR-I-HWRPB, Initializing Kernel Data Structures.
%VMS_BOOTMGR-I-HWRPB, Initializing HWRPB for Primary Kernel.
%VMS_BOOTMGR-I-HWRPB, Configuring System Clocks... (~3 second delay)
+ LAPIC Timer Mode: X2APIC, Div: 0, Start: 0xFFFFFFFF, End: 0xFD04E0A2, Diff: 0x02FB1F5D
+ HPET (clock) Rev: 1, BAR: 0xFED00000, Period: 0x429B17F, Frequency: 14.32 MHz
EventTimerBlockId: 0x8086A701
VendorID: 0x8086
LegacyReplacement IRQ Routing Capable? Y
Counter size: 64
Number of comparators in first timer block: 7
Address Space ID: SYSTEM MEMORY
Register Bit Width: 64, Register Bit Offset: 0
HpetNumber 0
MainCounterMinimumClockTickInPeriodicMode: 14318
NO Page Protection
%VMS_BOOTMGR-I-HWRPB, Initializing HWRPB for Dump Kernel.
HWRPB SysDisk_Unit: 0
SETTING UP HWRPB PHYSICAL BOOT DEVICE INFO...
System Disk Unit Number: 0, PCI(Seg:00, Bus:00, Dev:1F, Func:2)
%VMS_BOOTMGR-I-TRANSFER: Starting VSI OpenVMS
>>> Enter 'Y' to display the final HWRPB contents:
**contents snipped, unable to attach (full output exceeds post limits and can't attach text files)**
>>> Press any key to continue:
Calling ExitBootServices...
%%%%%%%%%%% VSI OpenVMS (tm) x86-64 XDELTA Console %%%%%%%%%%%
%SYSBOOT-I-CONSOLE, initializing Serial Port: 0x3F8
▒h▒▒ɕ▒сdate and time: 04-26-2023 01:06:01
Welcome to VSI OpenVMS SYSBOOT, Baselevel XGF4, built on Jan 23 2023 14:03:45
HWRPB address 00000000.00600000, SWRPB address 00000000.00412400
SYSBOOT message flags address 0x00412418 value 0x00000000
%SYSBOOT-I-HPETTIMER, This system is using the HPET as the hardware timer
VSI Primary Kernel SYSBOOT Jan 23 2023 14:03:45
%XDELTA-I-SIO, initializing SERIALIO on Port: 00000000.000003F8
▒ҕ5%==Q▒I-ONEGB, 1-GB pages ARE available on this system
%SYSBOOT-I-MOUNT, Mounting the boot memory disk
%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
%SYSBOOT-I-LOADPARAM, Loading parameter file X86_64VMSSYS.PAR
%SYSBOOT-I-LOADFILE, Loaded file [SYS0.SYSEXE]X86_64VMSSYS.PAR
boo$usefile: startup file SYS$SYSTEM:INS_STARTUP.COM
%SYSBOOT-I-CONVBOOT, Invoking conversational boot
SYSBOOT> C
%SYSBOOT-I-DISMOUNT, Dismounting the boot memory disk
%SYSBOOT-I-MEMDISKDISMNT, Boot memory disk dismounted
Best PXML memory PA ranges: a000000:6220ffff and 100000000:47fffffff
System physical memory address range is 00000000.00000000 to 00000004.7fffffff
Total physical memory size is 0x00000004.80000000 bytes (18,432 MB)
Physical memory size excluding memory holes is 0x00000004.00446000 bytes (16,388 MB)
%SYSBOOT-I-ALLOCMAPBLT, Allocation bitmap built
Allocation area 1 addresses 00000000.0a000000 to 00000000.6220ffff, size 58210000 bytes
Allocation area 1 PFNs a000 to 6220f, count 58210 PFNs
Allocation bitmap 1 addresses 00000000.0a000000 to 00000000.0a00bfff, size c000 bytes
Allocation area 2 addresses 00000001.00000000 to 00000004.7fffffff, size 380000000 bytes
Allocation area 2 PFNs 100000 to 47ffff, count 380000 PFNs
Allocation bitmap 2 addresses 00000001.00000000 to 00000001.0006ffff, size 70000 bytes
Creating the S0 space page tables
%SYSBOOT-I-S0PT_CREATED, S0 space page tables created
Remapping Boot MemoryDisk to S2 space
MemoryDisk PA = 00000000.04400000, size = 0x5c00000 bytes
Boot memdisk size 0x5c00000 bytes
Mapping the boot memory disk into megapages
MemoryDisk VA = ffff8300.00000000, size = 0x5c00000 bytes
%SYSBOOT-I-MAP_MD, Boot MemoryDisk remapped to S2 space
%SYSBOOT-I-MOUNT, Mounting the boot memory disk
%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
Base RAD memsize 0x80000 4-kB PFNs
system PHD sysphdln 0x10000 bytes
nonpaged pool 0x4400000 exec_data_bytes 0x4410000
paged pool 0x400000 exec_data_bytes 0x4810000
errorlogs 0x4000 exec_data_bytes 0x4814000
exec_data_pages 0x2600 8-kB pages exec_data_bytes 0x4814000
S2 pool size (initial param)= 0x2 MB
boo$gq_npagedynsz_s2 (initial) 0x200000
S2 erlbuf = 0x4000 bytes bufcnt 0x4 bufpagelets 0x8
Final boo$gq_npagedynsz_s2 0x3fc000 Final: boo$gq_npagexpvir_s2 0x7fc000
giga page size 0x40000 pages slice size 0x400000 bytes
ldr$init_mem: LDRHP PA 00000000.0a018000
ldr$map_huge_page: Mapping big pages, type 1
ldr$map_huge_page: Mapped huge page, type 1, VA ffffffff.80400000, PA 00000000.0a400000, size 0x01000000, alignment 0x00400000
ldr$map_huge_page: Mapped huge page, type 2, VA ffffffff.81400000, PA 00000000.0b400000, size 0x04c00000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page, type 3, VA ffffffff.92bfe000, PA 00000000.10400000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page, type 4, VA ffffffff.92ffe000, PA 00000000.10c00000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page, type 5, VA ffff8300.05c00000, PA 00000000.11400000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapping big pages, type 6
ldr$map_huge_page: Mapped huge page, type 6, VA ffff8300.06400000, PA 00000000.11c00000, size 0x02000000, alignment 0x00400000
ldr$map_huge_page: Mapped huge page, type 7, VA ffff8300.08400000, PA 00000000.13c00000, size 0x01400000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page, type 8, VA ffff8300.09800000, PA 00000000.15400000, size 0x00400000, alignment 0x00002000
ldr$map_huge_page: Mapping big pages, type 9
ldr$map_huge_page: Mapped huge page, type 9, VA ffffffff.93400000, PA 00000000.15c00000, size 0x00800000, alignment 0x00400000
ldr$map_huge_page: Mapped huge page, type 10, VA ffffffff.93c00000, PA 00000000.16400000, size 0x00800000, alignment 0x00002000
ldr$map_huge_page: Mapped huge page, type 11, VA ffff8300.09c00000, PA 00000000.17000000, size 0x00400000, alignment 0x00002000
%SYSBOOT-I-ALLOCPGS, Loader huge pages allocated
Loading base system images
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYSLIB]SYS$PUBLIC_VECTORS.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$BASE_IMAGE.EXE
%SYSBOOT-I-LOADSYSIMGS, Base system images loaded
%SYSBOOT-I-CONIO, ConIoData: 0x7F28D318, ComPortBAR: 0x3F8
PFN database ffff8300.0a400000, mapped 2, big 0
PFN database allocated starting at VA ffff8300.0a400000 ending at VA ffff8300.133fffff
%SYSBOOT-I-INITDATA, Key system data cells initialized
Balance set slots size 0x78 PFNs each 2 num 1e
from PHD 388 maxpstct 100 SEC 30
Working set slots size 0x21c PFNs each 9
from wslpte 4 emptpte 5 wsllen 8
from pql$gdwsdefault_pages c00 sgn$gl_maxwscnt_pages 2000
Creating the SYSPHD
Allocating the error log buffers
%SYSBOOT-I-ALLOCERL, Allocated Error Log Buffers
Creating paged and nonpaged pools
Allocating USB Addressable Pool (UAP)
HWRPB 00000000.00600000 Kernel Base area PA 00000000.00100000
PK UAP offset 100000 size 100000
DK UAP offset 200000 size 100000
UAP allocated size 0x100000 bytes, mmg$gq_bap ffffffff.94478000
UAP physical addresses 200000 to 2fffff
%SYSBOOT-I-POOLINIT, Created Paged and Nonpaged Pools
Copying PXML database to S2 space
PXML database copied to address ffff8300.1361e000
%SYSBOOT-I-PXMLCOPY, Copied PXML Database to S2 space
Primary CPU database ffffffff.81c00000
%SYSBOOT-I-CREATECPUDB, Created the CPU Database
Copying the SWRPB and remapping the HWRPB
HWRPB size 0x9a000 bytes
Remapped HWRPB to ffffffff.94578000 copied SWRPB to ffffffff.81c01140
%SYSBOOT-I-REMAP, Moved HWRPB and SWRPB to system space
Gathering CPUID information
%SYSBOOT-I-CPUID, Gathered CPUID information
Remapping the IDT
IDT size 0x1000 bytes
Remapping IDT from 00000000.7f267000 to ffffffff.94613000
%SYSBOOT-I-REMAPIDT, Remapped IDT to system space
Initializing the primary CPU database and kernel stack
Allocating the system kernel stack
kernel stack allocated at VA ffffffff.94616000 for 0xc pages
Kernel stack pointer/base ffffffff.94621e00 limit ffffffff.94616000
icpudb: mcheck logout 00000000.00000000, still to be done
%SYSBOOT-I-INITCPUDB, Initialized Primary CPU Database
Slot VA ffffffff.9457f000
Slot cycle counter freq = a0f8a9f0
Slot clock int freq = 0
Slot itc freq = da87d7
Initializing the global page table
GPT addr ffff8300.13622000 size 0x2002000 bytes
%SYSBOOT-I-INITGPT, Initialized Global Page Table
Creating the boot SYI and PFN memory maps
%SYSBOOT-I-PFNMAP, Created PFN Memory Map
%SYSBOOT-i-PFNDB, Creating the PFN database
%SYSBOOT-I-CREATEPFNDB, Created PFN Database
%SYSBOOT-I-UEFIREMAP, Remapping UEFI Services...
%SYSBOOT-I-UEFIRUNVIRT, Enabling Virtual Runtime Services.
%SYSBOOT-I-LOADEXEC, Loading execlets...
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$PLATFORM_SUPPORT.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]ERRORLOG.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$ACPI.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYSTEM_PRIMITIVES_7_MIN.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYSTEM_DEBUG.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]SYS$OPDRIVER.EXE
%SYSBOOT-I-LOADFILE, Loaded file [VMS$COMMON.SYS$LDR]EXEC_INIT.EXE
%SYSBOOT-I-LOADEXEC, Execlets loaded
Copying boot port allocation class list
empty paclist
%SYSBOOT-I-PARMSCOPIED, System parameters copied to the base image
Summary of Huge Pages
Huge Page Type Description Start VA End VA Physical Address Size (Bytes)
0 GH_EXEC_CODE SHOULD BE EMPTY 00000000.00000000 00000000.00000000 00000000.00000000h 0h
1 GH_EXEC_DATA execlet image RW data S0 URKW ffffffff.80400000 ffffffff.813fffff 00000000.0a400000h 1000000h
2 EXEC S0 region exec runtime RW data S0 ERKW ffffffff.81400000 ffffffff.85ffffff 00000000.0b400000h 4c00000h
3 GH_RES_CODE resident image code S0 URX ffffffff.92bfe000 ffffffff.92ffdfff 00000000.10400000h 400000h
4 GH_RES_DATA resident image data S0 URKW ffffffff.92ffe000 ffffffff.933fdfff 00000000.10c00000h 400000h
5 EXEC S2 region exec runtime RW data S2 ERKW ffff8300.05c00000 ffff8300.05ffffff 00000000.11400000h 400000h
6 GH_EXEC_CODE_S2 execlet code S2 URX ffff8300.06400000 ffff8300.083fffff 00000000.11c00000h 2000000h
7 GH_RES_CODE_S2 resident image code S2 URX ffff8300.08400000 ffff8300.097fffff 00000000.13c00000h 1400000h
8 GH_EXEC_DATA_S2 execlet image RW data S2 ERKW ffff8300.09800000 ffff8300.09bfffff 00000000.15400000h 400000h
9 GH_RO_EXEC_S0 execlet image RO data S0 URX ffffffff.93400000 ffffffff.93bfffff 00000000.15c00000h 800000h
10 GH_RO_RES_S0 resident image RO data S0 URX ffffffff.93c00000 ffffffff.943fffff 00000000.16400000h 800000h
11 GH_RES_DATA_S2 resident image data S2 ERKW ffff8300.09c00000 ffff8300.09ffffff 00000000.17000000h 400000h
Bitmap VA Bitmap Size (Bytes) Slice Size (Bytes) Used Free Total
0 00000000.00000000 00000000.00000000h 00000000.00000000h 0 0 0
1 ffffffff.80000680 00000000.00001000h 00000000.00000200h 1,538 31,230 32,768
2 ffffffff.80001680 00000000.00000980h 00000000.00001000h 18,452 1,004 19,456
3 ffffffff.80002000 00000000.00000400h 00000000.00000200h 0 8,192 8,192
4 ffffffff.80002400 00000000.00000400h 00000000.00000200h 0 8,192 8,192
5 ffffffff.80002800 00000000.00000080h 00000000.00001000h 1,024 0 1,024
6 ffffffff.80002880 00000000.00004000h 00000000.00000100h 16,710 114,362 131,072
7 ffffffff.80006880 00000000.00000280h 00000000.00001000h 0 5,120 5,120
8 ffffffff.80006b00 00000000.00000400h 00000000.00000200h 0 8,192 8,192
9 ffffffff.80006f00 00000000.00000800h 00000000.00000200h 2,029 14,355 16,384
10 ffffffff.80007700 00000000.00000800h 00000000.00000200h 0 16,384 16,384
11 ffffffff.80007f00 00000000.00000400h 00000000.00000200h 0 8,192 8,192
%SYSBOOT-I-TRANSFER, Transferring to EXEC_INIT at: ffff8300.067cc300
%EXECINIT-I-PERCPU, initializing per-CPU database
%EXECINIT-I-INITS, calling initialization routines
%LOADER-I-INIT, initializing SYS$BASE_IMAGE
%LOADER-I-INIT, initializing SYS$PLATFORM_SUPPORT
%LOADER-I-INIT, initializing ERRORLOG
%LOADER-I-INIT, initializing SYS$ACPI
%LOADER-I-INIT, initializing SYSTEM_PRIMITIVES_7_MIN
SWIS Logging is currently OFF.
Turn on by setting SWIS_LOG bit 1 or setting SYSTEM_CHECK non-0 and clearing SWIS_LOG bit 3.
%LOADER-I-INIT, initializing SYSTEM_SYNCHRONIZATION_MIN
%LOADER-I-INIT, initializing SYSTEM_DEBUG
▒▒*I▒I-INIT, initializing SYS$OPDRIVERon Port: 00000000.000003F8
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-1
Copyright 2023 VMS Software, Inc.
%EXECINIT-I-INIT_MMG, init free list, outer mode page tables and PFN database
%EXECINIT-I-DELBS, deleting bootstrap VA space
%EXECINIT-I-SWIS_PRIM, initializing SWIS on primary CPU
MDS Mitigation active, variant verw(MD_CLEAR)
%EXECINIT-I-INITS, calling initialization routines
%LOADER-I-INIT, initializing SYSTEM_PRIMITIVES_7_MIN
SWIS Logging is currently OFF.
Turn on by setting SWIS_LOG bit 1 or setting SYSTEM_CHECK non-0 and clearing SWIS_LOG bit 3.
%LOADER-I-INIT, initializing SYSTEM_SYNCHRONIZATION_MIN
%LOADER-I-INIT, initializing SYSTEM_PRIMITIVES_7_MIN
SWIS Logging is currently OFF.
Turn on by setting SWIS_LOG bit 1 or setting SYSTEM_CHECK non-0 and clearing SWIS_LOG bit 3.
%EXECINIT-I-EPB, defining erase pattern buffer
%EXECINIT-I-SHELLF, building SHELL filespec
%EXECINIT-I-BTINIT, initializing boot driver
%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
%EXECINIT-I-RESMEMLIS, building reserved memory registry list
%EXECINIT-I-LDIMGS, loading exec images
%EXECINIT-I-LOADING, loading EXCEPTION.EXE
%LOADER-I-INIT, initializing EXCEPTION
%EXECINIT-I-LOADING, loading IO_ROUTINES.EXE
%LOADER-I-INIT, initializing IO_ROUTINES
%EXECINIT-I-LOADING, loading SYSDEVICE.EXE
%LOADER-I-INIT, initializing SYSDEVICE
%EXECINIT-I-LOADING, loading PROCESS_MANAGEMENT.EXE
%LOADER-I-INIT, initializing PROCESS_MANAGEMENT
%EXECINIT-I-LOADING, loading LOCKING.EXE
%LOADER-I-INIT, initializing LOCKING
%EXECINIT-I-LOADING, loading SHELL8K.EXE
%LOADER-I-INIT, initializing SHELL8K
%EXECINIT-I-LOADING, loading LOGICAL_NAMES.EXE
%LOADER-I-INIT, initializing LOGICAL_NAMES
%EXECINIT-I-LOADING, loading F11BXQP.EXE
%LOADER-I-INIT, initializing F11BXQP
%EXECINIT-I-LOADING, loading RMS.EXE
%LOADER-I-INIT, initializing RMS
%EXECINIT-I-LOADING, loading IMAGE_MANAGEMENT.EXE
%LOADER-I-INIT, initializing IMAGE_MANAGEMENT
%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
%EXECINIT-I-LOADING, loading SECURITY.EXE
%LOADER-I-INIT, initializing SECURITY
%EXECINIT-I-LOADING, loading SYSGETSYI.EXE
%LOADER-I-INIT, initializing SYSGETSYI
%EXECINIT-I-LOADING, loading SYS$XFCACHE.EXE
%LOADER-I-INIT, initializing SYS$XFCACHE
%EXECINIT-I-LOADING, loading SYS$VM.EXE
%LOADER-I-INIT, initializing SYS$VM
%EXECINIT-I-LOADING, loading MESSAGE_ROUTINES.EXE
%LOADER-I-INIT, initializing MESSAGE_ROUTINES
%EXECINIT-I-LOADING, loading SYSLICENSE.EXE
%LOADER-I-INIT, initializing SYSLICENSE
%EXECINIT-I-LOADING, loading SYS$VFS.EXE
%EXECINIT-E-LOADERR, error loading SYS$VFS.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SYS$GFS2.EXE
%EXECINIT-E-LOADERR, error loading SYS$GFS2.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SYS$VAFS.EXE
%EXECINIT-E-LOADERR, error loading SYS$VAFS.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SYS$TRANSACTION_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$TRANSACTION_SERVICES
%EXECINIT-I-LOADING, loading SYS$UTC_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$UTC_SERVICES
%EXECINIT-I-LOADING, loading SYS$NETWORK_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$NETWORK_SERVICES
%DECnet-I-LOADED, network base image loaded, version = 05.92.04
%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
%DECnet-W-ZEROLEN, length of file is zero -- SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
%EXECINIT-I-LOADING, loading SYS$IPC_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$IPC_SERVICES
%EXECINIT-I-LOADING, loading SYSLDR_DYN.EXE
%LOADER-I-INIT, initializing SYSLDR_DYN
%SYSBOOT-I-MEMDISKMNT, Boot memory disk mounted
%EXECINIT-I-LOADING, loading SYS$MME_SERVICES.EXE
%LOADER-I-INIT, initializing SYS$MME_SERVICES
%EXECINIT-I-LOADING, loading SYS$NTA.EXE
%EXECINIT-E-LOADERR, error loading SYS$NTA.EXE, status = 00000910
%EXECINIT-I-LOADING, loading SSPI.EXE
%EXECINIT-E-LOADERR, error loading SSPI.EXE, status = 00000910
%EXECINIT-I-LOADING, loading ACME.EXE
%LOADER-I-INIT, initializing ACME
%EXECINIT-I-LOADING, loading SWIS$DEBUG.EXE
%LOADER-I-INIT, initializing SWIS$DEBUG
%EXECINIT-I-IOCONFIG, configuring the I/O database
Entering ini$iomap()
%GPS-I-ACPI_SUPPORT, Initializing ACPI Operating System Layer...
%ACPI-I-INITMMIO, PCIe MMIO space mapped to 0xFFFF8200.80000000
%ACPI-I-INIT, Initializing ACPI Subsystem...
ACPI: RSDP 0x000000007DFF5000 000024 (v02 SUPERM)
ACPI: XSDT 0x000000007DFF5090 0000A4 (v01 SUPERM SMCI--MB 00000001 AMI 00010013)
ACPI: FACP 0x000000007DFFFB48 0000F4 (v04 SUPERM SMCI--MB 00000001 AMI 00010013)
ACPI: DSDT 0x000000007DFF51D0 00A975 (v02 SUPERM SMCI--MB 00000000 INTL 20091112)
ACPI: FACS 0x000000007E0C9080 000040
ACPI: APIC 0x000000007DFFFC40 0001B4 (v03 00000001 AMI 00010013)
ACPI: FPDT 0x000000007DFFFDF8 000044 (v01 00000001 AMI 00010013)
ACPI: SRAT 0x000000007DFFFE40 000430 (v01 A M I AMI SRAT 00000001 AMI. 00000000)
ACPI: SLIT 0x000000007E000270 000030 (v01 A M I AMI SLIT 00000000 AMI. 00000000)
ACPI: HPET 0x000000007E0002A0 000038 (v01 SUPERM SMCI--MB 00000001 AMI. 00000005)
ACPI: PRAD 0x000000007E0002D8 0000CD (v02 PRADID PRADTID 00000001 MSFT 04000000)
ACPI: SPMI 0x000000007E0003A8 000040 (v05 A M I OEMSPMI 00000000 AMI. 00000000)
ACPI: SSDT 0x000000007E0003E8 0C7AE8 (v02 INTEL CpuPm 00004000 INTL 20091112)
ACPI: BGRT 0x000000007E0C7ED0 000038 (v00 SUPERM SMCI--MB 00000001 AMI 00010013)
ACPI: EINJ 0x000000007E0C7F08 000130 (v01 AMI AMI EINJ 00000000 00000000)
ACPI: ERST 0x000000007E0C8038 000230 (v01 AMIER AMI ERST 00000000 00000000)
ACPI: HEST 0x000000007E0C8268 00027C (v01 AMI AMI HEST 00000000 00000000)
ACPI: BERT 0x000000007E0C84E8 000030 (v01 AMI AMI BERT 00000000 00000000)
ACPI: DMAR 0x000000007E0C8518 000168 (v01 A M I OEMDMAR 00000001 INTL 00000001)
ACPI: MCFG 0x000000007E0C8680 00003C (v01 SUPERM SMCI--MB 00000001 MSFT 00000097)
%ACPI-I-LOAD, Loading ACPI Tables...
ACPI: 2 ACPI AML tables successfully acquired and loaded
%ACPI-I-SUBS, Enabling ACPI Subsystem...
%ACPI-I-OBJS, Initializing ACPI Objects...
VSI Dump Kernel SYSBOOT Jan 23 2023 14:03:45
%SYSTEM-W-POOLEXPF, Pool expansion failed -- insufficient NPAGEVIR
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Failure resolving symbol [Could not get pathname], AE_NO_MEMORY (20210930/dswload2-479)
ACPI Error: AE_NO_MEMORY, During name lookup/catalog (20210930/psobject-372)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Failure resolving symbol [Could not get pathname], AE_NO_MEMORY (20210930/dswload2-479)
ACPI Error: AE_NO_MEMORY, During name lookup/catalog (20210930/psobject-372)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Failure resolving symbol [Could not get pathname], AE_NO_MEMORY (20210930/dswload2-479)
ACPI Error: AE_NO_MEMORY, During name lookup/catalog (20210930/psobject-372)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Failure resolving symbol [Could not get pathname], AE_NO_MEMORY (20210930/dswload2-479)
ACPI Error: AE_NO_MEMORY, During name lookup/catalog (20210930/psobject-372)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Could not allocate an object descriptor (20210930/dsutils-813)
ACPI Error: Failure resolving symbol [Could not get pathname], AE_NO_MEMORY (20210930/dswload2-479)
ACPI Error: AE_NO_MEMORY, During name lookup/catalog (20210930/psobject-372)
ACPI Error: Aborting method \ due to previous error (AE_NO_MEMORY) (20210930/psparse-688)
ACPI Error: Invalid zero thread count in method (20210930/dsmethod-971)
ACPI Error: Invalid OwnerId: 0x000 (20210930/utownerid-318)
ACPI Error: AE_NO_MEMORY, (SSDT: CpuPm) while loading table (20210930/tbxfload-352)
ACPI Error: 1 table load failures, 1 successful (20210930/tbxfload-375)
Dump kernel has bugchecked, code = 000001C8
**** Bugcheck exception frame at FFFFFFFF.825B6350:
TRAP_TYPE = 00000041
FSBASE = 00000000.00000000
RAX = 00000000.00000600
RDI = 00000000.00100002
RSI = 00000000.000001C8
RDX = FFFFFFFF.825B6CA0
RCX = FFFFFFFF.825B6670
R8 = 00000000.00000000
R9 = 00000000.00000000
RBX = FFFFFFFF.800BAE08
RBP = FFFFFFFF.825B6960
R10 = 00000000.00000012
R11 = 00000000.00000001
R12 = FFFFFFFF.825B7D28
R13 = 00000000.00000000
R14 = 00000000.0000000C
R15 = FFFF8300.062E4600
ALPHAREG R0 = 00000000.00000034
R1 = 00000000.00000480
R2 = FFFFFFFF.825B7D10
R3 = FFFFFFFF.800ACBB0
R4 = FFFFFFFF.800AFFC5
R5 = 00000000.00000000
R6 = 00000000.00000003
R7 = 00000000.00000000
R8 = 00000000.00000000
R9 = 00000000.00000000
R10 = 00000000.00000000
R11 = FFFFFFFF.8250E000
R12 = FFFFFFFF.80C19140
R13 = FFFFFFFF.80C18000
R14 = 00000000.00000000
R15 = 00000000.00000000
R16 = FFFFFFFF.80013880
R17 = FFFFFFFF.80013880
R18 = FFFFFFFF.80146034
R19 = FFFFFFFF.825B74B0
R20 = 00000000.00000001
R21 = 00000000.00000006
R22 = FFFF8300.061119CD
R23 = FFFFFFFF.80017630
R24 = FFFFFFFF.81A9F440
R25 = 00000000.00000001
R26 = FFFF8300.061119CD
R27 = 00000000.00000000
R28 = 00000000.81A9F440
R29 = 00000000.00000000
R30 = 00000000.00000000
R31 = 00000000.00000000
PREV_FRAME = FFFFFFFF.825B6CA0
PREV_FRAME_MODE = 00000000
CPU_NUM = 00000000
VECTOR = 00000000.00000020
ERROR_CODE = 00000000.00000600
RIP = FFFF8300.063B2092
CS = 00000000.00000008
RFLAGS = 00000000.00000082
RSP = FFFFFFFF.825B6538
SS = 00000000.00000010
**** Original exception frame at FFFFFFFF.825B6CA0:
TRAP_TYPE = 0000000E
FSBASE = 00000000.00000000
RAX = FFFFFFFF.82787004
RDI = 00000000.FFFFFF00
RSI = 00000000.00000001
RDX = 00000000.0800000A
RCX = 00000000.0800000A
R8 = 00000000.00000000
R9 = FFFFFFFF.81AA0598
RBX = FFFFFFFF.825B7E01
RBP = FFFFFFFF.825B6F60
R10 = FFFFFFFF.820AF480
R11 = FFFF8300.061B1400
R12 = FFFFFFFF.825B7D28
R13 = 00000000.00000000
R14 = 00000000.00000000
R15 = FFFF8300.062E4614
ALPHAREG R0 = 00000000.00000034
R1 = 00000000.00000480
R2 = FFFFFFFF.825B7D10
R3 = FFFFFFFF.800ACBB0
R4 = FFFFFFFF.800AFFC5
R5 = 00000000.00000000
R6 = 00000000.00000003
R7 = 00000000.00000000
R8 = 00000000.00000000
R9 = 00000000.00000000
R10 = 00000000.00000000
R11 = FFFFFFFF.8250E000
R12 = FFFFFFFF.80C19140
R13 = FFFFFFFF.80C18000
R14 = 00000000.00000000
R15 = 00000000.00000000
R16 = FFFFFFFF.80013880
R17 = FFFFFFFF.80013880
R18 = FFFFFFFF.80146034
R19 = FFFFFFFF.825B74B0
R20 = 00000000.00000001
R21 = 00000000.00000006
R22 = FFFF8300.061119CD
R23 = FFFFFFFF.80017630
R24 = FFFFFFFF.81A9F440
R25 = 00000000.00000001
R26 = FFFF8300.061119CD
R27 = 00000000.00000000
R28 = 00000000.81A9F440
R29 = 00000000.00000000
R30 = 00000000.00000000
R31 = 00000000.00000000
PREV_FRAME = 00000000.00000000
PREV_FRAME_MODE = 00000000
CPU_NUM = 00000000
VECTOR = 00000000.0000000E
ERROR_CODE = 00000000.00000003
RIP = FFFF8300.060DAB0E
CS = 00000000.00000008
RFLAGS = 00000000.00010246
RSP = FFFFFFFF.825B6E80
SS = 00000000.00000010
**kernel stack and loaded images snipped, unable to attach (full output exceeds post limits and can't attach text files)**
Restarting the system...
-
- Master
- Posts: 201
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
Maybe try a conversational boot (set low bit in boot flags) into SYSBOOT> and increase NPAGEVIR ?gdwnldsksc wrote: ↑Wed Apr 26, 2023 1:14 amSupermicro X9DR3-LN4F+ boot failure due to ACPI issue
Code: Select all
... VSI Dump Kernel SYSBOOT Jan 23 2023 14:03:45 %SYSTEM-W-POOLEXPF, Pool expansion failed -- insufficient NPAGEVIR ...
Volker.
-
Topic author - Active Contributor
- Posts: 31
- Joined: Sat Apr 22, 2023 3:56 am
- Reputation: 0
- Status: Offline
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
I did attempt that (both doubling the default value that SHOW NPAGEVIR displayed, and then quadrupling it). I also attempted the same with NPAGEDYN (doubled then quadrupled) and doing both in lockstep, with no change in behavior.volkerhalle wrote: ↑Wed Apr 26, 2023 2:36 amMaybe try a conversational boot (set low bit in boot flags) into SYSBOOT> and increase NPAGEVIR ?gdwnldsksc wrote: ↑Wed Apr 26, 2023 1:14 amSupermicro X9DR3-LN4F+ boot failure due to ACPI issue
Code: Select all
... VSI Dump Kernel SYSBOOT Jan 23 2023 14:03:45 %SYSTEM-W-POOLEXPF, Pool expansion failed -- insufficient NPAGEVIR ...
Volker.
Re: E9.2-1 Hardware that doesn't work/potentially incompatible. (and what failed)
I installed a LSI sas3041e and flashed it to IT mode. The bootmgr sees it and appears to be happy...gdwnldsksc wrote: ↑Wed Apr 26, 2023 1:13 amThe controller doesn't need to have UEFI firmware to work, UEFI will still enumerate it just fine like any other PCIe card. UEFI firmware is really only required for configuration/management of it if you can't launch BIOS based option roms for things like configuration, etc. I use reflashed H310's all the time (which is an LSI SAS 2008 based card - even older, i'd wager) for other purposes in UEFI only systems for boot volumes. (You can flash them with UEFI configuration capable firmware, but otherwise, just reflashing to IT mode and booting "just works" usually)
Code: Select all
---------------
%VMS_BOOTMGR-I-MAP, Mapping Boot Devices.
Found 2 FS Handles
MAPPED UEFI DEVICES:
+ FS0: + BLK0: SCSI HD (0x2, 0x1) HD1j0b:
PciRoot(0x0)/Pci(0x1D,0x0)/Pci(0x0,0x0)/Scsi(0x9,0x0)/HD(1,GPT,C6413737-8FD0 -4E4F-903D-5570AE14705D,0x800,0x3A385800)
+ FS1: + BLK1: SATA CD/DVD (0x0, 0x0) CD0c0a0:
PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0x0,0x0)/CDROM(0x0)
Checking UEFI Disk 1 of 2.
PciRoot(0x0)/Pci(0x1D,0x0)/Pci(0x0,0x0)/Scsi(0x9,0x0)/HD(1,GPT,C6413737-8FD0-4 E4F-903D-5570AE14705D,0x800,0x3A385800)
Topology: S00:B01:D00:F00, Class:01, SubClass:00, ExClass:00
PCI Address: 0x01000000
>>> Press 'Q' to Quit or any other key to continue:
Found Controller Number 2 at Index: 12
+ Inserted File Device: FS0:
SCSI: PUN: 9, LUN: 0
Resulting SCSI Unit Number: 900
+ Supports BlockIO
+ Fixed Media
+ Supports FileIO
+ Is a bootable device
+ Is a Hard Disk
+ Has a GPT
+ Accessible Root
+ Has UEFI Volume Label
- No VMS Volume Label
ASSIGNED: DKB900
--------