Bug#1016827: (linux-image-amd64: __dma_async_device_channel_unregister called while 2 clients hold a reference)

2022-08-07 Thread ng

Forgot to attach dmesg
[0.00] Linux version 5.10.0-16-amd64 (debian-kernel@lists.debian.org) 
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 
2.35.2) #1 SMP Debian 5.10.127-2 (2022-07-23)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.10.0-16-amd64 
root=UUID=e2621cc7-952f-4003-a3eb-60c1d6b188cd ro acpi_osi=Linux 
ccp.dmaengine=0 drm.edid_firmware=HDMI-A-1:edid/edid.bin quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x09bf] usable
[0.00] BIOS-e820: [mem 0x09c0-0x09d80fff] reserved
[0.00] BIOS-e820: [mem 0x09d81000-0x09ef] usable
[0.00] BIOS-e820: [mem 0x09f0-0x09f0afff] ACPI NVS
[0.00] BIOS-e820: [mem 0x09f0b000-0xb8d8dfff] usable
[0.00] BIOS-e820: [mem 0xb8d8e000-0xbbd7dfff] reserved
[0.00] BIOS-e820: [mem 0xbbd7e000-0xbdd7dfff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbdd7e000-0xbddfdfff] ACPI data
[0.00] BIOS-e820: [mem 0xbddfe000-0xbeff] usable
[0.00] BIOS-e820: [mem 0xbf00-0xbfff] reserved
[0.00] BIOS-e820: [mem 0xfd20-0xfd2f] reserved
[0.00] BIOS-e820: [mem 0xfed8-0xfed80fff] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0002beff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] e820: update [mem 0xb3ff1018-0xb3fff057] usable ==> usable
[0.00] e820: update [mem 0xb3ff1018-0xb3fff057] usable ==> usable
[0.00] e820: update [mem 0xb3fe3018-0xb3ff0457] usable ==> usable
[0.00] e820: update [mem 0xb3fe3018-0xb3ff0457] usable ==> usable
[0.00] extended physical RAM map:
[0.00] reserve setup_data: [mem 0x-0x0009efff] 
usable
[0.00] reserve setup_data: [mem 0x0009f000-0x0009] 
reserved
[0.00] reserve setup_data: [mem 0x000e-0x000f] 
reserved
[0.00] reserve setup_data: [mem 0x0010-0x09bf] 
usable
[0.00] reserve setup_data: [mem 0x09c0-0x09d80fff] 
reserved
[0.00] reserve setup_data: [mem 0x09d81000-0x09ef] 
usable
[0.00] reserve setup_data: [mem 0x09f0-0x09f0afff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x09f0b000-0xb3fe3017] 
usable
[0.00] reserve setup_data: [mem 0xb3fe3018-0xb3ff0457] 
usable
[0.00] reserve setup_data: [mem 0xb3ff0458-0xb3ff1017] 
usable
[0.00] reserve setup_data: [mem 0xb3ff1018-0xb3fff057] 
usable
[0.00] reserve setup_data: [mem 0xb3fff058-0xb8d8dfff] 
usable
[0.00] reserve setup_data: [mem 0xb8d8e000-0xbbd7dfff] 
reserved
[0.00] reserve setup_data: [mem 0xbbd7e000-0xbdd7dfff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0xbdd7e000-0xbddfdfff] 
ACPI data
[0.00] reserve setup_data: [mem 0xbddfe000-0xbeff] 
usable
[0.00] reserve setup_data: [mem 0xbf00-0xbfff] 
reserved
[0.00] reserve setup_data: [mem 0xfd20-0xfd2f] 
reserved
[0.00] reserve setup_data: [mem 0xfed8-0xfed80fff] 
reserved
[0.00] reserve setup_data: [mem 0x0001-0x0002beff] 
usable
[0.00] efi: EFI v2.70 by Lenovo
[0.00] efi: ACPI=0xbddfd000 ACPI 2.0=0xbddfd014 TPMFinalLog=0xbdc2d000 
SMBIOS=0xba72c000 SMBIOS 3.0=0xba71f000 MEMATTR=0xb6a92018 ESRT=0xb92c9000 
MOKvar=0xb6a83000 RNG=0xba839598 TPMEventLog=0xb418 
[0.00] efi: seeding entropy pool
[0.00] random: crng init done
[0.00] Kernel is locked down from EFI Secure Boot; see man 
kernel_lockdown.7
[0.00] secureboot: Secure boot enabled
[0.00] SMBIOS 3.1.1 present.
[0.00] DMI: LENOVO 20NECTO1WW/20NECTO1WW, BIOS R11ET45P (1.25 ) 
07/04/2022
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 2096.078 MHz processor
[0.15] e820: 

Bug#1016807: linux-image-5.18.0-3-arm64: Please enable CONFIG_SPI_GPIO, CONFIG_SPI_SUN6I for arm64 (Allwinner A64)

2022-08-07 Thread Jonathan Hettwer (bauen1)
Source: linux
Severity: wishlist
X-Debbugs-Cc: j24...@gmail.com

Dear Linux Maintainers,

I have a pine a64-lts SBC running arm64 debian unstable.
A SPI NOR flash and a TPM2.0 are connected over SPI, but the
kernel is currently build without the modules required to access them.

To access both, I need the CONFIG_SPI_SUN6I as module for the builtin
SPI bus, and CONFIG_SPI_GPIO for accessing the TPM connected over a
non-standard SPI bus.

Thanks in advance.

-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: bauen1-policy



Bug#1016782: linux-image-5.18.0-3-amd64: no output on consoles tty2-tty6 when using systemd's graphical target

2022-08-07 Thread Peter Marschall
Package: src:linux
Version: 5.18.14-1
Severity: important

Hi,

with the upgrade to 5.18.14-1 no output is shown on consoles tty2 - tty4 [in my 
case] in systemd's graphical target

Systemd creates the getty.slice and starts the getty@service for tty2 - tty4
   │ ├─system-getty.slice
   │ │ ├─getty@tty2.service
   │ │ │ └─7311 /sbin/agetty -o "-p -- \\u" --noclear - linux
   │ │ ├─getty@tty3.service
   │ │ │ └─7117 /sbin/agetty -o "-p -- \\u" --noclear - linux
   │ │ └─getty@tty4.service
   │ │   └─6680 /sbin/agetty -o "-p -- \\u" --noclear - linux

Blingdly logging wuithout visual feedback also seems to be possible:

journalctl excerpt:
Aug 07 14:05:28 moth login[7112]: pam_unix(login:session): session 
opened for user peter(uid=1000) by LOGIN(uid=0)
Aug 07 14:05:28 moth systemd-logind[919]: New session 18 of user peter.
Aug 07 14:05:28 moth systemd[1]: Started Session 18 of User peter.

systemctl status excerpts
   │ ├─system-getty.slice
   │ │ ├─getty@tty3.service
   │ │ │ └─7117 /sbin/agetty -o "-p -- \\u" --noclear - linux
   │ │ └─getty@tty4.service
   │ │   └─6680 /sbin/agetty -o "-p -- \\u" --noclear - linux

 └─user-1000.slice
   ├─session-18.scope
   │ ├─7112 /bin/login -p --
   │ └─7142 -bash

After blindly logging out of tty2, systemctl status shows again all 
getty@sessions


The issue appears on two separate installations on the same HW.
Rebooting with an earlier version of the kernel makes the issue disappear in 
both installations.
(tested with kernekl 5.18.5-1 from linux-image-5.18.0-3-amd64)




-- Package-specific info:
** Version:
Linux version 5.18.0-3-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP 
PREEMPT_DYNAMIC Debian 5.18.14-1 (2022-07-23)

** Command line:
BOOT_IMAGE=/vmlinuz-5.18.0-3-amd64 
root=UUID=edb11cba-524f-4c12-b334-be64713e04c0 ro noapic consoleblank=600 quiet 
apparmor=1 security=apparmor

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: EXTRA Computer GmbH
product_name: exone Business S 1301
product_version: Default string
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: F3 EP
board_vendor: Gigabyte Technology Co., Ltd.
board_name: A520M DS3H
board_version: x.x

** Loaded modules:
ses
enclosure
scsi_transport_sas
snd_seq_dummy
snd_hrtimer
snd_seq
xt_MASQUERADE
xt_CHECKSUM
ip6t_REJECT
nf_reject_ipv6
ipt_REJECT
nf_reject_ipv4
nft_compat
nft_chain_nat
nf_nat
nf_tables
nfnetlink
bridge
stp
llc
cpufreq_powersave
cpufreq_conservative
cpufreq_userspace
cpufreq_ondemand
nvme_fabrics
cfg80211
rfkill
qrtr
binfmt_misc
pktcdvd
intel_rapl_msr
intel_rapl_common
snd_hda_codec_realtek
snd_hda_codec_generic
edac_mce_amd
ledtrig_audio
uvcvideo
snd_hda_codec_hdmi
videobuf2_vmalloc
snd_usb_audio
videobuf2_memops
videobuf2_v4l2
snd_hda_intel
videobuf2_common
snd_intel_dspcfg
kvm_amd
snd_usbmidi_lib
snd_intel_sdw_acpi
videodev
snd_rawmidi
snd_hda_codec
snd_seq_device
kvm
snd_hda_core
r8188eu(C)
mc
snd_hwdep
irqbypass
ftdi_sio
snd_pcm
xt_LOG
usbserial
libarc4
nf_log_syslog
rapl
snd_timer
ip6table_filter
ccp
ip6_tables
snd
wmi_bmof
rng_core
soundcore
pcspkr
sp5100_tco
xt_limit
watchdog
k10temp
sg
evdev
acpi_cpufreq
xt_tcpudp
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
libcrc32c
iptable_filter
nfsd
nfs_acl
lockd
auth_rpcgss
loop
grace
msr
ecryptfs
sunrpc
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
hid_generic
usbhid
hid
amdgpu
gpu_sched
crc32_pclmul
uas
i2c_algo_bit
crc32c_intel
drm_dp_helper
usb_storage
sr_mod
sd_mod
cec
cdrom
rc_core
drm_ttm_helper
ghash_clmulni_intel
ahci
xhci_pci
ttm
nvme
r8169
libahci
xhci_hcd
drm_kms_helper
aesni_intel
libata
drm
realtek
nvme_core
crypto_simd
mdio_devres
cryptd
t10_pi
usbcore
scsi_mod
libphy
crc64_rocksoft_generic
crc64_rocksoft
crc_t10dif
crct10dif_generic
i2c_piix4
crct10dif_pclmul
crc64
crct10dif_common
scsi_common
usb_common
wmi
video
gpio_amdpt
gpio_generic
button

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root 
Complex [1022:1630]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

Bug#1016780: linux-image-5.18.0-3-amd64: repatedly disconnects & reconnects USB drive Sandisk Extreme SSD

2022-08-07 Thread Peter Marschall
Package: src:linux
Version: 5.18.14-1
Severity: important


With the upgrade to Linux 5.18.14-1, the kernel continues to disconnect & 
reconnect my USB drive Sandisk Extreme SSD within a few seconds.
This behaviour makes using the drive impossible.
When trying to use it nevertheless, it may damage the filee-system, potentially 
risking data los..

This behaviour appear on 2 separate installations running on the same hardware,
and when rebooting the instances with an earlier kernel (tested with 5.18.5-1 
from linux-image-5.18.0-2-amd64 on boith installations),
the issue disappears and the USB disk works absolutely flawlessly.


Journalctl reports the followign messages for the first connections and the 
consecutive de- & re-connections

Aug 07 13:24:04 moth kernel: usb 2-1: new SuperSpeed USB device number 2 using 
xhci_hcd
Aug 07 13:24:04 moth kernel: usb 2-1: New USB device found, idVendor=0781, 
idProduct=558c, bcdDevice=10.12
Aug 07 13:24:04 moth kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
Aug 07 13:24:04 moth kernel: usb 2-1: Product: Extreme SSD
Aug 07 13:24:04 moth kernel: usb 2-1: Manufacturer: SanDisk
Aug 07 13:24:04 moth kernel: usb 2-1: SerialNumber: 323030323744343030313238
Aug 07 13:24:04 moth kernel: scsi host7: uas
Aug 07 13:24:04 moth kernel: scsi 7:0:0:0: Direct-Access SanDisk  Extreme 
SSD  1012 PQ: 0 ANSI: 6
Aug 07 13:24:04 moth kernel: scsi 7:0:0:1: Enclosure SanDisk  SES 
Device   1012 PQ: 0 ANSI: 6
Aug 07 13:24:04 moth kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0
Aug 07 13:24:04 moth kernel: scsi 7:0:0:1: Attached scsi generic sg5 type 13
Aug 07 13:24:04 moth kernel: sd 7:0:0:0: [sdd] Spinning up disk...
Aug 07 13:24:06 moth kernel: ..ready
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] 976773120 512-byte logical 
blocks: (500 GB/466 GiB)
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] 4096-byte physical blocks
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Write Protect is off
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Mode Sense: 67 00 10 08
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Write cache: disabled, read 
cache: enabled, supports DPO and FUA
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Optimal transfer size 33553920 
bytes not a multiple of physical block size (4096 bytes)
Aug 07 13:24:06 moth kernel:  sdd: sdd1
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Write cache: enabled, read 
cache: enabled, supports DPO and FUA
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Attached SCSI disk
Aug 07 13:24:06 moth kernel: scsi 7:0:0:1: Wrong diagnostic page; asked for 1 
got 8
Aug 07 13:24:06 moth kernel: scsi 7:0:0:1: Failed to get diagnostic page 0x1
Aug 07 13:24:06 moth kernel: scsi 7:0:0:1: Failed to bind enclosure -19
Aug 07 13:24:06 moth kernel: ses 7:0:0:1: Attached Enclosure device
Aug 07 13:24:16 moth kernel: EXT4-fs (sdd1): mounted filesystem with ordered 
data mode. Quota mode: none.
Aug 07 13:24:52 moth kernel: usb 2-1: USB disconnect, device number 2
Aug 07 13:24:52 moth kernel: device offline error, dev sdd, sector 0 op 
0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Aug 07 13:24:52 moth kernel: Buffer I/O error on dev sdd1, logical block 
60850176, lost sync page write
Aug 07 13:24:52 moth kernel: JBD2: Error -5 detected when updating journal 
superblock for sdd1-8.
Aug 07 13:24:52 moth kernel: Aborting journal on device sdd1-8.
Aug 07 13:24:52 moth kernel: Buffer I/O error on dev sdd1, logical block 
60850176, lost sync page write
Aug 07 13:24:52 moth kernel: JBD2: Error -5 detected when updating journal 
superblock for sdd1-8.
Aug 07 13:24:52 moth kernel: EXT4-fs error (device sdd1): ext4_put_super:1226: 
comm umount: Couldn't clean up the journal
Aug 07 13:24:52 moth kernel: EXT4-fs (sdd1): Remounting filesystem read-only
Aug 07 13:24:52 moth kernel: sd 7:0:0:0: [sdd] Synchronizing SCSI cache
Aug 07 13:24:52 moth kernel: sd 7:0:0:0: [sdd] Synchronize Cache(10) failed: 
Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Aug 07 13:24:52 moth kernel: usb 2-1: new SuperSpeed USB device number 3 using 
xhci_hcd
Aug 07 13:24:52 moth kernel: usb 2-1: New USB device found, idVendor=0781, 
idProduct=558c, bcdDevice=10.12
Aug 07 13:24:52 moth kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
Aug 07 13:24:52 moth kernel: usb 2-1: Product: Extreme SSD
Aug 07 13:24:52 moth kernel: usb 2-1: Manufacturer: SanDisk
Aug 07 13:24:52 moth kernel: usb 2-1: SerialNumber: 323030323744343030313238
Aug 07 13:24:52 moth kernel: scsi host7: uas
Aug 07 13:24:52 moth kernel: scsi 7:0:0:0: Direct-Access SanDisk  Extreme 
SSD  1012 PQ: 0 ANSI: 6
Aug 07 13:24:52 moth kernel: scsi 7:0:0:1: Enclosure SanDisk  SES 
Device   1012 PQ: 0 ANSI: 6
Aug 07 13:24:52 moth kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0
Aug 07 13:24:52 moth kernel: ses 7:0:0:1: Attached Enclosure device
Aug 07 13:24:52 moth kernel: ses 7:0:0:1: Attached scsi generic sg5 type 13
Aug 07 13:24:52 moth kernel: ses 

Bug#1016776: channel 13 broken on b43 (brcmsmac) driver since wireless-regdb-2022.04.08-2~deb11u1

2022-08-07 Thread kolafl...@kolahilft.de


Package: wireless-regdb
Version: 2022.04.08-2~deb11u1

Since version 2022.04.08-2~deb11u1 of wireless-regdb my Lenovo notebook 
doesn't show up channel 13 wireless networks.


Downgrading to version wireless-regdb-2020.04.29-2 fixes the problem.
https://snapshot.debian.org/archive/debian/20200630T204925Z/pool/main/w/wireless-regdb/wireless-regdb_2020.04.29-2_all.deb


OS: Debian-11 (KDE with NetworkManager)
Notebook: Lenovo G560 (Model: 0679)
CPU: Intel(R) Core(TM) i3 CPU   M 350  @ 2.27GHz


NIC:

06:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 
802.11bgn Wireless Network Adapter (rev 01)


product: BCM4313 802.11bgn Wireless Network Adapter

configuration: broadcast=yes driver=brcmsmac 
driverversion=5.10.0-16-amd64 firmware=610.812 ip=192.168.37.15 
latency=0 link=yes multicast=yes wireless=IEEE 802.11



I have no experience with the wireless stack.
But please feel free to tell me what to test or which logs to send.

Maybe related:
  wireless-regdb stable policy
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006127






I'm not sure how this is caused. I guess maybe it's an error in the 
regdb, maybe the b43 driver is interpreting the regdb wrongly.
I got another notebook (HP) with RTL8822BE wireless which is still 
connecting to channel 13 networks with wireless-regdb-2022.04.08-2~deb11u1.



I've tried
  rmmod b43; modprobe b43 allhwsupport=1
but that didn't help.

I picked some interesting dmesg lines. But they also show up when 
rebooting after downgrading to wireless-regdb-2020.04.29-2



 789 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.466425] cfg80211: Loading 
compiled-in X.509 certificates for regulatory database
 790 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.466920] cfg80211: Loaded 
X.509 cert 'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
 791 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.467404] cfg80211: Loaded 
X.509 cert 'romain.per...@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
 792 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.467890] cfg80211: Loaded 
X.509 cert 'sforshee: 00b28ddf47aef9cea7'
 793 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.740967] platform 
regulatory.0: firmware: direct-loading firmware regulatory.db
 794 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.763353] platform 
regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
 795 Aug  7 08:45:41 AnnaMargaretePC kernel: [   24.706741] Support for cores 
revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try 
b43.allhwsupport=1
 796 Aug  7 08:45:41 AnnaMargaretePC kernel: [   24.706756] b43: probe of 
bcma0:1 failed with error -524
 797 Aug  7 08:45:41 AnnaMargaretePC kernel: [   24.706811] Broadcom 43xx 
driver loaded [ Features: PNLS ]

[...]

 804 Aug  7 08:45:41 AnnaMargaretePC kernel: [   25.350732] brcmsmac bcma0:1: 
mfg 4bf core 812 rev 24 class 0 irq 17
 805 Aug  7 08:45:41 AnnaMargaretePC kernel: [   25.351802] ieee80211 phy0: 
Selected rate control algorithm 'minstrel_ht'





rmmod b43; rmmod brcmsmac; rmmod mac80211; rmmod cfg80211; iw reg get; 
iw reg set DE; iw reg get; modprobe -v cfg80211 ieee80211_regdom=DE; iw 
reg get; modprobe -v mac80211; iw reg get; iw reg get; modprobe -v 
brcmsmac; iw reg get; modprobe -v b43; iw reg get



global
country 00: DFS-UNSET
(755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)

global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

insmod /lib/modules/5.10.0-16-amd64/kernel/net/mac80211/mac80211.ko 
global

country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW