Processing commands for cont...@bugs.debian.org:
> # incorrect versions
> notfound 966218 linux/6.1.0-10
Bug #966218 [src:linux] firmware: failed to load iwl-debug-yoyo.bin (-2)
Bug #969264 [src:linux] firmware-iwlwifi: failed to load iwl-debug-yoyo.bin (-2)
Bug #996029 [src:linux] firmware-iwlwif
On Fri, 2023-07-21 at 18:35 +0100, Matthew Garrett wrote:
> On Fri, Jul 21, 2023 at 10:55:39AM +0200, Marco d'Itri wrote:
>
> > Unless somebody has a better idea then then my plan is to ship in the
> > next upload of kmod a file in /etc/modprobe.d/ which uses the blacklist
> > directive to preve
Ben, thank you for a quick reply! Issue created:
https://gitlab.freedesktop.org/drm/nouveau/-/issues/246
https://gitlab.freedesktop.org/drm/nouveau/-/issues/246. There I wonder: if the
message is purely informational, it probably better really not be yellow (and
thus warn the user because yello
Your message dated Sun, 23 Jul 2023 02:11:41 +0200
with message-id <48da8f52912954063846eccc25157b2387c13cac.ca...@decadent.org.uk>
and subject line Re: Bug#1035885: iwlwifi: api flags index 2 larger than
supported by driver
has caused the Debian Bug report #1035885,
regarding iwlwifi: api flags i
Processing commands for cont...@bugs.debian.org:
> # This is only a kernel bug; it should not warn about this
> notfound 966218 firmware-iwlwifi/20230210-5
Bug #966218 [src:linux] firmware: failed to load iwl-debug-yoyo.bin (-2)
Bug #969264 [src:linux] firmware-iwlwifi: failed to load iwl-debug-yo
Your message dated Sun, 23 Jul 2023 02:04:02 +0200
with message-id <8eacd4d678e1050eacc89dd709832b5f78800811.ca...@decadent.org.uk>
and subject line Re: Bug#1041743: kernel: MXM: GUID detected in BIOS
has caused the Debian Bug report #1041743,
regarding kernel: MXM: GUID detected in BIOS
to be mark
Processing control commands:
> affects -1 src:linux smartmontools
Bug #1041745 [linux-image-6.1.0-10-amd64] smartd[…]: Device: /dev/nvme0, number
of Error Log entries increased from … to …
Added indication that 1041745 affects src:linux and smartmontools
--
1041745: https://bugs.debian.org/cgi-
Package: linux-image-6.1.0-10-amd64
Version: 6.1.38-1
Control: affects -1 src:linux
In the journal I discover the yellow warning “MXM: GUID detected in BIOS”. Is
this a software, a firmware, or a hardware problem? In plain English, what are
we really warned about? What to do to avoid whichever
Processing control commands:
> affects -1 src:linux
Bug #1041743 [linux-image-6.1.0-10-amd64] kernel: MXM: GUID detected in BIOS
Added indication that 1041743 affects src:linux
--
1041743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041743
Debian Bug Tracking System
Contact ow...@bugs.deb
The warning is still there after upgrading the kernel to
linux-image-6.1.0-10-amd64 version 6.1.38-1. The logs are attached.
Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: enabling
device (0100 -> 0102)
Jul 22 22:35:22 AnonymizedMachineName kernel: [drm] Initialized ast 0.1.0
Processing commands for cont...@bugs.debian.org:
> found 966218 src:linux/6.1.0-10
Unknown command or malformed arguments to command.
> found 966218 linux/6.1.0-10
Bug #966218 [src:linux] firmware: failed to load iwl-debug-yoyo.bin (-2)
Bug #969264 [src:linux] firmware-iwlwifi: failed to load iwl-
found 966218 src:linux/6.1.0-10
found 966218 linux/6.1.0-10
found 966218 linux-image-6.1.0-10-amd64/6.1.38-1
found 966218 firmware-iwlwifi/20230210-5
thanks
The errors in the journal still occur by default (i.e., without any options)
with ASUS AX3000 Dual Band PCE-AX3000 Wi-Fi PCI-E Adapter. The r
Package: linux-image-6.1.0-10-amd64
Version: 6.1.38-1
Control: affects -1 scr:linux
On an ASUS WS C422 PRO/SE with a Samsung SSD 970 EVO 1TB, I get a yellow kernel
warning in the journal: “nvme nvme0: missing or invalid SUBNQN field.” The
relevant parts of the logs are attached. A software issue
Processing control commands:
> affects -1 scr:linux
Bug #1041741 [linux-image-6.1.0-10-amd64] kernel: nvme nvme0: missing or
invalid SUBNQN field.
Added indication that 1041741 affects scr:linux
--
1041741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041741
Debian Bug Tracking System
Con
Processing commands for cont...@bugs.debian.org:
> found 1041503 linux-image-6.1.0-10-amd64/6.1.38-1
Bug #1041503 [linux-image-6.1.0-10-amd64] kernel: usb: port power management
may be unreliable
The source linux-image-6.1.0-10-amd64 and version 6.1.38-1 do not appear to
match any binary package
found 1041503 linux-image-6.1.0-10-amd64/6.1.38-1
thanks
Same warning after kernel upgrade on a different machine (motherboard ASUS WS
C422 PRO/SE):
Jul 22 22:35:22 AnonymizedMachineName kernel: hub 1-0:1.0: USB hub found
Jul 22 22:35:22 AnonymizedMachineName kernel: hub 1-0:1.0: 16 ports detected
On Sat, 2023-07-22 at 22:57 +0200, Salvatore Bonaccorso wrote:
[...]
> Having 6.3.11-1 into testing would really have been preferred but I understand
> people do not want to have #1040178 exposed, so let's try to move ahead with
> the 6.4.y series.
>
> Ben and Bastian, let me know loudly if you di
Processing commands for cont...@bugs.debian.org:
> severity 1001286 important
Bug #1001286 [src:linux] linux: Systems with more than 4 memory slots not
supported yet, not instantiating SPD
Bug #1011069 [src:linux] decode-dimms does not detect SPD for kingston memory
strips
Bug #1011091 [src:linu
severity 1001286 important
found 1001286 linux/6.1.0-10
found 1001286 linux-image-6.1.0-10-amd64/6.1.38-1
thanks
Same restriction here, namely for two stationary computers with Asus WS C422
PRO/SE with Intel® Xeon® W-2235 CPU @ 3.80GHz (motherboard specification:
https://www.asus.com/de/motherboa
Processing commands for cont...@bugs.debian.org:
> severity 1001286 important
Bug #1001286 [src:linux] linux: Systems with more than 4 memory slots not
supported yet, not instantiating SPD
Bug #1011069 [src:linux] decode-dimms does not detect SPD for kingston memory
strips
Bug #1011091 [src:linu
severity 1001286 important
thanks
Same restriction here, namely for two stationary computers with Asus WS C422
PRO/SE with Intel® Xeon® W-2235 CPU @ 3.80GHz (motherboard specification:
https://www.asus.com/de/motherboards-components/motherboards/workstation/ws-c422-pro-se/techspec
https://www.a
I stand corrected – the very last message as of a few minutes ago concerned a
different machine: WS C422 PRO/SE with Intel® Xeon® W-2235 CPU @ 3.80GHz, 32 GB
RAM, ASPEED AST2500 64MB built-in graphics chip, and NVIDIA GeForce GTX 1660 Ti
PCIe graphics card.
Processing commands for cont...@bugs.debian.org:
> found 1041141 6.1.38-1
Bug #1041141 [linux-image-6.1.0-10-amd64] pmd_set_huge: Cannot satisfy [mem
0xf800-0xf820] with a huge-page mapping due to MTRR override.
Marked as found in versions linux-signed-amd64/6.1.38+1.
> thanks
Stopping pr
Hi Salvatore,
On Sat, Jul 22, 2023 at 10:07:39PM +0200, Salvatore Bonaccorso wrote:
> On Tue, Jul 18, 2023 at 02:35:25AM +0200, Daniel Gröber wrote:
> > I got the following BUG on my router while working on my nftables
> > ruleset. After this happened network connectivity was broken quite severely
Hi
I would like to upload linux version 6.4.4-1 later the upcoming days
to unstable. This is quite unfortunate as i wanted to have the
security fixes from 6.3.11-1 for a while now in unstable, but
transition is blocked due #1040178.
The new upload would consist of a new upstream version switching
Processing control commands:
> tags -1 + moreinfo
Bug #1041363 [src:linux] nft BUG: kernel NULL pointer dereference, address:
0038
Added tag(s) moreinfo.
--
1041363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041363
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Control: tags -1 + moreinfo
Hi Daniel,
On Tue, Jul 18, 2023 at 02:35:25AM +0200, Daniel Gröber wrote:
> Package: src:linux
> Version: 6.1.27-1
> Severity: normal
>
> Dear Maintainer,
>
> I got the following BUG on my router while working on my nftables
> ruleset. After this happened network con
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 14 Jul 2023 22:24:08 +0200
Source: linux-signed-i386
Architecture: source
Version: 5.10.179+2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel Team
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 14 Jul 2023 22:24:08 +0200
Source: linux-signed-arm64
Architecture: source
Version: 5.10.179+2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel Tea
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 14 Jul 2023 22:24:08 +0200
Source: linux-signed-amd64
Architecture: source
Version: 5.10.179+2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel Tea
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 14 Jul 2023 22:24:08 +0200
Source: linux
Architecture: source
Version: 5.10.179-2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Kernel Team
Changed-By
Package: src:linux
Version: 6.1.38-1
Severity: important
Dear Maintainer,
after upgrading a server to bookworm, I experience hangs on shutdown
while the console is spammed with "md: mdXX stopped." messages.
As this is a remote server, it's tricky for me to copy the entire
shutdown log, but I was
32 matches
Mail list logo
