Processed: found 985687 in 5.9.15-1, closing 985687
Processing commands for cont...@bugs.debian.org: > found 985687 5.9.15-1 Bug #985687 [src:linux] linux-image-5.9.0-0.bpo.5-armmp: Set CONFIG_CAN_J1939=m Marked as found in versions linux/5.9.15-1. > close 985687 5.10.19-1 Bug #985687 [src:linux] linux-image-5.9.0-0.bpo.5-armmp: Set CONFIG_CAN_J1939=m Marked as fixed in versions linux/5.10.19-1. Bug #985687 [src:linux] linux-image-5.9.0-0.bpo.5-armmp: Set CONFIG_CAN_J1939=m Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 985687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985687: linux-image-5.9.0-0.bpo.5-armmp: Set CONFIG_CAN_J1939=m
Package: src:linux Version: 5.9.15-1~bpo10+1 Severity: normal Dear Maintainer, Please consider setting kernel option "CONFIG_CAN_J1939=m" for at least buster-backports armmp. Without this setting the CAN J1939 protocol can not be easily used. Regards Andrew -- Package-specific info: ** Version: Linux version 5.9.0-0.bpo.5-armmp (debian-kernel@lists.debian.org) (gcc-8 (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP Debian 5.9.15-1~bpo10+1 (2020-12-31) ** Command line: vmalloc=400M root=/dev/mapper/avena-root ro rootfstype=ext4 rootwait consoleblank=0 no_console_suspend=5 console=tty1 console=ttymxc0,115200n8 mxc_hdmfbmem=32M ** Tainted: WE (8704) * kernel issued warning * unsigned module was loaded ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: Freescale i.MX6 Quad/DualLite (Device Tree) Revision: Device Tree model: Toradex Apalis iMX6Q/D Module on Ixora Carrier Board V1.1 ** Loaded modules: can_bcm(E) veth(E) xt_nat(E) xt_tcpudp(E) xt_conntrack(E) xt_MASQUERADE(E) nf_conntrack_netlink(E) xfrm_user(E) xfrm_algo(E) nft_counter(E) xt_addrtype(E) nft_compat(E) nft_chain_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) libcrc32c(E) nf_tables(E) nfnetlink(E) br_netfilter(E) bridge(E) stp(E) llc(E) wireguard(E) libchacha20poly1305(E) poly1305_arm(E) ip6_udp_tunnel(E) udp_tunnel(E) libblake2s(E) libblake2s_generic(E) libcurve25519_generic(E) libchacha(E) pps_ldisc(E) pps_core(E) rfkill(E) overlay(E) can_raw(E) can(E) joydev(E) dw_hdmi_ahb_audio(E) dw_hdmi_cec(E) sg(E) qmi_wwan(E) cdc_wdm(E) pl2303(E) option(E) usbnet(E) usb_wwan(E) mii(E) usbserial(E) stmpe_ts(E) snd_soc_sgtl5000(E) nvmem_imx_ocotp(E) snd_soc_imx_sgtl5000(E) snd_soc_imx_audmux(E) snd_soc_imx_spdif(E) imx_thermal(E) snd_soc_fsl_ssi(E) snd_soc_fsl_spdif(E) imx_pcm_fiq(E) imx_pcm_dma(E) imx2_wdt(E) snd_soc_core(E) snd_pcm_dmaengine(E) snd_pcm(E) snd_timer(E) snd(E) soundcore(E) flexcan(E) pwm_imx27(E) can_dev(E) dw_hdmi_imx(E) parallel_display(E) imx_ldb(E) imxdrm(E) dw_hdmi(E) etnaviv(E) imx_ipu_v3(E) gpu_sched(E) cec(E) drm_kms_helper(E) panel_simple(E) leds_gpio(E) drm(E) evdev(E) pwm_bl(E) imx6q_cpufreq(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) uas(E) usb_storage(E) dm_mod(E) sd_mod(E) t10_pi(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_common(E) pfuze100_regulator(E) ahci_imx(E) libahci_platform(E) libahci(E) libata(E) ci_hdrc_imx(E) phy_generic(E) ci_hdrc(E) ulpi(E) roles(E) scsi_mod(E) ehci_hcd(E) udc_core(E) sdhci_esdhc_imx(E) sdhci_pltfm(E) cqhci(E) usbcore(E) usbmisc_imx(E) sdhci(E) i2c_imx(E) anatop_regulator(E) phy_mxs_usb(E) micrel(E) ** PCI devices: 00:00.0 PCI bridge [0604]: Synopsys, Inc. DWC_usb3 [16c3:abcd] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport ** USB devices: Bus 002 Device 003: ID 1bc7:1201 Telit Wireless Solutions Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 5.9.0-0.bpo.5-armmp (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.9.0-0.bpo.5-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-5.9.0-0.bpo.5-armmp recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-5.9.0-0.bpo.5-armmp suggests: pn debian-kernel-handbook pn linux-doc-5.9 Versions of packages linux-image-5.9.0-0.bpo.5-armmp is related to: pn firmware-amd-graphics 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 pn firmware-linux-nonfree ii
Processed: Re: Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine
Processing control commands: > tags -1 - moreinfo Bug #985632 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine Removed tag(s) moreinfo. -- 985632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine
Control: tags -1 - moreinfo Hi Maximilian, thank you for your attention! > please provide info on the affected hardware, It is Raspberry Pi 4B 8GB model. > please show affected dmesg output working and non working, > the difference between 20210208-3 20210208-4 is minimal, > hence it should be easy to find out what broke? Not at all, unfortunately. 20210208-3 was completely broken on RPi4B as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984489 20210208-1 to 20210208-3 were broken... The last working version was 20201218-3, and I apt-mark-holded firmware-brcm80211. I unhold it in the weekend and found this issue. I attach dmesg of 20201218-3, 20210208-4, and 20210315-1. It was also interesting that installation of 20210315-1 causes boot failure and showed "Give root password for maintainance"... Should I file a separete report against 20210315-1? 20210315-1~exp1 was booted fine... Best regards, Ryutaroh dmesg.tar.xz Description: Binary data
Processed: found 857522 in 1:9.11.19+dfsg-2, reassign 985615 to src:linux, reassign 985612 to src:linux ...
Processing commands for cont...@bugs.debian.org:
> found 857522 1:9.11.19+dfsg-2
Bug #857522 [libbind-export-dev] libbind-export-dev: broken symlinks:
/usr/lib/x86_64-linux-gnu/liblwres-export.so ->
/lib/x86_64-linux-gnu/liblwres-export.so.141,
/usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10
Marked as found in versions bind9-libs/1:9.11.19+dfsg-2.
> reassign 985615 src:linux
Bug #985615 [kernel] Debian 10 Buster - kernel version 4.19.0-14-amd64
Warning: Unknown package 'kernel'
Bug reassigned from package 'kernel' to 'src:linux'.
No longer marked as found in versions 4.19.0-14-amd64.
Ignoring request to alter fixed versions of bug #985615 to the same values
previously set
> reassign 985612 src:linux
Bug #985612 {Done: "pham...@bluewin.ch" } [kernel] Debian
10 Buster - kernel version 4.19.0-14-amd64
Warning: Unknown package 'kernel'
Bug reassigned from package 'kernel' to 'src:linux'.
No longer marked as found in versions 4.19.0-14-amd64.
Ignoring request to alter fixed versions of bug #985612 to the same values
previously set
> fixed 985494 3.0.9
Bug #985494 [design-desktop] design-desktop: uninstallable in stretch due to
dependency on uninstallable xul-ext-sieve
Marked as fixed in versions debian-design/3.0.9.
> reassign 950788 src:procps
Bug #950788 {Done: Craig Small } [systemd]
/usr/share/man/man5/sysctl.d.5.gz: sysctl.d.5 man page has confusing directory
order
Bug reassigned from package 'systemd' to 'src:procps'.
No longer marked as found in versions systemd/244-3.
No longer marked as fixed in versions procps/2:3.3.17-1.
> fixed 950788 2:3.3.17-1
Bug #950788 {Done: Craig Small } [src:procps]
/usr/share/man/man5/sysctl.d.5.gz: sysctl.d.5 man page has confusing directory
order
Marked as fixed in versions procps/2:3.3.17-1.
> affects 950788 + src:systemd
Bug #950788 {Done: Craig Small } [src:procps]
/usr/share/man/man5/sysctl.d.5.gz: sysctl.d.5 man page has confusing directory
order
Added indication that 950788 affects src:systemd
> reassign 972525 src:gnupg2
Bug #972525 {Done: Daniel Kahn Gillmor } [src:sbuild]
buildd: sbuild randomly fails to sign changes file despite valid signature keys
Bug reassigned from package 'src:sbuild' to 'src:gnupg2'.
No longer marked as found in versions sbuild/0.80.0.
No longer marked as fixed in versions gnupg2/2.2.27-1.
> fixed 972525 2.2.27-1
Bug #972525 {Done: Daniel Kahn Gillmor } [src:gnupg2]
buildd: sbuild randomly fails to sign changes file despite valid signature keys
Marked as fixed in versions gnupg2/2.2.27-1.
> affects 972525 sbuild
Bug #972525 {Done: Daniel Kahn Gillmor } [src:gnupg2]
buildd: sbuild randomly fails to sign changes file despite valid signature keys
Added indication that 972525 affects sbuild
> notfixed 818688 1
Bug #818688 {Done: Eduard Bloch } [apt-cacher-ng] [apt-cacher-ng]
Fails to parse metadata from experimental
There is no source info for the package 'apt-cacher-ng' at version '1' with
architecture ''
Unable to make a source version for version '1'
No longer marked as fixed in versions 1.
> fixed 818688 1-1
Bug #818688 {Done: Eduard Bloch } [apt-cacher-ng] [apt-cacher-ng]
Fails to parse metadata from experimental
Marked as fixed in versions apt-cacher-ng/1-1.
> notfixed 619242 1:2.4.2-1
Bug #619242 {Done: "Francesco P. Lovergine" } [imapfilter]
imapfilter creates 8-bit mailbox names
There is no source info for the package 'imapfilter' at version '1:2.4.2-1'
with architecture ''
Unable to make a source version for version '1:2.4.2-1'
No longer marked as fixed in versions 1:2.4.2-1.
> fixed 619242 1:2.5.2-1
Bug #619242 {Done: "Francesco P. Lovergine" } [imapfilter]
imapfilter creates 8-bit mailbox names
Marked as fixed in versions imapfilter/1:2.5.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
619242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619242
818688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818688
857522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857522
950788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950788
972525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972525
985494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985494
985612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985612
985615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#985684: arm64: please enable CONFIG_ARCH_MXC for mx8 boards
Source: linux Severity: wishlist Dear Maintainer, Please enable CONFIG_ARCH_MXC and related configs for i.mx8 boards. In mainline's defconfig, CONFIG_ARCH_MXC is enabled by default. Thus the mainline kernel supports mx8 boards by default. But it seems that Debian kernel doesn't enable it. So please consider support mx8 boards. Yours, Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#985681: linux-cpupower: Fix Pkg Power tracking on Zen
Package: linux-cpupower
Version: 5.10.24-1
Severity: normal
Tags: patch
turbostat no longer works with at least some Zen-based systems, it exits
early with code 243.
A trivial fix has been proposed that reportedly works at least for Zen 2
and 3.
I myself have successfully tested it with Zen 2.
The patch has not yet been included upstream (there has been no reply to
it in quite a while), but since it's so trivial, perhaps it could be
included in our package, so that we may get back power statistics for
Zen CPUs.
(This may or may not warrant a higher severity. If Zen 2 belongs to the
officially supported platforms, that it should probably be more severe.)
Author: Kurt Garloff
Date: Sat Dec 26 13:00:15 2020 +0100
turbostat: Fix Pkg Power tracking on Zen
AMD Zen processors use a different MSR (MSR_PKG_ENERGY_STAT) than intel
(MSR_PKG_ENERGY_STATUS) to track package power; however we want to record
it at the same offset in our package_data.
offset_to_idx() however only recognized the intel MSR, erroring
out with -13 on Zen.
With this fix, it will support the Zen MSR.
Tested successfully on Ryzen 3000.
Signed-off-by: Kurt Garloff
Origin: https://lore.kernel.org/lkml/f6143d7a-079d-3f3c-c947-47fc9858a...@debian.org/T/#t
diff --git a/tools/power/x86/turbostat/turbostat.c b/tools/power/x86/turbostat/turbostat.c
index f3a1746f7f45..eb845421f492 100644
--- a/tools/power/x86/turbostat/turbostat.c
+++ b/tools/power/x86/turbostat/turbostat.c
@@ -325,6 +325,7 @@ int offset_to_idx(int offset)
int idx;
switch (offset) {
+ case MSR_PKG_ENERGY_STAT:
case MSR_PKG_ENERGY_STATUS:
idx = IDX_PKG_ENERGY;
break;
Processed: Re: Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine
Processing commands for cont...@bugs.debian.org: > severity 985632 important Bug #985632 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine Severity set to 'important' from 'grave' > tags 985632 moreinfo Bug #985632 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine Added tag(s) moreinfo. > stop Stopping processing here. Please contact me if you need assistance. -- 985632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine
severity 985632 important tags 985632 moreinfo stop On Sun, Mar 21, 2021 at 09:59:45AM +0900, Ryutaroh Matsumoto wrote: > Package: firmware-brcm80211 > Version: 20210208-4 > Severity: grave > Tags: sid bullseye > Justification: renders package unusable please provide info on the affected hardware, also using apropriate bug levels would be nice. > 5GHz WiFi stopped working with 20210208-4. > iw wlan0 scan does not show SSID of 5GHz WiFi. > With 20201218-3, 5GHz worked fine, > provided that vc4.ko is blacklisted (see #981616). please show affected dmesg output working and non working, the difference between 20210208-3 20210208-4 is minimal, hence it should be easy to find out what broke? thank you for your report + kind regards, signature.asc Description: PGP signature
