I am using an all-Intel i7 laptop running slowroll (KDE) installed fairly recently from a live USB and dup’ed frequently. Occasionally it crushes on initial start-up but works fine after re-start so I have ignored. But checking the trace of the latest crash I was surprised to see a reference to AMD. Previous report show similar:
Stack trace of thread 2310:
#0 0x00007f8f1c0a1c32 __syscall_cancel_arch (libc.so.6 + 0xa1c32)
#1 0x00007f8f1c09581c __internal_syscall_cancel (libc.so.6 + 0x9581c)
#2 0x00007f8f1c095fec __futex_abstimed_wait_common (libc.so.6 + 0x95fec)
#3 0x00007f8f1c098a78 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x98a78)
#4 0x00007f8f05b8b879 n/a (libgallium-25.0.5.so + 0x58b879)
#5 0x00007f8f05b5749b n/a (libgallium-25.0.5.so + 0x55749b)
#6 0x00007f8f05b8b7b7 n/a (libgallium-25.0.5.so + 0x58b7b7)
#7 0x00007f8f1c099546 start_thread (libc.so.6 + 0x99546)
#8 0x00007f8f1c11d94c __clone3 (libc.so.6 + 0x11d94c)
ELF object binary architecture: AMD x86-64
The kernel-firmware-amdgpu and libdrm-amdgpu1 are installed but the laptop is all-Intel:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
Subsystem: CLEVO/KAPOK Computer Device [1558:1313]
Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
Subsystem: CLEVO/KAPOK Computer Device [1558:1313]
Kernel driver in use: i915
Kernel modules: i915
Previous startup crash reports refer to gdb, plasmashell, brave, DiscoverNotifier but the final line reference to AMD repeats. So my questions are:
- Are the AMD modules necessary or why installed ?; and
- Are they connected to the start up crashes?.
[1] Not sure if relevant but the live USB was downloaded on a PC with Nvidia graphics card
[2] I had startup crashes when running Leap15.6 but never checked the crash reports
Regards