[Kernel-packages] [Bug 1946444] Re: ath11k_pci firmware crashes under regular usage on Dell XPS 13 9310 (no suspend and resume)

2022-07-13 Thread Rob Robertson
happens to me too.   Here's my info:  


$ uname -a
Linux  5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux



[ 7806.157472] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.260003] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.362401] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.464785] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.567221] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.669552] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.771745] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.874260] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7806.976683] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7807.079210] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7807.181602] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7807.284062] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7807.386275] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7807.488507] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7807.591494] wlp114s0: cannot understand ECSA IE operating class, 5, ignoring
[ 7817.827571] ath11k_pci :72:00.0: firmware crashed: MHI_CB_SYS_ERROR
[ 7817.904043] ath11k_pci :72:00.0: failed to transmit frame -108
[ 7818.086914] ath11k_pci :72:00.0: failed to transmit frame -108
[ 7818.148464] ath11k_pci :72:00.0: failed to send WMI_PDEV_GET_TEMPERATURE 
cmd
[ 7818.148468] ath11k_pci :72:00.0: failed to read temperature -108

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1946444

Title:
  ath11k_pci  firmware crashes under regular usage on Dell XPS 13 9310
  (no suspend and resume)

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  While I was normally working on my Dell XPS 13 9310 Laptop, noticed
  that WiFi suddenly got disconnected. Looking at dmesg, noticed that
  the firmware crashed.

  (I am also attaching the entire dmesg output as a file to this bug. )

  $ dmesg | grep ath11_k

  [   13.826871] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0
  [35908.890709] ath11k_pci :72:00.0: firmware crashed: MHI_CB_SYS_ERROR
  [36170.055770] ath11k_pci :72:00.0: wmi command 12290 timeout
  [36170.055776] ath11k_pci :72:00.0: failed to send WMI_STOP_SCAN_CMDID
  [36170.055783] ath11k_pci :72:00.0: failed to stop wmi scan: -11
  [36170.055786] ath11k_pci :72:00.0: failed to stop scan: -11
  [36170.055788] ath11k_pci :72:00.0: failed to start hw scan: -110
  ...
  ...
  [36305.230431] ath11k_pci :72:00.0: wmi command 16387 timeout
  [36305.230436] ath11k_pci :72:00.0: failed to send WMI_PDEV_SET_PARAM cmd
  [36305.230445] ath11k_pci :72:00.0: failed to enable PMF QOS: (-11

  I had to reboot the machine at least 2 times before WiFi started
  working. In the past, I had noticed WiFi would not work after boot a
  couple of times, but this is the first time I am seeing it breaking
  under normal, continuous usage. This is a major reliability issue if
  WiFi connection keeps breaking in the middle of work like this.

  Also, this is somewhat similar to the following bugs, but not exactly
  the same:

  https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018
  (here there is no message 'firmware crashed' but rather some failures
  from ath11k_pci. Moreover it occurred during suspend and resume.
  Whereas in my case, the last suspend + resume was at least 3 and half
  hours before the firmware crash)

  https://bugs.launchpad.net/ubuntu/+source/linux-signed-
  oem-5.10/+bug/1942060 (here there is 'firmware crashed' message, but
  all the error messages after that seem to be different. Moreover it
  seems to have occurred 56 seconds after system booted, when WiFi
  network was connected. Whereas I had a uptime of 9 hours and about 6
  hours after the last WiFi connection).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1946444/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-05-20 Thread Rob Robertson
** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp