Control: reassign -1 src:firmware-nonfree 20230625-2
On Friday, 26 April 2024 07:36:16 CEST Martin-Éric Racine wrote:
> Package: src:linux
> Version: 6.7.7-1
> Severity: normal
>
> W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module
> i915 W: Possible missing firmware
Control: forwarded -1 https://github.com/util-linux/util-linux/issues/2867
https://lore.kernel.org/all/20240328-mips_save_syscall-v1-1-9e1d62d69...@flygoat.com/
On Thursday, 25 April 2024 22:10:12 CEST Chris Hofstaedtler wrote:
> reassign 1068365 src:linux
> affects 1068365 src:util-linux
>
Control: tag -1 -moreinfo +upstream
Control: forwarded -1
https://lore.kernel.org/linux-bluetooth/CADRbXaDqx6S+7tzdDPPEpRu9eDLrHQkqoWTTGfKJSRxY=ht...@mail.gmail.com/
On Monday, 22 April 2024 10:32:00 CEST Jeremy Lainé wrote:
> Over the weekend I reported the issue to the linux-bluetooth mailing
patch and build a kernel.
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
describes a procedure with which you can apply (the attached) patches
HTH>From 21f7e476d0afe832f6656b917b976c6efe6b24f3 Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Tue, 16
the 6.7 kernel work properly again, we
likely have found the culprit for the kernel oops/panic.
Can you first try the Testing (6.6.15) kernel and if that works try
applying the attached patches to the 6.7 kernel?>From 407672343a738ede6f5e955e3afa57d16b37f4e6 Mon Sep 17 00:00:00 2001
From: Died
On Monday, 15 April 2024 10:41:55 CEST Eric Valette wrote:
> Why is there no 6.6 up-to-date kernel pushed in testing as well? Do you
> plan to wait until 6.6 enter stable? When?
Nothing gets 'pushed' to Testing. Packages *transition* to Testing when
several conditions are met.
On Wednesday, 10 April 2024 15:32:02 CEST Cyril Brulebois wrote:
> Cyril Brulebois (2024-04-10):
> > Salvatore Bonaccorso (2024-04-10):
> > > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > > > Does the problem go away if you rever
Hi Cyril,
On Tuesday, 9 April 2024 01:06:43 CEST Cyril Brulebois wrote:
> Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64
> leads to losing some SMART information, at least as queried by munin (in
> Debian 12) when it comes to sensors.
Does the problem go away if you
Control: forcemerge -1 1054889
On Monday, 8 April 2024 10:44:12 CEST dada007 wrote:
> I had an earlier report with this bug
No need to have 2 bugs for the same problem, thus merging
signature.asc
Description: This is a digitally signed message part.
ts).
>
> (3) Instead I will try first to use debian testing on a different NUC, but
> this will take some time.
>
> 2. April 2024 20:28, "Diederik de Haas" schrieb:
> > On Tuesday, 2 April 2024 19:54:41 CEST J. Pfennig wrote:
> >> Package: src:linux
> >>
On Tuesday, 2 April 2024 19:54:41 CEST J. Pfennig wrote:
> Package: src:linux
> Version: 6.1.76-1
> Severity: important
> Tags: upstream
I am/was inclined to remove that tag, but the problem is likely caused by
firmware which is too old for the 'backported' patches that upstream applied.
> The
On Tuesday, 19 March 2024 11:52:29 CET Josua Mayer wrote:
> May I ask if you are analyzing dts manually, or whether you are aware
> of an automatic tool?
Analyses is done by a MUCH improved scripts based upon what I came up with a
while ago:
Hi,
Since https://bugs.debian.org/863290 (2017) the Debian kernel has had a
patch to warn about the use of RAID 5/6 with BTRFS.
That bug mentions "It looks like there's a consensus that such a warning
should live in the kernel rather than userland"
Via [1] and [2] it seems userland did get a
ECC support should already work with the Stable 6.1 kernel (or newer).
> > Am 07.03.24 um 13:34 schrieb Diederik de Haas:
> >> On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> >>
> >>> LX2160 SoC early silicon revisions have a pci-e generation 4
&g
Hi Josua,
On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> LX2160 SoC early silicon revisions have a pci-e generation 4 controller.
> It requires a different driver from newer gen-3 silicon.
>
> This affects the SolidRun Honeycomb Workstation which
> is otherwise fully supported in
Control: clone -1 -2
Control: retitle -2 Additional support for SolidRun HoneyComb
On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote:
> LX2160 SoC early silicon revisions have a pci-e generation 4 controller.
> It requires a different driver from newer gen-3 silicon.
>
> This affects
Control: tag -1 moreinfo
On Saturday, 24 February 2024 14:16:53 CET Harald Dunkel wrote:
> Package: firmware-iwlwifi
> Version: 20230625-2
>
> The source URL mentioned in the copyright file doesn't work anymore.
Which URL do you mean?
Control: reassign -1 src:linux 5.10.178-1
On Wednesday, 10 May 2023 15:41:44 CET Christian Kiss wrote:
> Package: firmware-amd-graphics
> Version: 20210315-3
>
> kernel.log reports that radeon: 1 quad pipes, 2 z pipes initialized.
> the gpu an rv530 has atleast double to 4 of these each.
>
>
Control: tag -1 moreinfo
On Mon, 10 May 2021 18:13:43 + static wrote:
> Package: firmware-realtek
> Version: 20210315-2
>
> I am trying to install from scratch firmware-edu-bullseye-DI-rc1-amd64-
> BD-1.iso (also tried on debian-bullseye-DI-rc1-amd64-DVD-1.iso but interface
> is not
Control: tag -1 moreinfo
On 20 Jan 2020 22:32:26 +0100 Patrice Duroux wrote:
> Package: firmware-iwlwifi
> Version: 20190717-2
>
> I am reporting this «exception» here without being sure this is the right
> package or if it has been already reported (not easy to check).
>
> [ 48.335755]
On Fri, 17 Jan 2020 17:24:14 +0200 Sicelo wrote:
> Package: firmware-ti-connectivity
> Version: 20190717-2
>
> Please include TIInit_10.6.15.bts [1], which is needed for bluetooth on
> the Motorola Droid 4 and similar boards. Similar files are already part
> of the debian package, and the
Control: retitle -1 firmware-iwlwifi: Please update to version 20230804
On Sunday, 11 February 2024 18:56:23 CET Diederik de Haas wrote:
> It could/might be there would be some improvement somewhere with newer
> firmware, but as long as things keep working that is fine.
> Consequen
Control: tag -1 moreinfo
On Saturday, 3 February 2024 17:33:32 CET Aly Ghobashy wrote:
> Package: firmware-amd-graphics
> Version: 20230210-5
>
>* What led up to the situation?
> opening a video file with VLC
>* What exactly did you do
> video file to open normally.
>
On maandag 22 januari 2024 15:42:48 CET you wrote:
> I'm currently working on an update for upstream version 20230919, based
> upon MR86 (Release 20230804) [1], which itself is based upon MR85
> (Update to 20230625) [2] and I'm running into some major issues:
>
> 1) Salsa's CI now always fails as
On Tuesday, 20 February 2024 09:22:06 CET Ben Mesman | Spark Narrowcasting
wrote:
> mmc: sdhci-pci-o2micro: Fix a warm reboot issue that disk can't be
> detected by BIOS
> ...
> Link:
> https://lore.kernel.org/r/20240203102908.4683-1-fredaibayhubt...@126.com
>
> I'm still waiting for the
On Tuesday, 13 February 2024 17:59:55 CET Mario Limonciello wrote:
> > I think it's important to facilitate people having f.e. the following
> > combos:
> > - Intel CPU with AMD GPU
> > - AMD CPU with Nvidia GPU
> > - AMD CPU with AMD GPU (discrete or integrated)
> >
> > Preferably without
On Monday, 12 February 2024 21:25:35 CET Mario Limonciello wrote:
> > My logic was that this is about AMD TEE (Trusted Execution Environment),
> > which I *assumed* is part of/tied to the CPU. This thought is based on
> > that on ARM platforms, you also have a TEE and that is part of the CPU
> >
On Monday, 12 February 2024 19:38:12 CET Henrique de Moraes Holschuh wrote:
> On Fri, Feb 2, 2024, at 13:50, Diederik de Haas wrote:
> > This is about "AMD Platform Management Framework TA", which seems to be
> > about AMD CPU features. The first (and
Control: forwarded -1
https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/
On Monday, 12 February 2024 12:56:45 CET Arno Lehmann wrote:
> Reported upstream, see
>
> https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0d2a@its-lehm
> ann.de/T/#u
100, Diederik de Haas пишет:
> > Control: tag -1 moreinfo
> >
> > On Saturday, 10 February 2024 17:41:43 CET Nikolay Sabelnikov wrote:
> > > Package: linux-image-amd64
> > > Version: 6.1.76-1
> > >
> > > > update-initramfs: Generating /boot/in
Control: tag -1 moreinfo
On Saturday, 10 February 2024 17:41:43 CET Nikolay Sabelnikov wrote:
> Package: linux-image-amd64
> Version: 6.1.76-1
>
> > update-initramfs: Generating /boot/initrd.img-6.1.0-18-amd64
> > W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for
> > module
Control: reassign -1 firmware-iwlwifi 20230625-2
Control: retitle -1 firmware-iwlwifi: Please update to version 20230919
On Sunday, 11 February 2024 16:34:16 CET Miguel Angel Rojas wrote:
> > While 'annoying', this is expected behavior. It tries to load the newest
> > (-83)
> Yes, this is the
Hi Miguel,
On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote:
> I forgot to include you the dmesg as promised:
>
> [2.235947] iwlwifi :00:14.3: enabling device ( -> 0002)
> [2.237778] iwlwifi :00:14.3: Detected crf-id 0x1300504, cnv-id
> 0x80401 wfpm id
On Sunday, 11 February 2024 11:11:53 CET Miguel Angel Rojas wrote:
> My bad. Let me explain again. Taking into account the firmware errors:
>
>- Realtek messages are fixed now. There are no actions to be done here.
Good.
>- iwlwifi: If you are still working on a new version containing
Control: tag -1 moreinfo
Hi,
On Friday, 9 February 2024 19:35:01 CET Miguel A. Rojas wrote:
> A few days ago, I went to
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> and update the missing loaded modules.
>
> Indeed, I noticed that I have another messages
On Friday, 9 February 2024 13:39:23 CET Arno Lehmann wrote:
> [Fr Feb 9 13:25:08 2024] CPU: 20 PID: 84300 Comm: kworker/20:0 Not
> tainted 6.5.0-0.deb12.4-amd64 #1 Debian 6.5.10-1~bpo12+1
> [Fr Feb 9 13:25:08 2024] Hardware name: ASUS System Product Name/ROG
> STRIX X670E-A GAMING WIFI, BIOS
Control: tag -1 moreinfo
On Monday, 5 February 2024 15:47:08 CET Nate wrote:
> Would be possible to compile it as a module in the kernel ?
> There may be technical limitations that I am not aware of.
The kernel module depends on AMDTEE (Trusted Execution Environment) and I'm
not sure if you'd
On Friday, 2 February 2024 20:10:53 CET Miguel Angel wrote:
> Package: firmware-realtek
> Version: 20230625-2
> Severity: important
> X-Debbugs-Cc: mianro...@gmail.com
>
> At system boot, the following message is shown:
> "Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2".
>
>
Package: amd64-microcode
Version: 3.20231019.1
Severity: normal
X-Debbugs-Cc: debian-kernel@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
While working on a firmware-nonfree update I came across a commit where
a new file was added in a new directory: ``amdtee``:
On Thursday, 1 February 2024 14:33:05 CET Debian Bug Tracking System wrote:
> Source: rust-url
> Architecture: source
> Version: 2.5.0-1
> Maintainer: Debian Rust Maintainers
> Changed-By: Peter Michael
> Green
> Closes: 1061688
> Changes:
> rust-url (2.5.0-1) unstable; urgency=medium
> .
>
On Thursday, 1 February 2024 05:51:53 CET Francois Marier wrote:
> My solution is simple: ignore the "failed to load iwl-debug-yoyo.bin (-2)"
> for now.
Thanks for the warning and your solution seems sound to me.
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 -moreinfo
On Sunday, 28 January 2024 17:34:05 CET Diederik de Haas wrote:
> It seems to use a NVIDIA Tegra K1 CD570M-A1 which seems to be ARM
> Cortex-A15. So should these options (only) be enabled on armhf?
Got a response on IRC: yes
signature.asc
Descr
Control: tag -1 moreinfo
On Sunday, 28 January 2024 17:23:15 CET Alex wrote:
> Various Tegra K1 Chromebooks exist such as the Acer CB5-311, which are
> capable of booting Debian with an unmodified kernel. However there are a
> few missing modules which are needed for full functionality.
>
> On
Patrice,
On Sunday, 28 January 2024 11:44:59 CET Linux regression tracking (Thorsten
Leemhuis) wrote:
> On 27.01.24 14:14, Salvatore Bonaccorso wrote:
> > In Debian (https://bugs.debian.org/1061449) we got the following
> > quotred report:
> >
> > On Wed, Jan 24, 2024 at 07:38:16PM +0100,
Control: tag -1 moreinfo
On Wednesday, 24 January 2024 12:18:01 CET Răzvan Sandu wrote:
> ackage: firmware-realtek
> Version: 20230210-5
> Severity: normal
>
> I've noted that two Realtek-based Ethernet cards (hardware ID
> [10ec:8136], chipset RTL8111C) in my system operate as Fast Ethernet,
Control: tag -1 =upstream
On Wednesday, 24 January 2024 21:41:29 CET Patrice Duroux wrote:
> Finally, no more complaints!
>
> $ uname -a
> Linux kos-moceratops 6.7+unreleased-amd64 #1 SMP PREEMPT_DYNAMIC
> Debian 6.7.1-1~exp1a~test (2024-01-24) x86_64 GNU/Linux
Excellent, now we know commit
p 17 00:00:00 2001
From: Diederik de Haas
Date: Wed, 24 Jan 2024 19:59:35 +0100
Subject: [PATCH] Revert "drm/amd/display: Pass pwrseq inst for backlight and
ABM"
This reverts commit f90fb3a482d1d4705603ab6c320de0ccd611055c.
---
.../drm/amd/display/dc/bios/bios_parser2.c| 4 +-
On Monday, 22 January 2024 15:42:48 CET Diederik de Haas wrote:
> I'm currently working on an update for upstream version 20230919, based
> upon MR86 (Release 20230804) [1], which itself is based upon MR85
> (Update to 20230625) [2] and I'm running into some major issues:
https://salsa.d
Source: firmware-nonfree
Version: 20230625-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm currently working on an update for upstream version 20230919, based
upon MR86 (Release 20230804) [1], which itself is based upon MR85
(Update to 20230625) [2] and I'm running into
Control: found -1 20190717-1
On Wed, 24 Mar 2021 11:12:02 +0100 maximilian attems wrote:
> > I seem to have the same problem with version 20190717 (debian testing
> > 5.4.13-1 amd64).
>
> How about firmware 20210208-4, which should have an upgrade and
> latest linux in Debian Bullseye?
What's
Control: tag -1 moreinfo
On Wednesday, 30 August 2023 10:34:03 CET hanzoh wrote:
> installing Debian 12 on an HP ProDesk 400 G5 Mini works fine, but gives the
> following warning in dmesg:
> Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin
> So when installing firmware-misc-nonfree, this
On Friday, 23 June 2023 18:33:44 CET Alex Deucher wrote:
> On Wed, Jun 21, 2023 at 11:38 AM Ben Hutchings wrote:
> > On Thu, 27 Apr 2023 15:43:28 +0800 xiao sheng wen(
> > wrote:
> > > Package: firmware-amd-graphics
> > > Version: 20230310-1~exp1
> > >
> > > When I upgrade to kernel
On Monday, 15 January 2024 14:07:42 CET Emanuele Rocca wrote:
> A partial explanation for the confusion is that right now the master
> branch is where you land changes that target experimental, while the sid
> branch is for changes targeting sid. However, obviously not all commits
> end up in
I don't feel qualified on the general topic, but ...
On Thursday, 21 December 2023 17:30:26 CET Bastian Blank wrote:
> - All changes need to go via master, which they should do anyway.
I think this as a general rule, with few clearly defined exceptions (like
stable release updates), would be a
On Saturday, 13 January 2024 20:22:39 CET Arno Lehmann wrote:
> Am 13.01.2024 um 17:13 schrieb Diederik de Haas:
> > Via https://snapshot.debian.org/package/linux-signed-amd64/ you have easy
> > access to previous (6.1) kernels uploaded to Debian with which you can
> >
On Saturday, 13 January 2024 16:39:51 CET Arno Lehmann wrote:
> > Just to be clear, can you confirm this is or is not a regression from
> > a previous running 6.1.y kernel?
>
> On this hardware, the network issues appeared right from the start.
> ...
> Actually I don't even know which was the
On Saturday, 13 January 2024 11:45:29 CET Arno Lehmann wrote:
> Hardware name: ASUS System Product Name/ROG STRIX X670E-A GAMING WIFI,
> BIOS 1410 04/28/2023
Possibly not related, but there's BIOS 1807 available.
signature.asc
Description: This is a digitally signed message part.
On Thursday, 4 January 2024 14:34:10 CET Jy Deng wrote:
> 3. I find that if CONFIG_CPU_FREQ_GOV_POWERSAVE=m, then though such
> module cannot be in use after boot at once, but it is possible to
> manually modprobe them. So it may indicate that to use
> CONFIG_CPU_FREQ_GOV_POWERSAVE=m with
On Friday, 29 December 2023 13:50:34 CET Salvatore Bonaccorso wrote:
> > Version: 6.1.67-1
> >
> > When the system reboots, it switches to the 6.1.0-16 kernel package. At
> > this point, power delivery through the Steam Deck's USB-C connector works,
> > but it will not recognize a keyboard or
On Wednesday, 20 December 2023 22:08:27 CET Thorsten Glaser wrote:
> >So it was present on 5.9.0-2 (5.9.6-1), but no longer on 5.10.X?
>
> Yes to the former, unsure to the latter.
>
> >Do you want to keep the bug open for your other/original system?
The latter question was based on it on the
On Wednesday, 20 December 2023 14:02:57 CET Thorsten Glaser wrote:
> >The firmware file iwlwifi-4965-2.ucode hasn't been updated since
> >2009-07-09, but maybe/hopefully the kernel deals better with it now?
>
> Perhaps. On this different Thinkpad, I’m running bullseye and
> don’t get the
On Wednesday, 20 December 2023 18:28:44 CET Nikolay Sabelnikov wrote:
> also, the kernel should be built with this parameter of the kernel config
>
> CONFIG_SND_SOC_AMD_LEGACY_MACH=m
That's currently not enabled in Debian's kernel config, so that needs to be
added then.
signature.asc
On woensdag 20 december 2023 18:25:38 CET you wrote:
> it was possible to test only on the kernel version 6.7 built for ubuntu.
> Unfortunately, debian does not have this version of the kernel. Even in the
> experimental repository.
Then you wait until that kernel is available in Debian and test
On Wednesday, 20 December 2023 17:20:18 CET Nikolay Sabelnikov wrote:
> I also got a bug. I tried it on the 6.7-rc6 core. in my case, the sound did
> not work.
>
> https://github.com/codepayne/linux-sound-huawei/issues/27
What works, or in this case doesn't work, on a Ubuntu kernel, is
On Friday, 23 December 2022 18:40:32 CET Yuxuan Wang wrote:
> Package: firmware-iwlwifi
> Version: 20221109-4
>
> With firmware iwlwifi-cc-a0-72.ucode, the wifi chip would throw "Microcode
> SW error detected" after the system is idle for a while. After wakig up the
> system, the wifi would
Control: tag -1 moreinfo
On Mon, 05 Dec 2022 11:57:40 + Teo wrote:
> Package: firmware-linux
> Version: 20210315-3
> Severity: important
>
> I'm trying to install Debian Stable on an msi pulse gl76 equipped with an i7
> 12700h and an Nvidia 3060 laptop.
> The problem is that neither video
Control: tag -1 moreinfo
On Fri, 18 Oct 2019 09:36:07 +0200 Kamil Jońca wrote:
>* What led up to the situation?
> Trying to use wifi under new kernel
>
> When I install new kernel my wifi starts continously restart, when i do:
> (xz -dc /var/log/syslog-2019*.xz; cat
Control: tag -1 moreinfo
On Sat, 21 Nov 2020 11:32:08 +0100 Thorsten Glaser wrote:
> Package: firmware-iwlwifi
> Version: 20200918-1
> Followup-For: Bug #934781
> X-Debbugs-Cc: t...@mirbsd.de
>
> It still happens.
>
> [583944.226966] iwl4965 :03:00.0: Microcode SW error detected.
>
On Friday, 23 December 2022 12:25:08 CET Rui Dinis wrote:
> Installed the new firmware-nonfree 20221214-1 unstable and Debian still
> crashes after a few minutes/hours. The machine completely freezes/locks up.
> The graphic card is not defective, installed windows to test, played a few
> games,
Control: tag -1 moreinfo
On Monday, 7 November 2022 23:35:44 CET Julian Groß wrote:
> Package: firmware-misc-nonfree
> Version: 20221012-1
>
> I have been running into weird behaviour on my Creative Labs Sound Blaster Z
> (Serial number either SB1500 or SB1502). Just now I noticed that a
>
On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote:
> Same behaviour with 6.6.3-1 from experimental (that's what apt gave me,
> maybe tomoroow the 6.6.4).
Either your APT cache should be updated or you're using a mirror which is
rather severely out of date.
6.6.4-1 was uploaded to
Control: tag -1 +patch
On dinsdag 19 december 2023 17:14:22 CET you wrote:
> > If you manually create those links from the above "+Link:" lines,
> > would that fix the issues?
>
> I've added only the ga107 symlinks (since this is what is needed
> for my machine) with
> ...
> and this fixes all
Control: severity -1 important
Control: tag -1 moreinfo
On Tuesday, 19 December 2023 13:57:51 CET Vincent Lefevre wrote:
> Another piece of information: this is a regression.
>
> With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107"
> gives
>
> Dec 19 04:57:07 qaa kernel: nouveau
Control: reassign -1 src:linux 6.1.55-1
Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=218085
Control: tag -1 upstream
On Sunday, 29 October 2023 19:03:30 CET Николай wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218085
updating metadata accordingly
On Monday, 18
Control: reassign -1 src:linux 6.1.66-1
Control: close -1 6.1.67-1
On Wednesday, 13 December 2023 15:27:14 CET Doug Behl wrote:
> Package: linux-image-6.1.0-15-amd64
> Version: 6.1.661
>
> Recent update from Linux image 6.1.0-13-amd64 to Linux image
> 6.1.0-15-amd64 created an issue with system
On Monday, 11 December 2023 12:29:01 CET Salvatore Bonaccorso wrote:
> I cannot test for the regression explicitly myself, but 6.1.67 was
> released with just db46c77f3d51 ("Revert "wifi: cfg80211: fix CQM for
> non-range use""). Would you be in the position of do a test build with
> that commit
On Monday, 11 December 2023 13:01:58 CET Grand T wrote:
> Linux 6.6.6 is out and its only change over Linux 6.6.5 released just a few
> days ago is reverting the patch "wifi: cfg80211: fix CQM for non-range
> use." That patch ended up regressing Linux wireless support with deadlocks
> in the IWD
On Monday, 11 December 2023 12:46:40 CET Dr. André Desgualdo Pereira wrote:
> Package: src:linux
> Version: 6.1.64-1
> Severity: important
Stop using that kernel version ASAP!
It has an ext4 bug which could cause data loss. See
https://bugs.debian.org/1057843 and
On Saturday, 9 December 2023 00:28:50 CET Jeffrey Altman wrote:
> The bug is considered valid by upstream. A proposed fix for this issue is
> being reviewed.
> http://lists.infradead.org/pipermail/linux-afs/2023-December/007408.html
> Please leave this issue open until the fix has been back
Control: reassign -1 src:linux 6.5.13-1
Control: fixed-upstream
On Friday, 8 December 2023 16:10:50 CET Timo van Roermund wrote:
> Package: linux-image-6.5.0-5-amd64
> Version: linux-image-6.5.0-5-amd64
> Severity: important
>
> My RTL8125 NIC stoped working after upgrading the kernel
On Friday, 8 December 2023 14:51:52 CET David Heidelberg wrote:
> would be lovely to have a firmware-misc-nonfree based on architecture.
> Multiple of these firmwares are bound to arm64, x86_64 or other archs.
>
> Installing them for example in the CI for x86_64 leads to needing using:
>
> dpkg
On Tuesday, 5 December 2023 18:30:39 CET Diederik de Haas wrote:
> > Link: qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin ->
> > LENOVO/21BX/audioreach-tplg.bin
>
> Added upstream in commit f9a35b3f0779844aa686b76506344db70a72820d and part
> of upstream's 20230804
On Tuesday, 28 November 2023 14:29:28 CET Emanuele Rocca wrote:
> Package: firmware-qcom-soc
> Version: 20230515-3
>
> The file qcom/sc8280xp/LENOVO/21BX/audioreach-tplg.bin and its symlink
> qcom/sc8280xp/SC8280XP-LENOVO-X13S-tplg.bin are needed by the Lenovo
> Thinkpad X13s. Please consider
Control: forwarded -1
https://lore.kernel.org/linux-iommu/Y9qSwkLxeMpffZK%2F@gallifrey/
https://lore.kernel.org/linux-media/cover.1701349092.git.hverkuil-ci...@xs4all.nl/
On Sunday, 3 December 2023 17:50:07 CET Dr. David Alan Gilbert wrote:
> As well as the fixes in 6.6,
A 6.6 kernel is now
On Tuesday, 21 November 2023 17:58:55 CET John Vincent wrote:
> Do you have any update on the Bug#1053503 please (Enable additional Renesas
> platform like RZ/V2L). Is this change already got merged and available in
> the daily Debian builds for testing?
FTR: I do NOT speak on behalf of the Debian kernel team.
On Tuesday, 14 November 2023 20:58:58 CET Paul Menzel wrote:
> > Based upon the message:
> > [ 14.401143] firmware_class: See https://wiki.debian.org/Firmware
> > for information about missing firmware
> >
> > it seems you are not
Control: found -1 6.1~rc3-1~exp1
Control: found -1 6.1.55-1
On Saturday, 4 November 2023 20:35:43 CET Jose M Calhariz wrote:
> > Ok. Please test (when you have time) 6.1.55-1.
>
> Fail : Linux afs31 6.1.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian
> 6.1~rc3-1~exp1 (2022-11-02) x86_64 GNU/Linux
>
>
Control: retitle -1 No display output on Intel NUC 12 on DP/HDMI on cold boot;
works with CPU-integrated Intel Iris Xe (TB4)
On Saturday, 4 November 2023 10:19:49 CET kurom...@stodwa.org wrote:
> On 2023-11-03 14:20, Diederik de Haas wrote:
> > On Friday, 3 November 2023 13:49:01 CET Di
On Thursday, 30 March 2023 00:27:41 CET Diederik de Haas wrote:
> The patch description which turned the module from a `bool` into a
> `tristate` explicitly mentioned security as a reason so that the module
> would ONLY be loaded when needed, instead of always for everyone ... for
&
On Friday, 3 November 2023 13:49:01 CET Diederik de Haas wrote:
> My findings are:
> > 1. If I use Thunderbolt 4 output (usb-c at the back) everything works
> > fine.
> > 2. If I use one of DP or HDMI ports the issue occurs.
> >
> > Manual for this Intel NUC12 sta
Control: reopen -1
Control: notfixed -1 6.5.8-1
Control: retitle -1 Cold boot failure on Intel NUC 12 with Intel ARC GPU output
(DP or HDMI), but not with CPU-integrated Intel Iris Xe (TB4)
On Friday, 3 November 2023 10:04:03 CET kurom...@stodwa.org wrote:
> I found out, issue is not fixed -
Control: found -1 6.1.37-1
On Thursday, 2 November 2023 18:03:25 CET Jose M Calhariz wrote:
> On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote:
> > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> > > Package: src:linux
> > > Version: 6.
On Monday, 24 July 2023 11:23:19 CET Salvatore Bonaccorso wrote:
> On Sun, Jul 02, 2023 at 09:14:50PM +, Hervé Werner wrote:
> > I've just faced this issue on the SSD disk as well, so it seems that
> > the probability is just lower on a speedier disk.
>
> Are you able to reliably preoeduce
Control: tag -1 moreinfo
On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote:
> Package: src:linux
> Version: 6.1.27-1
Can you try with the latest version in the 6.1.x series to see if the problem
is still there?
> On this hardware I am chasing a data corruption for several months on
Please, always keep the bug address in To/CC so everyone can track progress!
I think proton is quite horrible as it encourages top posting and generally
makes using email properly difficult, but please adjust for their shortcomings.
On Thursday, 2 November 2023 14:46:05 CET Peter Malmberg wrote:
On Sunday, 29 October 2023 03:39:22 CET Peter Malmberg wrote:
> Which files should I download?
My bad, I referenced the meta package which depends on the 'actual' package:
Please, always keep the bug address in To/CC so everyone can track progress.
On zaterdag 28 oktober 2023 14:17:29 CEST you wrote:
> I'm sorry. I don't know how to install the rc kernel. I have downloaded it
> and tried both apt and dpkg but it does not install. Am I missing som
> packages to be
On Saturday, 28 October 2023 06:20:43 CEST dada007 wrote:
> Package: src:linux
> Version: 6.5.6-1
>
>* What led up to the situation?
> Updating from kernel 6.4 to 6.5
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> When I later changed
On Tuesday, 17 October 2023 19:07:30 CEST Ben Hutchings wrote:
> > > > I think it should be explicitly enabled (or disabled) and not be it
> > > > dependent on some other, possibly unrelated, Kconfig option being
> > > > enabled
> >
> > It seems an important difference between your view and mine
Control: forwarded -1 https://mastodon.tn/@ghazi/111240903155846113
On Sunday, 15 October 2023 17:20:25 CEST Gabriel Francisco wrote:
> I found this link: https://gitlab.freedesktop.org/drm/amd/-/issues/2877
> where other people are facing the same issue as me
signature.asc
Description: This
1 - 100 of 675 matches
Mail list logo
