Bug#990312: linux-image-5.10.0-8-amd64: GPU usage stuck at 99%
Hi, I have a similar issue and found bugreports in upstream: https://bugzilla.kernel.org/show_bug.cgi?id=213599 https://bugzilla.kernel.org/show_bug.cgi?id=212107#c11
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 983818 5.10.46-1 Bug #983818 [src:linux] linux-image-5.10.0-3-arm64: often fails to bring up ethernet / dwmac_rk module on rockpro64 Marked as found in versions linux/5.10.46-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 983818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990162: power consumption regression
I tested going back to kernel 4.19 which increased power use even more. While testing reverting to linux-image-5.10.0-7-amd64 and linux-image-5.10.0-8-amd64, I noticed that there was a message on the screen which should have been blanked (grub command line has consoleblank=5). What happens is that the screen is blanked for 5 seconds and then shown again. # cat /sys/module/kernel/parameters/consoleblank 5 /etc/default/grub contains: GRUB_CMDLINE_LINUX_DEFAULT="quiet consoleblank=5" The message on screen is: dev/sda2: recovering journal dev/sda2: clean 4536/1517 584 files, 1757736/60668160 blocks [2.278775] i915 :00:02.0: firmware: failed to load i915/kbl_dmc_ver1_04.bin (-2) [2.278780] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware There is no login prompt or cursor on screen. The system does not respond to key presses. It is possible to log in remotely using ssh. It seems consoleblank is overridden by the "recovery journal". This is not a good situation, the screen should blank as instructed. Blanking the screen should save power consumption, if indeed the monitor and/or the integrated GPU driving it is set to low power. If there is something displayed on screen, it will not save power. This forces the monitor to blank: # echo 1 > /sys/devices/pci:00/:00:02.0/graphics/fb0/blank The effect is the same as pulling the VGA plug: power consumption drops with about 9%. Obviously, this not near 25%. The monitor is re-enabled by: echo > /sys/devices/pci:00/:00:02.0/graphics/fb0/blank The monitor turns on again, displays a login prompt and blanks after 5 seconds as expected. Power saved remains 9%. The monitor does not wake by keyboard as it does in Debian 10.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 983818 linux-image-5.10.0-3-arm64: often fails to bring up ethernet / > dwmac_rk module on rockpro64 Bug #983818 [src:linux] linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module Changed Bug title to 'linux-image-5.10.0-3-arm64: often fails to bring up ethernet / dwmac_rk module on rockpro64' from 'linux-image-5.10.0-3-arm64: often fails to bring up eth0 / dwmac_rk module'. > thanks Stopping processing here. Please contact me if you need assistance. -- 983818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989778: Regression in at least 5.10.y and mainline: Firewire audio interface fails to work properly (when booted under Xen)
On Thu, 24 Jun 2021 at 04:50, Salvatore Bonaccorso
wrote:
> Hi Robin,
>
> On Mon, Jun 14, 2021 at 02:29:08PM +0100, Robin Murphy wrote:
> > On 2021-06-13 07:29, Salvatore Bonaccorso wrote:
> > > A user in Debian reported the above issue, which was reproducible with
> > > 5.13-rc5 and 5.10.y as packaged in Debian and found that 85a5a6875ca9
> > > ("swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single") that
> > > introduced the issue.
> >
> > Sounds like it's probably the same thing as being discussed over here:
> >
> >
> https://lore.kernel.org/linux-iommu/2e899de2-4b69-c4b6-33a6-09fb8949d...@nxp.com/
>
> Thanks for the pointer, it seems that now it has been fixed upstream
> with 5f89468e2f06 ("swiotlb: manipulate orig_addr when tlb_addr has
> offset").
>
I've checked out upstream v5.13 b7050b242430f3170e0b57f5f55136e44cb8dc66
(which includes the above commit) and confirmed that my issue is now
resolved.
Now to wait for it to reach Debian :)
Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38
Source: linux Followup-For: Bug #989010 X-Debbugs-Cc: pitsior...@gmail.com I noticed that 5.10.46 reached unstable yesterday. If it was not for this issue, I would have already upgraded, like I udually do when a kernel upgrade comes out. However, this time I had to check the config file for that -8 upgrade. And the only difference between -7 and -8 is this version number. The build flags, and I mean ALL of them, are EXACTLY the same. So, since I have no other gpus to sacrifice, I won't risk it again. If anyone with more experience can inform me about the worthy changes, please do. All I can see in the changelog that might be related is this bit - [x86] nmi_watchdog: Fix old-style NMI watchdog regression on old Intel CPUs If there is any more info on that change, please show me. In other news, the gpu that half-survived (gt210) was tested on a last year's ryzen pc (with windows though) and it boots and works fine. It was tested for ~1 hour with no issues.
