Package: firmware-iwlwifi
Version: 20220913-1
Severity: important
X-Debbugs-Cc: a...@transient.nz
Dear Maintainer,
firmware-iwlwifi 20220913-1 fails to load on Intel Corporation Wireless-AC 9260
(rev 29), breaking network connectivity. Downgrading to firmware-iwlwifi
20210818-1, running "update-i
I can no longer reproduce this. Currently running Ubuntu 22.10 with kernel
5.19.0-23-generic. C-states enabled in the BIOS.
> Package: linux-image-5.18.0-4-amd64
> Severity: important
>
> The intel/ibt-20-1-3.sfi file loads fine on linux-image-5.18.0-3-amd64.
> Used that to report this bug as the failure to load leaves me without a
> working keyboard. It's a bluetooth-only keyboard and it not working at
> all is why I'
Processing control commands:
> reassign -1 src:linux 6.0.3-1
Bug #1023076 [linux-headers-6.0.0-2-amd64] linux-headers-6.0.0-2-amd64:
bluetooth crashes after returning from suspend
Bug reassigned from package 'linux-headers-6.0.0-2-amd64' to 'src:linux'.
No longer marked as found in versions linux
Control: reassign -1 src:linux 6.0.3-1
Control: severity -1 important
On Sunday, 30 October 2022 00:50:25 CEST Gabriel Francisco wrote:
> Package: linux-headers-6.0.0-2-amd64
> Version: 6.0.3-1
> Severity: normal
>
> With this kernel seems to crash bluetooth when returning from
> suspend. Few day
Package: linux-headers-6.0.0-2-amd64
Version: 6.0.3-1
Severity: normal
X-Debbugs-Cc: frc.gabr...@gmail.com
Dear Maintainer,
With this kernel seems to crash bluetooth when returning from
suspend. Few days ago my cursor froze, the computer rebooted and I
couldn't find logs in /var/log/syslog.
I th
On 2022-10-29 20:05, Diederik de Haas wrote:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?qt=grep&q=WCN6855
does show various results which come very close ...SILICONZ_LITE-3.6510.7 vs
the referenced ...SILICONZ_LITE-3.6510.16.
And one commit is for symlinks to
On Sat, 2022-10-29 at 09:44 +0200, Salvatore Bonaccorso wrote:
> We do similar with intel-microcode updates, so maybe this is
> something
> we should consider to. But I think it's to early to think about a
> potential 20220913-1~deb11u1 via a bullseye point release.
It's just that for any bullseye
On Sat, 2022-10-29 at 09:23 +0200, Salvatore Bonaccorso wrote:
>
> No unfortunately we cannot do that. The reason is similar to what
> lead
> to
> https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
> or caused bugs like #916927.
Forgive me my ignorance, b
binary:affs-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:affs
For completeness: The problem persists with the new kernel in Sid.
> 6.0.0-2-amd64 / Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux
linux_6.0.3-1~bpo11+1_source.changes uploaded successfully to localhost
along with the files:
linux_6.0.3-1~bpo11+1.dsc
linux_6.0.3-1~bpo11+1.debian.tar.xz
linux_6.0.3-1~bpo11+1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing commands for cont...@bugs.debian.org:
> # bts housekeeping
> fixed 950271 1.8.6~rc2-1
Bug #950271 {Done: Bastian Germann } [netperfmeter] Please
provide a backported netperfmeter for Buster
Marked as fixed in versions netperfmeter/1.8.6~rc2-1.
> reassign 1014283 nvidia-tesla-driver 510
Processing control commands:
> tag -1 -a11y
Bug #1023025 [src:linux] linux-image-6.0.0-2-686: kernel BUG at
mm/memory.c:2660!
Removed tag(s) a11y.
--
1023025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 -a11y
On zaterdag 29 oktober 2022 12:33:59 CEST femenia wrote:
> Package: src:linux
> Version: 6.0.3-1
> Severity: grave
> Tags: a11y
I don't see how a11y is relevant here, so removing the tag
signature.asc
Description: This is a digitally signed message part.
On zaterdag 29 oktober 2022 07:15:19 CEST Vincent Bernat wrote:
> On 2022-10-29 00:50, Diederik de Haas wrote:
> >> The card works just fine with a 5.19 kernel after installing these files
> >> in /usr/lib/firmware/ath11k/WCN6855/hw2.0/:
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6
Mapping sid to unstable.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 28 Oct 2022 08:53:43 +0200
Source: linux-signed-i386
Architecture: source
Version: 6.0.5+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
linux-signed-i386_6.0.5+1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-i386_6.0.5+1.dsc
linux-signed-i386_6.0.5+1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing commands for cont...@bugs.debian.org:
> notfound 1021315 5.19.0-2
Bug #1021315 [src:linux] Linux kernel very slow to boot
The source 'linux' and version '5.19.0-2' do not appear to match any binary
packages
No longer marked as found in versions linux/5.19.0-2.
> found 1021315 5.19.11-1
Processing commands for cont...@bugs.debian.org:
> # bts housekeeping
> reassign 1021315 src:linux 5.19.0-2
Bug #1021315 [linux-image-5.19.0-2-arm64] Linux kernel very slow to boot
Warning: Unknown package 'linux-image-5.19.0-2-arm64'
Bug reassigned from package 'linux-image-5.19.0-2-arm64' to 'sr
Mapping sid to unstable.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 28 Oct 2022 08:53:43 +0200
Source: linux-signed-arm64
Architecture: source
Version: 6.0.5+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
linux-signed-arm64_6.0.5+1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-arm64_6.0.5+1.dsc
linux-signed-arm64_6.0.5+1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Package: src:linux
Version: 6.0.3-1
Severity: grave
Tags: a11y
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (o
Mapping sid to unstable.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 28 Oct 2022 08:53:43 +0200
Source: linux-signed-amd64
Architecture: source
Version: 6.0.5+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
linux-signed-amd64_6.0.5+1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-amd64_6.0.5+1.dsc
linux-signed-amd64_6.0.5+1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
On Sat, Oct 29, 2022 at 12:31:18AM +0200, Christoph Anton Mitterer wrote:
> Is this going to be backported to bullseye?
First is needs to settle a bit.
But as you can see, in the past we did produce backports:
| firmware-nonfree | 20210818-1~bpo11+1 | bullseye-backports/non-free | source
Bastia
On Saturday, 29 October 2022 11:08:01 CEST karol wrote:
> Package: src:linux
> Version: 6.0.3-1
>
> I noticed several internal crashed in linux kernel ...
> This happened today during resume.
>
> They are follow as below:
>
> paź 29 10:55:35 karol kernel: [ cut here ]
> p
On Saturday, 29 October 2022 10:59:21 CEST Salvatore Bonaccorso wrote:
> > It was based on that log that I did most/all my recent bug closing.
>
> The files are present in the source and copied to debian/build/install
> . But they are then not installed in any of the produced binary
> packages in
Package: src:linux
Version: 6.0.3-1
Severity: normal
X-Debbugs-Cc: karol...@gmail.com
Dear Maintainer,
I noticed several internal crashed in linux kernel after the lates testing
migration
(https://tracker.debian.org/news/1378942/linux-signed-amd64-6031-migrated-to-testing/).
This happened today
Hi,
On Sat, Oct 29, 2022 at 10:37:11AM +0200, Diederik de Haas wrote:
> On Saturday, 29 October 2022 09:01:49 CEST Salvatore Bonaccorso wrote:
> > > They are part of the above version, thus closing.
> >
> > Actually they are shipped with amd64-microcode instead:
>
> Indeed. How come it 'still' s
Package: src:linux
Version: 6.0.3-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Close lid of laptop (an LG Gram 16 2022
* What exactly did you do (or not do) that was effective (or ineffective)?
Reopen it later.
* What was the outcome of this action?
Resume sc
On Sat, Oct 29, 2022, at 1:00 AM, Diederik de Haas wrote:
> On Sunday, 19 December 2021 04:12:27 CEST Alexander Prinsier wrote:
>> Package: firmware-iwlwifi
>> Version: 20210818-1
>>
>> Recently did a dist upgrade, which upgraded firmware-iwlwifi to version
>> 20210818-1.
>>
>> On the next reboot
On Saturday, 29 October 2022 09:01:49 CEST Salvatore Bonaccorso wrote:
> > They are part of the above version, thus closing.
>
> Actually they are shipped with amd64-microcode instead:
Indeed. How come it 'still' shows up in firmware-nonfree's build log?
https://buildd.debian.org/status/fetch.php
On 2022-10-29 09:23, Salvatore Bonaccorso wrote:
So question is,.. would it make sense to request that linux-image-amd64
depends on the signed | unsigned version?
No unfortunately we cannot do that. The reason is similar to what lead
to
https://salsa.debian.org/kernel-team/linux/-/commit/248736
Hi Bastian,
On Sun, Oct 23, 2022 at 03:27:24PM +0200, Bastian Blank wrote:
> On Sat, Oct 22, 2022 at 11:15:05AM +0200, Bastian Blank wrote:
> > On Sat, Oct 22, 2022 at 10:59:30AM +0200, Bastian Blank wrote:
> > > I would like to do some last minute changes to the linux package
> > # Drop special c
Hi,
On Sat, Oct 29, 2022 at 12:31:18AM +0200, Christoph Anton Mitterer wrote:
> Hey Bastian.
>
> Thanks for fixing.
>
> Is this going to be backported to bullseye?
We do similar with intel-microcode updates, so maybe this is something
we should consider to. But I think it's to early to think ab
Hi Christoph,
On Sat, Oct 29, 2022 at 12:36:01AM +0200, Christoph Anton Mitterer wrote:
> Hey Salvatore.
>
> On Fri, 2022-10-28 at 06:49 +0200, Salvatore Bonaccorso wrote:
> > I did decide to still do so, so we can have the CVE fix migrate
> > finally to testing (which took some time as well give
Processing commands for cont...@bugs.debian.org:
> tags 1021157 - moreinfo
Bug #1021157 [firmware-atheros] missing firmwares for Qualcomm NFA725A
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1021157: https://bugs.debian.org/cgi-bin/bugr
Hi,
On Sat, Oct 29, 2022 at 12:18:16AM +0200, Diederik de Haas wrote:
> Control: fixed -1 20220913-1
>
> On Wednesday, 6 July 2022 12:46:16 CEST Enrique wrote:
> > Package: firmware-brcm80211
> > Version: 20210315-3
> >
> > I have installed pure Debian on a Raspberry Pi 4 and the kernel shows
>
Processing commands for cont...@bugs.debian.org:
> reassign 1005400 src:amd64-microcode
Bug #1005400 {Done: Diederik de Haas }
[firmware-nonfree] firmware-nonfree: Please package AMD SEV firmware.
Bug reassigned from package 'firmware-nonfree' to 'src:amd64-microcode'.
No longer marked as found i
Hi,
> Version: 20220913-1
>
> On Saturday, 12 February 2022 21:40:30 CEST Sebastian Andrzej Siewior wrote:
> > Version: 20210818-1
> >
> > The orig contains already the AMD SEV firmware in the amd folder:
> > | $ ls -lh amd
> > | 33K Aug 18 13:08 amd_sev_fam17h_model0xh.sbin
> > | 43K Aug 18 13:
41 matches
Mail list logo
