Hello.

I restarted my device and checked the box where it said to install application updates when rebooting. After restarting, it boots in insecure mode even though secure boot is enabled.
Then, it shows the GRUB menu with three options:
-Ubuntu
-Advanced options for Ubuntu
-System Setup

After choosing Ubuntu I get a bunch of ACPI Errors, which I will write down after this. I need help fixing this and an explanation why this happened please, keeping in mind that I am a new Ubuntu user. This did not happen during installation, I have been using Ubuntu for almost a month on that PC now (I am posting from another PC). I have tried googling but no issues were similar to mine. Any and all help is appreciated. Thanks in advance.

*Black screen with error messages:

[ 0.049147] ACPI Error: [_SB_>PCI0.RPO5.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[ 0.049156] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831)/psobject-252)
[ 0.049159] ACPI Error: Method parse/execution failed\_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.049193] ACPI Error: [_SB_.PCI0.RP09,PXSX] Namespace lookup failure, AE_NOT_FOUND (20170821/dswload2-191)
[ 0.049199] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[ 0.049501] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.299501] Kernel panic - not syncing: VSF: Unable to mount root fs on unkown-block(0,0)
[ 0.299538] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-38-generic #41-Ubuntu
[ 0.299554] Hardware name: Dell Inc. Inspiron 5570/0ydf7t, BIOS 1.1.4 03/13/2018
[ 0.299570] Call Trace:
[ 0.299580] dump_stack+0x63/0x8b
[ 0.299590] panic+0xe4/0x244
[ 0.299600] mount_block_root+0x1f6/0x2da
[ 0.299610] ? set_debug_rodata+0x17/0x17
[ 0.299620] mount_root+0x38/0x3a
[ 0.299629] prepare_namespace+0x139/0x18e
[ 0.299639] kernel_init_freeable+0x224/0x251
[ 0.299650] ? rest_init+0xb0/0xb0
[ 0.299660] kernel_init+0xe/0x110
[ 0.299669] ret_from_fork+0x35/0x40
[ 0.299688] Kernel Offset: 0x39200000 from 0xffffffff81000000 (relocation range: 0x(etc...)
[ 0.299710] ---[ end Kernel panic - not syncing: VFS: unable to mount root fs on unkown_block(0,0)

I find a good deal of information related to the error message, but if you put in the part in brackets, you'll find nothing..those are specific to your machine. That being said, there is a bug report listed:
https://bugs.launchpad.net/ubuntu/+s...x/+bug/1584407

...related to this issue. Since you're using a Debian-based system, you can *TRY* to install/upgrade the "intel-microcode" package, which may resolve some of these issue. Also, there are numerous reports of ACPI issues that are BIOS related, so you may want to update the BIOS on your system. Seems like a fairly older box, with the last update being from 2011, according to Dell's website.

Update your BIOS first, to see if that clears the issue up. Does your system actually finish booting and come up normally?

To Help ALL,

First an explanation of why ACPI errors occur in Linux, and why it can USUALLY be ignored

Second, if hundreds of errors happen on boot like my Hp OmenX Bleeding Edge Laptop, I will show you a trick for Grub (the boot loader) to ignore them, and boot normally

Third, I am posting this as I just upgraded my Kernel, and all my "Errors: have disappeared, and I will show you how to upgrade your Kernel.

#############################################################
First,
ACPI Errors - Microsoft's Fault!!
‣ https://en.wikipedia.org/wiki/Advanc...ower_Interface
∘ It's suppose to be a standard that any operating system can properly implement. However, in typical Microsoft fashion, MS operating systems do not follow or properly implement the ACPI standard. Instead, MS gives motherboard manufacturers their own improperly implemented ACPI code for inclusion in the motherboard BIOS/UEFI. The code runs fine with MS windows but all for other operating systems like linux there can be problems. Because of MS's market dominance, the faulty ACPI implementation from MS has become the de facto industry standard. As a result, linux and other non-MS operating systems have to reverse engineer the faulty ACPI implementation from MS. That's why you can see problems in linux with ACPI related functionality like suspend to ram, hibernate, etc.

∘ Apparently, the ACPI related code in certain newer linux kernels has a problem with the typical BIOS/UEFI ACPI implementation on certain motherboards which is why we're getting those error messages. Even though I get those error messages at the beginning of the boot process, I've had no problems with suspend/resume or any other ACPI related issues. Here's another guy with the same problem so you are not alone:
‣ https://www.reddit.com/r/linux/comme..._installation/
∘ The advice there was to not run in BIOS legacy mode by disabling UEFI but to run in UEFI mode instead with secure boot disabled. I haven't bothered with it myself since I have several operating systems already installed with BIOS legacy mode and I would have to reinstall everything if I wanted to switch to UEFI mode.
(UEFI Mode is working GREAT for my install)
##########################################################################

2nd

Hp / acpi Errors
∘ ACPI - Advanced Configuration & Power Interface
• ERROR "acpi int3400 unsupported event" ERRORS .....
‣ add to grub's ...
...
‣ "acpi=off" or "noacpi" "acpi=strict"

∘ .
‣ "acpi=strict" WORKING BEST AS OF 09/15/18
∘ or " acpi=force "

‣ "pnpacpi=off" Worked For another HP Spector and Another posted it AWESOME

To Edit Grub
After Update Grub with
• and Update your kernel with
• and of course Restart to take effect

3rd The latest kernel 4.19.5 has ELIMINATED ALL my problematic acpi:3400 errors
Install UKUU

UKUU - Ubuntu Kernel Update Utility
• Manage and Install Newest Bleeding Edge Kernels

• • and after run UKUU and it will offer to Install or Uninstall any and of course the newest (stable or not so stable KERNEL.

IT ALWAYS LEAVES your last working kernel in grub as a backup should it not work as well as you would like

Good Luck, Always trying to help, Mark

What I find puzzling about this thread is that the kernel panics because apparently it can't mount the root device. That doesn't seem to have anything to do with the acpi errors. I wonder if those are a red herring. acpi errors are very common because of the sloppy acpi coding that Mark describes but they don't usually lead to the kernel panicking.

You say this happened after an update. What did that update include? Did it install a new kernel? If so, the Advanced options choice should give you the option of using the old one instead.

@Mark: don't use your email address as a user name. It'll get harvested by spammers.

No Worries, Was My Post Helpful?

I had a few weeks of irritation with this problem? And wanted to share the new insights!

And to add a OBVIOUSLY MISSED helpful point (if you are stuck with not booting properly or black screen of death).

If not booting, the same can be added at boot time, and it is NOT obvious at all to newbies!

Just (when GRUB opens) select "Advanced Options"
Now IF you have 2 or more kernels use an (select) the older one that WAS working,
... EASY PEASY.
Now, IF it a new install or there is only one kernel (Ubuntu ALWAYS leaves at least one [SECOND] OLDER working kernel in grub - SMART!)

SO if all above fails here is the more tricky option ...
... add the "acpi=strict" as mentioned above ... AT BOOT TIME! ...
... highlight (select) the kernel in the advanced option and

PRESS Now it will give you a page of garbled code but worry not, Just find
and add acpi=strict, to look like
and look at the bottom of this page and find the option to save and/or boot with the changes.

This CAN BE REALLY USEFUL!

Good Luck, Any More Questions feel free to ask!
As Always,

Trying to help, Mark