Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#59059 - [linux] Kernel 4.17.2-1 errors, no input

Attached to Project: Arch Linux
Opened by Mehmet Karataş (kingfared) - Tuesday, 19 June 2018, 07:21 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 21 June 2018, 15:51 GMT
Task Type Bug Report
Category Kernel
Status Assigned
Assigned To Tobias Powalowski (tpowa)
Jan Steffens (heftig)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 3
Private No

Details

Description: With latest Linux kernel from core repository on ASUS k555ub laptop system throws ACPI errors. Not able to control laptop with built in keyboard and touchpad. External mouse and keyboard is working. Networking not possible.


Additional info:
* package version(s)
Linux kernel 4.17.2-1-ARCH
Clean install according to arch wiki without enabling testing repository.
* config and/or log files etc.
Dmesg and Journal added

Steps to reproduce:
Clean install according to arch wiki without enabling testing repository.
Boot to newly installed sysyem
   journal.txt (115.7 KiB)
   dmesg.txt (59.1 KiB)
This task depends upon

Comment by loqs (loqs) - Tuesday, 19 June 2018, 09:51 GMT
[ 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
Comment by loqs (loqs) - Tuesday, 19 June 2018, 15:28 GMT
[ 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.
Comment by Michael (ZeroBeat) - Thursday, 21 June 2018, 10:13 GMT
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
Comment by loqs (loqs) - Thursday, 21 June 2018, 15:30 GMT
@ZeroBeat where in kingfared's dmesg did you any find of the six messages you posted from the kernel?
Comment by Michael (ZeroBeat) - Thursday, 21 June 2018, 15:40 GMT
@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.
Comment by loqs (loqs) - Thursday, 21 June 2018, 15:46 GMT
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.
Comment by Michael (ZeroBeat) - Thursday, 21 June 2018, 15:57 GMT
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.

Loading...