Bugzilla – Bug 1078408
X Segmentation fault at address 0x20
Last modified: 2018-06-16 12:30:26 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Starting with kernel 126.96.36.199 system would not finish booting...the screen display the login prompt (right before it would normally go to the full screen user login page), and continusouly blink...after pressing enter key, this message is displayed and the screen continues to blink:
logitech-hidpp-device 0003:046D:200D.0006 Unable to retrieve the name of the device.
It seems that the system is not reading the device name correctly because 200D is not a valid logitech device. Here is the lusb output when I boot back with 188.8.131.52:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 003 Device 007: ID 046d:082c Logitech, Inc. HD Webcam C615
Bus 003 Device 005: ID 0a5c:216c Broadcom Corp. BCM43142A0 Bluetooth Device
Bus 003 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 0557:2255 ATEN International Co., Ltd
Bus 003 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
What more information do you need?
Steps to Reproduce:
1. I presume it's the kernel level...184.108.40.206 works OK...Anytime I install updates that include a kernel update, it breaks. So 220.127.116.11, 18.104.22.168 and 22.214.171.124 I have tried and they all fail with the same error conditions. I recover by rolling back to 126.96.36.199
boot does not complete. at tty login, screen just blinks continuously and outputs the logitech error whenever enter key pressed.
boot to complete.
Kernel 188.8.131.52 did not resolve the problem.
I can't see anything obviously broken between 4.14.12 and 4.14.13 in this area.
Could you boot without splash-silent and quiet?
Created attachment 769933 [details]
Xorg.0.log during boot
Shows segment fault in X near end of log.
From just looking at the journald log I mistakenly viewed this as a usbhid problem. But now looking at the Xorg.0.log I can see a segment fault. Xorg.0.log attached from attempt to boot with the latest kernel 4.16.6-1-default.
Same symptoms as when first reported with 4.14.13-1 kernel.
Reverting back to 4.14.12-1 i see that the X server is version 1.19.5, and the X server version that now fails with the segmentation fault is 1.19.6. Not sure when 1.19.6 was introduced, but I suspect 4.14.13-1 was using 1.19.6.
Created attachment 769936 [details]
Xorg.0.log Kernel 4.14.12-1 (good boot)
Attached the Xorg.0.log for boot with kernel 4.14.12-1, when things work OK>
Also, I'll try to boot without Splash and quiet and report back.
Created attachment 769986 [details]
Kernel 4.16.6-1-default boot with nosplash
Attached log from boot with nosplash, with same result:
322.729] Current Operating System: Linux linux-nab9 4.16.6-1-default #1 SMP PREEMPT Mon Apr 30 20:33:51 UTC 2018 (566acbc) x86_64
[ 322.729] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.6-1-default root=UUID=44d379df-676b-4295-b7aa-3e0503178afc rootflags=subvol=/@/.snapshots/593/snapshot
322.781] (EE) Segmentation fault at address 0x20
(In reply to Jiri Slaby from comment #2)
> I can't see anything obviously broken between 4.14.12 and 4.14.13 in this
> Could you boot without splash-silent and quiet?
Any chance you could look at this again with the additional documentation?
Does your system have Mesa-dri package installed?
Closing due to lack of response.