Hello I have been having problems for some time now with displaying any linux distribution with the new kernal. The only thing that can fix it are older kernals. I can't describe it very well, so I'm attaching some pictures, but it's like whenever anything happens on the screen, it pushes the upper left half up from the bottom. But it only goes to a certain extent, after that it just shakes around and jumps back a bit. Also, for example, the firefox icon is not where it is displayed, but where it should be (I tried it with touch). I think it has something to do with the framebuffer, because an usb stick with just the arch iso show the same issue in the tty. The hardware is a Huawei Matebook E 2022. Cpu: Intel® Core™ i5-1130G7 Graphics: Intel® Iris® Xe Example under Manjaro that worked was with the linux-lqx-6.1.0.lqx2-1-x86_64.pkg.tar.zst kernal 22-Dec-2022 14:44 154507169 from https://repo.blacksky3.com/x86_64/linux-lqx/old/ Kernals above that Version dosent work, Example with 6.1.1-lqx1-linux-lqx: ` $inxi -F System: Host: Johannes Kernel: 6.1.1-lqx1-linux-lqx arch: x86_64 bits: 64 Desktop: GNOME v: 43.5 Distro: Manjaro Linux Machine: Type: Detachable System: HUAWEI product: DRC-WXX v: M1010 serial: Mobo: HUAWEI model: DRC-WXX-PCB v: M1010 serial: UEFI: HUAWEI v: 1.30 date: 06/29/2022 Battery: ID-1: BAT1 charge: 27.8 Wh (66.0%) condition: 42.1/42.1 Wh (100.0%) volts: 11.9 min: 11.5 CPU: Info: quad core model: 11th Gen Intel Core i5-1130G7 bits: 64 type: MT MCP cache: L2: 5 MiB Speed (MHz): avg: 1395 min/max: 400/1801 cores: 1: 897 2: 1046 3: 962 4: 1801 5: 1801 6: 1801 7: 1801 8: 1052 Graphics: Device-1: Intel Tiger Lake-UP4 GT2 [Iris Xe Graphics] driver: i915 v: kernel Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1 compositor: gnome-shell driver: gpu: i915 resolution: 2560x1600~60Hz API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel Xe Graphics (TGL GT2) Audio: Device-1: Intel driver: N/A Device-2: Intel Tiger Lake-LP Smart Sound Audio driver: sof-audio-pci-intel-tgl API: ALSA v: k6.1.1-lqx1-linux-lqx status: kernel-api Server-1: PulseAudio v: 16.1 status: active Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi IF: wlp0s20f3 state: up mac: f4:b3:01:b7:c6:6d Bluetooth: Device-1: Intel AX201 Bluetooth driver: btusb type: USB Report: rfkill ID: hci0 state: up address: see --recommends Drives: Local Storage: total: 476.94 GiB used: 9.65 GiB (2.0%) ID-1: /dev/nvme0n1 model: PCIe-8 SSD 512GB size: 476.94 GiB Partition: ID-1: / size: 468.09 GiB used: 9.65 GiB (2.1%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 299.4 MiB used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 35.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 241 Uptime: 0m Memory: available: 15.42 GiB used: 1.18 GiB (7.6%) Shell: Zsh inxi: 3.3.27 ` Distros I testet: Ubuntu 20.04.2 results in Blackscreen/poweroff Fedora 38 (Bug as I mentiond) Manjaro (Bug as I mentiond) It all works fine when you start from grub2 in Rescue mode. That all is very new to me, so I am sorry if I did something wrong. I mean, I reported that bug first at the wrong place.. Anyway Best regreds Johannes
Created attachment 304616 [details] Here you can see the Display issue
Created attachment 304617 [details] Here with older kernal
Created attachment 304620 [details] Arch-Linux-tty errors while startup When the errors show up, right at this moment, the screen "splits." I think this could help a lot to figure the problem out.
(In reply to Johannes from comment #0) > Hello I have been having problems for some time now with displaying any > linux distribution with the new kernal. The only thing that can fix it are > older kernals. > > I can't describe it very well, so I'm attaching some pictures, but it's like > whenever anything happens on the screen, it pushes the upper left half up > from the bottom. But it only goes to a certain extent, after that it just > shakes around and jumps back a bit. Also, for example, the firefox icon is > not where it is displayed, but where it should be (I tried it with touch). > > I think it has something to do with the framebuffer, because an usb stick > with just the arch iso show the same issue in the tty. > > The hardware is a Huawei Matebook E 2022. > Cpu: Intel® Core™ i5-1130G7 > Graphics: Intel® Iris® Xe > > Example under Manjaro that worked was with the > linux-lqx-6.1.0.lqx2-1-x86_64.pkg.tar.zst kernal > 22-Dec-2022 14:44 154507169 > from https://repo.blacksky3.com/x86_64/linux-lqx/old/ > > Kernals above that Version dosent work, Example with 6.1.1-lqx1-linux-lqx: > ` Do you have this issue on vanilla v6.1.y stable series?
As of kernel version 6.1.10, the bug is reproducible. The kernels I used for testing were obtained from https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ . The kernels tested were: linux-6.0.tar.gz -Works fine linux-6.1.1.tar.gz -Works fine linux-6.1.10.tar.gz -Shows the bug stable series: linux-6.4.3.tar.xz -Shows the bug and hangup during boot after choosing the kernel in grub None of the default makeconfig values have been changed. How I compiled the kernel: $tar xvf linuxKernel.tar.xz $make menuconfig $make -j8 $sudo make modules_install $sudo make install §sudo grub2-mkconfig -o /boot/grub2/grub.cfg
I have also tested linux 6.5.0-ec1, which does not hang like 6.4.3. Maybe I have done something wrong to make this version do that. 6.5.0-ec1 also has the bug.
(In reply to Johannes from comment #6) > I have also tested linux 6.5.0-ec1, which does not hang like 6.4.3. > Maybe I have done something wrong to make this > version do that. > 6.5.0-ec1 also has the bug. I'm confused. Are you sure v6.5-rc1 also have this regression?
Can you attach dmesg output instead?
(In reply to Johannes from comment #5) > As of kernel version 6.1.10, the bug is reproducible. > The kernels I used for testing were obtained from > https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ . > > The kernels tested were: > linux-6.0.tar.gz -Works fine > linux-6.1.1.tar.gz -Works fine > linux-6.1.10.tar.gz -Shows the bug > > stable series: > linux-6.4.3.tar.xz -Shows the bug and hangup during boot after choosing the > kernel in grub > Then can you bisect between v6.1 and v6.4 to find the culprit of your regression? > None of the default makeconfig values have been changed. > > How I compiled the kernel: > $tar xvf linuxKernel.tar.xz > $make menuconfig > $make -j8 > $sudo make modules_install > $sudo make install > §sudo grub2-mkconfig -o /boot/grub2/grub.cfg Because you're about to compile your own kernel during bisection, see [1] for how to compile kernel with trimmed configuration. [1]: https://docs.kernel.org/admin-guide/quickly-build-trimmed-linux.html
I'm sorry for confusing you, I meant that 6.4.3 hangs up during boot, while v6.5-rc1 does not. But both versions have the same display error. In case of 6.4.3 I said that (maybe) I have done something wrong while Build-installation to make that version hang up during boot.
(In reply to Bagas Sanjaya from comment #9) > (In reply to Johannes from comment #5) > > As of kernel version 6.1.10, the bug is reproducible. > > The kernels I used for testing were obtained from > > https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ . > > > > The kernels tested were: > > linux-6.0.tar.gz -Works fine > > linux-6.1.1.tar.gz -Works fine > > linux-6.1.10.tar.gz -Shows the bug > > > > stable series: > > linux-6.4.3.tar.xz -Shows the bug and hangup during boot after choosing the > > kernel in grub > > > > Then can you bisect between v6.1 and v6.4 to find the culprit of your > regression? Yes, it is the linux-6.1.10 version where the error first occurs. > > > None of the default makeconfig values have been changed. > > > > How I compiled the kernel: > > $tar xvf linuxKernel.tar.xz > > $make menuconfig > > $make -j8 > > $sudo make modules_install > > $sudo make install > > §sudo grub2-mkconfig -o /boot/grub2/grub.cfg > > Because you're about to compile your own kernel during bisection, see [1] > for how to compile kernel with trimmed configuration. > > [1]: https://docs.kernel.org/admin-guide/quickly-build-trimmed-linux.html
Created attachment 304644 [details] dmesgoutput linux-6.1.10
(In reply to Johannes from comment #11) > (In reply to Bagas Sanjaya from comment #9) > > Then can you bisect between v6.1 and v6.4 to find the culprit of your > > regression? > Yes, it is the linux-6.1.10 version where the error first occurs. That's not a bisection. Please perform one (maybe between v6.1.1..v6.1.10 while afterwards verifiying the result on mailine), otherwise I guess this bug is unlikely to be fixed. BTW, you mentioned so many different kernels, hence please allow me to ask: did you use the same base config for your tests? See https://docs.kernel.org/admin-guide/reporting-regressions.html for details. And overall: this bug report is pretty confusing. And in the wrong place. You might want to report it here instead: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs Afterwards drop a link here and close this.
Johannes, any conclusion on the bisection as Thorsten asked? And the link to gitlab.freedesktop.org issue?
I'm sorry for my delay but the last weeks I had some issues to solve (not software related). Anyway, I found out, that newer kernels than v6.1.4 show the bug. I reported the bug here https://gitlab.freedesktop.org/drm/intel/-/issues/8992 Thank you for your support!
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #13) > (In reply to Johannes from comment #11) > > (In reply to Bagas Sanjaya from comment #9) > > > Then can you bisect between v6.1 and v6.4 to find the culprit of your > > > regression? > > Yes, it is the linux-6.1.10 version where the error first occurs. > > That's not a bisection. Please perform one (maybe between v6.1.1..v6.1.10 > while afterwards verifiying the result on mailine), otherwise I guess this > bug is unlikely to be fixed. > > BTW, you mentioned so many different kernels, hence please allow me to ask: > did you use the same base config for your tests? See > https://docs.kernel.org/admin-guide/reporting-regressions.html for details. Yes, I used the same basic configuration. The only kernel I compiled with a different one was https://www.intel.com/content/www/us/en/docs/graphics-for-linux/developer-reference/1-0/build-guide.html. I used the default Fedora kernel v6.2.9-300. fc38. x86_64, but after some more testing and building on my kernels created for testing, the result is the same. > And overall: this bug report is pretty confusing. And in the wrong place. > You might want to report it here instead: > https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs > > Afterwards drop a link here and close this.