• Unable to boot 6.10.0-rc2 after upgrading from 6.10.0-rc1 Gigabyte Z590 AORUS MASTER


    JD3V1L
    • Urgent

    System specifications, Gigabyte Z590 AORUS MASTER/10700K/128GB RAM/GTX 1660.

     

    Legacy boot gets it to boot the furthest, booting of motherboard USB 2 header port gets stuck at bellow error message

    ACPI:PCI Interrupt Link LNKH configured for IRQ 0

    fyi I get to same boot point with 3.1 ports.

     

    Edit, Subsequent testing i have managed to get it to boot a bit further from another upgrade attempt.

     

    ACPI: PCI: Interrupt link LNKH configured for IRQ 0

    ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.PGOF.PBGE], AE_NOT_FOUND (20210604/psargs-330

    ACPI Error: Aborting method \_SB.PC00.PGOF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)

    ACPI Error: Aborting method \_SB.PC00.PEG2.PG02._OFF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)

     

    Some of the things I have tried:

    Legacy boot enabled (CSM Support)

    Disabled igpu

    Removed nvidia GTX 1660

    Swapping usb media, multiple USB stick brands, different ports USB3.1 etc

    All GUI and Command line options get stuck at the same point.

     

    Modifying EFI folder -
    Switching on EFI gets stuck at loading bzroot bzroot-gui on all cli and gui options

     

    Switching back to 6.9.2 OR 6.10.0-rc1 clean install or from 6.10.0-rc1 backup boots perfectly.

    Booting 6.10.0-rc1 with EFI enabled works fine.

    same result with clean install of RC2, legacy and EFI same result, gets stuck at same exact spot for each scenario.  

     

    I tried second motherboard ASRock Z490 Phantom Gaming-ITX/TB3, which has similar issues on most usb ports, booting legacy with USB 3.2 Gen1 5Gb/s works.

    booting USB 3.2 Gen2 10Gb/s gets stuck at mid boot, I don’t remember exact error message, but it was sooner in the boot process, did not reach ACPI: stage.

    turning on EFI gets stuck at bzroot for cli and gui similar to the other motherboard.   




    User Feedback

    Recommended Comments

    This may not be the answer as not 100% sure ACPI is the issue but you can turn it off in syslinux.cfg for a test to see if it boots.

     

    Edit the file on the flash and change the append line to have acpi=off, not sure what other entries your config may have.

     

    i.e. append initrd=/bzroot acpi=off

     

    root@computenode:/boot/syslinux# cat syslinux.cfg
    default menu.c32
    menu title Lime Technology, Inc.
    prompt 0
    timeout 50
    label Unraid OS
      menu default
      kernel /bzimage
      append initrd=/bzroot isolcpus=2-11 acpi_enforce_resources=lax
    label Unraid OS GUI Mode
      kernel /bzimage
      append initrd=/bzroot,/bzroot-gui isolcpus=2-11 acpi_enforce_resources=lax
    label Unraid OS Safe Mode (no plugins, no GUI)
      kernel /bzimage
      append initrd=/bzroot unraidsafemode
    label Unraid OS GUI Safe Mode (no plugins)
      kernel /bzimage
      append initrd=/bzroot,/bzroot-gui unraidsafemode
    label Memtest86+
      kernel /memtest

     

     

    Link to comment
    23 hours ago, SimonF said:

    This may not be the answer as not 100% sure ACPI is the issue but you can turn it off in syslinux.cfg for a test to see if it boots.

     

    Edit the file on the flash and change the append line to have acpi=off, not sure what other entries your config may have.

     

    i.e. append initrd=/bzroot acpi=off

     

    root@computenode:/boot/syslinux# cat syslinux.cfg
    default menu.c32
    menu title Lime Technology, Inc.
    prompt 0
    timeout 50
    label Unraid OS
      menu default
      kernel /bzimage
      append initrd=/bzroot isolcpus=2-11 acpi_enforce_resources=lax
    label Unraid OS GUI Mode
      kernel /bzimage
      append initrd=/bzroot,/bzroot-gui isolcpus=2-11 acpi_enforce_resources=lax
    label Unraid OS Safe Mode (no plugins, no GUI)
      kernel /bzimage
      append initrd=/bzroot unraidsafemode
    label Unraid OS GUI Safe Mode (no plugins)
      kernel /bzimage
      append initrd=/bzroot,/bzroot-gui unraidsafemode
    label Memtest86+
      kernel /memtest

     

     

    thanks for the suggestion, it fails shortly after a bunch of usb port detection's. last few lines from console below.

     

    hub 4-0:1.0: 4 ports detected

    usbcore: registered new interface driver usb-storage

    i8042: PNP: No PS/2 controller found
    i8042: Probing ports directly.

    Link to comment
    45 minutes ago, JD3V1L said:

    thanks for the suggestion, it fails shortly after a bunch of usb port detection's. last few lines from console below.

     

    hub 4-0:1.0: 4 ports detected

    usbcore: registered new interface driver usb-storage

    i8042: PNP: No PS/2 controller found
    i8042: Probing ports directly.

    Are you able to post diagnostics from your RC1 version. 

     

    Have you set any PCI devices to be mapped to VFIO in the systems devices? i.e. USB controllers?

    Link to comment
    13 hours ago, SimonF said:

    Are you able to post diagnostics from your RC1 version. 

     

    Have you set any PCI devices to be mapped to VFIO in the systems devices? i.e. USB controllers?

    I get the same boot failure on a clean fresh install of RC2 as i do when using an inline upgrade. 

    jd3v1lnas-diagnostics-20211229-2216.zipjd3v1lnas-diagnostics-20211229-2216.zipMost recent error messages shows a bit more detail.

     

    ACPI: PCI: Interrupt link LNKH configured for IRQ 0

    ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.PGOF.PBGE], AE_NOT_FOUND (20210604/psargs-330

    ACPI Error: Aborting method \_SB.PC00.PGOF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)

    ACPI Error: Aborting method \_SB.PC00.PEG2.PG02._OFF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)

    Link to comment
    16 minutes ago, JD3V1L said:

    I get the same boot failure on a clean fresh install of RC2 as i do when using an inline upgrade. 

    jd3v1lnas-diagnostics-20211229-2216.zipjd3v1lnas-diagnostics-20211229-2216.zipMost recent error messages shows a bit more detail.

     

    ACPI: PCI: Interrupt link LNKH configured for IRQ 0

    ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.PGOF.PBGE], AE_NOT_FOUND (20210604/psargs-330

    ACPI Error: Aborting method \_SB.PC00.PGOF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)

    ACPI Error: Aborting method \_SB.PC00.PEG2.PG02._OFF due to previous error (AE_NOT_FOUND) (20210604/psparse-529)

    Did you try setting acpi=off? Haveyou checked for bios updates?

    Edited by SimonF
    Link to comment
    2 hours ago, SimonF said:

    Did you try setting acpi=off? Haveyou checked for bios updates?

    On the latest bios update, upgraded to latest version as part of troubleshooting attempts. when i set acpi=off it fails at bellow error with legacy boot.

     

    hub 4-0:1.0: 4 ports detected

    usbcore: registered new interface driver usb-storage

    i8042: PNP: No PS/2 controller found
    i8042: Probing ports directly.

     

    Testing EFI with acpi=off i managed to get a clean system to boot.

     

    going to performing a bunch of user case testing to see if i can get my main usb working with vm pass-though ect. .

    Edited by JD3V1L
    Link to comment

    i can get it to boot under efi with acpi=off but it kills all pass-though iommu groups ect, any ideas to make the hba card  visible to the freenas vm.  

    Link to comment
    5 hours ago, JD3V1L said:

    On the latest bios update, upgraded to latest version as part of troubleshooting attempts. when i set acpi=off it fails at bellow error with legacy boot.

     

    hub 4-0:1.0: 4 ports detected

    usbcore: registered new interface driver usb-storage

    i8042: PNP: No PS/2 controller found
    i8042: Probing ports directly.

     

    Testing EFI with acpi=off i managed to get a clean system to boot.

     

    going to performing a bunch of user case testing to see if i can get my main usb working with vm pass-though ect. .

     

    5 hours ago, SimonF said:

    Did you try setting acpi=off? Haveyou checked for bios updates?

    i had to fallback to rc1 as i need iommu remapping for my user case, HBA card, GPU pass-though for VM's ect. i am hoping this testing can help developers find a fix. something breaks for acpi in RC2 for this motherboard. turning acpi=off with efi boot enable got it to boot at least.

    Link to comment
    On 12/30/2021 at 7:00 AM, SimonF said:

    Are you able to post diagnostics for both rc1 and rc2? Have you looked at the BIOS for acpi?

    Hi Simon,

     

    Were you able to track this back to a change in RC2? any chance i can try test a build with the RC2 ACPI changes omitted? happy to test anything you need.

    Link to comment
    4 hours ago, JD3V1L said:

    Hi Simon,

     

    Were you able to track this back to a change in RC2? any chance i can try test a build with the RC2 ACPI changes omitted? happy to test anything you need.

    Hi These are the differnences between 6.9.2 and RC2

     

    If you can provide output of this for rc1 I can add that into the spreadsheet.

     

    cat /usr/src/linux-5.15.15-Unraid/.config | grep ACPI you will need to change to the correct kernel directory for rc1 as it will not be linux-5.15.15

     

    Spoiler

    image.thumb.png.bc905cfacaa1be4ea83ef49d6d666666.png6.9.2rc2

     

     

    Link to comment
    14 hours ago, SimonF said:

    Hi These are the differnences between 6.9.2 and RC2

     

    If you can provide output of this for rc1 I can add that into the spreadsheet.

     

    cat /usr/src/linux-5.15.15-Unraid/.config | grep ACPI you will need to change to the correct kernel directory for rc1 as it will not be linux-5.15.15

     

      Hide contents

    image.thumb.png.bc905cfacaa1be4ea83ef49d6d666666.png6.9.2rc2

     

     

     

    As requested, please see output.

     

    cat /usr/src/linux-5.13.8-Unraid/.config | grep ACPI
    CONFIG_X86_64_ACPI_NUMA=y
    # Power management and ACPI options
    CONFIG_ARCH_SUPPORTS_ACPI=y
    CONFIG_ACPI=y
    CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y
    CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y
    CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
    # CONFIG_ACPI_DEBUGGER is not set
    CONFIG_ACPI_SPCR_TABLE=y
    # CONFIG_ACPI_FPDT is not set
    CONFIG_ACPI_LPIT=y
    CONFIG_ACPI_SLEEP=y
    CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y
    # CONFIG_ACPI_EC_DEBUGFS is not set
    # CONFIG_ACPI_AC is not set
    # CONFIG_ACPI_BATTERY is not set
    CONFIG_ACPI_BUTTON=m
    # CONFIG_ACPI_TINY_POWER_BUTTON is not set
    CONFIG_ACPI_VIDEO=m
    CONFIG_ACPI_FAN=m
    # CONFIG_ACPI_TAD is not set
    CONFIG_ACPI_DOCK=y
    CONFIG_ACPI_CPU_FREQ_PSS=y
    CONFIG_ACPI_PROCESSOR_CSTATE=y
    CONFIG_ACPI_PROCESSOR_IDLE=y
    CONFIG_ACPI_CPPC_LIB=y
    CONFIG_ACPI_PROCESSOR=y
    CONFIG_ACPI_IPMI=m
    CONFIG_ACPI_HOTPLUG_CPU=y
    CONFIG_ACPI_PROCESSOR_AGGREGATOR=m
    CONFIG_ACPI_THERMAL=m
    CONFIG_ACPI_CUSTOM_DSDT_FILE=""
    CONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=y
    CONFIG_ACPI_TABLE_UPGRADE=y
    # CONFIG_ACPI_DEBUG is not set
    # CONFIG_ACPI_PCI_SLOT is not set
    CONFIG_ACPI_CONTAINER=y
    # CONFIG_ACPI_HOTPLUG_MEMORY is not set
    CONFIG_ACPI_HOTPLUG_IOAPIC=y
    # CONFIG_ACPI_SBS is not set
    # CONFIG_ACPI_HED is not set
    # CONFIG_ACPI_CUSTOM_METHOD is not set
    # CONFIG_ACPI_BGRT is not set
    # CONFIG_ACPI_NFIT is not set
    CONFIG_ACPI_NUMA=y
    # CONFIG_ACPI_HMAT is not set
    CONFIG_HAVE_ACPI_APEI=y
    CONFIG_HAVE_ACPI_APEI_NMI=y
    # CONFIG_ACPI_APEI is not set
    # CONFIG_ACPI_DPTF is not set
    # CONFIG_ACPI_EXTLOG is not set
    CONFIG_ACPI_ADXL=y
    # CONFIG_ACPI_CONFIGFS is not set
    CONFIG_X86_ACPI_CPUFREQ=m
    CONFIG_X86_ACPI_CPUFREQ_CPB=y
    # end of Power management and ACPI options
    CONFIG_PNPACPI=y
    CONFIG_ATA_ACPI=y
    # CONFIG_PATA_ACPI is not set
    # ACPI drivers
    CONFIG_GPIO_ACPI=y
    # ACPI drivers
    CONFIG_SENSORS_ACPI_POWER=m
    # ACPI INT340X thermal drivers
    CONFIG_ACPI_THERMAL_REL=m
    # end of ACPI INT340X thermal drivers
    # CONFIG_MFD_INTEL_LPSS_ACPI is not set
    # CONFIG_I2C_HID_ACPI is not set
    CONFIG_DMA_ACPI=y
    CONFIG_XEN_ACPI_PROCESSOR=y
    CONFIG_XEN_ACPI=y
    CONFIG_ACPI_WMI=m
    # CONFIG_ACPI_CMPC is not set
    # CONFIG_SYSTEM76_ACPI is not set

    Link to comment

    These are the differences between rc2 and rc1. 

     

    image.thumb.png.483cce06b90347fc28bafb00a1a30b8b.png6.9.2dif rc2 and 6.9.2rc1Diff rc1 and rc2rc2

    Mismatch# CONFIG_ACPI_FPDT is not setMismatchCONFIG_ACPI_FPDT=y

    # CONFIG_ACPI_AC is not setMismatch# CONFIG_ACPI_AC is not setMismatchCONFIG_ACPI_AC=m

    # CONFIG_ACPI_BATTERY is not setMismatch# CONFIG_ACPI_BATTERY is not setMismatchCONFIG_ACPI_BATTERY=m

    # CONFIG_ACPI_TAD is not setMismatch# CONFIG_ACPI_TAD is not setMismatchCONFIG_ACPI_TAD=m

    # CONFIG_ACPI_HOTPLUG_MEMORY is not setMismatch# CONFIG_ACPI_HOTPLUG_MEMORY is not setMismatchCONFIG_ACPI_HOTPLUG_MEMORY=y

    # CONFIG_ACPI_HED is not setMismatch# CONFIG_ACPI_HED is not setMismatchCONFIG_ACPI_HED=y

    # CONFIG_ACPI_BGRT is not setMismatch# CONFIG_ACPI_BGRT is not setMismatchCONFIG_ACPI_BGRT=y

    # CONFIG_ACPI_HMAT is not setMismatch# CONFIG_ACPI_HMAT is not setMismatchCONFIG_ACPI_HMAT=y

    # CONFIG_ACPI_APEI is not setMismatch# CONFIG_ACPI_APEI is not setMismatchCONFIG_ACPI_APEI=y

    MismatchMismatchCONFIG_ACPI_APEI_GHES=y

    MismatchMismatchCONFIG_ACPI_APEI_PCIEAER=y

    MismatchMismatch# CONFIG_ACPI_APEI_EINJ is not set

    MismatchMismatch# CONFIG_ACPI_APEI_ERST_DEBUG is not set

    # CONFIG_ACPI_DPTF is not setMismatch# CONFIG_ACPI_DPTF is not setMismatchCONFIG_ACPI_DPTF=y

    # CONFIG_ACPI_CONFIGFS is not setMismatch# CONFIG_ACPI_CONFIGFS is not setMismatchCONFIG_ACPI_CONFIGFS=m

    MismatchMismatchCONFIG_ACPI_PRMT=y

    CONFIG_X86_ACPI_CPUFREQ=mMatchMismatchCONFIG_X86_ACPI_CPUFREQ=m

    CONFIG_X86_ACPI_CPUFREQ_CPB=yMatchMismatchCONFIG_X86_ACPI_CPUFREQ_CPB=y

    MismatchMismatchCONFIG_ACPI_MDIO=y

    MismatchMismatch# CONFIG_THINKPAD_ACPI is not set

    Link to comment
    On 1/22/2022 at 12:41 PM, SimonF said:

    These are the differences between rc2 and rc1. 

     

    image.thumb.png.483cce06b90347fc28bafb00a1a30b8b.png6.9.2dif rc2 and 6.9.2rc1Diff rc1 and rc2rc2

    Mismatch# CONFIG_ACPI_FPDT is not setMismatchCONFIG_ACPI_FPDT=y

    # CONFIG_ACPI_AC is not setMismatch# CONFIG_ACPI_AC is not setMismatchCONFIG_ACPI_AC=m

    # CONFIG_ACPI_BATTERY is not setMismatch# CONFIG_ACPI_BATTERY is not setMismatchCONFIG_ACPI_BATTERY=m

    # CONFIG_ACPI_TAD is not setMismatch# CONFIG_ACPI_TAD is not setMismatchCONFIG_ACPI_TAD=m

    # CONFIG_ACPI_HOTPLUG_MEMORY is not setMismatch# CONFIG_ACPI_HOTPLUG_MEMORY is not setMismatchCONFIG_ACPI_HOTPLUG_MEMORY=y

    # CONFIG_ACPI_HED is not setMismatch# CONFIG_ACPI_HED is not setMismatchCONFIG_ACPI_HED=y

    # CONFIG_ACPI_BGRT is not setMismatch# CONFIG_ACPI_BGRT is not setMismatchCONFIG_ACPI_BGRT=y

    # CONFIG_ACPI_HMAT is not setMismatch# CONFIG_ACPI_HMAT is not setMismatchCONFIG_ACPI_HMAT=y

    # CONFIG_ACPI_APEI is not setMismatch# CONFIG_ACPI_APEI is not setMismatchCONFIG_ACPI_APEI=y

    MismatchMismatchCONFIG_ACPI_APEI_GHES=y

    MismatchMismatchCONFIG_ACPI_APEI_PCIEAER=y

    MismatchMismatch# CONFIG_ACPI_APEI_EINJ is not set

    MismatchMismatch# CONFIG_ACPI_APEI_ERST_DEBUG is not set

    # CONFIG_ACPI_DPTF is not setMismatch# CONFIG_ACPI_DPTF is not setMismatchCONFIG_ACPI_DPTF=y

    # CONFIG_ACPI_CONFIGFS is not setMismatch# CONFIG_ACPI_CONFIGFS is not setMismatchCONFIG_ACPI_CONFIGFS=m

    MismatchMismatchCONFIG_ACPI_PRMT=y

    CONFIG_X86_ACPI_CPUFREQ=mMatchMismatchCONFIG_X86_ACPI_CPUFREQ=m

    CONFIG_X86_ACPI_CPUFREQ_CPB=yMatchMismatchCONFIG_X86_ACPI_CPUFREQ_CPB=y

    MismatchMismatchCONFIG_ACPI_MDIO=y

    MismatchMismatch# CONFIG_THINKPAD_ACPI is not set

    Hopefully the developers can do something with this data

    Link to comment

    in the end i gave up on this motherboard and replaced it with new threadripper board and cpu, new combo working flawlessly. 

    • Like 1
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.