Processed: Re: Bug#1059607: linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm
Processing commands for cont...@bugs.debian.org: > found 1059607 6.5.13-1 Bug #1059607 [src:linux] linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm Marked as found in versions linux/6.5.13-1. > found 1059607 6.6.9-1 Bug #1059607 [src:linux] linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm Marked as found in versions linux/6.6.9-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059607: linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm
found 1059607 6.5.13-1 found 1059607 6.6.9-1 thanks On 2024-01-06 06:24, Salvatore Bonaccorso wrote: And given this commit was backported to 4.19.298, 5.10.200, 6.1.62, 6.5.11 and 6.6.1. Can you confirm the problem is as well present in the current available 6.5.13-1 and 6.6.9-1? I can confirm the problem is present in those versions as well. Sincerely, Cory Bloor
Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version
Hi , The full log for that upgrade was: Start-Date: 2024-01-02 20:30:06 Commandline: apt upgrade Requested-By: bitseater (1000) Install: linux-image-6.6.9-amd64:amd64 (6.6.9-1, automatic) Upgrade: qemu-system-x86:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), udev:amd64 (255.2-2, 255.2-3), libexttextcat-2.0-0:amd64 (3.4.6-1, 3.4.7-1), libmm-glib0:amd64 (1.22.0-1, 1.22.0-2), systemd-container:amd64 (255.2-2, 255.2-3), libnss-myhostname:amd64 (255.2-2, 255.2-3), modemmanager:amd64 (1.22.0-1, 1.22.0-2), qemu-system-modules-opengl:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), libpam-systemd:amd64 (255.2-2, 255.2-3), sed:amd64 (4.9-1, 4.9-2), xxd:amd64 (2:9.0.2116-1, 2:9.0.2189-1), python3-httpx:amd64 (0.23.3-1, 0.26.0-1), libnorm1:amd64 (1.5.9+dfsg-2, 1.5.9+dfsg-3), vim-common:amd64 (2:9.0.2116-1, 2:9.0.2189-1), qemu-system-modules-spice:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), libsystemd0:amd64 (255.2-2, 255.2-3), libudev-dev:amd64 (255.2-2, 255.2-3), systemd:amd64 (255.2-2, 255.2-3), libudev1:amd64 (255.2-2, 255.2-3), qemu-utils:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), systemd-dev:amd64 (255.2-2, 255.2-3), libnss-mymachines:amd64 (255.2-2, 255.2-3), linux-image-amd64:amd64 (6.6.8-1, 6.6.9-1), vim-tiny:amd64 (2:9.0.2116-1, 2:9.0.2189-1), qemu-system-misc:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), libcrypt-dev:amd64 (1:4.4.36-2, 1:4.4.36-4), multipath-tools:amd64 (0.9.4-7, 0.9.4-10), libcrypt1:amd64 (1:4.4.36-2, 1:4.4.36-4), qemu-system-common:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), python3-httpcore:amd64 (0.17.3-1, 1.0.2-1), qemu-block-extra:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), libopenmpi3:amd64 (4.1.6-4, 4.1.6-5), libsystemd-shared:amd64 (255.2-2, 255.2-3), systemd-sysv:amd64 (255.2-2, 255.2-3), libexttextcat-data:amd64 (3.4.6-1, 3.4.7-1), libxml-parser-perl:amd64 (2.46-4, 2.47-1), qemu-system-data:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), kpartx:amd64 (0.9.4-7, 0.9.4-10), valgrind:amd64 (1:3.20.0-2, 1:3.20.0-2.1), qemu-system-gui:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), libsystemd-dev:amd64 (255.2-2, 255.2-3), linux-libc-dev:amd64 (6.6.8-1, 6.6.9-1) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2024-01-02 20:31:08 / / I don't have any dkms module packages installed. Regards El 6/1/24 a las 15:40, Salvatore Bonaccorso escribió: Hi, On Sat, Jan 06, 2024 at 02:00:58PM +0100, Carlos Suérez wrote: Package: linux-image-6.6.9-amd64 Version: 6.6.9-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? System update failure with manual 'apt update' at terminal. * What exactly did you do (or not do) that was effective (or ineffective)? I have tried to install the package only * What was the outcome of this action? I get the same error * What outcome did you expect instead? Update done -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.8-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.6.9-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod 31-1 ii linux-base 4.9 Versions of packages linux-image-6.6.9-amd64 recommends: ii apparmor 3.0.12-1+b2 ii firmware-linux-free 20200122-3 Versions of packages linux-image-6.6.9-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.12~rc1-12 pn linux-doc-6.6 *** Output when i try to update/install the linux-image package from 6.6.8 to 6.6.9 *** /run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure): el subproceso instalado paquete linux-image-6.6.9-amd64 script post-installatio n devolvió el código de salida de error 1 Se encontraron errores al procesar: linux-image-6.6.9-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1)/ Can you please provide the full log of the update, which other packages are involved? Do you have any dkms modules packages installed? Regards, Salvatore
Bug#942563: closed by car...@debian.org (Closing this bug (BTS maintenance for src:linux bugs))
Salvatore Bonaccorso writes: [..] >> please reopen the bug, see https://www.debian.org/Bugs/server-control >> for details. > > Oh it seems I miss-closed while doing housekeeping of linux bugs, as > this was re-eassociated with firmware-nonfree. but I won't open it now > again. In case the issue is still reproducible with recent version > then please do so. To be honest I am not able to recreate bug - I have different hardware now (new laptop), so now I am not hit by it. KJ
Bug#942563: closed by car...@debian.org (Closing this bug (BTS maintenance for src:linux bugs))
Hi, On Sat, Jan 06, 2024 at 08:27:06AM +, Debian Bug Tracking System wrote: [...] > Hi > > This bug was filed for a very old kernel or the bug is old itself > without resolution. > > If you can reproduce it with > > - the current version in unstable/testing > - the latest kernel from backports > > please reopen the bug, see https://www.debian.org/Bugs/server-control > for details. Oh it seems I miss-closed while doing housekeeping of linux bugs, as this was re-eassociated with firmware-nonfree. but I won't open it now again. In case the issue is still reproducible with recent version then please do so. Regards, Salvatore
Processed: tagging 1042885, severity of 1042885 is normal
Processing commands for cont...@bugs.debian.org: > tags 1042885 + moreinfo unreproducible Bug #1042885 [initramfs-tools] initramfs-tools: breaks system boot after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1 Added tag(s) unreproducible and moreinfo. > severity 1042885 normal Bug #1042885 [initramfs-tools] initramfs-tools: breaks system boot after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1 Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1042885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040663: linux: Please build linux-libc-dev package for loong64
On Wed, Jul 12, 2023 at 11:07:12AM +0200, Bastian Blank wrote: > Control: tags -1 confirmed > > Hi > > On Sat, Jul 08, 2023 at 08:41:03PM +0200, John Paul Adrian Glaubitz wrote: > > Please enable building the linux-libc-dev package for the new Debian > > architecture loong64. > > The corresponding kernel architecture is called "loongarch". > > I can't find loong64 in the debian architecture table used on > ftp-master, so we can't add it yet. This changed in 6.6.8-1 where you made the linux-libc-dev package binary-all. The problem you mention no longer exists in this form, but not having loong64 headers in the now binary-all package made many packages FTBFS on loong64. Please add support for linux-libc-dev-only architectures in debian/bin/gencontrol.py. With a binary-all linux-libc-dev it does still work to have a different src:linux in unreleased, but linux-libc-dev does now break every time src:linux gets updated since a binary-all package 6.6.10-1 has a higher version than linux-libc-dev_6.6.9+loong64 in unreleased. In practice this means that linux-libc-dev must ship headers at the latest when an architecture gets added in ports, far earlier than building kernel images (which as you said might require other changes on the ftp-master side). > Bastian Thanks Adrian
Bug#1058887: linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor
Hi Jean-Marc,
On Sat, Jan 06, 2024 at 03:01:10PM +0100, Salvatore Bonaccorso wrote:
> Hi
>
> The issue should be fixed with
> https://git.kernel.org/linus/400f6ebbc175286576c7f7fddf3c347d09d12310
> . Can you check that commit on top of the most current version in
> unstable to confirm?
Let me be a bit more specific: This is about testing the attached
patch with help of
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
to build a kernel image with the patch applied, to confirm if it fixes
the issue. Though I'm almost sure that this is the same issue.
Regards,
Salvatore
From: Johannes Berg
Date: Fri, 15 Dec 2023 11:13:34 +0100
Subject: wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ
Origin: https://git.kernel.org/linus/400f6ebbc175286576c7f7fddf3c347d09d12310
Bug-Debian: https://bugs.debian.org/1058887
On older devices (before unified image!) we can end up calling
stop_device from an rfkill interrupt. However, in stop_device
we attempt to synchronize IRQs, which then of course deadlocks.
Avoid this by checking the context, if running from the IRQ
thread then don't synchronize. This wouldn't be correct on a
new device since RSS is supported, but older devices only have
a single interrupt/queue.
Fixes: 37fb29bd1f90 ("wifi: iwlwifi: pcie: synchronize IRQs before NAPI")
Reviewed-by: Miri Korenblit
Reviewed-by: Emmanuel Grumbach
Signed-off-by: Johannes Berg
Signed-off-by: Kalle Valo
Link: https://msgid.link/20231215111335.59aab00baed7.Iadfe154d6248e7f9dfd69522e5429dbbd72925d7@changeid
---
.../net/wireless/intel/iwlwifi/pcie/internal.h | 4 ++--
drivers/net/wireless/intel/iwlwifi/pcie/rx.c| 8
drivers/net/wireless/intel/iwlwifi/pcie/trans.c | 17 +
3 files changed, 15 insertions(+), 14 deletions(-)
diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/internal.h b/drivers/net/wireless/intel/iwlwifi/pcie/internal.h
index 56def20374f3..7805a42948af 100644
--- a/drivers/net/wireless/intel/iwlwifi/pcie/internal.h
+++ b/drivers/net/wireless/intel/iwlwifi/pcie/internal.h
@@ -770,7 +770,7 @@ static inline void iwl_enable_rfkill_int(struct iwl_trans *trans)
}
}
-void iwl_pcie_handle_rfkill_irq(struct iwl_trans *trans);
+void iwl_pcie_handle_rfkill_irq(struct iwl_trans *trans, bool from_irq);
static inline bool iwl_is_rfkill_set(struct iwl_trans *trans)
{
@@ -817,7 +817,7 @@ static inline bool iwl_pcie_dbg_on(struct iwl_trans *trans)
return (trans->dbg.dest_tlv || iwl_trans_dbg_ini_valid(trans));
}
-void iwl_trans_pcie_rf_kill(struct iwl_trans *trans, bool state);
+void iwl_trans_pcie_rf_kill(struct iwl_trans *trans, bool state, bool from_irq);
void iwl_trans_pcie_dump_regs(struct iwl_trans *trans);
#ifdef CONFIG_IWLWIFI_DEBUGFS
diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/rx.c b/drivers/net/wireless/intel/iwlwifi/pcie/rx.c
index bc6a9f861711..07931c2db494 100644
--- a/drivers/net/wireless/intel/iwlwifi/pcie/rx.c
+++ b/drivers/net/wireless/intel/iwlwifi/pcie/rx.c
@@ -1783,7 +1783,7 @@ static u32 iwl_pcie_int_cause_ict(struct iwl_trans *trans)
return inta;
}
-void iwl_pcie_handle_rfkill_irq(struct iwl_trans *trans)
+void iwl_pcie_handle_rfkill_irq(struct iwl_trans *trans, bool from_irq)
{
struct iwl_trans_pcie *trans_pcie = IWL_TRANS_GET_PCIE_TRANS(trans);
struct isr_statistics *isr_stats = &trans_pcie->isr_stats;
@@ -1807,7 +1807,7 @@ void iwl_pcie_handle_rfkill_irq(struct iwl_trans *trans)
isr_stats->rfkill++;
if (prev != report)
- iwl_trans_pcie_rf_kill(trans, report);
+ iwl_trans_pcie_rf_kill(trans, report, from_irq);
mutex_unlock(&trans_pcie->mutex);
if (hw_rfkill) {
@@ -1947,7 +1947,7 @@ irqreturn_t iwl_pcie_irq_handler(int irq, void *dev_id)
/* HW RF KILL switch toggled */
if (inta & CSR_INT_BIT_RF_KILL) {
- iwl_pcie_handle_rfkill_irq(trans);
+ iwl_pcie_handle_rfkill_irq(trans, true);
handled |= CSR_INT_BIT_RF_KILL;
}
@@ -2370,7 +2370,7 @@ irqreturn_t iwl_pcie_irq_msix_handler(int irq, void *dev_id)
/* HW RF KILL switch toggled */
if (inta_hw & MSIX_HW_INT_CAUSES_REG_RF_KILL)
- iwl_pcie_handle_rfkill_irq(trans);
+ iwl_pcie_handle_rfkill_irq(trans, true);
if (inta_hw & MSIX_HW_INT_CAUSES_REG_HW_ERR) {
IWL_ERR(trans,
diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
index 92253260f568..d10208075ae5 100644
--- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
+++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
@@ -1082,7 +1082,7 @@ bool iwl_pcie_check_hw_rf_kill(struct iwl_trans *trans)
report = test_bit(STATUS_RFKILL_OPMODE, &trans->status);
if (prev != report)
- iwl_trans_pcie_rf_kill(trans, report);
+ iwl_trans_pcie_rf_kill(trans, report, false);
return hw_rfkill;
}
@@ -1237,7 +1237,7 @@ static void iwl_pcie_init_msix(struct iwl_trans_pcie *trans_pcie)
trans_pcie->hw_mask = trans_pcie->hw_init_mask;
}
-static void _iwl_trans_pcie_stop_device(struct iwl_trans *trans)
+static v
Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version
Hi, On Sat, Jan 06, 2024 at 02:00:58PM +0100, Carlos Suérez wrote: > Package: linux-image-6.6.9-amd64 > Version: 6.6.9-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate > *** > > * What led up to the situation? System update failure with manual 'apt > update' at terminal. > * What exactly did you do (or not do) that was effective (or > ineffective)? I have tried to install the package only > * What was the outcome of this action? I get the same error > * What outcome did you expect instead? Update done > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.6.8-amd64 (SMP w/12 CPU threads; PREEMPT) > Kernel taint flags: TAINT_USER > Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages linux-image-6.6.9-amd64 depends on: > ii initramfs-tools [linux-initramfs-tool] 0.142 > ii kmod 31-1 > ii linux-base 4.9 > > Versions of packages linux-image-6.6.9-amd64 recommends: > ii apparmor 3.0.12-1+b2 > ii firmware-linux-free 20200122-3 > > Versions of packages linux-image-6.6.9-amd64 suggests: > pn debian-kernel-handbook > ii grub-pc 2.12~rc1-12 > > pn linux-doc-6.6 > > > *** Output when i try to update/install the linux-image package from 6.6.8 > to 6.6.9 *** > > > /run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return > > code 127 > > dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure): > > el subproceso instalado paquete linux-image-6.6.9-amd64 script > > post-installatio > > n devolvió el código de salida de error 1 > > Se encontraron errores al procesar: > > linux-image-6.6.9-amd64 > > E: Sub-process /usr/bin/dpkg returned an error code (1)/ Can you please provide the full log of the update, which other packages are involved? Do you have any dkms modules packages installed? Regards, Salvatore
Processed: reassign 1060150 to src:linux, tagging 1060150
Processing commands for cont...@bugs.debian.org: > reassign 1060150 src:linux 6.6.9-1 Bug #1060150 [linux-image-6.6.9-amd64] linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version Bug reassigned from package 'linux-image-6.6.9-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/6.6.9+1. Ignoring request to alter fixed versions of bug #1060150 to the same values previously set Bug #1060150 [src:linux] linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version Marked as found in versions linux/6.6.9-1. > tags 1060150 + moreinfo Bug #1060150 [src:linux] linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1058887 to rfkill Intel Dual Band Wireless AC 8265 locks up machine
Processing commands for cont...@bugs.debian.org: > retitle 1058887 rfkill Intel Dual Band Wireless AC 8265 locks up machine Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Changed Bug title to 'rfkill Intel Dual Band Wireless AC 8265 locks up machine' from 'linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1058887 is important
Processing commands for cont...@bugs.debian.org: > severity 1058887 important Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1058887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1058887 in 6.1.64-1, found 1058887 in 6.5.13-1, found 1058887 in 6.6.3-1~exp1 ...
Processing commands for cont...@bugs.debian.org: > found 1058887 6.1.64-1 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Marked as found in versions linux/6.1.64-1. > found 1058887 6.5.13-1 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Ignoring request to alter found versions of bug #1058887 to the same values previously set > found 1058887 6.6.3-1~exp1 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Marked as found in versions linux/6.6.3-1~exp1. > forwarded 1058887 https://bugzilla.kernel.org/show_bug.cgi?id=218206 > https://lore.kernel.org/regressions/5ef14fe7-84a5-407f-b514-1527f7279...@gmail.com/#t Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Changed Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=218206 https://lore.kernel.org/regressions/5ef14fe7-84a5-407f-b514-1527f7279...@gmail.com/#t' from 'https://lore.kernel.org/regressions/5ef14fe7-84a5-407f-b514-1527f7279...@gmail.com/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058887: linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor
Hi The issue should be fixed with https://git.kernel.org/linus/400f6ebbc175286576c7f7fddf3c347d09d12310 . Can you check that commit on top of the most current version in unstable to confirm? Regards, Salvatore
Processed: tagging 1058887 ...
Processing commands for cont...@bugs.debian.org: > tags 1058887 + upstream Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Added tag(s) upstream. > forwarded 1058887 > https://lore.kernel.org/regressions/5ef14fe7-84a5-407f-b514-1527f7279...@gmail.com/ Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Set Bug forwarded-to-address to 'https://lore.kernel.org/regressions/5ef14fe7-84a5-407f-b514-1527f7279...@gmail.com/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1058887, found 1058887 in 6.6.8-1, found 1058887 in 6.6.9-1, found 1058887 in 6.1.69-1 ...
Processing commands for cont...@bugs.debian.org: > affects 1058887 - linux-image-6.1.0-17-amd64 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Removed indication that 1058887 affects linux-image-6.1.0-17-amd64 > found 1058887 6.6.8-1 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Marked as found in versions linux/6.6.8-1. > found 1058887 6.6.9-1 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Marked as found in versions linux/6.6.9-1. > found 1058887 6.1.69-1 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Marked as found in versions linux/6.1.69-1. > tags 1058887 + moreinfo Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1058887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1059607
Processing commands for cont...@bugs.debian.org: > tags 1059607 + moreinfo Bug #1059607 [src:linux] linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059607: linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm
Hi, On Sat, Jan 06, 2024 at 05:44:39AM -0700, Cordell Bloor wrote: > I was discussing this bug with Christian Kastner the other day. He > suggested: > > On 2024-01-02 14:55, Christian Kastner wrote: > > The hint in the offending comment regarding the dwc3 driver made me > > curious. It seems that it is not enabled in the Debian kernel, so this > > is probably something Debian-specific: > > > >$ grep DWC3 /boot/config-6.1.0-17-amd64 > ># CONFIG_USB_DWC3 is not set > > > > The solution would be to request enabling this driver in that bug report > > (ideally building/testing it first, if it's not too much work). > > I gave that a try last night and I can confirm that enabling USB_DWC3 > resolved the problem when I tested it with > b25a2f247083389e44a1c7ffb9375c7cf20fabb5. I then tested 6.1.71 with USB_DWC3 > disabled and with it enabled. My testing confirmed that USB devices work as > expected when USB_DWC3 was enabled. Thanks! And given this commit was backported to 4.19.298, 5.10.200, 6.1.62, 6.5.11 and 6.6.1. Can you confirm the problem is as well present in the current available 6.5.13-1 and 6.6.9-1? Regards, Salvatore
Processed: tagging 1059607
Processing commands for cont...@bugs.debian.org: > tags 1059607 - moreinfo Bug #1059607 [src:linux] linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version
Package: linux-image-6.6.9-amd64 Version: 6.6.9-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? System update failure with manual 'apt update' at terminal. * What exactly did you do (or not do) that was effective (or ineffective)? I have tried to install the package only * What was the outcome of this action? I get the same error * What outcome did you expect instead? Update done -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.8-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.6.9-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod 31-1 ii linux-base 4.9 Versions of packages linux-image-6.6.9-amd64 recommends: ii apparmor 3.0.12-1+b2 ii firmware-linux-free 20200122-3 Versions of packages linux-image-6.6.9-amd64 suggests: pn debian-kernel-handbook ii grub-pc 2.12~rc1-12 pn linux-doc-6.6 *** Output when i try to update/install the linux-image package from 6.6.8 to 6.6.9 *** /run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure): el subproceso instalado paquete linux-image-6.6.9-amd64 script post-installatio n devolvió el código de salida de error 1 Se encontraron errores al procesar: linux-image-6.6.9-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1)/ Thanks for your attention and greetings. Carlos Suárez (bitseater)
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 1058887 + linux-image-6.1.0-17-amd64 Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Added indication that 1058887 affects linux-image-6.1.0-17-amd64 > thanks Stopping processing here. Please contact me if you need assistance. -- 1058887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059607: linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm
I was discussing this bug with Christian Kastner the other day. He suggested: On 2024-01-02 14:55, Christian Kastner wrote: The hint in the offending comment regarding the dwc3 driver made me curious. It seems that it is not enabled in the Debian kernel, so this is probably something Debian-specific: $ grep DWC3 /boot/config-6.1.0-17-amd64 # CONFIG_USB_DWC3 is not set The solution would be to request enabling this driver in that bug report (ideally building/testing it first, if it's not too much work). I gave that a try last night and I can confirm that enabling USB_DWC3 resolved the problem when I tested it with b25a2f247083389e44a1c7ffb9375c7cf20fabb5. I then tested 6.1.71 with USB_DWC3 disabled and with it enabled. My testing confirmed that USB devices work as expected when USB_DWC3 was enabled. Sincerely, Cory Bloor
Bug#1058887: issue also impacts Debian stable
The Debian stable having the issue runs linux-image-6.1.0-17 (6.1.69-1). -- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: issue also impacts Debian stable
Processing control commands: > severity 1058887 serious Bug #1058887 [src:linux] linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor Severity set to 'serious' from 'normal' -- 1058887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058887: issue also impacts Debian stable
Control: severity 1058887 serious thanks It also impact Debian stable. I just installed Debian bookworm on a laptop and it gets the same issue. Switching off the wi-fi hangs and impacts other softwares and the poweroff. Raising the severity to serious. -- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: severity of 1060005 is serious
Processing commands for cont...@bugs.debian.org: > severity 1060005 serious Bug #1060005 [src:linux] cifs-utils: Copy file with cp, hangs with a kernel NULL pointer dereference. Bug #1060052 [src:linux] cifs-utils: Copy file from same cifs mount to cifs mount --> kernel NULL pointer derefernce Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1060005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060005 1060052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059607: linux-image-6.1.0-16-amd64: Steam Deck does not recognize USB keyboard on Bookworm
Hi Cordell,
On Sun, Dec 31, 2023 at 03:25:53AM -0700, Cordell Bloor wrote:
> b25a2f247083389e44a1c7ffb9375c7cf20fabb5 is the first bad commit
> commit b25a2f247083389e44a1c7ffb9375c7cf20fabb5
> Author: Vicki Pfau
> Date: Wed Sep 27 13:22:12 2023 -0700
>
> PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device
>
> commit 7e6f3b6d2c352b5fde37ce3fed83bdf6172eebd4 upstream.
>
> The AMD VanGogh SoC contains a DesignWare USB3 Dual-Role Device that can
> be
> operated as either a USB Host or a USB Device, similar to on the AMD
> Nolan
> platform.
>
> be6646bfbaec ("PCI: Prevent xHCI driver from claiming AMD Nolan USB3 DRD
> device") added a quirk to let the dwc3 driver claim the Nolan device
> since
> it provides more specific support.
>
> Extend that quirk to include the VanGogh SoC USB3 device.
>
> Link: https://lore.kernel.org/r/20230927202212.2388216-1...@endrift.com
> Signed-off-by: Vicki Pfau
> [bhelgaas: include be6646bfbaec reference, add stable tag]
> Signed-off-by: Bjorn Helgaas
> Cc: sta...@vger.kernel.org # v3.19+
> Signed-off-by: Greg Kroah-Hartman
>
> drivers/pci/quirks.c | 8 +---
> include/linux/pci_ids.h | 1 +
> 2 files changed, 6 insertions(+), 3 deletions(-)
Thanks. The above commit was backported to several stable series,
relevant for Debian are 5.10.200, 6.1.62, (6.5.11) and 6.6.1.
Is the issue as well reproducible with the kernels 6.5.13-1 in
testing, 6.6.9-1 in unstable?
With those datapoints it might now be good if you can report it to
upstream. Contact point would be the people from the issue introducing
commit, expanded with the linux-...@vger.kernel.org and
linux-ker...@vger.kernel.org lists.
Regards,
Salvatore
Bug#942563: marked as done (linux-image-5.2.0-3-amd64: iwlwifi continously restarts)
Your message dated Sat, 6 Jan 2024 09:24:01 +0100 (CET) with message-id <20240106082401.a0266be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #942563, regarding linux-image-5.2.0-3-amd64: iwlwifi continously restarts to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-5.2.0-3-amd64 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Trying to use wifi under new kernel * What exactly did you do (or not do) that was effective (or ineffective)? Install new kernel and try to turn on wifi card * What was the outcome of this action? wifi card continously restarted and wifi almost does not work * What outcome did you expect instead? Working wifi When I install new kernel my wifi starts continously restart, when i do: (xz -dc /var/log/syslog-2019*.xz; cat /var/log/syslog-20191018 /var/log/syslog) |grep 'Microcode SW error detected' |less -N i got 1 2019-10-08T14:45:44.172176+02:00 dorsz kernel: [23505.590088] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 2 2019-10-08T14:46:08.488163+02:00 dorsz kernel: [23529.909771] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 3 2019-10-08T14:46:20.967379+02:00 dorsz kernel: [23542.458048] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 4 2019-10-08T14:46:32.739357+02:00 dorsz kernel: [23554.230462] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 5 2019-10-08T14:46:50.147332+02:00 dorsz kernel: [23571.638079] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 6 2019-10-08T14:47:08.907810+02:00 dorsz kernel: [23590.326523] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 7 2019-10-08T14:47:22.147416+02:00 dorsz kernel: [23603.638338] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 8 2019-10-10T08:36:34.189047+02:00 dorsz kernel: [68903.707435] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 9 2019-10-10T08:37:19.245176+02:00 dorsz kernel: [68948.764097] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 10 2019-10-16T11:23:36.325515+02:00 dorsz kernel: [204894.500325] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 11 2019-10-16T11:23:48.436385+02:00 dorsz kernel: [204906.532416] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 12 2019-10-17T08:40:03.701789+02:00 dorsz kernel: [40883.812985] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 13 2019-10-17T08:41:15.461414+02:00 dorsz kernel: [40955.493970] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. [..snip...] 134 2019-10-17T11:17:27.903362+02:00 dorsz kernel: [ 1638.227436] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 135 2019-10-18T08:42:15.505884+02:00 dorsz kernel: [22331.953226] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 136 2019-10-18T08:43:04.911067+02:00 dorsz kernel: [22381.362274] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 137 2019-10-18T08:44:01.742808+02:00 dorsz kernel: [22438.194936] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. (at 11:18 2019-10-17 I returned to previous kernel) Example restart: 2019-10-17T08:40:03.700678+02:00 dorsz kernel: [40883.812797] iwlwifi :3a:00.0: Queue 10 is active on fifo 1 and stuck for 1 ms. SW [110, 128] HW [110, 128] FH TRB=0x0c010a07d 2019-10-17T08:40:03.701789+02:00 dorsz kernel: [40883.812985] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. 2019-10-17T08:40:03.701797+02:00 dorsz kernel: [40883.813172] iwlwifi :3a:00.0: Start IWL Error Log Dump: 2019-10-17T08:40:03.701800+02:00 dorsz kernel: [40883.813179] iwlwifi :3a:00.0: Status: 0x0080, count: 6 2019-10-17T08:40:03.701804+02:00 dorsz kernel: [40883.813183] iwlwifi :3a:00.0: Loaded firmware version: 36.8fd77bb3.0 2019-10-17T08:40:03.701806+02:00 dorsz kernel: [40883.813189] iwlwifi :3a:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN 2019-10-17T08:40:03.701808+02:00 dor
