Bug#1029816: wifi: mt76: mt7612u/mt7610u - 6.1.x hard locking systems

Source: linux Version: 6.1.4-1 Severity: important Dear Maintainer, My Netgear A6210 (Mediatek MT7612U) hard locks the system on login. If I instead log in via console, the first network access (such as ping) results in a kernel panic. I found this upstream bug report: http://lists.infradead.o

Re: Moving firmware packages from non-free to non-free-firmware

Hi, Here's an update regarding firmware packages vs. non-free-firmware. I'm extending the list of recipients a little; feel free to let me know if you spot packages/teams that I would have missed! Cyril Brulebois (2023-01-17): > For this first round, I've checked on amd64/unstable which packages

Re: Request to cherry picking a patch to fix bug #989705 for kernels 5.10.y

On Friday, 27 January 2023 21:05:47 CET Computer Enthusiastic wrote: > This patch [2] applies to kernel version 5.10.y, too. I used it with a > custom built kernel since it was published . > > The author of the patch acknowledged that the patch applies to kernel > version 5.10.y asking me to send

Bug#1029755: "sh: 1: xed: not found" when listing samples with assembler

Hi Philipp, On Fri, Jan 27, 2023 at 08:31:02AM +0100, Philipp Marek wrote: > Package: linux-perf > Version: 6.1.7-1 > Severity: minor > File: /usr/bin/perf > X-Debbugs-Cc: phil...@marek.priv.at > > I've written a trace with "perf record"; when viewing via "perf report" > it I zoom into a function

Bug#1029709: linux-image-6.1.0-1-amd64: failed to start Load Kernel Modules

Hi, On Thu, Jan 26, 2023 at 02:41:02PM -0500, Rex Abert wrote: > Might be the same issue.  I simply did an upgrade in bookworm, kernel was > upgraded from 6.0 ->6.1.  On reboot, nvidia driver was not working.  Noticed > the message during boot: > > failed to start Load Kernel Modules Might you b

Request to cherry picking a patch to fix bug #989705 for kernels 5.10.y

Hello, The bug #989705 [1] is currently closed. It was solved for kernels version 5.15+ using the patch [2] from upstream. This patch [2] applies to kernel version 5.10.y, too. I used it with a custom built kernel since it was published . The author of the patch acknowledged that the patch

firmware-nonfree_20221214-5_amd64.changes is NEW

binary:firmware-amd-graphics is NEW. binary:firmware-atheros is NEW. binary:firmware-bnx2 is NEW. binary:firmware-bnx2x is NEW. binary:firmware-brcm80211 is NEW. binary:firmware-cavium is NEW. binary:firmware-intel-sound is NEW. binary:firmware-ipw2x00 is NEW. binary:firmware-ivtv is NEW. binary:fi

Re: Processing of firmware-nonfree_20221214-5_amd64.changes

Debian FTP Masters (2023-01-27): > firmware-nonfree_20221214-5_amd64.changes uploaded successfully to localhost > along with the files: > firmware-nonfree_20221214-5.dsc > firmware-nonfree_20221214-5.debian.tar.xz > firmware-amd-graphics_20221214-5_all.deb > firmware-atheros_20221214-5_all

Processing of firmware-nonfree_20221214-5_amd64.changes

firmware-nonfree_20221214-5_amd64.changes uploaded successfully to localhost along with the files: firmware-nonfree_20221214-5.dsc firmware-nonfree_20221214-5.debian.tar.xz firmware-amd-graphics_20221214-5_all.deb firmware-atheros_20221214-5_all.deb firmware-bnx2_20221214-5_all.deb firm

Bug#993612: [PATCH] of/address: Return an error when no valid dma-ranges are found

On Fri, Jan 27, 2023 at 12:37:35PM -0600, Rob Herring wrote: > Looks to me like we are leaking 'r' with this change. Oh, probably now that you mention it. Usually the OF code keeps track of more things than I expect... > Wouldn't this change work: > diff --git a/drivers/of/address.c b/drivers/

Bug#993612: [PATCH] of/address: Return an error when no valid dma-ranges are found

On Thu, Jan 26, 2023 at 10:27 AM Mark Brown wrote: > > Commit 7a8b64d17e35 ("of/address: use range parser for of_dma_get_range") > converted the parsing of dma-range properties to use code shared with the > PCI range parser. The intent was to introduce no functional changes however > in the case w

Processed: Re: Bug#1024831: Acknowledgement (xorg: xserver fails to resume after suspend-to-disk)

Processing control commands: > tag -1 moreinfo Bug #1024831 [src:linux] xorg: xserver fails to resume after suspend-to-disk Added tag(s) moreinfo. -- 1024831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1024831: Acknowledgement (xorg: xserver fails to resume after suspend-to-disk)

Control: tag -1 moreinfo On 26 Nov 2022 20:31:25 +0100 Klaus Singvogel wrote: > This issue only happens only with linux-image-6.0.0-0.deb11.2-amd64 > After I booted the old linux-image-5.19.0-0.deb11.2-amd64, the issue does > not occur. Does this issue still occur with version 6.0.12-1~bpo11+1 w

Processed: Submitter says this was caused by a kernel upgrade

Processing commands for cont...@bugs.debian.org: > reassign 1024831 src:linux 6.0.3-1 Bug #1024831 [xorg] xorg: xserver fails to resume after suspend-to-disk Bug reassigned from package 'xorg' to 'src:linux'. No longer marked as found in versions xorg/1:7.7+22. Ignoring request to alter fixed vers