FS#64001 - linux 5.3.1.arch1-1 update with integram graphic card (i5-8400)
Attached to Project:
Arch Linux
Opened by Alexander (Imave) - Thursday, 03 October 2019, 13:44 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 16 November 2019, 18:38 GMT
Opened by Alexander (Imave) - Thursday, 03 October 2019, 13:44 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 16 November 2019, 18:38 GMT
|
Details
Description:
After updating linux 5.2.14.arch2-1 -> 5.3.1.arch1-1 and linux-firmware 20190815.07b925b-1 -> 20190923.417a9c6-1 I had problem with Intel(R) Core(TM) i5-8400 integral graphic card. Visual error: After gnome-desktop-manager(gdm) had been loaded screan blinked and I could only work with another tty. When I switched Wayland to Xorg, screen didn't blink, but still didn't work. This error doesn't exist in nomodeset (for me i915.setmode = 0), but wayland/xorg cannot up. Downgrade of linux helped me out journalctl: ``` kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x30c/0x350 [drm] kernel: Hardware name: System manufacturer System Product Name/PRIME B360M-A, BIOS 0805 08/03/2018 kernel: CPU: 1 PID: 345 Comm: systemd-udevd Not tainted 5.3.1-arch1-1-ARCH #1 kernel: Modules linked in: fjes(+) pcc_cpufreq(-) wmi_bmof snd_pcm_dmaengine crct10dif_pclmul acpi_cpufreq(-) crc32_pclmul ghash_clmulni_intel i915(+) snd_hda_intel aesni_intel ... kernel: WARNING: CPU: 1 PID: 345 at drivers/gpu/drm/drm_vblank.c:638 drm_calc_vbltimestamp_from_scanoutpos+0x30c/0x350 [drm] kernel: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 66: Can't calculate constants, dotclock = 0! ``` Additional info: * package version(s) linux 5.3.1.arch1-1 linux-firmware 20190923.417a9c6-1 wayland 1.17.0-1 * config and/or log files etc. lscpu: ``` Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 6 On-line CPU(s) list: 0-5 Thread(s) per core: 1 Core(s) per socket: 6 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz Stepping: 10 CPU MHz: 800.077 CPU max MHz: 4000.0000 CPU min MHz: 800.0000 BogoMIPS: 5618.00 Virtualization: VT-x L1d cache: 192 KiB L1i cache: 192 KiB L2 cache: 1.5 MiB L3 cache: 9 MiB NUMA node0 CPU(s): 0-5 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 m onitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase ts c_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hw p hwp_notify hwp_act_window hwp_epp flush_l1d ``` |
This task depends upon
I ask to avoid waiting until one to two months for 5.4 to be packaged by arch before it is discovered the bug is still present and upstream is not aware of it.