Jump to content

  • ACPI BIOS Error (bug): Could not resolve symbol (concerns ACPI 5, my board does 2)

    couzin2000

    By couzin2000

      • Minor

    So I have this bug in the logs.  

    Mar 13 22:24:46 sebunraid1 kernel: ACPI: Early table checksum verification disabled
Mar 13 22:24:46 sebunraid1 kernel: pci 0000:02:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
Mar 13 22:24:46 sebunraid1 kernel: pci 0000:02:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
Mar 13 22:24:46 sebunraid1 kernel: floppy0: no floppy controllers found
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:46 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Mar 13 22:24:46 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Mar 13 22:24:50 sebunraid1  mcelog: failed to prefill DIMM database from DMI data

    I can't figure out the specifics but I am reading https://blog.le-vert.net/?p=24 explaining that this has to do with ACPI 5.0 being implemented, yet my board (Asus P8Z77-V LE) only supports ACPI 2.0. BIOS has been updated since 2016, last version available is dated 2014.

     

    From  the author's post, "The proper fix is simply to boot your kernel with libata.noacpi=1 and resume works again". Great. How do I do this?

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    JorgeB

    Add that to syslinux.cfg, you can do that using the GUI, click on the flash drive and add it to relevant boot option(s(.

    Link to comment
    3limin4tor
    On 3/14/2023 at 9:20 AM, JorgeB said:

    Add that to syslinux.cfg, you can do that using the GUI, click on the flash drive and add it to relevant boot option(s(.

    Can you describe where exactly i need to place it? I have the same error and tried to add it but then my unraid doesn't even boot anymore and when i remove it my unraid boots normal but those messages are flooding my syslog extremely fast until my ram is full and unraid becomes unresponsive and tells me that there is no space left on device (28). 

    Link to comment
    JorgeB

    Click on the flash drive, scroll down to "Syslinux Configuration" and add to the relevant boot options, in the "append" line, like the blacklist Radeon option bellow.

     

    imagem.png

    Link to comment
    3limin4tor

    Hi thanks for your help, i‘ve insterted it here IMG_2759.thumb.jpeg.529abee47ef96eecc060528bc3b09dd0.jpeg

    and unraid booted successfully but unfortunately the error still appears:

    IMG_2761.thumb.jpeg.9acedcdef990590aed8f899039b86569.jpeg

    I have to look further. Seems like it is beeing ignored. 

    Link to comment
    JorgeB

    Look for a BIOS update, this is usually a BIOS problem, not much else you can do, a newer kernel might also help.

    Link to comment
    steveme

    Having the same issue, Updated my bios last night and a whole bunch of other stuff still having the same problem.

     

    190411613_Screenshot2023-03-30at1_12_24PM.thumb.png.b2bb2185fc1f549bcee85cb30bfae789.png

     

     

    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.

×
×
  • Create New...