Bug#990296: linux-image-5.10.0-7-amd64: Bluetooth device not detected by kernel.
Package: src:linux
Version: 5.10.40-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- Package-specific info:
** Version:
Linux version 5.10.0-7-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.40-1 (2021-05-28)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64
root=UUID=fe679841-421e-40a5-8476-2e0c6454f9cc ro quiet
** Tainted: OE (12288)
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 0707
board_vendor: ASUSTeK COMPUTER INC.
board_name: ROG MAXIMUS XIII HERO
board_version: Rev 1.xx
** Loaded modules:
md4
sha512_ssse3
sha512_generic
vmnet(OE)
cmac
nls_utf8
vmw_vsock_vmci_transport
vsock
cifs
vmw_vmci
vmmon(OE)
dns_resolver
fscache
libdes
intel_rapl_msr
intel_rapl_common
bnep
mei_hdcp
binfmt_misc
btusb
btrtl
btbcm
btintel
bluetooth
iwlmvm
snd_sof_pci
snd_sof_intel_byt
snd_sof_intel_ipc
snd_sof_intel_hda_common
jitterentropy_rng
snd_sof_xtensa_dsp
x86_pkg_temp_thermal
snd_sof
intel_powerclamp
drbg
snd_sof_intel_hda
coretemp
snd_soc_hdac_hda
snd_hda_codec_hdmi
mac80211
snd_hda_ext_core
nls_ascii
snd_soc_acpi_intel_match
nls_cp437
snd_soc_acpi
ledtrig_audio
kvm_intel
vfat
fat
libarc4
kvm
snd_hda_intel
snd_intel_dspcfg
soundwire_intel
soundwire_generic_allocation
snd_soc_core
snd_compress
soundwire_cadence
irqbypass
iwlwifi
snd_usb_audio
snd_hda_codec
aes_generic
ghash_clmulni_intel
asus_nb_wmi
eeepc_wmi
snd_hda_core
asus_wmi
snd_usbmidi_lib
battery
cfg80211
aesni_intel
efi_pstore
pcspkr
snd_rawmidi
sparse_keymap
wmi_bmof
snd_hwdep
snd_seq_device
iTCO_wdt
soundwire_bus
intel_pmc_bxt
mc
iTCO_vendor_support
crypto_simd
ee1004
watchdog
cryptd
snd_pcm
glue_helper
ansi_cprng
snd_timer
joydev
snd
ecdh_generic
rfkill
mei_me
ecc
soundcore
libaes
mei
sg
intel_pmc_core
evdev
acpi_tad
acpi_pad
msr
parport_pc
ppdev
lp
parport
fuse
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
hid_generic
usbhid
hid
sr_mod
cdrom
sd_mod
nouveau
i2c_algo_bit
ttm
drm_kms_helper
cec
xhci_pci
ahci
drm
libahci
xhci_hcd
libata
thunderbolt
nvme
usbcore
crc32_pclmul
nvme_core
igc
scsi_mod
crc32c_intel
i2c_i801
mxm_wmi
i2c_smbus
t10_pi
ptp
crc_t10dif
intel_lpss_pci
pps_core
crct10dif_generic
intel_lpss
crct10dif_pclmul
idma64
usb_common
crct10dif_common
fan
video
wmi
button
** Network interface configuration:
*** /etc/network/interfaces:
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
** Network status:
*** IP interfaces and addresses:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether f0:2f:74:d4:3d:b9 brd ff:ff:ff:ff:ff:ff
inet 192.168.5.114/24 brd 192.168.5.255 scope global dynamic noprefixroute
enp4s0
valid_lft 367sec preferred_lft 367sec
inet6 fe80::f22f:74ff:fed4:3db9/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp7s0: mtu 1500 qdisc mq state DOWN
group default qlen 1000
link/ether f0:2f:74:d4:3d:ba brd ff:ff:ff:ff:ff:ff
4: wlp5s0: mtu 1500 qdisc noqueue state
DOWN group default qlen 1000
link/ether 3a:46:69:c7:fa:00 brd ff:ff:ff:ff:ff:ff permaddr
14:18:c3:40:32:8d
5: vmnet1: mtu 1500 qdisc pfifo_fast state
UNKNOWN group default qlen 1000
link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.210.1/24 brd 192.168.210.255 scope global vmnet1
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fec0:1/64 scope link
valid_lft forever preferred_lft forever
6: vmnet8: mtu 1500 qdisc pfifo_fast state
UNKNOWN group default qlen 1000
link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
inet 172.16.84.1/24 brd 172.16.84.255 scope global vmnet8
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fec0:8/64 scope link
valid_lft forever preferred_lft forever
*** Device statistics:
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
linux-signed-amd64_5.10.46+1_source.changes is NEW
Mapping sid to unstable. binary:acpi-modules-5.10.0-8-amd64-di is NEW. binary:ata-modules-5.10.0-8-amd64-di is NEW. binary:btrfs-modules-5.10.0-8-amd64-di is NEW. binary:cdrom-core-modules-5.10.0-8-amd64-di is NEW. binary:crc-modules-5.10.0-8-amd64-di is NEW. binary:crypto-dm-modules-5.10.0-8-amd64-di is NEW. binary:crypto-modules-5.10.0-8-amd64-di is NEW. binary:efi-modules-5.10.0-8-amd64-di is NEW. binary:event-modules-5.10.0-8-amd64-di is NEW. binary:ext4-modules-5.10.0-8-amd64-di is NEW. binary:f2fs-modules-5.10.0-8-amd64-di is NEW. binary:fat-modules-5.10.0-8-amd64-di is NEW. binary:fb-modules-5.10.0-8-amd64-di is NEW. binary:firewire-core-modules-5.10.0-8-amd64-di is NEW. binary:fuse-modules-5.10.0-8-amd64-di is NEW. binary:i2c-modules-5.10.0-8-amd64-di is NEW. binary:input-modules-5.10.0-8-amd64-di is NEW. binary:isofs-modules-5.10.0-8-amd64-di is NEW. binary:jfs-modules-5.10.0-8-amd64-di is NEW. binary:kernel-image-5.10.0-8-amd64-di is NEW. binary:linux-image-5.10.0-8-amd64 is NEW. binary:linux-image-5.10.0-8-cloud-amd64 is NEW. binary:linux-image-5.10.0-8-rt-amd64 is NEW. binary:loop-modules-5.10.0-8-amd64-di is NEW. binary:md-modules-5.10.0-8-amd64-di is NEW. binary:mmc-core-modules-5.10.0-8-amd64-di is NEW. binary:mmc-modules-5.10.0-8-amd64-di is NEW. binary:mouse-modules-5.10.0-8-amd64-di is NEW. binary:mtd-core-modules-5.10.0-8-amd64-di is NEW. binary:multipath-modules-5.10.0-8-amd64-di is NEW. binary:nbd-modules-5.10.0-8-amd64-di is NEW. binary:nic-modules-5.10.0-8-amd64-di is NEW. binary:nic-pcmcia-modules-5.10.0-8-amd64-di is NEW. binary:nic-shared-modules-5.10.0-8-amd64-di is NEW. binary:nic-usb-modules-5.10.0-8-amd64-di is NEW. binary:nic-wireless-modules-5.10.0-8-amd64-di is NEW. binary:pata-modules-5.10.0-8-amd64-di is NEW. binary:pcmcia-modules-5.10.0-8-amd64-di is NEW. binary:pcmcia-storage-modules-5.10.0-8-amd64-di is NEW. binary:ppp-modules-5.10.0-8-amd64-di is NEW. binary:rfkill-modules-5.10.0-8-amd64-di is NEW. binary:sata-modules-5.10.0-8-amd64-di is NEW. binary:scsi-core-modules-5.10.0-8-amd64-di is NEW. binary:scsi-modules-5.10.0-8-amd64-di is NEW. binary:scsi-nic-modules-5.10.0-8-amd64-di is NEW. binary:serial-modules-5.10.0-8-amd64-di is NEW. binary:sound-modules-5.10.0-8-amd64-di is NEW. binary:speakup-modules-5.10.0-8-amd64-di is NEW. binary:squashfs-modules-5.10.0-8-amd64-di is NEW. binary:udf-modules-5.10.0-8-amd64-di is NEW. binary:uinput-modules-5.10.0-8-amd64-di is NEW. binary:usb-modules-5.10.0-8-amd64-di is NEW. binary:usb-serial-modules-5.10.0-8-amd64-di is NEW. binary:usb-storage-modules-5.10.0-8-amd64-di is NEW. binary:xfs-modules-5.10.0-8-amd64-di is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Processing of linux-signed-amd64_5.10.46+1_source.changes
linux-signed-amd64_5.10.46+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.10.46+1.dsc linux-signed-amd64_5.10.46+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#990286: linux-image-5.10.0-7-amd64: Lid open/close events detected but not always forwarded
Package: src:linux Version: 5.10.40-1 Severity: important X-Debbugs-Cc: tra...@wrightsman.org Dear Maintainer, My laptop rarely suspends when the lid is closed. The kernel always seems to detect the lid open and close events but doesn't always forward them to the event devices. Checking /proc/acpi/button/lid/LID0/state in a loop while opening and closing the lid always shows the state correctly changing between "open" and "closed". $ ./test_lid.sh 2021-06-24T11:42:00-04:00 state: open 2021-06-24T11:42:01-04:00 state: open 2021-06-24T11:42:02-04:00 state: open 2021-06-24T11:42:03-04:00 state: closed 2021-06-24T11:42:04-04:00 state: closed 2021-06-24T11:42:05-04:00 state: closed 2021-06-24T11:42:06-04:00 state: closed 2021-06-24T11:42:07-04:00 state: open 2021-06-24T11:42:08-04:00 state: open evtest reports the following on a rare successful suspend. $ sudo evtest /dev/input/event7 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x5 version 0x0 Input device name: "Lid Switch" Supported events: Event type 0 (EV_SYN) Event type 5 (EV_SW) Event code 0 (SW_LID) state 0 Properties: Testing ... (interrupt to exit) Event: time 1624548763.334619, type 5 (EV_SW), code 0 (SW_LID), value 1 Event: time 1624548763.334619, -- SYN_REPORT Event: time 1624548776.442945, type 5 (EV_SW), code 0 (SW_LID), value 0 Event: time 1624548776.442945, -- SYN_REPORT systemd-logind did record this event: Jun 03 18:01:37 strider systemd-logind[676]: Lid closed. Below is what I normally see while listening with libinput and opening/closing the lid. $ sudo libinput debug-events --device /dev/input/event7 -event7 DEVICE_ADDED Lid Switchseat0 default group1 cap:S -- Package-specific info: ** Version: Linux version 5.10.0-7-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.40-1 (2021-05-28) ** Command line: root=[redacted] ro quiet intel_iommu=on ** Tainted: I (2048) * workaround for bug in platform firmware applied ** Model information sys_vendor: Purism product_name: librem_14 product_version: 1.0 chassis_vendor: Purism chassis_version: bios_vendor: coreboot bios_version: PureBoot-Release-17.1 board_vendor: Purism board_name: librem_14 board_version: 1.0 ** Loaded modules: overlay ctr ccm bnep ath9k ath9k_common ath9k_hw ath mac80211 wireguard libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 nf_log_ipv4 nf_log_common ipt_REJECT curve25519_x86_64 nf_reject_ipv4 libcurve25519_generic libchacha snd_hda_codec_hdmi xt_LOG libblake2s_generic ath3k btusb btrtl btbcm btintel bluetooth snd_sof_pci x86_pkg_temp_thermal snd_sof_intel_byt intel_powerclamp snd_sof_intel_ipc nft_limit coretemp snd_hda_codec_realtek snd_sof_intel_hda_common cfg80211 snd_hda_codec_generic snd_sof_xtensa_dsp jitterentropy_rng snd_sof snd_sof_intel_hda drbg snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match ansi_cprng snd_soc_acpi kvm_intel ledtrig_audio snd_hda_intel snd_intel_dspcfg soundwire_intel joydev xt_limit soundwire_generic_allocation ecdh_generic snd_soc_core xt_addrtype kvm snd_compress soundwire_cadence xt_tcpudp snd_hda_codec intel_rapl_msr binfmt_misc irqbypass xt_conntrack snd_hda_core nf_conntrack snd_hwdep soundwire_bus rapl nf_defrag_ipv6 nf_defrag_ipv4 intel_cstate snd_pcm nft_compat sg snd_timer ecc intel_uncore snd nft_counter soundcore processor_thermal_device iTCO_wdt rfkill intel_rapl_common tpm_tis intel_pmc_bxt hid_multitouch iTCO_vendor_support int340x_thermal_zone serio_raw libarc4 watchdog intel_soc_dts_iosf pcspkr tpm_tis_core intel_pch_thermal ee1004 tpm rng_core evdev intel_hid intel_pmc_core sparse_keymap button ac nf_tables parport_pc libcrc32c nfnetlink ppdev lp parport fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common xts algif_skcipher af_alg sd_mod uas usb_storage scsi_mod dm_crypt dm_mod hid_generic i915 crc32_pclmul crc32c_intel ghash_clmulni_intel i2c_algo_bit xhci_pci drm_kms_helper xhci_hcd cec aesni_intel drm nvme r8169 usbcore nvme_core psmouse realtek libaes mdio_devres crypto_simd libphy cryptd i2c_hid glue_helper t10_pi intel_lpss_pci crc_t10dif hid i2c_i801 crct10dif_generic intel_lpss crct10dif_pclmul i2c_smbus crct10dif_common idma64 usb_common battery video -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND 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: Ap
[bts-link] source package src:linux
# # bts-link upstream status pull for source package src:linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #606713 (http://bugs.debian.org/606713) # Bug title: screen power and lid open/close issues # * http://bugzilla.kernel.org/show_bug.cgi?id=60526 # * remote status changed: NEEDINFO -> CLOSED # * remote resolution changed: (?) -> OBSOLETE # * closed upstream tags 606713 + fixed-upstream usertags 606713 - status-NEEDINFO usertags 606713 + status-CLOSED resolution-OBSOLETE thanks
Processed: [bts-link] source package src:linux
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:linux > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #606713 (http://bugs.debian.org/606713) > # Bug title: screen power and lid open/close issues > # * http://bugzilla.kernel.org/show_bug.cgi?id=60526 > # * remote status changed: NEEDINFO -> CLOSED > # * remote resolution changed: (?) -> OBSOLETE > # * closed upstream > tags 606713 + fixed-upstream Bug #606713 [src:linux] screen power and lid open/close issues Added tag(s) fixed-upstream. > usertags 606713 - status-NEEDINFO Usertags were: status-NEEDINFO. There are now no usertags set. > usertags 606713 + status-CLOSED resolution-OBSOLETE There were no usertags set. Usertags are now: status-CLOSED resolution-OBSOLETE. > thanks Stopping processing here. Please contact me if you need assistance. -- 606713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux_5.10.46-1_source.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 24 Jun 2021 14:11:37 +0200 Source: linux Architecture: source Version: 5.10.46-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 982270 987361 987365 989451 990008 Changes: linux (5.10.46-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.41 - context_tracking: Move guest exit context tracking to separate helpers - context_tracking: Move guest exit vtime accounting to separate helpers - [x86] KVM: Defer vtime accounting 'til after IRQ handling https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.42 - ALSA: hda/realtek: the bass speaker can't output sound on Yoga 9i - ALSA: hda/realtek: Headphone volume is controlled by Front mixer - ALSA: hda/realtek: Chain in pop reduction fixup for ThinkStation P340 - ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 - ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook G8 - ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 15 G8 - ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 17 G8 - ALSA: usb-audio: scarlett2: Fix device hang with ehci-pci - ALSA: usb-audio: scarlett2: Improve driver startup messages - cifs: set server->cipher_type to AES-128-CCM for SMB3.0 - NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() - iommu/vt-d: Fix sysfs leak in alloc_iommu() - proc: Check /proc/$pid/attr/ writes against file opener - net: hso: fix control-request directions - net/sched: fq_pie: re-factor fix for fq_pie endless loop - net/sched: fq_pie: fix OOB access in the traffic path - netfilter: nft_set_pipapo_avx2: Add irq_fpu_usable() check, fallback to non-AVX2 version - mac80211: assure all fragments are encrypted (CVE-2020-26147) - mac80211: prevent mixed key and fragment cache attacks (CVE-2020-24586, CVE-2020-24587) - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks (CVE-2020-24588) - mac80211: drop A-MSDUs on old ciphers (CVE-2020-24588) - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well - mac80211: do not accept/forward invalid EAPOL frames (CVE-2020-26139) - mac80211: extend protection against mixed key and fragment cache attacks (CVE-2020-24586, CVE-2020-24587) - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe (CVE-2020-26145) - ath10k: drop fragments with multicast DA for SDIO (CVE-2020-26145) - ath10k: drop MPDU which has discard flag set by firmware for SDIO (CVE-2020-24588) - ath10k: Fix TKIP Michael MIC verification for PCIe (CVE-2020-26141) - ath10k: Validate first subframe of A-MSDU before processing the list - ath11k: Clear the fragment cache during key install (CVE-2020-24587) - dm snapshot: properly fix a crash when an origin has no snapshots - drm/amdgpu/vcn1: add cancel_delayed_work_sync before power gate - [amd64] drm/amdkfd: correct sienna_cichlid SDMA RLC register offset error - drm/amdgpu/vcn2.0: add cancel_delayed_work_sync before power gate - drm/amdgpu/vcn2.5: add cancel_delayed_work_sync before power gate - drm/amdgpu/jpeg2.0: add cancel_delayed_work_sync before power gate - Documentation: seccomp: Fix user notification documentation - seccomp: Refactor notification handler to prepare for new semantics - serial: core: fix suspicious security_locked_down() call - misc/uss720: fix memory leak in uss720_probe - [x86] thunderbolt: usb4: Fix NVM read buffer bounds and offset issue - [x86] thunderbolt: dma_port: Fix NVM read buffer bounds and offset issue - [x86] KVM: Fix vCPU preempted state from guest's point of view - [arm64] KVM: Prevent mixed-width VM creation - [x86] mei: request autosuspend after sending rx flow control - iio: gyro: fxas21002c: balance runtime power in error path - iio: dac: ad5770r: Put fwnode in error case during ->probe() - iio: adc: ad7768-1: Fix too small buffer passed to iio_push_to_buffers_with_timestamp() - iio: adc: ad7124: Fix missbalanced regulator enable / disable on error. - iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers - iio: adc: ad7923: Fix undersized rx buffer. - iio: adc: ad7793: Add missing error code in ad7793_setup() - iio: adc: ad7192: Avoid disabling a clock that was never enabled. - iio: adc: ad7192: handle regulator voltage error first - serial: 8250: Add UART_BUG_TXRAC
Bug#990008: marked as done (linux-image-5.10.0-7-amd64: e1000e driver fails to load after upgrade to bullseye from buster)
Your message dated Thu, 24 Jun 2021 15:00:09 + with message-id and subject line Bug#990008: fixed in linux 5.10.46-1 has caused the Debian Bug report #990008, regarding linux-image-5.10.0-7-amd64: e1000e driver fails to load after upgrade to bullseye from buster 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.) -- 990008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.40-1 Severity: important Dear Maintainer, Running Debian on a Lenovo ThinkCentre M90n system. It's a common all-in-one stock system. This system was running perfectly on Debain buster, however on the upgrade to bullseye, lacks all network functionality. Previously, the e1000e driver would load as follows: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k e1000e: Copyright(c) 1999 - 2015 Intel Corporation. e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode e1000e :00:1f.6 :00:1f.6 (uninitialized): registered PHC clock e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 98:fa:9b:70:3b:52 e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network Connection e1000e :00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FF-0FF e1000e :00:1f.6 eno2: renamed from eth0 e1000e: eno2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Now the e1000e driver seems the following: e1000e: Intel(R) PRO/1000 Network Driver e1000e: Copyright(c) 1999 - 2015 Intel Corporation. e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode e1000e :00:1f.6 :00:1f.6 (uninitialized): Failed to disable ULP e1000e: probe of :00:1f.6 failed with error -2 No other changes to the system took place other than the upgrade to bullseye. Concerning since I assume others will experience this upgrade challenge. Network controller works fine with Windows or if going back to 4.19 for testing. -- Package-specific info: ** Version: Linux version 5.10.0-7-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.40-1 (2021-05-28) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=UUID=b49cd91a-b8ea-424f-a6f0-3a80621652ff ro quiet ** Not tainted ** Kernel log: [5.972985] NET: Registered protocol family 38 [5.993961] Bluetooth: RFCOMM TTY layer initialized [5.993969] Bluetooth: RFCOMM socket layer initialized [5.993975] Bluetooth: RFCOMM ver 1.11 [6.940483] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [7.161973] rfkill: input handler disabled [8.665113] FS-Cache: Loaded [8.697699] FS-Cache: Netfs 'nfs' registered for caching [8.699966] Key type dns_resolver registered [8.778065] kauditd_printk_skb: 8 callbacks suppressed [8.778066] audit: type=1400 audit(1623941140.775:19): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=1122 comm="apparmor_parser" [8.843335] NFS: Registering the id_resolver key type [8.843342] Key type id_resolver registered [8.843343] Key type id_legacy registered [9.361898] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [9.363214] Bridge firewalling registered [9.395338] Initializing XFRM netlink socket [9.687026] br-f5d44323feea: port 1(vethda7e498) entered blocking state [9.687030] br-f5d44323feea: port 1(vethda7e498) entered disabled state [9.687340] device vethda7e498 entered promiscuous mode [9.691158] br-f5d44323feea: port 1(vethda7e498) entered blocking state [9.691162] br-f5d44323feea: port 1(vethda7e498) entered forwarding state [9.691213] IPv6: ADDRCONF(NETDEV_CHANGE): br-f5d44323feea: link becomes ready [9.691330] br-f5d44323feea: port 1(vethda7e498) entered disabled state [9.728132] br-f5d44323feea: port 2(veth7bfadb3) entered blocking state [9.728136] br-f5d44323feea: port 2(veth7bfadb3) entered disabled state [9.728418] device veth7bfadb3 entered promiscuous mode [9.734020] br-f5d44323feea: port 2(veth7bfadb3) entered blocking state [9.734023] br-f5d44323feea: port 2(veth7bfadb3) entered forwarding state [ 10.149671] eth0: renamed from veth98f4f77 [ 10.209455] eth0: renamed from veth51e2bf6 [ 10.229203] IPv6: ADDRCONF(NETDEV_CHANGE): veth7bfadb3: link becomes ready [ 10.229690] IPv6: ADDRCONF(NETDEV_CHANGE): vethda7e498: link b
Bug#987365: marked as done (linux-image-5.10.0-6-armmp: please enable support for i.mx6 mipi-csi capture devices)
Your message dated Thu, 24 Jun 2021 15:00:09 + with message-id and subject line Bug#987365: fixed in linux 5.10.46-1 has caused the Debian Bug report #987365, regarding linux-image-5.10.0-6-armmp: please enable support for i.mx6 mipi-csi capture devices 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.) -- 987365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.28-1 Severity: wishlist Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Please enable support for the mipi-csi capture devices on i.MX6 SoCs, as used e.g. by the SolidRun i.MX6 HummingBoard (config patch attached). Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.10.0-6-armmp (debian-kernel@lists.debian.org) (arm-linux-gnueabihf-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.28-1 (2021-04-09) ** Command line: console=ttymxc0,115200 deferred_probe_timeout=10 ahci_imx.hotplug=1 log_level=7 net.ifnames=0 ** Tainted: WCE (9728) * kernel issued warning * staging driver was loaded * unsigned module was loaded ** Kernel log: [ 11.819025] systemd[1]: modprobe@fuse.service: Succeeded. [ 11.834720] systemd[1]: Finished Load Kernel Module fuse. [ 11.859671] systemd[1]: Finished Load Kernel Modules. [ 11.879573] systemd[1]: Finished Remount Root and Kernel File Systems. [ 11.915841] systemd[1]: Mounting FUSE Control File System... [ 11.955104] systemd[1]: Mounting Kernel Configuration File System... [ 11.998308] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 12.007284] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [ 12.023562] systemd[1]: Starting Load/Save Random Seed... [ 12.050667] systemd[1]: Starting Apply Kernel Variables... [ 12.078727] systemd[1]: Starting Create System Users... [ 12.114011] systemd[1]: Started Journal Service. [ 12.303087] systemd-journald[173]: Received client request to flush runtime journal. [ 14.239809] Registered IR keymap rc-empty [ 14.289888] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 14.302153] imx-ipuv3 240.ipu: IPUv3H probed [ 14.329978] imx-ipuv3 280.ipu: IPUv3H probed [ 14.344837] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 14.469667] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 14.512465] random: crng init done [ 14.515899] random: 7 urandom warning(s) missed due to ratelimiting [ 14.560825] imx_media_common: module is from the staging directory, the quality is unknown, you have been warned. [ 14.618396] imx6_media: module is from the staging directory, the quality is unknown, you have been warned. [ 14.626716] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 14.644798] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 14.651935] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 14.661415] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 14.708623] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 14.740237] coda 204.vpu: firmware: direct-loading firmware vpu/vpu_fw_imx6q.bin [ 14.756779] coda 204.vpu: Using fallback firmware vpu/vpu_fw_imx6q.bin [ 14.768056] coda 204.vpu: Firmware code revision: 46076 [ 14.773727] coda 204.vpu: Initialized CODA960. [ 14.778621] coda 204.vpu: Firmware version: 3.1.1 [ 14.785300] coda 204.vpu: encoder registered as video0 [ 14.795329] coda 204.vpu: decoder registered as video1 [ 14.801191] coda 204.vpu: encoder registered as video2 [ 14.807040] coda 204.vpu: decoder registered as video3 [ 14.813297] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 14.819955] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 14.830926] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 14.837222] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 14.843443] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 14.850929] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0 [ 14.864206] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 14.938450] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 14.991703] imx-drm display-subsystem: bound imx-ipu
Bug#989451: marked as done (Please backport "net: usb: cdc_ncm: don't spew notifications" (de658a195ee23ca6aaffe197d1d2ea040beea0a2))
Your message dated Thu, 24 Jun 2021 15:00:09 + with message-id and subject line Bug#989451: fixed in linux 5.10.46-1 has caused the Debian Bug report #989451, regarding Please backport "net: usb: cdc_ncm: don't spew notifications" (de658a195ee23ca6aaffe197d1d2ea040beea0a2) 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.) -- 989451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.40-1 Severity: normal X-Debbugs-Cc: j...@joshtriplett.org Some USB Ethernet devices using the cdc_ncm driver produce several of these messages per second: Jun 03 19:25:17 s kernel: cdc_ncm 3-2.2:2.0 enx(mac address): 1000 mbit/s downlink 1000 mbit/s uplink This results in substantial log noise and disk usage. Please consider backporting the upstream patch "net: usb: cdc_ncm: don't spew notifications" (git commit de658a195ee23ca6aaffe197d1d2ea040beea0a2), which fixes this problem. Thank you, Josh Triplett --- End Message --- --- Begin Message --- Source: linux Source-Version: 5.10.46-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 24 Jun 2021 14:11:37 +0200 Source: linux Architecture: source Version: 5.10.46-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 982270 987361 987365 989451 990008 Changes: linux (5.10.46-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.41 - context_tracking: Move guest exit context tracking to separate helpers - context_tracking: Move guest exit vtime accounting to separate helpers - [x86] KVM: Defer vtime accounting 'til after IRQ handling https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.42 - ALSA: hda/realtek: the bass speaker can't output sound on Yoga 9i - ALSA: hda/realtek: Headphone volume is controlled by Front mixer - ALSA: hda/realtek: Chain in pop reduction fixup for ThinkStation P340 - ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8 - ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook G8 - ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 15 G8 - ALSA: hda/realtek: fix mute/micmute LEDs and speaker for HP Zbook Fury 17 G8 - ALSA: usb-audio: scarlett2: Fix device hang with ehci-pci - ALSA: usb-audio: scarlett2: Improve driver startup messages - cifs: set server->cipher_type to AES-128-CCM for SMB3.0 - NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() - iommu/vt-d: Fix sysfs leak in alloc_iommu() - proc: Check /proc/$pid/attr/ writes against file opener - net: hso: fix control-request directions - net/sched: fq_pie: re-factor fix for fq_pie endless loop - net/sched: fq_pie: fix OOB access in the traffic path - netfilter: nft_set_pipapo_avx2: Add irq_fpu_usable() check, fallback to non-AVX2 version - mac80211: assure all fragments are encrypted (CVE-2020-26147) - mac80211: prevent mixed key and fragment cache attacks (CVE-2020-24586, CVE-2020-24587) - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks (CVE-2020-24588) - mac80211: drop A-MSDUs on old ciphers (CVE-2020-24588) - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well - mac80211: do not accept/forward invalid EAPOL frames (CVE-2020-26139) - mac80211: extend protection against mixed key and fragment cache attacks (CVE-2020-24586, CVE-2020-24587) - ath10k: add CCMP PN replay protection for fragmented frames
Bug#982270: marked as done (linux: [armhf] several imx6 systems unable to detect ethernet)
Your message dated Thu, 24 Jun 2021 15:00:09 + with message-id and subject line Bug#982270: fixed in linux 5.10.46-1 has caused the Debian Bug report #982270, regarding linux: [armhf] several imx6 systems unable to detect ethernet 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.) -- 982270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Boot method: Followed the instruction in the README file Image version: https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/ dated 2021-01-30 (also tried 2021-02-06) Date: 2021-02-06 Machine: Cubox-i4P Partitions: Didn't get that far in the installation Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ok] Detect network card:[failed] could not proceed Overall install:[failed ] Comments/Problems: I downloaded the two-part image from [1] dated 2021-01-30 and tried to install it on my Cubox-i4. It booted fine but when it got to the "Detect network hardware" phase, it failed and said: > No Ethernet card was detected. If you know the name of the driver > needed by your Ethernet card, you can select it from the list. > Driver needed by your Ethernet card: and gave a long list of available ethernet drivers, none of which seemed to be relevant. I tried it again, this time with the components dated 2021-02-06. I was hoping that the problem was transient and might have been fixed in the intervening week, but I still got the same result: "No Ethernet card was detected." Vagrant says: > Pretty sure it is a kernel bug, since I can make it go away on a similar > system by downgrading to linux 5.9.x. Please CC me on the report and > I'll try to contribute what I can! -- Log files attached to this report are from a successful Buster installation on the same hardware, in hopes they might be some help... Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u7" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux cube 4.19.0-13-armmp #1 SMP Debian 4.19.160-2 (2020-11-28) armv7l GNU/Linux usb-list: usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 4.19.0-13-armmp ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 02 Device 01: EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 4.19.0-13-armmp ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub lsmod: Module Size Used by lsmod: dm_mod122880 9 lsmod: md_mod143360 0 lsmod: jfs 184320 0 lsmod: btrfs1241088 0 lsmod: libcrc32c 16384 1 btrfs lsmod: xor16384 1 btrfs lsmod: zstd_decompress61440 1 btrfs lsmod: zstd_compress 159744 1 btrfs lsmod: xxhash 20480 2 zstd_compress,zstd_decompress lsmod: zlib_deflate 28672 1 btrfs lsmod: raid6_pq 98304 1 btrfs lsmod: vfat 24576 0 lsmod: fat73728 1 vfat lsmod: ext4 618496 3 lsmod: crc16 16384 1 ext4 lsmod: mbcache16384 1 ext4 lsmod: jbd2 102400 1 ext4 lsmod: crc32c_generic 16384 6 lsmod: fscrypto 28672 1 ext4 lsmod: ecb16384 0 lsmod: brcmfmac 253952 0 lsmod: brcmutil 16384 1 brcmfmac lsmod: cfg80211
Bug#987361: marked as done (linux-image-5.10.0-6-armmp: bluetooth broken on i.MX6 Cubox-i and related devices)
Your message dated Thu, 24 Jun 2021 15:00:09 + with message-id and subject line Bug#987361: fixed in linux 5.10.46-1 has caused the Debian Bug report #987361, regarding linux-image-5.10.0-6-armmp: bluetooth broken on i.MX6 Cubox-i and related devices 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.) -- 987361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.28-1 Severity: important Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Bluetooth drivers for the two chips used on SolidRun i.MX6 SoMs have recently disappeared from the debian kernel package. Please re-add them, patch attached and verified with both BCM4330 and WL1837. Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.10.0-6-armmp (debian-kernel@lists.debian.org) (arm-linux-gnueabihf-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.28-1 (2021-04-09) ** Command line: root=/dev/mmcblk1p1 console=ttymxc0,115200 deferred_probe_timeout=10 log_level=7 net.ifnames=0 ** Tainted: WE (8704) * kernel issued warning * unsigned module was loaded ** Kernel log: [ 10.481988] systemd[1]: Mounting Kernel Debug File System... [ 10.510173] systemd[1]: Mounting Kernel Trace File System... [ 10.539156] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 10.570585] systemd[1]: Starting Load Kernel Module configfs... [ 10.598475] systemd[1]: Starting Load Kernel Module drm... [ 10.631165] systemd[1]: Starting Load Kernel Module fuse... [ 10.654693] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 10.664703] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [ 10.675493] fuse: init (API version 7.32) [ 10.698147] systemd[1]: Starting Journal Service... [ 10.734232] systemd[1]: Starting Load Kernel Modules... [ 10.763521] systemd[1]: Starting Remount Root and Kernel File Systems... [ 10.799102] systemd[1]: Starting Coldplug All udev Devices... [ 10.835732] systemd[1]: Mounted POSIX Message Queue File System. [ 10.844498] EXT4-fs (mmcblk1p1): re-mounted. Opts: (null) [ 10.869237] systemd[1]: Mounted Kernel Debug File System. [ 10.891964] systemd[1]: Mounted Kernel Trace File System. [ 10.917529] systemd[1]: Finished Create list of static device nodes for the current kernel. [ 10.949890] systemd[1]: modprobe@configfs.service: Succeeded. [ 10.958122] systemd[1]: Finished Load Kernel Module configfs. [ 10.985586] systemd[1]: modprobe@drm.service: Succeeded. [ 10.993079] systemd[1]: Finished Load Kernel Module drm. [ 11.021581] systemd[1]: modprobe@fuse.service: Succeeded. [ 11.029043] systemd[1]: Finished Load Kernel Module fuse. [ 11.051899] systemd[1]: Started Journal Service. [ 11.258052] systemd-journald[196]: Received client request to flush runtime journal. [ 11.288371] systemd-journald[196]: File /var/log/journal/9bbcae0a3ade4af68637450cb7940ea7/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 12.656525] Registered IR keymap rc-empty [ 12.661105] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 12.672050] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 12.703052] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input1 [ 12.842870] rc rc0: two consecutive events of type space [ 12.847048] imx-ipuv3 240.ipu: IPUv3H probed [ 12.858932] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 12.875330] imx-ipuv3 280.ipu: IPUv3H probed [ 12.875434] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 12.964800] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 12.972142] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 13.069408] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 13.077309] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 13.086018] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 13.092640] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 13.099867] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 13.109337] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 13.183812] coda 204.vpu: firmware: failed to load vpu/vpu_fw_imx6q.bin (-2) [ 13.191344] coda 204.vpu: Direct fir
Bug#990279: linux-image-5.10.0-7-powerpc64le: Upgrade to 5.10.0-7-powerpc64le from 5.10.0-0.bpo.5-powerpc64le breaks amdgpu
Package: src:linux
Version: 5.10.40-1
Severity: normal
X-Debbugs-Cc: nwfila...@gmail.com
Dear Maintainer,
Upgrading from 5.10.0-0.bpo.5-powerpc64le=5.10.24-1~bpo10+1 to
5.10.0-7-powerpc64le=5.10.40-1 has broken my X server's ability to use GL, and
has, indeed, lead to markedly poor performance even in things like rxvt.
Quoting /var/log/Xorg.0.log:
[19.084] (II) LoadModule: "glx"
[19.087] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[19.102] (II) Module glx: vendor="X.Org Foundation"
[19.143] (II) Loading sub module "glamoregl"
[19.143] (II) LoadModule: "glamoregl"
[19.143] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[19.159] (II) Module glamoregl: vendor="X.Org Foundation"
[19.573] (II) modeset(0): glamor X acceleration enabled on AMD Radeon (TM)
Pro WX 7100 Graphics (POLARIS10, DRM 3.40.0, 5.10.0-7-powerpc64le, LLVM 11.0.1)
[19.573] (II) modeset(0): glamor initialized
[19.647] (II) Initializing extension GLX
[19.656] (II) AIGLX: Loaded and initialized radeonsi
[19.656] (II) GLX: Initialized DRI2 GL provider for screen 0
[20.985] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[21.018] (WW) glamor: Failed to allocate 48x48 FBO due to GL_OUT_OF_MEMORY.
[21.018] (WW) glamor: Expect reduced performance.
Things work just fine with the same machine on the old kernel, so I'm holding
back for now, but this isn't a great long-term solution. This is a Talos II
workstation, making it a little niche and therefore unsurprising that
regressions have crept in, but it'd be nice to get them resolved. Any
suggestions, advice, requests for further information, &c are all appreciated.
I can rebuild kernels and bisect if pointed at the right git repository and
tags, if that'd be a useful thing.
FWIW, the same thing happened, I believe, with 5.10.0-6-powerpc64le, previously,
but I no longer have it installed to check again.
Thanks much in advance,
--nwf;
-- Package-specific info:
** Version:
Linux version 5.10.0-7-powerpc64le (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.40-1 (2021-05-28)
** Command line:
root=ZFS=rpool/ROOT/debian ro quiet
** Tainted: POE (12289)
* proprietary module was loaded
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[5.306593] [drm] amdgpu kernel modesetting enabled.
[5.309579] amdgpu 0030:01:00.0: vgaarb: deactivate vga console
[5.309753] amdgpu 0030:01:00.0: enabling device (0140 -> 0142)
[5.309767] amdgpu 0030:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature
not supported
[5.644486] amdgpu 0030:01:00.0: amdgpu: Fetched VBIOS from ROM BAR
[5.644492] amdgpu: ATOM BIOS: 113-C9540101-103
[5.647802] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_mc.bin
[5.647819] amdgpu 0030:01:00.0: BAR 2: releasing [mem
0x620001000-0x62000101f 64bit pref]
[5.647822] amdgpu 0030:01:00.0: BAR 0: releasing [mem
0x62000-0x62fff 64bit pref]
[5.647869] amdgpu 0030:01:00.0: BAR 0: assigned [mem
0x62000-0x62001 64bit pref]
[5.647879] amdgpu 0030:01:00.0: BAR 2: assigned [mem
0x62002-0x62002001f 64bit pref]
[5.647913] amdgpu 0030:01:00.0: amdgpu: VRAM: 8192M 0x00F4 -
0x00F5 (8192M used)
[5.647916] amdgpu 0030:01:00.0: amdgpu: GART: 256M 0x00FF -
0x00FF0FFF
[5.648123] [drm] amdgpu: 8192M of VRAM memory ready
[5.648128] [drm] amdgpu: 8192M of GTT memory ready.
[5.649983] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_pfp_2.bin
[5.650921] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_me_2.bin
[5.651856] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_ce_2.bin
[5.652822] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_rlc.bin
[5.654748] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_mec_2.bin
[5.657197] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_mec2_2.bin
[5.659428] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_sdma.bin
[5.661056] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_sdma1.bin
[5.661159] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[5.663358] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_uvd.bin
[5.666276] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_vce.bin
[5.668251] amdgpu 0030:01:00.0: firmware: direct-loading firmware
amdgpu/polaris10_smc.bin
[5.727666] snd_hda_intel 0030:01:00.1: bound 0030:01:00.0 (ops
amdgpu_dm_audio_component_bind_ops [amdgpu])
[5.946750] amdgpu 0030:01:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9,
active_cu_number 36
[6.091370] amdgpu 0
linux_5.10.46-1_source.changes is NEW
binary:affs-modules-5.10.0-8-4kc-malta-di is NEW. binary:affs-modules-5.10.0-8-5kc-malta-di is NEW. binary:affs-modules-5.10.0-8-loongson-3-di is NEW. binary:affs-modules-5.10.0-8-octeon-di is NEW. binary:ata-modules-5.10.0-8-4kc-malta-di is NEW. binary:ata-modules-5.10.0-8-5kc-malta-di is NEW. binary:ata-modules-5.10.0-8-armmp-di is NEW. binary:ata-modules-5.10.0-8-loongson-3-di is NEW. binary:ata-modules-5.10.0-8-powerpc64le-di is NEW. binary:btrfs-modules-5.10.0-8-4kc-malta-di is NEW. binary:btrfs-modules-5.10.0-8-5kc-malta-di is NEW. binary:btrfs-modules-5.10.0-8-armmp-di is NEW. binary:btrfs-modules-5.10.0-8-loongson-3-di is NEW. binary:btrfs-modules-5.10.0-8-marvell-di is NEW. binary:btrfs-modules-5.10.0-8-octeon-di is NEW. binary:btrfs-modules-5.10.0-8-powerpc64le-di is NEW. binary:btrfs-modules-5.10.0-8-s390x-di is NEW. binary:cdrom-core-modules-5.10.0-8-4kc-malta-di is NEW. binary:cdrom-core-modules-5.10.0-8-5kc-malta-di is NEW. binary:cdrom-core-modules-5.10.0-8-armmp-di is NEW. binary:cdrom-core-modules-5.10.0-8-loongson-3-di is NEW. binary:cdrom-core-modules-5.10.0-8-marvell-di is NEW. binary:cdrom-core-modules-5.10.0-8-octeon-di is NEW. binary:cdrom-core-modules-5.10.0-8-powerpc64le-di is NEW. binary:cdrom-core-modules-5.10.0-8-s390x-di is NEW. binary:crc-modules-5.10.0-8-4kc-malta-di is NEW. binary:crc-modules-5.10.0-8-5kc-malta-di is NEW. binary:crc-modules-5.10.0-8-armmp-di is NEW. binary:crc-modules-5.10.0-8-loongson-3-di is NEW. binary:crc-modules-5.10.0-8-marvell-di is NEW. binary:crc-modules-5.10.0-8-octeon-di is NEW. binary:crc-modules-5.10.0-8-powerpc64le-di is NEW. binary:crc-modules-5.10.0-8-s390x-di is NEW. binary:crypto-dm-modules-5.10.0-8-4kc-malta-di is NEW. binary:crypto-dm-modules-5.10.0-8-5kc-malta-di is NEW. binary:crypto-dm-modules-5.10.0-8-armmp-di is NEW. binary:crypto-dm-modules-5.10.0-8-loongson-3-di is NEW. binary:crypto-dm-modules-5.10.0-8-marvell-di is NEW. binary:crypto-dm-modules-5.10.0-8-octeon-di is NEW. binary:crypto-dm-modules-5.10.0-8-powerpc64le-di is NEW. binary:crypto-dm-modules-5.10.0-8-s390x-di is NEW. binary:crypto-modules-5.10.0-8-4kc-malta-di is NEW. binary:crypto-modules-5.10.0-8-5kc-malta-di is NEW. binary:crypto-modules-5.10.0-8-armmp-di is NEW. binary:crypto-modules-5.10.0-8-loongson-3-di is NEW. binary:crypto-modules-5.10.0-8-marvell-di is NEW. binary:crypto-modules-5.10.0-8-octeon-di is NEW. binary:crypto-modules-5.10.0-8-powerpc64le-di is NEW. binary:crypto-modules-5.10.0-8-s390x-di is NEW. binary:dasd-extra-modules-5.10.0-8-s390x-di is NEW. binary:dasd-modules-5.10.0-8-s390x-di is NEW. binary:efi-modules-5.10.0-8-armmp-di is NEW. binary:event-modules-5.10.0-8-4kc-malta-di is NEW. binary:event-modules-5.10.0-8-5kc-malta-di is NEW. binary:event-modules-5.10.0-8-armmp-di is NEW. binary:event-modules-5.10.0-8-loongson-3-di is NEW. binary:event-modules-5.10.0-8-marvell-di is NEW. binary:event-modules-5.10.0-8-octeon-di is NEW. binary:event-modules-5.10.0-8-powerpc64le-di is NEW. binary:ext4-modules-5.10.0-8-4kc-malta-di is NEW. binary:ext4-modules-5.10.0-8-5kc-malta-di is NEW. binary:ext4-modules-5.10.0-8-armmp-di is NEW. binary:ext4-modules-5.10.0-8-loongson-3-di is NEW. binary:ext4-modules-5.10.0-8-marvell-di is NEW. binary:ext4-modules-5.10.0-8-octeon-di is NEW. binary:ext4-modules-5.10.0-8-powerpc64le-di is NEW. binary:ext4-modules-5.10.0-8-s390x-di is NEW. binary:f2fs-modules-5.10.0-8-4kc-malta-di is NEW. binary:f2fs-modules-5.10.0-8-5kc-malta-di is NEW. binary:f2fs-modules-5.10.0-8-armmp-di is NEW. binary:f2fs-modules-5.10.0-8-loongson-3-di is NEW. binary:f2fs-modules-5.10.0-8-marvell-di is NEW. binary:f2fs-modules-5.10.0-8-octeon-di is NEW. binary:f2fs-modules-5.10.0-8-powerpc64le-di is NEW. binary:f2fs-modules-5.10.0-8-s390x-di is NEW. binary:fancontrol-modules-5.10.0-8-powerpc64le-di is NEW. binary:fat-modules-5.10.0-8-4kc-malta-di is NEW. binary:fat-modules-5.10.0-8-5kc-malta-di is NEW. binary:fat-modules-5.10.0-8-armmp-di is NEW. binary:fat-modules-5.10.0-8-loongson-3-di is NEW. binary:fat-modules-5.10.0-8-marvell-di is NEW. binary:fat-modules-5.10.0-8-octeon-di is NEW. binary:fat-modules-5.10.0-8-powerpc64le-di is NEW. binary:fat-modules-5.10.0-8-s390x-di is NEW. binary:fb-modules-5.10.0-8-4kc-malta-di is NEW. binary:fb-modules-5.10.0-8-5kc-malta-di is NEW. binary:fb-modules-5.10.0-8-armmp-di is NEW. binary:fb-modules-5.10.0-8-loongson-3-di is NEW. binary:fb-modules-5.10.0-8-marvell-di is NEW. binary:fb-modules-5.10.0-8-powerpc64le-di is NEW. binary:firewire-core-modules-5.10.0-8-loongson-3-di is NEW. binary:firewire-core-modules-5.10.0-8-powerpc64le-di is NEW. binary:fuse-modules-5.10.0-8-4kc-malta-di is NEW. binary:fuse-modules-5.10.0-8-5kc-malta-di is NEW. binary:fuse-modules-5.10.0-8-armmp-di is NEW. binary:fuse-modules-5.10.0-8-loongson-3-di is NEW. binary:fuse-modules-5.10.0-8-marvell-di is NEW. binary:fuse-modules-5.10.0-8-octeon-di is NEW. binary:fuse-modules-5.10.0-8-powerpc64le-di is NEW. binary:fuse-modules-5.10.0-8-s390x-di i
Processing of linux_5.10.46-1_source.changes
linux_5.10.46-1_source.changes uploaded successfully to localhost along with the files: linux_5.10.46-1.dsc linux_5.10.46.orig.tar.xz linux_5.10.46-1.debian.tar.xz linux_5.10.46-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#988688: linux-source-5.10: Lenovo ThinkPad Yoga 260 fails to suspend and resume
Package: src:linux Version: 5.10.40-1 Followup-For: Bug #988688 Getting this in both a Thinkpad L15 freshly installed on current bullseye/testing, and a Thinkpad T460s upgraded from a buster/stable. The T460s resumed normally with the buster kernel. With 5.10 they get a dark screen, keyboard LEDs on but don't react. Manually installing kernel 5.12.0 (grabbed it from liquorix for convenience) fixed it. Log has nothing useful between suspend and failed/frozen resume: --- Jun 24 06:06:29 localhost kernel: [ 283.154932] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Jun 24 06:06:29 localhost kernel: [ 283.206322] wlp4s0: deauthenticating from 16:e5:b0:b3:17:83 by local choice (Reason: 3=DEAUTH_LEAVING) ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jun 24 10:33:53 localhost kernel: [0.00] microcode: microcode updated early to revision 0xe2, date = 2020-07-14 Jun 24 10:33:53 localhost kernel: [0.00] Linux version 5.10.0-7-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.40-1 (2021-05-28) Jun 24 10:33:53 localhost kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/onluksvg-root ro --- -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20U70004GE product_version: ThinkPad L15 Gen 1 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: R19ET32W (1.16 ) board_vendor: LENOVO board_name: 20U70004GE board_version: SDK0J40697 WIN ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630] Subsystem: Lenovo Renoir Root Complex [17aa:507e] 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- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (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 00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (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 00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (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 00:02.5 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] (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 00:08.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-
