Re: Re: Severity: High / Debian 10 amp; 11 with Kernel 5.10.x-amd64 =gt; Intel AX210 Wifi amp; Bluetooth not work

2021-06-17 Thread Vincent Blut
Salut Philippe,

Le 2021-06-14 23:09, pham...@bluewin.ch a écrit :
> The boot is difficult, I have a recurring error message that turns in a loop.
> 
> journalctl -k | grep -Ei "iwl|bluetooth :
> 
> 
> root@portable-1:~# journalctl -k | grep -Ei "iwl|bluetooth"
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: enabling device 
> ( -> 0002)
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: firmware: 
> direct-loading firmware iwlwifi-ty-a0-gf-a0-59.ucode
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: api flags index 2 
> larger than supported by driver
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: TLV_FW_FSEQ_VERSION: 
> FSEQ Version: 93.8.63.28
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: loaded firmware 
> version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: firmware: failed to 
> load iwl-debug-yoyo.bin (-2)
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: Detected Intel(R) 
> Wi-Fi 6 AX210 160MHz, REV=0x420
> jun 14 22:48:12 portable-1 kernel: Bluetooth: Core ver 2.22
> jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI device and connection 
> manager initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: L2CAP socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: SCO socket layer initialized
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: firmware: failed to 
> load iwlwifi-ty-a0-gf-a0.pnvm (-2)
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: base HW address: 
> 54:14:f3:52:7b:e1
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
> information failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
> (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
> FW download
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0 wlp59s0: renamed from 
> wlan0
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 
> 1.3
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP filters: protocol multicast
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
> information failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
> (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
> FW download
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
> information failed (-22)
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
> (-22)
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
> FW download
> 
> 
> systemctl status bluetooth.service :
> 
> 
> root@portable-1:~# systemctl status bluetooth.service
> ● bluetooth.service - Bluetooth service
>  Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
> preset: enabled)
>  Active: active (running) since Mon 2021-06-14 22:48:12 CEST; 10min ago
>Docs: man:bluetoothd(8)
>Main PID: 649 (bluetoothd)
>  Status: "Running"
>   Tasks: 1 (limit: 38030)
>  Memory: 2.6M
> CPU: 266ms
>  CGroup: /system.slice/bluetooth.service
>  └─649 /usr/libexec/bluetooth/bluetoothd
> 
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEScanIntervalConnect” in >
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEScanWindowConnect” in gr>
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEMinConnectionInterval” i>
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEMaxConnectionInterval” i>
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEConnectionLatency” in gr>
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEConnectionSupervisionTim>
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEAutoconnecttimeout” in g>
> jun 14 22:48:12 portable-1 systemd[1]: Started Bluetooth service.
> jun 14 22:48:12 portable-1 bluetoothd[649]: Starting SDP server
> jun 14 22:48:12 portable-1 bluetoothd[649]: Bluetooth management interface 
> 1.18 initialized
> lines 1-22/22 (END)
> 
> 
> If I can be useful for make a test on my system, do not hesitate to ask me it.

Thanks for the logs, Phillipe. From the information I gathered, it seems
Linux 5.11 is required to get bluetooth work on this adapter.

Before rebasing on Linux 5.11 for the 21.04 

Processed: tagging 927209

2021-06-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 927209 + moreinfo
Bug #927209 [src:linux] /boot/vmlinuz-4.19.0-4-amd64: Accupoint and touchpad 
(buttons) non-functional on Toshiba X30 and X40
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



[bts-link] source package src:linux

2021-06-17 Thread debian-bts-link
#
# 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: REOPENED -> NEEDINFO
usertags 606713 - status-REOPENED
usertags 606713 + status-NEEDINFO

thanks



Bug#990008: linux-image-5.10.0-7-amd64: e1000e driver fails to load after upgrade to bullseye from buster

2021-06-17 Thread Michael Krieger
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 becomes ready
[   10.229724] br-f5d44323feea: port 1(vethda7e498) entered blocking state
[   10.229726] br-f5d44323feea: port 1(vethda7e498) entered forwarding state
[   26.785343] rfkill: input handler enabled
[   28.238953] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[   28.496041] rfkill: input handler disabled
[   95.503702] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7

** Model information
sys_vendor: LENOVO
product_name: 11ADS0E600
product_version: ThinkCentre M90n-1
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: M2AKT29A
board_vendor: LENOVO
board_name: 314D
board_version: SDK0J40697 WIN 3305310468669

** Loaded modules:
ctr
ccm
xt_nat
veth
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack_netlink
xfrm_user
xfrm_algo
br_netfilter
bridge
stp