Bug#990312: linux-image-5.10.0-8-amd64: GPU usage stuck at 99%

2021-06-26 Thread Yuya Nishihara
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

2021-06-26 Thread Debian Bug Tracking System
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

Bug#990162: power consumption regression

2021-06-26 Thread John
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

Processed: your mail

2021-06-26 Thread Debian Bug Tracking System
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

Bug#989778: Regression in at least 5.10.y and mainline: Firewire audio interface fails to work properly (when booted under Xen)

2021-06-26 Thread ‍小太
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

Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38

2021-06-26 Thread jim_p
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