Bug#823485: kernel: brcmsmac bcma0:1: START: tid 1 is not agg'able
I'm seeing the same thing on a MacBookAir5,2 device with this hardware:
02:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n
[14e4:4353] (rev 01)
Subsystem: Apple Inc. AirPort Extreme [106b:00e9]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at a040 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [58] Vendor Specific Information: Len=78
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 7a-79-c3-ff-ff-da-7c-d1
Capabilities: [16c] Power Budgeting
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma
The device seems to work fine (I'm filling out this bug report over ssh)
but this spams the kernel log multiple times per second. This patch
from wireless-drivers-next looks like it could help:
https://patchwork.kernel.org/patch/10653373/
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git/commit/?id=96fca788e5788b7ea3b0050eb35a343637e0a465
commit 96fca788e5788b7ea3b0050eb35a343637e0a465
Author: Ali MJ Al-Nasrawy
Date: Tue Oct 23 19:12:35 2018 +0300
brcmsmac: never log "tid x is not agg'able" by default
This message greatly spams the log under heavy Tx of frames with BK access
class which is especially true when operating as AP. It is also not
informative
as the "agg'ablity" of TIDs are set once and never change.
Fix this by logging only in debug mode.
Signed-off-by: Ali MJ Al-Nasrawy
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmsmac/mac80211_if.c
b/drivers/net/wireless/broadcom/brcm80211/brcmsmac/mac80211_if.c
index 81ff558046a8..6188275b17e5 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmsmac/mac80211_if.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmsmac/mac80211_if.c
@@ -846,8 +846,8 @@ brcms_ops_ampdu_action(struct ieee80211_hw *hw,
status = brcms_c_aggregatable(wl->wlc, tid);
spin_unlock_bh(&wl->lock);
if (!status) {
- brcms_err(wl->wlc->hw->d11core,
- "START: tid %d is not agg\'able\n", tid);
+ brcms_dbg_ht(wl->wlc->hw->d11core,
+"START: tid %d is not agg\'able\n", tid);
return -EINVAL;
}
ieee80211_start_tx_ba_cb_irqsafe(vif, sta->addr, tid);
Processed: linux: FTBFS on arm64: changed ABI
Processing control commands: > affects -1 release.debian.org Bug #914556 [src:linux] linux: FTBFS on arm64: changed ABI Added indication that 914556 affects release.debian.org -- 914556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914556: linux: FTBFS on arm64: changed ABI
Source: linux Version: 4.9.135-1 Severity: serious Justification: FTBFS Control: affects -1 release.debian.org For tracking the issue: 4.9.135-1 FTBFS on arm64 due to changed ABI: https://buildd.debian.org/status/fetch.php?pkg=linux&arch=arm64&ver=4.9.135-1&stamp=1543036173&raw=0 Relevant part: hnae_ae_register module: drivers/net/ethernet/hisilicon/hns/hnae, version: 0xdf635812 -> 0xbdde09c7, export: EXPORT_SYMBOL hnae_ae_unregister module: drivers/net/ethernet/hisilicon/hns/hnae, version: 0xe679c9fd -> 0x1c9eb41e, export: EXPORT_SYMBOL hnae_get_handle module: drivers/net/ethernet/hisilicon/hns/hnae, version: 0xafb4a8fd -> 0x29ae7935, export: EXPORT_SYMBOL hnae_put_handle module: drivers/net/ethernet/hisilicon/hns/hnae, version: 0x899f69bb -> 0x43a26da5, export: EXPORT_SYMBOL hnae_reinit_handle module: drivers/net/ethernet/hisilicon/hns/hnae, version: 0x767c1c31 -> 0xbc41182f, export: EXPORT_SYMBOL Regards, Salvatore
Re: linux: enable CONFIG_CRYPTO_MORUS* and CONFIG_CRYPTO_AEGIS*
Hey. Just wondered if a maintainer could possibly tell me whether this could happen anytime soon? It's no big problem for me if not, I'd just want to avoid compiling the whole kernel on my system (which is not the fastest one ^^) if you'd enable it anyway on the next version or so. Cheers, Chris.
Bug#914526: marked as done (linux-image-4.18.0-0.bpo.1-amd64: Invalidating filesystems can corrupt dentry table leading to busy loop in kernel.)
Your message dated Sat, 24 Nov 2018 18:23:11 + with message-id and subject line Re: Bug#914526: linux-image-4.18.0-0.bpo.1-amd64: Invalidating filesystems can corrupt dentry table leading to busy loop in kernel. has caused the Debian Bug report #914526, regarding linux-image-4.18.0-0.bpo.1-amd64: Invalidating filesystems can corrupt dentry table leading to busy loop in kernel. 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.) -- 914526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Tags: upstream patch Please see https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/commit/?h=for-linus - invalidating filesystems can cause dentry table corruption leading to busy loop in kernel. Easily triggered from userspace (observed triggers using NFS, XFS and ZFS). Patch supplied upstream; please consider cherrypicking this to BPO kernel. Thanks. -- Package-specific info: ** Version: Linux version 4.18.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13) ** Command line: BOOT_IMAGE=/boot@/boot/vmlinuz-4.18.0-0.bpo.1-amd64 root=ZFS=rpool/boot ro ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: product_name: product_version: chassis_vendor: chassis_version: bios_vendor: Intel Corporation bios_version: MYBDWi30.86A.0038.2016.0913.1446 board_vendor: Intel Corporation board_name: NUC5i3MYBE board_version: H47781-206 ** Loaded modules: xt_nat cfg80211 xt_tcpmss ipt_MASQUERADE xt_limit xt_recent ip6table_nat nf_nat_ipv6 ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 nf_log_ipv6 ip6table_filter ip6_tables xt_comment iptable_nat nf_nat_ipv4 ipt_REJECT nf_reject_ipv4 xt_addrtype bridge xt_mark iptable_mangle xt_TCPMSS xt_tcpudp xt_CT iptable_raw xt_multiport nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack xt_NFLOG xt_LOG nf_log_ipv4 nf_log_common nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_nat nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack libcrc32c crc32c_generic iptable_filter nfnetlink_queue nfnetlink_log nfnetlink bluetooth drbg ansi_cprng ecdh_generic rfkill crc16 pppoe pppox ppp_generic slhc binfmt_misc nls_ascii nls_cp437 vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iTCO_wdt iTCO_vendor_support evdev kvm i915 irqbypass crct10dif_pclmul crc32_pclmul pl2303 drm_kms_helper usbserial ghash_clmulni_intel sg drm intel_cstate mei_me mei intel_uncore lpc_ich pcspkr efi_pstore intel_rapl_perf efivars video button acpi_pad pcc_cpufreq bonding 8021q garp mrp stp llc efivarfs ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) sd_mod crc32c_intel ahci libahci libata igb i2c_algo_bit scsi_mod dca aesni_intel xhci_pci ehci_pci xhci_hcd ehci_hcd aes_x86_64 crypto_simd i2c_i801 cryptd glue_helper usbcore e1000e usb_common fan thermal ** PCI devices: not available ** USB devices: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 2109:0813 VIA Labs, Inc. Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303] Bus 002 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 002 Device 002: ID 2109:2813 VIA Labs, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.18.0-0.bpo.1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.130 ii kmod
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 910607 by 914526 Bug #910607 [src:zfs-linux] zfs-linux: 'zfs receive' can apparently corrupt system mount table. 910607 was not blocked by any bugs. 910607 was not blocking any bugs. Added blocking bug(s) of 910607: 914526 > End of message, stopping processing here. Please contact me if you need assistance. -- 910607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914526: linux-image-4.18.0-0.bpo.1-amd64: Invalidating filesystems can corrupt dentry table leading to busy loop in kernel.
Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Tags: upstream patch Please see https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/commit/?h=for-linus - invalidating filesystems can cause dentry table corruption leading to busy loop in kernel. Easily triggered from userspace (observed triggers using NFS, XFS and ZFS). Patch supplied upstream; please consider cherrypicking this to BPO kernel. Thanks. -- Package-specific info: ** Version: Linux version 4.18.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13) ** Command line: BOOT_IMAGE=/boot@/boot/vmlinuz-4.18.0-0.bpo.1-amd64 root=ZFS=rpool/boot ro ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: product_name: product_version: chassis_vendor: chassis_version: bios_vendor: Intel Corporation bios_version: MYBDWi30.86A.0038.2016.0913.1446 board_vendor: Intel Corporation board_name: NUC5i3MYBE board_version: H47781-206 ** Loaded modules: xt_nat cfg80211 xt_tcpmss ipt_MASQUERADE xt_limit xt_recent ip6table_nat nf_nat_ipv6 ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 nf_log_ipv6 ip6table_filter ip6_tables xt_comment iptable_nat nf_nat_ipv4 ipt_REJECT nf_reject_ipv4 xt_addrtype bridge xt_mark iptable_mangle xt_TCPMSS xt_tcpudp xt_CT iptable_raw xt_multiport nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack xt_NFLOG xt_LOG nf_log_ipv4 nf_log_common nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_nat nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack libcrc32c crc32c_generic iptable_filter nfnetlink_queue nfnetlink_log nfnetlink bluetooth drbg ansi_cprng ecdh_generic rfkill crc16 pppoe pppox ppp_generic slhc binfmt_misc nls_ascii nls_cp437 vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iTCO_wdt iTCO_vendor_support evdev kvm i915 irqbypass crct10dif_pclmul crc32_pclmul pl2303 drm_kms_helper usbserial ghash_clmulni_intel sg drm intel_cstate mei_me mei intel_uncore lpc_ich pcspkr efi_pstore intel_rapl_perf efivars video button acpi_pad pcc_cpufreq bonding 8021q garp mrp stp llc efivarfs ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) sd_mod crc32c_intel ahci libahci libata igb i2c_algo_bit scsi_mod dca aesni_intel xhci_pci ehci_pci xhci_hcd ehci_hcd aes_x86_64 crypto_simd i2c_i801 cryptd glue_helper usbcore e1000e usb_common fan thermal ** PCI devices: not available ** USB devices: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 2109:0813 VIA Labs, Inc. Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303] Bus 002 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 002 Device 002: ID 2109:2813 VIA Labs, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.18.0-0.bpo.1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.130 ii kmod23-2 ii linux-base 4.5 Versions of packages linux-image-4.18.0-0.bpo.1-amd64 recommends: ii apparmor 2.11.0-3+deb9u2 ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2.3 Versions of packages linux-image-4.18.0-0.bpo.1-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.02~beta3-5+deb9u1 pn linux-doc-4.18 Versions of packages linux-image-4.18.0-0.bpo.1-amd64 is related to: ii firmware-amd-graphics 20180825+dfsg-1~bpo9+1 pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas ii firmware-linux-nonfree20180825+dfsg-1~bpo9+1 ii firmware-misc-nonfree 20180825+dfs
Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1
Hi, On 11/24/18 2:19 AM, Cesare Leonardi wrote: > > On Sat, 24 Nov 2018 01:08:56 +0100 Hans van Kranenburg > wrote: >> You didn't share any part of your logging. Can you share a part of dmesg >> logging that shows Oops in it? > > Here it is, attached to this message. > Previously I didn't attached it because to me it looks substantially the > same as the one I attached in the opening message of this bug (#913119). Thanks. Your logging indeed also only shows the 'task [...] blocked for more than 120 seconds', and no actual OOPS messages. >> If a task hangs while doing disk IO, it might cause messages like these >> in dmesg: >> >> INFO: task kthxbye:1157 blocked for more than 120 seconds. >> Not tainted blah #1 Debian someversion >> [...] >> >> >> These are 'just' informational messages. The process will still wait >> until it can continue. >> >> A kernel Oops is something really different. It usually means that some >> data structures or code to be executed are corrupt and there's a real >> problem going on, it's not just stalled and waiting. > > Thank you very much for this explanation: I didn't know this difference > and indeed I realized that I didn't know what a oops really is. I'm unfortunately not the person who can fix this issue. Anyway, it's good to confirm there is no actual real oops in your log. :) Hans
