Arch Linux

[ 8.362181] rtl8723be: probe of 0000:03:00.0 failed with error -107
[ 8.422058] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
Please work with upstream to resolve the Null pointer dereference
Please do not post journal output generated with -x https://lists.freedesktop.org/archives/systemd-devel/2013-September/013029.html

[ 0.712000] xhci_hcd 0000:00:14.0: can't derive routing for PCI INT A
[ 0.712002] xhci_hcd 0000:00:14.0: PCI INT A: no GSI
https://bbs.archlinux.org/viewtopic.php?id=237875 can you verify the bisect result as the cause and work with upstream on the issue please.

I can confirm this issue for an ASUS X555UB-XO064D and LINUX kernel 4.17.2-1-ARCH:

Running during boot into emergency shell. No keyboard input is possible.

starting version 238
[ 16.45xxxx] xhci_hcd 0000:03:00.0: Abort failed to stop command ring : -110
[ 16.45xxxx] xhci_hcd 0000:03:00.0: xHCI host controller not responding, assume dead
[ 16.45xxxx] xhci_hcd 0000:03:00.0: HC died, cleaning up
[ 16.45xxxx] xhci_hcd 0000:03:00.0: Error while assigning device slot ID
[ 16.45xxxx] xhci_hcd 0000:03:00.0: Max number of devices with this xHCI host support is 254
[ 16.45xxxx] usb usb1-port2 : couldn't allocate usb_device
ERROR: device 'UUID=........' not found. Skipping fsck
mount: /new_root : can't find UUID=.......
You are being dropped into an emergency shell
sh: can't acces tty: job control turned off
[rootfs ]# _

Looks like an issue with the xhci_hcd controller.

Last working LINUX kernel: 4.16.13-2-ARCH
Boot parameters pci=noaer

@ZeroBeat where in kingfared's dmesg did you any find of the six messages you posted from the kernel?

@loqs: Found them in my log and I supected that there is a connection (xhci_hcd related) between that issue and my issue
because in both cases keyboard (and more) isn't accessible and laptops are of the same kind. So I decided to report no new bug and use this one.

As it is a kernel bug please do not expect any action to result from this bug report.
Bisect the issue report the result of the bisection upstream work with upstream to produce a fix.

That's ok and I do not expect any action results. I'm shure it's a kernel bug. Just added this comment to show that kingfared is not alone with this bug and that a (little bit) newer laptop doesn't boot with this bug. If I have some time, I'll check kernel 4.18-rcX if that bug still exists.

I also had the same issue (Asus X556UF). The issue wasn't there in 4.17.1 and was there in 4.17.2 I'll do a bisect if I get time.
As of now, I am using LTS kernel. Bug doesn't exist in 4.18-rc1 (tried using linux-mainline when 4.18-rc1 was released)

Same issue for Asus X555UF

The sad fact is that, this bug is like a chameleon. It seems to appear and disappear from kernel version to kernel version (https://bugzilla.kernel.org/buglist.cgi?quicksearch=xhci)

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/patch/?id=5088814a6e931350e5bd29f5d59fa40c6dbbdf10
"https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1716520.html"
This is believed by upstream to be the reason why the issue was fixed in 4.18-rc1 can someone affected build 4.17.2 with that commit cherry-picked and test.
Edit: quoted second link to try and stop flyspray incorrectly processing it.
Edit2:
Queued for 4.17.3 https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-4.17/acpica-aml-parser-attempt-to-continue-loading-table-after-error.patch?id=4a89ad609db01d7d24bc10c47d42e07516ff09ee

Build a custom kernel 4.17.2 with acpica-aml-parser-attempt-to-continue-loading-table-after-error.patch
Patch isn't working. Kernel hangs on boot, keyboard isn't accessable. Can't even open a terminal.
Issue still exists - same situation as before. (EDIT: No, not the same - not even emergency shell started)

Build also a custom kernel 4.18-rc2.
Working fine, so far. Keyboard and mouse are accessable again.
xhci working fine: Host supports USB 3.0 SuperSpeed
3ACPI BIOS Error (bug) AE_NOT_FOUND still exists (ASUS firmware bug?)
2 ACPI Errors:
Ignore error and continue table load (20180531/psobject-604)
Skipping While/if block (20180531/psobject-594)
I assume this is related to "https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1716520.html"

@fireion: Going back to linux-lts,too. 4.14.51 working like a charm. Reading the mailing lists and I don't think that they can handle this issue during the next weeks.

@kingfared @fireion @balise69 please test 4.17.3-1 currently in testing

Runs fine. What fixed the issue?

Most likely https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-4.17/acpica-aml-parser-attempt-to-continue-loading-table-after-error.patch?id=4a89ad609db01d7d24bc10c47d42e07516ff09ee
that did not work for zerobeat as the dmesg from zerobeat's system looked diferent to kingfareds so a different cause.

Works fine for me too. Thank you.

@loqs: xhci problem fixed, too:
[ 0.686845] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.686853] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 0.688036] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00109810
[ 0.688042] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 0.688309] usb usb1: Manufacturer: Linux 4.17.3-1-ARCH xhci-hcd
[ 0.689887] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.689890] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 0.689893] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
[ 0.689933] usb usb2: Manufacturer: Linux 4.17.3-1-ARCH xhci-hcd
[ 1.016719] usb 1-1: new low-speed USB device number 2 using xhci_hcd
[ 1.290259] usb 1-3: new high-speed USB device number 3 using xhci_hcd
[ 1.556918] usb 1-4: new high-speed USB device number 4 using xhci_hcd
[ 1.823573] usb 1-6: new high-speed USB device number 5 using xhci_hcd
[ 2.113434] usb 1-8: new full-speed USB device number 6 using xhci_hcd
Thanks to the kernel hackers. I was wrong, they did it within a few days.

ASUS X555UF here. Can confirm that 4.17.3-1 in testing fixes things over here.

ASUS X555UB - Installing 4.17.3-1 fixes too