date:20220125

Interesting, I have the "same" problem on Jammy Jellyfish (22.04).

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041

My suspend is also not working, freezes at the same state. Mainline
kernel works.

Also a Lenovo Device.

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

Title:
  Regression in 5.13.0-23: laptop cannot suspend or turn off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from 5.13.0-23-lowlatency my laptop fails to suspend, turn
  off or reboot.

  On suspend the screen turns off, but the power button LED stays on (it
  should be blinking when suspended), the keyboard backlight and the CPU
  fan stays on. I cannot resume the laptop by pressing the power button
  or any other button.

  On power off and restart I see the splash screen and nothing happens.

  The last working Ubuntu kernel is 5.13.0-22-lowlatency. 5.13.0-23-lowlatency 
and 5.13.0-25-lowlatency are broken.
  I also tried the latest upstream mainline kernel, 
linux-image-unsigned-5.16.0-051600-lowlatency_5.16.0-051600.202201091830_amd64.deb,
 and it doesn't have this regression.

  This happens on a Lenovo IdeaPad Flex 5, the AMD variant (Ryzen 7
  4700U).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-lowlatency 5.13.0.25.36
  ProcVersionSignature: Ubuntu 5.13.0-23.23-lowlatency 5.13.19
  Uname: Linux 5.13.0-23-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dszoboszlay   2528 F pulseaudio
   /dev/snd/controlC0:  dszoboszlay   2528 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 09:01:15 2022
  InstallationDate: Installed on 2020-06-04 (589 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-lowlatency N/A
   linux-backports-modules-5.13.0-23-lowlatency  N/A
   linux-firmware1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-29 (77 days ago)
  dmi.bios.date: 10/15/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN29WW:bd10/15/2020:br1.29:efr1.19:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:skuLENOVO_MT_81X2_BU_idea_FM_IdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version: IdeaPad Flex 5 14ARE05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958007/+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 1958774] Re: Blackscreen after suspending and closing LID

maybe this website will help you to debug your problem:

https://01.org/blogs/rzhang/2015/best-practice-debug-linux-
suspend/hibernate-issues

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

Title:
  Blackscreen after suspending and closing LID

Status in linux package in Ubuntu:
  New

Bug description:
  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:

  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).

  These bugs really trouble me. It will be very helpful if you fix it.

  UPDATE at 2022/01/25: After I upgraded the "core" package using "snap
  refresh", the first bug has been fixed. However, the second bug
  related to laptop devices is still there.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: NH5x_7xDCx_DDx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958774/+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 1958968] Re: failed to resume PC

Maybe this website will help you to debug your issue

https://01.org/blogs/rzhang/2015/best-practice-debug-linux-
suspend/hibernate-issues

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

Title:
  failed to resume PC

Status in linux package in Ubuntu:
  New

Bug description:
  Sometimes I cannot resume my PC after suspend. Pressing keys or moving
  the mouse doesn't help: the login screen doesn't appear. In some cases
  pressing Ctrl+Alt+F1 helps, but not always. This time I had to make a
  hard reset. Check 25 January 10:43 in the logs.

  Ubuntu 20.04.3 LTS
  5.4.0-96-generic x86_64
  GNOME 3.36.8 X11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958968/+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 1959041] Re: STR (suspend-to-RAM) freezes at suspend

** Description changed:

  Hi,
  
- I want to report, that your delivered kernel has problem with STR on my 
Laptop.
- When I run `echo mem | sudo tee /sys/power/state` the systems trys to go in 
standby mode. Everything shuts down, but the power led flashes fast (how it 
does every time between going into standby and before the standby is reached). 
It never reaches the state that the led starts slowly "breathing in and out".
+ I want to report, that Ubuntu's shipped kernel has a problem with STR on my 
Laptop.
+ When I run `echo mem | sudo tee /sys/power/state` the systems try to go in 
standby mode. Everything shuts down, but the power led flashes fast (how it 
does every time between going into standby and before the standby is reached). 
It never reaches the state that the led starts slowly "breathing in and out". 
So the final step is missing and the machine can only be forced to poweroff and 
on again.
  
  I already tested with the mainline kernel from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/
  
  And there standby works flawless.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  thomas 1409 F pipewire-media-
-   thomas 1410 F pulseaudio
-  /dev/snd/seq:thomas 1408 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  thomas 1409 F pipewire-media-
+   thomas 1410 F pulseaudio
+  /dev/snd/seq:thomas 1408 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Jan 25 20:06:44 2022
  InstallationDate: Installed on 2022-01-21 (4 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  MachineType: LENOVO 20ELS03U00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic 
root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug 
no_console_suspend ignore_loglevel
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-17-generic N/A
-  linux-backports-modules-5.15.0-17-generic  N/A
-  linux-firmware 1.204
+  linux-restricted-modules-5.15.0-17-generic N/A
+  linux-backports-modules-5.15.0-17-generic  N/A
+  linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2019
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R05ET81W (1.59)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ELS03U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460:
  dmi.product.family: ThinkPad Yoga 460
  dmi.product.name: 20ELS03U00
  dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460
  dmi.product.version: ThinkPad Yoga 460
  dmi.sys.vendor: LENOVO

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

Title:
  STR (suspend-to-RAM) freezes at suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  I want to report, that Ubuntu's shipped kernel has a problem with STR on my 
Laptop.
  When I run `echo mem | sudo tee /sys/power/state` the systems try to go in 
standby mode. Everything shuts down, but the power led flashes fast (how it 
does every time between going into standby and before the standby is reached). 
It never reaches the state that the led starts slowly "breathing in and out". 
So the final step is missing and the machine can only be forced to poweroff and 
on again.

  I already tested with the mainline kernel from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/

  And there standby works flawless.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1409 F pipewire-media-
    thomas 1410 F pulseaudio
   /dev/snd/seq:thomas 1408 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Jan 25 20:06:44 2022
  InstallationDate: Installed on 2022-01-21 (4

[Kernel-packages] [Bug 1959041] [NEW] STR (suspend-to-RAM) freezes at suspend

Public bug reported:

Hi,

I want to report, that your delivered kernel has problem with STR on my Laptop.
When I run `echo mem | sudo tee /sys/power/state` the systems trys to go in 
standby mode. Everything shuts down, but the power led flashes fast (how it 
does every time between going into standby and before the standby is reached). 
It never reaches the state that the led starts slowly "breathing in and out".

I already tested with the mainline kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/

And there standby works flawless.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-17-generic 5.15.0-17.17
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  thomas 1409 F pipewire-media-
  thomas 1410 F pulseaudio
 /dev/snd/seq:thomas 1408 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Jan 25 20:06:44 2022
InstallationDate: Installed on 2022-01-21 (4 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121)
MachineType: LENOVO 20ELS03U00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic 
root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug 
no_console_suspend ignore_loglevel
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-17-generic N/A
 linux-backports-modules-5.15.0-17-generic  N/A
 linux-firmware 1.204
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2019
dmi.bios.release: 1.59
dmi.bios.vendor: LENOVO
dmi.bios.version: R05ET81W (1.59)
dmi.board.asset.tag: Not Available
dmi.board.name: 20ELS03U00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460:
dmi.product.family: ThinkPad Yoga 460
dmi.product.name: 20ELS03U00
dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460
dmi.product.version: ThinkPad Yoga 460
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy regression-release

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

Title:
  STR (suspend-to-RAM) freezes at suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  I want to report, that your delivered kernel has problem with STR on my 
Laptop.
  When I run `echo mem | sudo tee /sys/power/state` the systems trys to go in 
standby mode. Everything shuts down, but the power led flashes fast (how it 
does every time between going into standby and before the standby is reached). 
It never reaches the state that the led starts slowly "breathing in and out".

  I already tested with the mainline kernel from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/

  And there standby works flawless.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1409 F pipewire-media-
thomas 1410 F pulseaudio
   /dev/snd/seq:thomas 1408 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Jan 25 20:06:44 2022
  InstallationDate: Installed on 2022-01-21 (4 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  MachineType: LENOVO 20ELS03U00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic 
root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug 
no_console_suspend ignore_loglevel
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2019
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R05ET81W (1.59)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ELS03U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO

[Kernel-packages] [Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

2022-01-25 Thread Aaron Kriegman

I'm thinking of trying to roll back my software so that I can continue
using my computer until this is fixed. Can anyone recommend which
package I should try rolling back, or how I should go about this?

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

Title:
  [amdgpu] Random noise 'static' display after internal display turned
  off/on

Status in linux-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Laptop internal display shows random looking 'static' after it's
  turned off and then on again.   e.g. on suspend/resume, or when
  plugging/unplugging an external monitor.

  This appeared to come after a `dist-upgrade` took the kernel from
  5.11.0-44 to 5.13.0-25 (hwe).

  Others are seeing this with both NVidia and AMD graphics hardware:
  - 
https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/
  - 
https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/

  I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome
  both X and Wayland, and gnome-flashback/metacity.  All showed the same
  problem.

  Also tried an `apt install --reinstall xserver-xorg-video-radeon
  libdrm-radeon1` for luck - no joy.

  Running a 20.04.3 live stick the problem does *not* occur.

  System: Thinkpad X13 Gen1
  Processor: AMD Ryzen 7 PRO 4750U
  System Firmware: 1.35

  $ lsb_release -rd
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

  Happy to assist with investigations.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME
  Date: Thu Jan 20 19:37:09 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:5082]
  InstallationDate: Installed on 2021-06-24 (210 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20UF0014US
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET67W(1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UF0014US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.36
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1:
  dmi.product.family: ThinkPad X13 Gen 1
  dmi.product.name: 20UF0014US
  dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1
  dmi.product.version: ThinkPad X13 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+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 1958412] Re: [amdgpu] Flickering/noise on screen started in kernel 5.13

2022-01-25 Thread Mariusz

In my case the problem is severe. I can see login screen, but when I log
in I see a white noise screen. It renders my computer unusable. That is
unless I use older kernel.

There is how to do it: When your computer boots press escape (UEFI boot)
or shift (BIOS boot). You may have to try several times to press it in
right time. A menu should appear. Choose option 'Advanced options for
Ubuntu'. Then choose 'Ubuntu, with Linux 5.11.0-46-generic'.

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

Title:
  [amdgpu] Flickering/noise on screen started in kernel 5.13

Status in linux-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  After the kernel release 5.13.0-27-generic was installed today, the
  startup and shutdown processes finish with white noise screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jan 19 16:17:35 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:18b2]
  InstallationDate: Installed on 2022-01-19 (0 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: TP420UA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP420UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+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 1959033] [NEW] Bionic update: upstream stable patchset 2022-01-25

2022-01-25 Thread Kamal Mostafa

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2022-01-25

Ported from the following upstream stable releases:
v4.14.260, v4.19.223

   from git://git.kernel.org/

IB/qib: Use struct_size() helper
IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
net: usb: lan78xx: add Allied Telesis AT29M2-AF
can: kvaser_usb: get CAN clock frequency from device
HID: holtek: fix mouse probing
spi: change clk_disable_unprepare to clk_unprepare
IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
netfilter: fix regression in looped (broad|multi)cast's MAC handling
qlcnic: potential dereference null pointer of rx_queue->page_ring
net: accept UFOv6 packages in virtio_net_hdr_to_skb
net: skip virtio_net_hdr_set_proto if protocol already set
bonding: fix ad_actor_system option setting to default
fjes: Check for error irq
drivers: net: smc911x: Check for error irq
sfc: falcon: Check null pointer of rx_queue->page_ring
hwmon: (lm90) Fix usage of CONFIG2 register in detect function
ALSA: jack: Check the return value of kstrdup()
ALSA: drivers: opl3: Fix incorrect use of vp->state
Input: atmel_mxt_ts - fix double free in mxt_read_info_block
x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
usb: gadget: u_ether: fix race in setting MAC address in setup phase
KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
hwmon: (lm90) Do not report 'busy' status bit as alarm
ax25: NPD bug when detaching AX25 device
hamradio: defer ax25 kfree after unregister_netdev
hamradio: improve the incomplete fix to avoid NPD
phonet/pep: refuse to enable an unbound pipe
parisc: Correct completer in lws start
UBUNTU: upstream stable to v4.14.260, v4.19.223

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2022-01-25
+    from git://git.kernel.org/
  
-upstream stable patchset 2022-01-25
-from git://git.kernel.org/
+ IB/qib: Use struct_size() helper
+ IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
+ net: usb: lan78xx: add Allied Telesis AT29M2-AF
+ can: kvaser_usb: get CAN clock frequency from device
+ HID: holtek: fix mouse probing
+ spi: change clk_disable_unprepare to clk_unprepare
+ IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
+ netfilter: fix regression in looped (broad|multi)cast's MAC handling
+ qlcnic: potential dereference null pointer of rx_queue->page_ring
+ net: accept UFOv6 packages in virtio_net_hdr_to_skb
+ net: skip virtio_net_hdr_set_proto if protocol already set
+ bonding: fix ad_actor_system option setting to default
+ fjes: Check for error irq
+ drivers: net: smc911x: Check for error irq
+ sfc: falcon: Check null pointer of rx_queue->page_ring
+ hwmon: (lm90) Fix usage of CONFIG2 register in detect function
+ ALSA: jack: Check the return value of kstrdup()
+ ALSA: drivers: opl3: Fix incorrect use of vp->state
+ Input: atmel_mxt_ts - fix double free in mxt_read_info_block
+ x86/pkey: Fix undefined

[Kernel-packages] [Bug 1959034] [NEW] nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build

2022-01-25 Thread John Martin

Public bug reported:

Won't load newest kernel, have to boot via advancedthen this error
is received.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.13.0-27-generic
Date: Mon Jan 24 09:47:23 2022
Dependencies:
 
DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23:
 error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state 
*)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct 
drm_plane_state *)’ [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2021-02-14 (345 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
PackageVersion: 460.73.01-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-460
Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-460 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  Won't load newest kernel, have to boot via advancedthen this error
  is received.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.13.0-27-generic
  Date: Mon Jan 24 09:47:23 2022
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23:
 error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state 
*)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct 
drm_plane_state *)’ [-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2021-02-14 (345 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  PackageVersion: 460.73.01-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1959034/+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 1959030] Re: [SOF - sof-bytcht rt5651, playback] No sound at all

2022-01-25 Thread Ilya Lebedev

When booting into
5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux
Sound still working

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [SOF - sof-bytcht rt5651, playback] No sound at all

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  After last update sound stopped to work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ttrolka1260 F pulseaudio
   /dev/snd/pcmC1D0p:   ttrolka1260 F...m pulseaudio
   /dev/snd/controlC0:  ttrolka1260 F pulseaudio
   /dev/snd/timer:  ttrolka1260 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 25 20:29:29 2022
  InstallationDate: Installed on 2021-09-04 (143 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:rt5651 failed
  Symptom_Card: Built-in Audio - sof-bytcht rt5651
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ttrolka1260 F pulseaudio
   /dev/snd/pcmC1D0p:   ttrolka1260 F...m pulseaudio
   /dev/snd/controlC0:  ttrolka1260 F pulseaudio
   /dev/snd/timer:  ttrolka1260 f pulseaudio
  Symptom_Type: No sound at all
  Title: [SOF - sof-bytcht rt5651, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Digma12x.WJ3142.NFNKRCN01
  dmi.board.asset.tag: Default string
  dmi.board.name: CITI E401 ET4007EW
  dmi.board.vendor: Digma
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrDigma12x.WJ3142.NFNKRCN01:bd07/03/2018:br5.11:svnDigma:pnCITIE401ET4007EW:pvrDefaultstring:rvnDigma:rnCITIE401ET4007EW:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku1806078:
  dmi.product.family: CHT
  dmi.product.name: CITI E401 ET4007EW
  dmi.product.sku: 1806078
  dmi.product.version: Default string
  dmi.sys.vendor: Digma

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1959030/+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 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic

2022-01-25 Thread Simon Kammermeier

I can confirm that it works until 5.13.22 and from 5.13.23 onward
shutting down does not work.

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

Title:
  System Shutdown and resume hangs since Kernel linux-
  image-5.13.0-23-generic

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21.
  Since Version 5.13.0.23 System Shutdown and resume hangs. The System
  does not stop also after a long time.

  The last messages in recovery mode on the root console are:

  Reached target Power-off
  ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time
  Waiting for process systemd-udevd, systemd-udevd 

  Perhaps my attached dmesg and lsmod helps. All messages are in one file.
   
  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:59:05 2022
  InstallationDate: Installed on 2021-12-25 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+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 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match

2022-01-25 Thread Some Guy On The Net

This affects
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/index.php?1959017
(for some reason couldn't link the bug URL)

GitHub URL is: https://github.com/ubuntu/zsys/issues/220

** Also affects: zsys (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: github.com/ubuntu/zsys/issues #220
   https://github.com/ubuntu/zsys/issues/220

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

Title:
  When using HWE, zfs-kmod and zfs user tools versions must match

Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zsys package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.2 LTS

  I ran into a problem recently
  (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due
  to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11
  where the userspace tools don't match the zfs-kmod version. After the
  update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs-
  kmod-2.0.2-1ubuntu5

  My understanding from asking in the OpenZFS github is that the two
  versions must match.

  This bug is to figure out what to do for those of us who use HWE and
  zfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+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 1947206] Re: Updates to ib_peer_memory requested by Nvidia

2022-01-25 Thread dann frazier

It appears that the reason verification-needed-focal is applied here is
because these patches were included in the linux-intel flavor, whose
description says "A kernel image for Intel IOTG devices." I'm not sure
what the expectations are for verifying bugs with that flavor - should
they all be done on the target hardware? If so, I do not have access to
the hardware to do so.

For this specific issue, I'll go ahead and mark verified with the
following justification:

 (1) The only consumer of the IB Peer Memory interface at this time is
the nvidia driver stack, and we do not appear to provide pre-compiled
nvidia drivers for the -intel flavor at this time. Now, a user could
install an nvidia-dkms package and build their own modules but,

 (2) This appears to be the first version of linux-intel in the focal
series, so it can not possibly be a regression against an earlier
version.


** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Updates to ib_peer_memory requested by Nvidia

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Nvidia notified me via private email that they'd discovered some issues with 
the ib_peer_memory patch we are carrying in hirsute/impish and sent me a patch 
intended to resolve them. My knowledge of these changes is limited to what is 
mentioned in the commit message:

  - Allow clients to opt out of unmap during invalidation
  - Fix some bugs in the sequencing of mlx5 MRs
  - Enable ATS for peer memory

  [Test Case]
  ib_write_bw from the perftest package, rebuilt with CUDA support, can be used 
as a smoke test of this feature. I'll attach a sample test script here. I've 
verified this test passes with the kernels in the archive, and continues to 
pass with the provided patch applied.

  [Fix]
  Nvidia has emailed me fixes for both trees. They are not currently available 
in a public tree elsewhere, though I'm told at some point they should end up in 
a branch here:
    https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/

  [What could go wrong]
  The only known use case for ib_peer_memory are Nvidia GPU users making use of 
the GPU PeerDirect feature where GPUs can share memory with one another over an 
Infiniband network. Bugs here could cause problems (hangs, crashes, corruption) 
with such workloads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947206/+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 1959012] [NEW] MANA updates

2022-01-25 Thread Tim Gardner

Public bug reported:

SRU Justification

[Impact]

The MANA driver is missing 2 updates.

commit 6cc74443a7732d7e93bee3d0c3704a22cc7274d9 ("net: mana: Add RX fencing")
commit 9acfc57fa2b8944ed079cedbf846823ea32b8a31 ("net: mana: Fix memory leak in 
mana_hwc_create_wq")

[Test Plan]

Microsoft tested

[Where things could go wrong]

Fencing requests could get dropped or sent out of order.

[Other Info]

SF: #00324494

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: linux-azure (Ubuntu Impish)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress


** Tags: bot-stop-nagging

** Tags added: bot-stop-nagging

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

** Also affects: linux-azure (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux-azure (Ubuntu Impish)
   Status: New => In Progress

** Changed in: linux-azure (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Impish)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux-azure (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-azure (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  MANA updates

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Focal:
  New
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The MANA driver is missing 2 updates.

  commit 6cc74443a7732d7e93bee3d0c3704a22cc7274d9 ("net: mana: Add RX fencing")
  commit 9acfc57fa2b8944ed079cedbf846823ea32b8a31 ("net: mana: Fix memory leak 
in mana_hwc_create_wq")

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  Fencing requests could get dropped or sent out of order.

  [Other Info]

  SF: #00324494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959012/+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 1954757] Re: Missing overlays/README

2022-01-25 Thread Dave Jones

** Changed in: flash-kernel (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  Missing overlays/README

Status in flash-kernel package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Invalid
Status in linux-raspi source package in Focal:
  Fix Committed
Status in linux-raspi source package in Hirsute:
  Fix Committed
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [ Impact ]

  overlays/README is used by the 'dtoverlay' command to display info on
  available overlays and params.

  [ Test Case ]

  $ apt install libraspberrypi-bin
  $ dtoverlay -h uart0
  * Help file not found

  With the README present:
  $ dtoverlay -h uart0
  Name:   uart0

  Info:   Change the pin usage of uart0

  Usage:  dtoverlay=uart0,=

  Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 -
  default 14)

  rxd0_pinGPIO pin for RXD0 (15, 33 or 37 -
  default 15)

  pin_funcAlternative pin function - 4(Alt0) for 14&15,
  7(Alt3) for 32&33, 6(Alt2) for 36&37

  [ Where Problems Could Occur ]

  The output of the `dtoverlay` could be wrong but it's only
  informational so should have no negative impact.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954757/+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 1949075] Re: Bluetooth headset not autoconnecting on power-on on 21.10

2022-01-25 Thread Sebastien Bacher

Daniel could you check if that's a regression for any hardware or if
it's specific to some configuration?

** Tags removed: champagne rls-ii-incoming
** Tags added: rls-ii-notfixing

** Tags added: champagne

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
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/1949075

Title:
  Bluetooth headset not autoconnecting on power-on on 21.10

Status in bluez package in Ubuntu:
  New

Bug description:
  After moving to Impish, my bluetooth headset doesn't automatically
  connect when I power it on (it was working fine on hirsute).

  
  When I go to the bluetooth settings, select it and click connect, the first 
time it disconnects immediately and I see this line in bluetoothd log:

  Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb()
  Unable to get Hands-Free Voice gateway SDP record: Host is down

  After that, clicking the connect button again makes it work.

  I'm not sure where to find info to debug this furhter

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 28 13:57:34 2021
  InstallationDate: Installed on 2021-10-16 (11 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20F6CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2019
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET71W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X260
  dmi.product.name: 20F6CTO1WW
  dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:01:19:D5  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:56756 acl:285 sco:0 events:6453 errors:0
TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+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 1958768] Re: System fails to shutdown or reboot

2022-01-25 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Status: New => Confirmed

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

Title:
  System fails to shutdown or reboot

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  My system has suddenly stopped from powering off or rebooting. It hangs on 
"systemd-shutdown: waiting for process"
  I have tried several suggestions on the ubuntu forum to alleviate this - but 
none work.
  This seemed to begin after an update last week.
  I have waited 30 minutes or more and the messages :waiting for 
process:system-udevdworker[###] contine to be posted on the command line, but 
no stutdown occurs

  I have removed "quiet splash" from grub and can see that Shutdown
  Target is reached but then the system hangs before actual poweroff.

  Ubuntu 20.04.3 LTS Release 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 11:23:43 2022
  InstallationDate: Installed on 2021-04-17 (281 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958768/+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 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part

for jammy it's incl. in kernel 5.15.0-18.18

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

Title:
  [UBUNTU 20.04] KVM hardware diagnose data improvements for guest
  kernel - kernel part

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
  handled.

  * A fix is needed to enhance problem determination of guest kernel
  under KVM using DIAG 0x318 instruction execution.

  * The s390x diagnose 318 instruction sets the control program name
  code (CPNC) and control program version code (CPVC) to provide useful
  information regarding the OS during debugging.

  * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.

  [Fix]

  * In general the following 4 commits are needed:

  * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug 
statement for diag 318 CPNC data"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch

  * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove 
diag318 reset code"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch

  * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose 
0x318 sync and reset"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch

  * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag 
318: refactor struct"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch

  * For jammy, hirsute and impish only the first commit is needed, the
  others are already in.

  * For focal all 4 commits are needed, but since they do not apply
  cleanly on focal, the attached backports need to be used instead.

  [Test Case]

  * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.

  * And setup an Ubuntu KVM virtual machine on top.

  * It can then be observed if the CPNC (diag318 data) has been
  successfully set by looking at the s390dbf messages for the KVM guest.

  * The CPNC will always be 4 (denotes Linux environment).

  * Another way to test this is by running the sync_regs_test under
  tools/testing/selftests/kvm/s390x/sync_regs_test.   Just running the
  kernel self test suite can trigger this.

  [Where problems could occur]

  * The approach here is to provide additional debug and diagnose
  information on top.

  * Hence even if the diag318 changes are broken, the existing
  functionality shouldn't be harmed.

  * The changes themselves are relatively discernible and mostly
  introduce new structures.

  * However, with the functional changes broken code could be introduced
  (e.g. due to erroneous pointer arithmetic for example) that does not
  compile or causes crashes. But this is what the test builds are for
  (https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).

  * On top the diag318 diagnose data might not properly provided - maybe
  empty or wrong. Again that is what the test builds and the
  verification later is targeted at.

  * Since diag318 is s390x specific, all the modifications touch s390x
  code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
  arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
  diag.h). At least no other other architecture will be affected.

  * Well, there is one tiny bit of a common code change, but it's just a
  new define statement in include/uapi/linux/kvm.h ('#define
  KVM_CAP_S390_DIAG318 186').

  [Other]

  * Request was to add the patches to focal / 20.04, but to avoid
  potential regressions on upgrades, the patches need to be added to
  jammy, impish and hirsute, too.

  * As mentioned above, Jammy, Hirsute and Impish includes almost
  everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
  for diag 318 CPNC data".

  * Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
  invasive for Jammy, Hirsute and Impish, also because commit
  3fd8417f2c72 can be cleanly cherry-picked form there.

  * LP#1953338 is related to this bug and covers the qemu/KVM bits.
  __

  Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled.
  Fix needed to enhance problem determination of guest kernel under KVM

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [UBUNTU 20.04] KVM hardware diagnose data improvements for guest
  kernel - kernel part

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
  handled.

  * A fix is needed to enhance problem determination of guest kernel
  under KVM using DIAG 0x318 instruction execution.

  * The s390x diagnose 318 instruction sets the control program name
  code (CPNC) and control program version code (CPVC) to provide useful
  information regarding the OS during debugging.

  * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.

  [Fix]

  * In general the following 4 commits are needed:

  * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug 
statement for diag 318 CPNC data"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch

  * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove 
diag318 reset code"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch

  * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose 
0x318 sync and reset"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch

  * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag 
318: refactor struct"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch

  * For jammy, hirsute and impish only the first commit is needed, the
  others are already in.

  * For focal all 4 commits are needed, but since they do not apply
  cleanly on focal, the attached backports need to be used instead.

  [Test Case]

  * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.

  * And setup an Ubuntu KVM virtual machine on top.

  * It can then be observed if the CPNC (diag318 data) has been
  successfully set by looking at the s390dbf messages for the KVM guest.

  * The CPNC will always be 4 (denotes Linux environment).

  * Another way to test this is by running the sync_regs_test under
  tools/testing/selftests/kvm/s390x/sync_regs_test.   Just running the
  kernel self test suite can trigger this.

  [Where problems could occur]

  * The approach here is to provide additional debug and diagnose
  information on top.

  * Hence even if the diag318 changes are broken, the existing
  functionality shouldn't be harmed.

  * The changes themselves are relatively discernible and mostly
  introduce new structures.

  * However, with the functional changes broken code could be introduced
  (e.g. due to erroneous pointer arithmetic for example) that does not
  compile or causes crashes. But this is what the test builds are for
  (https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).

  * On top the diag318 diagnose data might not properly provided - maybe
  empty or wrong. Again that is what the test builds and the
  verification later is targeted at.

  * Since diag318 is s390x specific, all the modifications touch s390x
  code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
  arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
  diag.h). At least no other other architecture will be affected.

  * Well, there is one tiny bit of a common code change, but it's just a
  new define statement in include/uapi/linux/kvm.h ('#define
  KVM_CAP_S390_DIAG318 186').

  [Other]

  * Request was to add the patches to focal / 20.04, but to avoid
  potential regressions on upgrades, the patches need to be added to
  jammy, impish and hirsute, too.

  * As mentioned above, Jammy, Hirsute and Impish includes almost
  everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
  for diag 318 CPNC data".

  * Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
  invasive for Jammy, Hirsute and Impish, also because commit
  3fd8417f2c72 can be cleanly cherry-picked form there.

  * LP#1953338 is related to this bug and covers the qemu/KVM bits.
  __

  Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled.
  Fix

[Kernel-packages] [Bug 1958155] Re: Pod traffic not taking advantage of interfaces with multiple tx queues

** Changed in: linux-hwe-5.11 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Pod traffic not taking advantage of interfaces with multiple tx queues

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-hwe-5.11 source package in Impish:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/

  Performance is impacted when multiple TX queues are enabled.

  [Fix]
  commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx 
queue hint in veth_xmit")

  This patch is already scheduled for release in these stable kernel
  versions:

  linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record 
rx queue hint in veth_xmit
  linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record 
rx queue hint in veth_xmit
  linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record 
rx queue hint in veth_xmit
  linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record 
rx queue hint in veth_xmit

  [Test Plan]

  Upstream tested

  [Where things could go wrong]

  Transmit performance could be impacted in other ways.

  [Other Info]

  SF: #00326544

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958155/+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 1958461] Re: Hirsute update: upstream stable patchset 2022-01-19

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  Hirsute update: upstream stable patchset 2022-01-19

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-01-19

  Ported from the following upstream stable releases:
  v5.10.86, v5.15.9
  v5.10.87, v5.15.10
  v5.10.88, v5.15.11

     from git://git.kernel.org/

  netfilter: selftest: conntrack_vrf.sh: fix file permission
  UBUNTU: upstream stable to v5.10.86, v5.15.9
  nfc: fix segfault in nfc_genl_dump_devices_done
  drm/msm/dsi: set default num_data_lanes
  KVM: arm64: Save PSTATE early on exit
  s390/test_unwind: use raw opcode instead of invalid instruction
  Revert "tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP"
  net/mlx4_en: Update reported link modes for 1/10G
  ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid
  ALSA: hda/hdmi: fix HDA codec entry table order for ADL-P
  parisc/agp: Annotate parisc agp init functions with __init
  i2c: rk3x: Handle a spurious start completion interrupt flag
  net: netlink: af_netlink: Prevent empty skb by adding a check on len.
  drm/amd/display: Fix for the no Audio bug with Tiled Displays
  drm/amd/display: add connector type check for CRC source set
  tracing: Fix a kmemleak false positive in tracing_map
  staging: most: dim2: use device release method
  bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc
  fuse: make sure reclaim doesn't write the inode
  hwmon: (dell-smm) Fix warning on /proc/i8k creation error
  ethtool: do not perform operations on net devices being unregistered
  perf inject: Fix itrace space allowed for new attributes
  perf intel-pt: Fix some PGE (packet generation enable/control flow packets) 
usage
  perf intel-pt: Fix sync state when a PSB (synchronization) packet is found
  perf intel-pt: Fix intel_pt_fup_event() assumptions about setting state type
  perf intel-pt: Fix state setting when receiving overflow (OVF) packet
  perf intel-pt: Fix next 'err' value, walking trace
  perf intel-pt: Fix missing 'instruction' events with 'q' option
  perf intel-pt: Fix error timestamp setting on the decoder error path
  memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER
  memblock: align freed memory map on pageblock boundaries with SPARSEMEM
  memblock: ensure there is no overflow in memblock_overlaps_region()
  arm: extend pfn_valid to take into account freed memory map alignment
  arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
  hwmon: (corsair-psu) fix plain integer used as NULL pointer
  drm/msm/dp: Avoid unpowered AUX xfers that caused crashes
  UBUNTU: upstream stable to v5.10.87, v5.15.10
  KVM: selftests: Make sure kvm_create_max_vcpus test won't hit RLIMIT_NOFILE
  KVM: downgrade two BUG_ONs to WARN_ON_ONCE
  mac80211: fix regression in SSN handling of addba tx
  mac80211: mark TX-during-stop for TX in in_reconfig
  mac80211: send ADDBA requests using the tid/queue of the aggregation session
  mac80211: validate extended element ID is present
  firmware: arm_scpi: Fix string overflow in SCPI genpd driver
  bpf: Fix signed bounds propagation after mov32
  bpf: Make 32->64 bounds propagation slightly more robust
  bpf, selftests: Add test case trying to taint map value pointer
  virtio_ring: Fix querying of maximum DMA mapping size for virtio device
  vdpa: check that offsets are within bounds
  recordmcount.pl: look for jgnop instruction as well as bcrl on s390
  dm btree remove: fix use after free in rebalance_children()
  audit: improve robustness of the audit queue handling
  arm64: dts: imx8m: correct assigned clocks for FEC
  arm64: dts: imx8mp-evk: Improve the Ethernet PHY description
  arm64: dts: rockchip: remove mmc-hs400-enhanced-strobe from rk3399-khadas-edge
  arm64: dts: rockchip: fix rk3308-roc-cc vcc-sd supply
  arm64: dts: rockchip: fix rk3399-leez-p710 vcc3v3-lan supply
  arm64: dts: rockchip: fix audio-supply for Rock Pi 4
  mac80211: track only QoS data frames for admission control
  tee: amdtee: fix an IS_ERR() vs NULL bug
  ceph: fix duplicate increment of opened_inodes metric
  ceph: initialize pathlen variable in reconnect_caps_cb
  ARM:

[Kernel-packages] [Bug 1957842] Re: Hirsute update: upstream stable patchset 2022-01-13

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  Hirsute update: upstream stable patchset 2022-01-13

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-01-13

  Ported from the following upstream stable releases:
  v5.10.85, v5.15.8

     from git://git.kernel.org/

  usb: gadget: uvc: fix multiple opens
  HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
  HID: google: add eel USB id
  HID: add hid_is_usb() function to make it simpler for USB detection
  HID: add USB_HID dependancy to hid-prodikeys
  HID: add USB_HID dependancy to hid-chicony
  HID: add USB_HID dependancy on some USB HID drivers
  HID: bigbenff: prevent null pointer dereference
  HID: wacom: fix problems when device is not a valid USB device
  HID: check for valid USB device for many HID drivers
  nft_set_pipapo: Fix bucket load in AVX2 lookup routine for six 8-bit groups
  IB/hfi1: Insure use of smp_processor_id() is preempt disabled
  IB/hfi1: Fix early init panic
  IB/hfi1: Fix leak of rcvhdrtail_dummy_kvaddr
  can: kvaser_usb: get CAN clock frequency from device
  can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct 
stats->{rx,tx}_errors counter
  can: sja1000: fix use after free in ems_pcmcia_add_card()
  x86/sme: Explicitly map new EFI memmap table as encrypted
  drm/amd/amdkfd: adjust dummy functions' placement
  drm/amdkfd: separate kfd_iommu_resume from kfd_resume
  drm/amdgpu: add amdgpu_amdkfd_resume_iommu
  drm/amdgpu: move iommu_resume before ip init/resume
  drm/amdgpu: init iommu after amdkfd device init
  drm/amdkfd: fix boot failure when iommu is disabled in Picasso.
  nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
  selftests: netfilter: add a vrf+conntrack testcase
  vrf: don't run conntrack on vrf with !dflt qdisc
  bpf, x86: Fix "no previous prototype" warning
  bpf: Fix the off-by-two error in range markings
  ice: ignore dropped packets during init
  bonding: make tx_rebalance_counter an atomic
  nfp: Fix memory leak in nfp_cpp_area_cache_add()
  seg6: fix the iif in the IPv6 socket control block
  udp: using datalen to cap max gso segments
  netfilter: conntrack: annotate data-races around ct->timeout
  iavf: restore MSI state on reset
  iavf: Fix reporting when setting descriptor count
  IB/hfi1: Correct guard on eager buffer deallocation
  devlink: fix netns refcount leak in devlink_nl_cmd_reload()
  net/sched: fq_pie: prevent dismantle issue
  KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush 
hypercall
  mm: bdi: initialize bdi_min_ratio when bdi is unregistered
  ALSA: ctl: Fix copy of updated id with element read/write
  ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
  ALSA: hda/realtek: Fix quirk for TongFang PHxTxX1
  ALSA: pcm: oss: Fix negative period/buffer sizes
  ALSA: pcm: oss: Limit the period size to 16MB
  ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
  scsi: qla2xxx: Format log strings only if needed
  btrfs: clear extent buffer uptodate when we fail to write it
  btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
  md: fix update super 1.0 on rdev size change
  nfsd: fix use-after-free due to delegation race
  nfsd: Fix nsfd startup race (again)
  tracefs: Have new files inherit the ownership of their parent
  mmc: renesas_sdhi: initialize variable properly when tuning
  clk: qcom: regmap-mux: fix parent clock lookup
  drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
  can: pch_can: pch_can_rx_normal: fix use after free
  can: m_can: Disable and ignore ELO interrupt
  libata: add horkage for ASMedia 1092
  wait: add wake_up_pollfree()
  UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
  binder: use wake_up_pollfree()
  signalfd: use wake_up_pollfree()
  aio: keep poll requests on waitqueue until completed
  aio: fix use-after-free due to missing POLLFREE handling
  net: mvpp2: fix XDP rx queues registering
  tracefs: Set all files to the same group ownership as the mount option
  block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
  scsi: pm80xx: Do not call scsi_remove_host() in pm8001_alloc()
  scsi:

[Kernel-packages] [Bug 1956800] Re: Hirsute update: upstream stable patchset 2022-01-07

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  Hirsute update: upstream stable patchset 2022-01-07

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-01-07

  Ported from the following upstream stable releases:
  v5.10.84, v5.15.7

     from git://git.kernel.org/

  NFSv42: Fix pagecache invalidation after COPY/CLONE
  can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM
  gfs2: release iopen glock early in evict
  gfs2: Fix length of holes reported at end-of-file
  powerpc/pseries/ddw: Revert "Extend upper limit for huge DMA window for 
persistent memory"
  drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY
  mac80211: do not access the IV when it was stripped
  net/smc: Transfer remaining wait queue entries during fallback
  atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait
  net: return correct error code
  platform/x86: thinkpad_acpi: Add support for dual fan control
  platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep
  s390/setup: avoid using memblock_enforce_memory_limit
  btrfs: check-integrity: fix a warning on write caching disabled disk
  thermal: core: Reset previous low and high trip during thermal zone init
  scsi: iscsi: Unblock session then wake up error handler
  drm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
  drm/amd/amdgpu: fix potential memleak
  ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile
  ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in 
hns_dsaf_ge_srst_by_port()
  ipv6: check return value of ipv6_skip_exthdr
  net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of 
bound
  net: ethernet: dec: tulip: de4x5: fix possible array overflows in 
type3_infoblock()
  perf inject: Fix ARM SPE handling
  perf hist: Fix memory leak of a perf_hpp_fmt
  perf report: Fix memory leaks around perf_tip()
  net/smc: Avoid warning of possible recursive locking
  ACPI: Add stubs for wakeup handler functions
  vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit
  kprobes: Limit max data_size of the kretprobe instances
  rt2x00: do not mark device gone on EPROTO errors during start
  cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink()
  s390/pci: move pseudo-MMIO to prevent MIO overlap
  fget: check that the fd still exists after getting a ref to it
  sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl
  sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl
  ipv6: fix memory leak in fib6_rule_suppress
  drm/amd/display: Allow DSC on supported MST branch devices
  KVM: Disallow user memslot with size that exceeds "unsigned long"
  KVM: nVMX: Flush current VPID (L1 vs. L2) for KVM_REQ_TLB_FLUSH_GUEST
  KVM: x86: Use a stable condition around all VT-d PI paths
  KVM: arm64: Avoid setting the upper 32 bits of TCR_EL2 and CPTR_EL2 to 1
  KVM: X86: Use vcpu->arch.walk_mmu for kvm_mmu_invlpg()
  tracing/histograms: String compares should not care about signed values
  wireguard: selftests: increase default dmesg log size
  wireguard: allowedips: add missing __rcu annotation to satisfy sparse
  wireguard: selftests: actually test for routing loops
  wireguard: selftests: rename DEBUG_PI_LIST to DEBUG_PLIST
  wireguard: device: reset peer src endpoint when netns exits
  wireguard: receive: use ring buffer for incoming handshakes
  wireguard: receive: drop handshakes if queue lock is contended
  wireguard: ratelimiter: use kvcalloc() instead of kvzalloc()
  i2c: stm32f7: flush TX FIFO upon transfer errors
  i2c: stm32f7: recover the bus on access timeout
  i2c: stm32f7: stop dma transfer in case of NACK
  i2c: cbus-gpio: set atomic transfer callback
  natsemi: xtensa: fix section mismatch warnings
  tcp: fix page frag corruption on page fault
  net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings()
  net: mpls: Fix notifications when deleting a device
  siphash: use _unaligned version by default
  arm64: ftrace: add missing BTIs
  net/mlx4_en: Fix an use-after-free bug in mlx4_en_try_alloc_resources()
  selftests: net: Correct case name
  mt76: mt7915: fix NULL pointer

[Kernel-packages] [Bug 1956513] Re: Hirsute update: upstream stable patchset 2022-01-05

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  Hirsute update: upstream stable patchset 2022-01-05

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2022-01-05

  Ported from the following upstream stable releases:
  v5.10.83, v5.15.6

     from git://git.kernel.org/

  ACPI: Get acpi_device's parent from the parent field
  USB: serial: option: add Telit LE910S1 0x9200 composition
  USB: serial: option: add Fibocom FM101-GL variants
  usb: dwc2: gadget: Fix ISOC flow for elapsed frames
  usb: dwc2: hcd_queue: Fix use of floating point literal
  usb: dwc3: gadget: Ignore NoStream after End Transfer
  usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
  usb: dwc3: gadget: Fix null pointer exception
  net: nexthop: fix null pointer dereference when IPv6 is not enabled
  usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in probe
  usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
  usb: hub: Fix usb enumeration issue due to address0 race
  usb: hub: Fix locking issues with address0_mutex
  binder: fix test regression due to sender_euid change
  ALSA: ctxfi: Fix out-of-range access
  ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
  ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
  media: cec: copy sequence field for the reply
  Revert "parisc: Fix backtrace to always include init funtion names"
  HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
  staging/fbtft: Fix backlight
  staging: greybus: Add missing rwsem around snd_ctl_remove() calls
  staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
  fuse: release pipe buf after last use
  xen: don't continue xenstore initialization in case of errors
  xen: detect uninitialized xenbus in xenbus_init
  KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
  tracing/uprobe: Fix uprobe_perf_open probes iteration
  tracing: Fix pid filtering when triggers are attached
  mmc: sdhci-esdhc-imx: disable CMDQ support
  mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
  mdio: aspeed: Fix "Link is Down" issue
  powerpc/32: Fix hardlockup on vmap stack overflow
  PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
  PCI: aardvark: Implement re-issuing config requests on CRS response
  PCI: aardvark: Simplify initialization of rootcap on virtual bridge
  PCI: aardvark: Fix link training
  proc/vmcore: fix clearing user buffer by properly using clear_user()
  netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
  netfilter: ctnetlink: do not erase error code with EINVAL
  netfilter: ipvs: Fix reuse connection if RS weight is 0
  netfilter: flowtable: fix IPv6 tunnel addr match
  ARM: dts: BCM5301X: Fix I2C controller interrupt
  ARM: dts: BCM5301X: Add interrupt properties to GPIO node
  ARM: dts: bcm2711: Fix PCIe interrupts
  ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
  ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
  ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
  ASoC: codecs: wcd934x: return error code correctly from hw_params
  net: ieee802154: handle iftypes as u32
  firmware: arm_scmi: pm: Propagate return value to caller
  NFSv42: Don't fail clone() unless the OP_CLONE operation failed
  ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
  drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
  scsi: mpt3sas: Fix kernel panic during drive powercycle test
  drm/vc4: fix error code in vc4_create_object()
  net: marvell: prestera: fix double free issue on err path
  iavf: Prevent changing static ITR values if adaptive moderation is on
  ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
  mptcp: fix delack timer
  firmware: smccc: Fix check for ARCH_SOC_ID not implemented
  ipv6: fix typos in __ip6_finish_output()
  nfp: checking parameter process for rx-usecs/tx-usecs is invalid
  net: stmmac: fix system hang caused by eee_ctrl_timer during suspend/resume
  net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
  net: ipv6: add fib6_nh_release_dsts stub
  net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
  ice:

[Kernel-packages] [Bug 1958990] [NEW] Add sunrpc module parameters for NFSv3 nconnect

2022-01-25 Thread Tim Gardner

Public bug reported:

SRU Justification

[Impact]

Microsoft has requested the addition of 2 module parameters to sunrpc.
The primary purpose of which is to restrict or pin NFSv3 TCP connections
to one server in order to take advantage of local server connection
caching. In the presence of a load balancer, round robin connection
requests defeats the advantages of local caching.

[Test Plan]

Microsoft tested

[Where things could go wrong]

NFSv3 connection attempts could be slow or fail altogether.

[Other Info]

SF: #00312346

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-azure (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: linux-azure (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Undecided
 Status: New


** Tags: bot-stop-nagging

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

** Also affects: linux-azure (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Tags added: bot-stop-nagging

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

Title:
  Add sunrpc module parameters for NFSv3 nconnect

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  New
Status in linux-azure source package in Impish:
  New
Status in linux-azure source package in Jammy:
  New

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the addition of 2 module parameters to sunrpc.
  The primary purpose of which is to restrict or pin NFSv3 TCP
  connections to one server in order to take advantage of local server
  connection caching. In the presence of a load balancer, round robin
  connection requests defeats the advantages of local caching.

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  NFSv3 connection attempts could be slow or fail altogether.

  [Other Info]

  SF: #00312346

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958990/+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 1956525] Re: amdgpu crash in dp_set_panel_mode from perform_link_training_with_retries

2022-01-25 Thread Jof Thibaut

After updating the kernel to version 5.13.0-27, the problem no longer
appears, thank you very much for the backport of this kernel .

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

Title:
  amdgpu crash in dp_set_panel_mode from
  perform_link_training_with_retries

Status in linux-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  From time to time after waking up the screen on Ubuntu Budgie, the
  refresh rate goes from 120hz to 48hz followed by a flashing of the
  screen.

  With dmesg this output appear:

  [12947.570681] WARNING: CPU: 6 PID: 891 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:4282 
dp_set_panel_mode+0xbb/0xd0 [amdgpu]
  [12947.571031] Modules linked in: ses enclosure scsi_transport_sas uas 
usb_storage btrfs blake2b_generic xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs 
msdos jfs xfs libcrc32c nls_iso8859_1 nvidia_uvm(POE) nvidia_drm(POE) 
nvidia_modeset(POE) intel_rapl_msr intel_rapl_common nvidia(POE) edac_mce_amd 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi 
snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation 
soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep soundwire_bus 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi kvm_amd amdgpu snd_seq snd_seq_device iommu_v2 
gpu_sched snd_timer drm_ttm_helper ttm kvm snd drm_kms_helper crct10dif_pclmul 
ghash_clmulni_intel cec rc_core joydev asus_nb_wmi hid_multitouch efi_pstore 
i2c_algo_bit wmi_bmof aesni_intel fb_sys_fops crypto_simd syscopyarea cryptd 
sysfillrect glue_helper k10temp soundcore sysimgblt input_leds ccp rapl 
serio_raw asus_wireless
  [12947.571130]  mac_hid sch_fq_codel msr parport_pc ppdev lp drm parport 
ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid 
hid_generic mfd_aaeon asus_wmi sparse_keymap crc32_pclmul nvme r8169 ahci 
i2c_hid xhci_pci xhci_pci_renesas nvme_core libahci i2c_piix4 realtek wmi video 
hid
  [12947.571172] CPU: 6 PID: 891 Comm: Xorg Tainted: P   OE 
5.11.0-44-generic #48~20.04.2-Ubuntu
  [12947.571178] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming 
FX505DT_FX505DT/FX505DT, BIOS FX505DT.316 01/28/2021
  [12947.571181] RIP: 0010:dp_set_panel_mode+0xbb/0xd0 [amdgpu]
  [12947.571538] Code: fe b9 01 00 00 00 48 8d 55 e7 48 89 df 44 09 e0 be 0a 01 
00 00 44 89 45 dc 88 45 e7 e8 8e b8 ff ff 44 8b 45 dc 83 f8 01 74 a1 <0f> 0b eb 
9d e8 7c 99 3b d5 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f
  [12947.571543] RSP: 0018:a3d881a17660 EFLAGS: 00010282
  [12947.571548] RAX:  RBX: 9841d0ab9800 RCX: 
010a
  [12947.571551] RDX: 9841c3a0eba0 RSI: c079367b RDI: 
0100
  [12947.571554] RBP: a3d881a17688 R08: 0001 R09: 
fffb
  [12947.571556] R10: 0001 R11:  R12: 
0001
  [12947.571559] R13: a3d881a176e8 R14: 0001 R15: 
9841d0ab9800
  [12947.571562] FS:  7f49db6fda40() GS:9844cf38() 
knlGS:
  [12947.571572] CS:  0010 DS:  ES:  CR0: 80050033
  [12947.571575] CR2: 7f6f24003f88 CR3: 00010a03 CR4: 
003506e0
  [12947.571579] Call Trace:
  [12947.571586]  perform_link_training_with_retries+0xa7/0x140 [amdgpu]
  [12947.571920]  enable_link_dp+0xe2/0x230 [amdgpu]
  [12947.572255]  core_link_enable_stream+0x699/0x830 [amdgpu]
  [12947.572588]  dce110_apply_ctx_to_hw+0x5c1/0x600 [amdgpu]
  [12947.572923]  ? dcn10_verify_allow_pstate_change_high+0x22/0x350 [amdgpu]
  [12947.573275]  ? dcn10_wait_for_mpcc_disconnect+0x43/0x140 [amdgpu]
  [12947.573626]  dc_commit_state_no_check+0x28f/0xa00 [amdgpu]
  [12947.573961]  dc_commit_state+0x96/0xb0 [amdgpu]
  [12947.574295]  amdgpu_dm_atomic_commit_tail+0x56d/0x1510 [amdgpu]
  [12947.574643]  ? ktime_get_raw+0x34/0x90
  [12947.574652]  ? ttm_bo_mem_compat+0x28/0x60 [ttm]
  [12947.574663]  ? ttm_bo_validate+0x4c/0x160 [ttm]
  [12947.574676]  ? dm_plane_helper_prepare_fb+0x1b4/0x270 [amdgpu]
  [12947.575021]  ? _cond_resched+0x19/0x30
  [12947.575029]  ? wait_for_completion_timeout+0x3a/0x100
  [12947.575033]  ? _cond_resched+0x19/0x30
  [12947.575039]  commit_tail+0x99/0x130 [drm_kms_helper]
  [12947.575068]  drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper]
  [12947.575096]  drm_atomic_commit+0x4a/0x50 [drm]
  [12947.575149]  drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper]
  [12947.575177]  drm_mode_setcrtc+0x20d/0x7e0 [drm]
  [12947.575223]  ? drm_mode_getcrtc+0x190/0x190 [drm]
  [12947.575267]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [12947.575308]  drm_ioctl+0x257/0x410 [drm]
  [12947.575349]  ? drm_mode_getcrtc+0x190/0x190 [drm]
  [12947.575395]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  [12947.575665]  __x64_sys_ioctl+0x91/0xc0
  [12947.575675]  do_syscall_64+0x38/0x90

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-01-25 Thread Alberto Milone

** Description changed:

  [Impact]
  
-  * In any Ubuntu series, if user using a old GPU (which supported by
+  * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB
  GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver
  correctly.
  
  [Test Plan]
  
-  * install nvidia-390 on nvidia-390 supported system.
-  * prime-select on-demand
-  * reboot
-  * glxinfo
-  * after applying this patch, it will fall back to "ON" mode after reboot.
+  * install nvidia-390 on nvidia-390 supported system.
+  * prime-select on-demand
+  * reboot
+  * glxinfo
+  * after applying this patch, it will fall back to "ON" mode after reboot.
  
  [Where problems could occur]
-  * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
-  * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
+  * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
+  * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
+ * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.
+ 
  
  ---
  
  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.
  
  It impacts Jammy and Impish so far.
  
  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo
  
  [Expected result]
  Shows intel or nvidia drives monitor
  
  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig
  
  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Triaged
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  
  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1958911] Re: BCM4356 wifi chipset fail to connect

This problem has been going on since before I installed lowlatency.
I use USB-wifi-dongle to send this message.

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64

[Kernel-packages] [Bug 1954926] Re: Focal: CIFS stable updates

2022-01-25 Thread Tim Gardner

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Focal: CIFS stable updates

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Backport several stable updates to v5.4 Azure

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  Samba connections could fail

  [Other Info]

  SF: #00324495

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954926/+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 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-01-25 Thread Alberto Milone

@Robie I am not sure what rejecting the uploads actually accomplished
(other than forcing me to re-upload the exact same sources) for
something that can be amended in the bug description on Launchpad.

This said, I did not notice that the section was missing. While mistakes
can happen, please restrain from implying that I "just sponsor and
leave". Thank you.

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Impish:
  New
Status in ubuntu-drivers-common source package in Impish:
  Triaged
Status in nvidia-settings source package in Jammy:
  New
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1958911] Re: BCM4356 wifi chipset fail to connect

and I attach Journal log.


** Attachment added: "journald_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958911/+attachment/5557340/+files/journald_log.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType:

[Kernel-packages] [Bug 1958911] Re: BCM4356 wifi chipset fail to connect

I ran "apport-collect 1958911"

and
I tried follow command.

~$ sudo nmcli general logging level TRACE
~$ nmcli device wifi connect elecom-b3306f password foobarcorrectpass
エラー: 接続のアクティベーションに失敗しました: (7) シークレットが必要でしたが入力されませんでした.
~$ nmcli device wifi connect elecom-b3306f password foobarcorrectpass
エラー: 接続のアクティベーションに失敗しました: (7) シークレットが必要でしたが入力されませんでした.
~$ nmcli device wifi
IN-USE  BSSID  SSID  MODE  CHAN  RATE   
 SIGNAL  BARS  SECURITY
04:AB:18:xx:xx:xx  elecom-b3306f インフラ  10270 Mbit/s  92 
 ▂▄▆█  WPA2
xx:xx:xx:xx:xx:xx  foo   インフラ  2 270 Mbit/s  69 
 ▂▄▆_  WPA2
xx:xx:xx:xx:xx:xx  foofooインフラ  1 130 Mbit/s  27 
 ▂___  WPA1 WPA2
xx:xx:xx:xx:xx:xx  foofoofoo インフラ  1 65 Mbit/s   27 
 ▂___  WPA2
xx:xx:xx:xx:xx:xx  foofoofoofoofoofooインフラ  10130 Mbit/s  22 
 ▂___  WPA2
xx:xx:xx:xx:xx:xx  bar   インフラ  1 195 Mbit/s  20 
 ▂___  WPA1 WPA2
xx:xx:xx:xx:xx:xx  barbarインフラ  3 405 Mbit/s  19 
 ▂___  WPA1 WPA2
xx:xx:xx:xx:xx:xx  barbarbar インフラ  3 54 Mbit/s   19 
 ▂___  WEP
xx:xx:xx:xx:xx:xx  barbarbarbar  インフラ  2 130 Mbit/s  17 
 ▂___  WPA2
xx:xx:xx:xx:xx:xx  barbarbarbarbar   インフラ  9 130 Mbit/s  15 
 ▂___  WPA2


Japanese message "シークレットが必要でしたが入力されませんでした." means "Secret is needed, but there 
is not it."

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan'

[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part

** Attachment added: "test_focal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5557339/+files/test_focal.txt

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

Title:
  [UBUNTU 20.04] KVM hardware diagnose data improvements for guest
  kernel - kernel part

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
  handled.

  * A fix is needed to enhance problem determination of guest kernel
  under KVM using DIAG 0x318 instruction execution.

  * The s390x diagnose 318 instruction sets the control program name
  code (CPNC) and control program version code (CPVC) to provide useful
  information regarding the OS during debugging.

  * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.

  [Fix]

  * In general the following 4 commits are needed:

  * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug 
statement for diag 318 CPNC data"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch

  * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove 
diag318 reset code"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch

  * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose 
0x318 sync and reset"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch

  * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag 
318: refactor struct"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch

  * For jammy, hirsute and impish only the first commit is needed, the
  others are already in.

  * For focal all 4 commits are needed, but since they do not apply
  cleanly on focal, the attached backports need to be used instead.

  [Test Case]

  * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.

  * And setup an Ubuntu KVM virtual machine on top.

  * It can then be observed if the CPNC (diag318 data) has been
  successfully set by looking at the s390dbf messages for the KVM guest.

  * The CPNC will always be 4 (denotes Linux environment).

  * Another way to test this is by running the sync_regs_test under
  tools/testing/selftests/kvm/s390x/sync_regs_test.   Just running the
  kernel self test suite can trigger this.

  [Where problems could occur]

  * The approach here is to provide additional debug and diagnose
  information on top.

  * Hence even if the diag318 changes are broken, the existing
  functionality shouldn't be harmed.

  * The changes themselves are relatively discernible and mostly
  introduce new structures.

  * However, with the functional changes broken code could be introduced
  (e.g. due to erroneous pointer arithmetic for example) that does not
  compile or causes crashes. But this is what the test builds are for
  (https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).

  * On top the diag318 diagnose data might not properly provided - maybe
  empty or wrong. Again that is what the test builds and the
  verification later is targeted at.

  * Since diag318 is s390x specific, all the modifications touch s390x
  code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
  arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
  diag.h). At least no other other architecture will be affected.

  * Well, there is one tiny bit of a common code change, but it's just a
  new define statement in include/uapi/linux/kvm.h ('#define
  KVM_CAP_S390_DIAG318 186').

  [Other]

  * Request was to add the patches to focal / 20.04, but to avoid
  potential regressions on upgrades, the patches need to be added to
  jammy, impish and hirsute, too.

  * As mentioned above, Jammy, Hirsute and Impish includes almost
  everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
  for diag 318 CPNC data".

  * Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
  invasive for Jammy, Hirsute and Impish, also because commit
  3fd8417f2c72 can be cleanly cherry-picked form there.

  * LP#1953338 is related to this bug and covers the qemu/KVM bits.
  __

  Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled.
  Fix needed to enhance

[Kernel-packages] [Bug 1958911] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1958911/+attachment/5557335/+files/RfKill.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557338/+files/acpidump.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557329/+files/ProcCpuinfo.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557332/+files/ProcInterrupts.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion:

[Kernel-packages] [Bug 1958911] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557337/+files/WifiSyslog.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557330/+files/ProcCpuinfoMinimal.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion:

[Kernel-packages] [Bug 1958911] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1958911/+attachment/5557328/+files/PaInfo.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557331/+files/ProcEnviron.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557333/+files/ProcModules.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557334/+files/PulseList.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1958911/+attachment/5557336/+files/UdevDb.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1958911/+attachment/5557322/+files/CRDA.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture:

[Kernel-packages] [Bug 1958911] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557324/+files/IwConfig.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557327/+files/Lsusb-v.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1958911/+attachment/5557325/+files/Lspci.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture:

[Kernel-packages] [Bug 1958911] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557326/+files/Lspci-vt.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1958911/+attachment/5557323/+files/CurrentDmesg.txt

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71

[Kernel-packages] [Bug 1958911] Re: BCM4356 wifi chipset fail to connect

apport information

** Tags added: apport-collected impish staging

** Description changed:

  My machine fails to connect wifi network.
  
  I use Kubuntu 21.10.
  
  Here are my machine's information.
  
  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac
  
  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02
  
  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  iwa 906 F pulseaudio
+  /dev/snd/controlC0:  iwa 906 F pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: KDE
+ Dependencies:
+  
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-12-19

[Kernel-packages] [Bug 1950792] Re: No boot possible - Cannot open root device

2022-01-25 Thread Alberto Donato

>From what I see, this could be indeed an issue with missing driver for
the specific network card in the initrd.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: maas
   Status: Incomplete => Triaged

** Changed in: maas
   Importance: Undecided => Medium

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

Title:
  No boot possible - Cannot open root device

Status in MAAS:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  MaaS cannot boot on my X11DPi-NT and will therefore fail to
  commission. It will instantly fail after grub.

  It will fail to boot saying that is not able to open root device. I
  even tried supplying the squashfs via python on a different port as
  the url is somehow cut off a bit, but to no avail. The python
  webserver doesn't even see any connection try.

  ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs
  python webserver: python3 -m http.server 8080)

  Steps to reproduce:

  1. Setup maas ;)
  2. Try to commision server
  3. See the kernel and initrd download fly by 
  4. Boom kernel panic

  Hardware:
  Supermicro X11DPi-NT with UEFI http Networkboot enabled
  NIC: Intel X722

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1950792/+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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

2022-01-25 Thread You-Sheng Yang

Already in jammy branch but not yet released.

** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-firmware (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-firmware (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.14 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => Invalid

** Changed in: linux-firmware (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-firmware (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-oem-5.14 (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1957026/+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 1958977] [NEW] Jammy update: v5.15.16 upstream stable release

2022-01-25 Thread Paolo Pisati

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.16 upstream stable release
   from git://git.kernel.org/


Linux 5.15.16
mtd: fixup CFI on ixp4xx
ALSA: hda/realtek: Re-order quirk entries for Lenovo
ALSA: hda/realtek: Add quirk for Legion Y9000X 2020
ALSA: hda/tegra: Fix Tegra194 HDA reset failure
ALSA: hda: ALC287: Add Lenovo IdeaPad Slim 9i 14ITL5 speaker quirk
ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after 
reboot from Windows
ALSA: hda/realtek: Use ALC285_FIXUP_HP_GPIO_LED on another HP laptop
ALSA: hda/realtek: Add speaker fixup for some Yoga 15ITL5 devices
KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
perf annotate: Avoid TUI crash when navigating in the annotation of recursive 
functions
firmware: qemu_fw_cfg: fix kobject leak in probe error path
firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
firmware: qemu_fw_cfg: fix sysfs information leak
rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
media: uvcvideo: fix division by zero at stream start
video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
9p: only copy valid iattrs in 9P2000.L setattr implementation
remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP
KVM: s390: Clarify SIGP orders versus STOP/RESTART
KVM: x86: don't print when fail to read/write pv eoi memory
KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest
KVM: x86: Register perf callbacks after calling vendor's hardware_setup()
perf: Protect perf_guest_cbs with RCU
vfs: fs_context: fix up param length parsing in legacy_parse_param
remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided
orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
drm/amd/display: explicitly set is_dsc_supported to false before use
devtmpfs regression fix: reconfigure on each mount

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Jammy update: v5.15.16 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.16 upstream stable release
 from git://git.kernel.org/

  
  Linux 5.15.16
  mtd: fixup CFI on ixp4xx
  ALSA: hda/realtek: Re-order quirk entries for Lenovo
  ALSA: hda/realtek: Add quirk for Legion Y9000X 2020
  ALSA: hda/tegra: Fix Tegra194 HDA reset failure
  ALSA: hda: ALC287: Add Lenovo IdeaPad Slim 9i 14ITL5 speaker quirk
  ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after 
reboot from Windows
  ALSA: hda/realtek: Use ALC285_FIXUP_HP_GPIO_LED on another HP laptop
  ALSA: hda/realtek: Add speaker fixup for some Yoga 15ITL5 devices
  KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
  perf annotate: Avoid TUI crash when navigating in the annotation of recursive 
functions
  firmware: qemu_fw_cfg: fix kobject leak in probe error path
  firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
  firmware: qemu_fw_cfg: fix sysfs information leak
  rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
  media: uvcvideo: fix division by zero at stream start
  video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
  9p: only copy valid iattrs in 9P2000.L setattr implementation
  remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP
  KVM: s390: Clarify SIGP orders versus STOP/RESTART
  KVM: x86: don't print when fail to read/write pv eoi memory
  KVM: x86: Register Processor Trace interrupt hook iff PT

[Kernel-packages] [Bug 1958975] Re: linux-image-5.13.0-28-generic hangs randomly

2022-01-25 Thread Ben Aceler

** Attachment added: "yet another journalctl output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+attachment/5557317/+files/bug3

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

Title:
  linux-image-5.13.0-28-generic hangs randomly

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process
  ". Using previous build (5.13.0-25) solves the
  problem.

  The symptoms are that the system just hangs up. Only hardreset works.

  I started ubuntu-bug with 5.13.0-25 kernel, because the system is
  stable with this kernel, but I also add a journalctl output with -28
  kernel to indicate the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 25 13:30:53 2022
  IwConfig:
   lono wireless extensions.
   
   enp42s0   no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C95
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic 
root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-25-generic N/A
   linux-backports-modules-5.13.0-25-generic  N/A
   linux-firmware 1.201.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago)
  dmi.bios.date: 06/22/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550M PRO-VDH (MS-7C95)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C95
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+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 1958975] Re: linux-image-5.13.0-28-generic hangs randomly

2022-01-25 Thread Ben Aceler

** Attachment added: "another journalctl output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+attachment/5557316/+files/bug2

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

Title:
  linux-image-5.13.0-28-generic hangs randomly

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process
  ". Using previous build (5.13.0-25) solves the
  problem.

  The symptoms are that the system just hangs up. Only hardreset works.

  I started ubuntu-bug with 5.13.0-25 kernel, because the system is
  stable with this kernel, but I also add a journalctl output with -28
  kernel to indicate the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 25 13:30:53 2022
  IwConfig:
   lono wireless extensions.
   
   enp42s0   no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C95
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic 
root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-25-generic N/A
   linux-backports-modules-5.13.0-25-generic  N/A
   linux-firmware 1.201.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago)
  dmi.bios.date: 06/22/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550M PRO-VDH (MS-7C95)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C95
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+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 1958975] [NEW] linux-image-5.13.0-28-generic hangs randomly

2022-01-25 Thread Ben Aceler

Public bug reported:

Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process
". Using previous build (5.13.0-25) solves the problem.

The symptoms are that the system just hangs up. Only hardreset works.

I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable
with this kernel, but I also add a journalctl output with -28 kernel to
indicate the problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-28-generic 5.13.0-28.31
ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
Uname: Linux 5.13.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 25 13:30:53 2022
IwConfig:
 lono wireless extensions.
 
 enp42s0   no wireless extensions.
 
 virbr0no wireless extensions.
MachineType: Micro-Star International Co., Ltd. MS-7C95
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic 
root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-25-generic N/A
 linux-backports-modules-5.13.0-25-generic  N/A
 linux-firmware 1.201.3
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago)
dmi.bios.date: 06/22/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B550M PRO-VDH (MS-7C95)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C95
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish package-from-proposed wayland-session

** Attachment added: "bug1"
   https://bugs.launchpad.net/bugs/1958975/+attachment/5557296/+files/bug1

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

Title:
  linux-image-5.13.0-28-generic hangs randomly

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process
  ". Using previous build (5.13.0-25) solves the
  problem.

  The symptoms are that the system just hangs up. Only hardreset works.

  I started ubuntu-bug with 5.13.0-25 kernel, because the system is
  stable with this kernel, but I also add a journalctl output with -28
  kernel to indicate the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 25 13:30:53 2022
  IwConfig:
   lono wireless extensions.
   
   enp42s0   no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C95
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic 
root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-25-generic N/A
   linux-backports-modules-5.13.0-25-generic  N/A
   linux-firmware 1.201.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago)
  dmi.bios.date: 06/22/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550M PRO-VDH (MS-7C95)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias:

[Kernel-packages] [Bug 1958911] Re: BCM4356 wifi chipset fail to connect

Can you please run 'apport-collect 1958911'?

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected

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


-- 
Mailing list:

[Kernel-packages] [Bug 1958973] [NEW] impish:linux-riscv: icmp.sh from selftests.net fails

2022-01-25 Thread Kleber Sacilotto de Souza

Public bug reported:

icmp.sh from selftests.net is a relatively new testcase which started to
be run on impish (5.13) kernels only in the latest builds after commit
"ca3676f94b8f kselftests/net: add missed icmp.sh test to Makefile".

With impish:linux-riscv kernel version 5.13.0-1011.12 the testcase fails
with the following error:

19:41:38 DEBUG| Running 'make run_tests -C net TEST_PROGS=icmp.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
19:41:38 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
19:41:38 DEBUG| [stdout] make --no-builtin-rules ARCH=riscv -C ../../../.. 
headers_install
19:41:38 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
19:41:46 DEBUG| [stdout]   INSTALL ./usr/include
19:41:47 DEBUG| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
19:41:47 DEBUG| [stdout] TAP version 13
19:41:47 DEBUG| [stdout] 1..1
19:41:48 DEBUG| [stdout] # selftests: net: icmp.sh
19:41:49 DEBUG| [stdout] # FAIL - got ICMP response from , should be 192.0.0.8
19:41:52 DEBUG| [stdout] not ok 1 selftests: net: icmp.sh # exit=1

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux (Ubuntu Impish)
 Importance: Undecided
 Status: Confirmed


** Tags: 5.13 impish net riscv64 ubuntu-kernel-selftests

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Impish)
   Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: 5.13 impish net riscv64 ubuntu-kernel-selftests

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

Title:
  impish:linux-riscv: icmp.sh from selftests.net fails

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  Confirmed

Bug description:
  icmp.sh from selftests.net is a relatively new testcase which started
  to be run on impish (5.13) kernels only in the latest builds after
  commit "ca3676f94b8f kselftests/net: add missed icmp.sh test to
  Makefile".

  With impish:linux-riscv kernel version 5.13.0-1011.12 the testcase
  fails with the following error:

  19:41:38 DEBUG| Running 'make run_tests -C net TEST_PROGS=icmp.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
  19:41:38 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  19:41:38 DEBUG| [stdout] make --no-builtin-rules ARCH=riscv -C ../../../.. 
headers_install
  19:41:38 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  19:41:46 DEBUG| [stdout]   INSTALL ./usr/include
  19:41:47 DEBUG| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  19:41:47 DEBUG| [stdout] TAP version 13
  19:41:47 DEBUG| [stdout] 1..1
  19:41:48 DEBUG| [stdout] # selftests: net: icmp.sh
  19:41:49 DEBUG| [stdout] # FAIL - got ICMP response from , should be 192.0.0.8
  19:41:52 DEBUG| [stdout] not ok 1 selftests: net: icmp.sh # exit=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958973/+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 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

2022-01-25 Thread Dmitrii Shcherbakov

Thanks!

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  The ESW_ALLOWED marco was later converted into a helper routine in
  commit b16f2bb6.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+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 1958968] Re: failed to resume PC

2022-01-25 Thread Paul White 

** Tags added: focal

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  failed to resume PC

Status in linux package in Ubuntu:
  New

Bug description:
  Sometimes I cannot resume my PC after suspend. Pressing keys or moving
  the mouse doesn't help: the login screen doesn't appear. In some cases
  pressing Ctrl+Alt+F1 helps, but not always. This time I had to make a
  hard reset. Check 25 January 10:43 in the logs.

  Ubuntu 20.04.3 LTS
  5.4.0-96-generic x86_64
  GNOME 3.36.8 X11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958968/+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 1958968] [NEW] failed to resume PC

2022-01-25 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Sometimes I cannot resume my PC after suspend. Pressing keys or moving
the mouse doesn't help: the login screen doesn't appear. In some cases
pressing Ctrl+Alt+F1 helps, but not always. This time I had to make a
hard reset. Check 25 January 10:43 in the logs.

Ubuntu 20.04.3 LTS
5.4.0-96-generic x86_64
GNOME 3.36.8 X11

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal
-- 
failed to resume PC
https://bugs.launchpad.net/bugs/1958968
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1958911] Re: BCM4356 wifi chipset fail to connect

** Package changed: ubuntu => linux-firmware (Ubuntu)

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

Title:
  BCM4356 wifi chipset fail to connect

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My machine fails to connect wifi network.

  I use Kubuntu 21.10.

  Here are my machine's information.

  lspci -vvnn | grep -A 9 Network
  01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
  Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless 
Network Adapter [17f9:0036]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: brcmfmac
  Kernel modules: brcmfmac

  lshw
   *-network
     description: Wireless interface
     product: BCM4356 802.11ac Wireless Network Adapter
     vendor: Broadcom Inc. and subsidiaries
     physical id: 0
     bus info: pci@:01:00.0
     logical name: wlan1
     version: 02

  And Ksystemlog says
  2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
  2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
  2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: 
NetworkManager state is now CONNECTING
  2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
  2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
  2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
  2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7251] device 
(p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
  2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
  2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
  2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
  2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'bgscan' value 'simple:30:-70:86400'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
  2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
  2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
  2022/01/22 2:49 NetworkManager  [1642787376.7870] device 
(p2p-dev-wlan1): supplicant management interface state: scanning -> inactive
  2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
  2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
  2022/01/22 2:49 NetworkManager  [1642787376.8467] device 
(p2p-dev-wlan1): supplicant management interface state: inactive -> associating
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
  2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
  2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
  2022/01/22 2:49 NetworkManager  [1642787377.4250] device 
(p2p-dev-wlan1): supplicant management interface state: associating -> 
disconnected

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


-- 
Mailing list:

[Kernel-packages] [Bug 1958911] [NEW] BCM4356 wifi chipset fail to connect

2022-01-25 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

My machine fails to connect wifi network.

I use Kubuntu 21.10.

Here are my machine's information.

lspci -vvnn | grep -A 9 Network
01:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4356 
802.11ac Wireless Network Adapter [14e4:43ec] (rev 02)
Subsystem: Gemtek Technology Co., Ltd BCM4356 802.11ac Wireless Network 
Adapter [17f9:0036]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: brcmfmac
Kernel modules: brcmfmac

lshw
 *-network
   description: Wireless interface
   product: BCM4356 802.11ac Wireless Network Adapter
   vendor: Broadcom Inc. and subsidiaries
   physical id: 0
   bus info: pci@:01:00.0
   logical name: wlan1
   version: 02

And Ksystemlog says
2022/01/22 2:49 NetworkManager  [1642787376.6460] device (wlan1): 
Activation: starting connection 'elecom-b3306f' 
(81bdc1ee-e44b-4121-aab5-62f3395e399d)
2022/01/22 2:49 NetworkManager  [1642787376.6482] audit: 
op="connection-activate" uuid="81bdc1ee-e44b-4121-aab5-62f3395e399d" 
name="elecom-b3306f" pid=1168 uid=1000 result="success"
2022/01/22 2:49 NetworkManager  [1642787376.6486] device (wlan1): state 
change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2022/01/22 2:49 NetworkManager  [1642787376.6503] manager: NetworkManager 
state is now CONNECTING
2022/01/22 2:49 NetworkManager  [1642787376.6512] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2022/01/22 2:49 NetworkManager  [1642787376.6535] device (wlan1): 
Activation: (wifi) access point 'elecom-b3306f' has security, but secrets are 
required.
2022/01/22 2:49 NetworkManager  [1642787376.6536] device (wlan1): state 
change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
2022/01/22 2:49 NetworkManager  [1642787376.6547] 
sup-iface[039a263b9d4622b5,1,wlan1]: wps: type pbc start...
2022/01/22 2:49 wpa_supplicant wlan1: WPS-PBC-ACTIVE
2022/01/22 2:49 NetworkManager  [1642787376.7249] device (wlan1): 
supplicant interface state: disconnected -> scanning
2022/01/22 2:49 NetworkManager  [1642787376.7251] device (p2p-dev-wlan1): 
supplicant management interface state: disconnected -> scanning
2022/01/22 2:49 NetworkManager  [1642787376.7502] device (wlan1): state 
change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
2022/01/22 2:49 NetworkManager  [1642787376.7523] device (wlan1): state 
change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2022/01/22 2:49 NetworkManager  [1642787376.7549] device (wlan1): 
Activation: (wifi) connection 'elecom-b3306f' has security, and secrets exist. 
No new secrets needed.
2022/01/22 2:49 NetworkManager  [1642787376.7564] Config: added 'ssid' 
value 'elecom-b3306f'
2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 
'scan_ssid' value '1'
2022/01/22 2:49 NetworkManager  [1642787376.7565] Config: added 'bgscan' 
value 'simple:30:-70:86400'
2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 
'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
2022/01/22 2:49 NetworkManager  [1642787376.7566] Config: added 'psk' 
value ''
2022/01/22 2:49 NetworkManager  [1642787376.7853] device (wlan1): 
supplicant interface state: scanning -> inactive
2022/01/22 2:49 NetworkManager  [1642787376.7870] device (p2p-dev-wlan1): 
supplicant management interface state: scanning -> inactive
2022/01/22 2:49 wpa_supplicant wlan1: Trying to associate with SSID 
'elecom-b3306f'
2022/01/22 2:49 NetworkManager  [1642787376.8465] device (wlan1): 
supplicant interface state: inactive -> associating
2022/01/22 2:49 NetworkManager  [1642787376.8467] device (p2p-dev-wlan1): 
supplicant management interface state: inactive -> associating
2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-ASSOC-REJECT 
bssid=00:00:00:00:00:00 status_code=16
2022/01/22 2:49 wpa_supplicant wlan1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 
ssid="elecom-b3306f" auth_failures=1 duration=10 reason=CONN_FAILED
2022/01/22 2:49 NetworkManager  [1642787377.4247] device (wlan1): 
supplicant interface state: associating -> disconnected
2022/01/22 2:49 NetworkManager  [1642787377.4250] device (p2p-dev-wlan1): 
supplicant management interface state: associating -> disconnected

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
BCM4356 wifi chipset fail to connect
https://bugs.launchpad.net/bugs/1958911
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-firmware in Ubuntu.

-- 
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 1958774] Re: Blackscreen after suspending and closing LID

2022-01-25 Thread Chuyang Chen

** Description changed:

  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:
  
  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).
  
  These bugs really trouble me. It will be very helpful if you fix it.
  
- UPDATE: After I upgrade the "core" package using "snap refresh", the
- first bug has been fixed. However, the second bug related to laptop
- devices is still there.
+ UPDATE at 2022/01/25: After I upgrade the "core" package using "snap
+ refresh", the first bug has been fixed. However, the second bug related
+ to laptop devices is still there.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: NH5x_7xDCx_DDx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

** Description changed:

  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:
  
  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).
  
  These bugs really trouble me. It will be very helpful if you fix it.
  
- UPDATE at 2022/01/25: After I upgrade the "core" package using "snap
+ UPDATE at 2022/01/25: After I upgraded the "core" package using "snap
  refresh", the first bug has been fixed. However, the second bug related
  to laptop devices is still there.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

https://lists.ubuntu.com/archives/kernel-team/2022-January/127401.html

** Description changed:

  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16
  
  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.
  
  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.
  
  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
-  eswitch manager
+  eswitch manager
  
  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.
+ 
+ The ESW_ALLOWED marco was later converted into a helper routine in
+ commit b16f2bb6.
  
  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
  
  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.
  
  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.
  
- 
  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
  
  It would be good to have this fix in Focal+ kernels.
  
  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in question
  affects the hypervisor side.

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  The ESW_ALLOWED marco was later converted into a helper routine in
  commit b16f2bb6.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to :

[Kernel-packages] [Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)

2022-01-25 Thread Krzysztof Kozlowski

Found on: 2022.01.03/bionic/linux-ibm-gt-5.4/5.4.0-1007.9

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

Title:
  cpuset_memory_spread from controllers test suite in LTP failed (hog
  the memory on the unexpected node)

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux source package in Focal:
  New
Status in linux-azure source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux-azure source package in Hirsute:
  New

Bug description:
  Test failed with:
  cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected 
node(FilePages_For_Nodes(KB): _0: 2276
  _1: 102428, Expect Nodes: 1).

  <<>>
  tag=cpuset_memory_spread stime=1558937747
  cmdline="   cpuset_memory_spread_testset.sh"
  contacts=""
  analysis=exit
  <<>>
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s
  cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected 
node(FilePages_For_Nodes(KB): _0: 2276
  _1: 102428, Expect Nodes: 1).
  cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded.
  <<>>
  initiation_status="ok"
  duration=10 termination_type=exited termination_id=1 corefile=no
  cutime=364 cstime=383
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 27 05:39 seq
   crw-rw 1 root audio 116, 33 May 27 05:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon May 27 06:16:49 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+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 1958850] Re: USB port lost function after unplugging usb drive

2022-01-25 Thread Timo Aaltonen

reverting the patches from bug 1950974 were tested to not help, so
bisecting is needed

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

Title:
  USB port lost function after unplugging usb drive

Status in OEM Priority Project:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Incomplete

Bug description:
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Precision 5750
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem 
root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-1021-oem N/A
   linux-backports-modules-5.14.0-1021-oem  N/A
   linux-firmware   1.201.3
  Tags:  impish
  Uname: Linux 5.14.0-1021-oem x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1958850/+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 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

** Description changed:

  [Impact]
- There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16
+ There is an issue with hypervisor host side mlx5 driver operation on
+ Bluefield devices in kernels <=5.16
  
- Copied from patch description:
+ From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.
  
  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.
  
  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
-  eswitch manager
+  eswitch manager
  
  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.
  
  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
  
- Kernels tested by Dmitrii Shcherbakov with positive feedback.
+ Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
+ passed with positive feedback.
  
  [Where problems could occur]
- If this patch is erroneous, it might cause issue to this mlx5 driver with 
certain operations (passing vlan 0).
+ If this patch is erroneous, it might cause issue to this mlx5 driver
+ with certain operations (setting vid 0). And other programs such as
+ libvirt that depends on this return value might be affected as well.
+ 
  
  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
  
  It would be good to have this fix in Focal+ kernels.
  
  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in question
  affects the hypervisor side.

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Impish)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => In Progress

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  
  [Original Bug

[Kernel-packages] [Bug 1954757] Re: Missing overlays/README

Flash-kernel needs to copy the README to the correct location.

** Also affects: flash-kernel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Missing overlays/README

Status in flash-kernel package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Invalid
Status in linux-raspi source package in Focal:
  Fix Committed
Status in linux-raspi source package in Hirsute:
  Fix Committed
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [ Impact ]

  overlays/README is used by the 'dtoverlay' command to display info on
  available overlays and params.

  [ Test Case ]

  $ apt install libraspberrypi-bin
  $ dtoverlay -h uart0
  * Help file not found

  With the README present:
  $ dtoverlay -h uart0
  Name:   uart0

  Info:   Change the pin usage of uart0

  Usage:  dtoverlay=uart0,=

  Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 -
  default 14)

  rxd0_pinGPIO pin for RXD0 (15, 33 or 37 -
  default 15)

  pin_funcAlternative pin function - 4(Alt0) for 14&15,
  7(Alt3) for 32&33, 6(Alt2) for 36&37

  [ Where Problems Could Occur ]

  The output of the `dtoverlay` could be wrong but it's only
  informational so should have no negative impact.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954757/+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 1958952] Re: ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9"

** Description changed:

  While investigating the SRU deployment failure, I noticed the dmesg will
  be spammed with:
  
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885627] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885628] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1218): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885629] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885631] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  
  Issue found with Focal 5.4.0-96-generic
  
  Please find attachment for the syslog.
  
  Not sure if this is cause of our deployment issue, but it seems odd to me.
- Deployment issue:
-   1. System successfully deployed with Focal
-   2. Deployment process hangs with "Enabling PPA" stage
-   3. I cannot connect to this system manually, ssh hangs (soft lockup maybe?) 
after:
- Warning: Permanently added '10.229.50.13' (ECDSA) to the list of 
known hosts.
- 
+ And here is our deployment issue:
+   1. System successfully deployed with Focal
+   2. Deployment process hangs with "Enabling PPA" stage
+   3. I cannot connect to this system manually, ssh hangs (soft lockup maybe?) 
after:
+ Warning: Permanently added '10.229.50.13' (ECDSA) to the list of 
known hosts.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-96-generic 5.4.0-96.109
  ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157
  Uname: Linux 5.4.0-96-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 25 07:48 seq
   crw-rw 1 root audio 116, 33 Jan 25 07:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Tue Jan 25 07:53:33 2022
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 004: ID 12d1:0003 Huawei Technologies Co., Ltd.
   Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
   Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 1: Dev 4, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
   |__ Port 1: Dev 4, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: Hisilicon D05
  PciMultimedia:
  
  ProcFB: 0 hibmcdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic 
root=UUID=3abb8e5a-2f46-4221-b664-cb02a273a249 ro sysrq_always_enabled
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-96-generic N/A
   linux-backports-modules-5.4.0-96-generic  N/A
   linux-firmware1.187.25
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: Huawei
  dmi.bios.version: 1.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: BC11SPCD
  dmi.board.vendor: Huawei
  dmi.board.version: VER.A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Hisilicon
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnHuawei:bvr1.50:bd06/01/2018:svnHisilicon:pnD05:pvrV100R001C00:rvnHuawei:rnBC11SPCD:rvrVER.A:cvnHisilicon:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D05
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: V100R001C00
  dmi.sys.vendor: Hisilicon

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

Title:
  ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0:
  mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ
  0x5a5aa9"

Status in linux package in Ubuntu:
  New

Bug description:
  While investigating the SRU deployment failure, I noticed the dmesg
  will be spammed with:

  Jan 25 07:48:36 appleton-kernel kernel: [   22.885627] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885628] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1218): Completion event for

[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part

** Description changed:

SRU Justification:
==

[Impact]

* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.

* A fix is needed to enhance problem determination of guest kernel under
KVM using DIAG 0x318 instruction execution.

* The s390x diagnose 318 instruction sets the control program name code
(CPNC) and control program version code (CPVC) to provide useful
information regarding the OS during debugging.

* The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.

[Fix]

* In general the following 4 commits are needed:

* 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug
statement for diag 318 CPNC data"
-
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch

* 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove
diag318 reset code"
-
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch

* 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose
0x318 sync and reset"
-
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch

* a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag
318: refactor struct"
-
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch

* For jammy, hirsute and impish only the first commit is needed, the
others are already in.

* For focal all 4 commits are needed, but since they do not apply
cleanly on focal, the attached backports need to be used instead.

[Test Case]

* Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.

- * And setup an Ubuntu KVM virtual on top.
+ * And setup an Ubuntu KVM virtual machine on top.

* It can then be observed if the CPNC (diag318 data) has been
successfully set by looking at the s390dbf messages for the KVM guest.

* The CPNC will always be 4 (denotes Linux environment).

* Another way to test this is by running the sync_regs_test under
tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the
kernel self test suite can trigger this.

[Where problems could occur]

* The approach here is to provide additional debug and diagnose
information on top.

* Hence even if the diag318 changes are broken, the existing
functionality shouldn't be harmed.

* The changes themselves are relatively discernible and mostly introduce
new structures.

* However, with the functional changes broken code could be introduced
(e.g. due to erroneous pointer arithmetic for example) that does not
compile or causes crashes. But this is what the test builds are for
(https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).

* On top the diag318 diagnose data might not properly provided - maybe
empty or wrong. Again that is what the test builds and the verification
later is targeted at.

* Since diag318 is s390x specific, all the modifications touch s390x
code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
diag.h). At least no other other architecture will be affected.

* Well, there is one tiny bit of a common code change, but it's just a
new define statement in include/uapi/linux/kvm.h ('#define
KVM_CAP_S390_DIAG318 186').

[Other]

* Request was to add the patches to focal / 20.04, but to avoid
potential regressions on upgrades, the patches need to be added to
jammy, impish and hirsute, too.

* As mentioned above, Jammy, Hirsute and Impish includes almost
everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
for diag 318 CPNC data".

* Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
invasive for Jammy, Hirsute and Impish, also because commit 3fd8417f2c72
can be cleanly cherry-picked form there.

* LP#1953338 is related to this bug and covers the qemu/KVM bits.
__

Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled.
Fix needed to enhance problem determination of guest kernel under

[Kernel-packages] [Bug 1958952] Re: ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9"

** Description changed:

  While investigating the SRU deployment failure, I noticed the dmesg will
  be spammed with:
  
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885627] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885628] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1218): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885629] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885631] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  
- 
  Issue found with Focal 5.4.0-96-generic
  
- Please find attachment for syslog
+ Please find attachment for the syslog.
+ 
+ Not sure if this is cause of our deployment issue, but it seems odd to me.
+ Deployment issue:
+   1. System successfully deployed with Focal
+   2. Deployment process hangs with "Enabling PPA" stage
+   3. I cannot connect to this system manually, ssh hangs (soft lockup maybe?) 
after:
+ Warning: Permanently added '10.229.50.13' (ECDSA) to the list of 
known hosts.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-96-generic 5.4.0-96.109
  ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157
  Uname: Linux 5.4.0-96-generic aarch64
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 Jan 25 07:48 seq
-  crw-rw 1 root audio 116, 33 Jan 25 07:48 timer
+  total 0
+  crw-rw 1 root audio 116,  1 Jan 25 07:48 seq
+  crw-rw 1 root audio 116, 33 Jan 25 07:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Tue Jan 25 07:53:33 2022
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
-  Bus 001 Device 004: ID 12d1:0003 Huawei Technologies Co., Ltd. 
-  Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
-  Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 004: ID 12d1:0003 Huawei Technologies Co., Ltd.
+  Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
+  Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M
-  |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
-  |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
-  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
-  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M
+  |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
+  |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
+  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, 
Driver=usbhid, 12M
+  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, 
Driver=usbhid, 12M
  MachineType: Hisilicon D05
  PciMultimedia:
-  
+ 
  ProcFB: 0 hibmcdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic 
root=UUID=3abb8e5a-2f46-4221-b664-cb02a273a249 ro sysrq_always_enabled
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-96-generic N/A
-  linux-backports-modules-5.4.0-96-generic  N/A
-  linux-firmware1.187.25
+  linux-restricted-modules-5.4.0-96-generic N/A
+  linux-backports-modules-5.4.0-96-generic  N/A
+  linux-firmware1.187.25
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: Huawei
  dmi.bios.version: 1.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: BC11SPCD
  dmi.board.vendor: Huawei
  dmi.board.version: VER.A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Hisilicon
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnHuawei:bvr1.50:bd06/01/2018:svnHisilicon:pnD05:pvrV100R001C00:rvnHuawei:rnBC11SPCD:rvrVER.A:cvnHisilicon:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D05
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: V100R001C00
  dmi.sys.vendor: Hisilicon

-- 
You received this bug notification because you are a member of

[Kernel-packages] [Bug 1954757] Re: Missing overlays/README

Verified that all packages now contain the README file.

** Tags removed: verification-needed-focal verification-needed-hirsute 
verification-needed-impish
** Tags added: verification-done-focal verification-done-hirsute 
verification-done-impish

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

Title:
  Missing overlays/README

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Invalid
Status in linux-raspi source package in Focal:
  Fix Committed
Status in linux-raspi source package in Hirsute:
  Fix Committed
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [ Impact ]

  overlays/README is used by the 'dtoverlay' command to display info on
  available overlays and params.

  [ Test Case ]

  $ apt install libraspberrypi-bin
  $ dtoverlay -h uart0
  * Help file not found

  With the README present:
  $ dtoverlay -h uart0
  Name:   uart0

  Info:   Change the pin usage of uart0

  Usage:  dtoverlay=uart0,=

  Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 -
  default 14)

  rxd0_pinGPIO pin for RXD0 (15, 33 or 37 -
  default 15)

  pin_funcAlternative pin function - 4(Alt0) for 14&15,
  7(Alt3) for 32&33, 6(Alt2) for 36&37

  [ Where Problems Could Occur ]

  The output of the `dtoverlay` could be wrong but it's only
  informational so should have no negative impact.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1954757/+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 1958952] [NEW] ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9"

Public bug reported:

While investigating the SRU deployment failure, I noticed the dmesg will
be spammed with:

Jan 25 07:48:36 appleton-kernel kernel: [   22.885627] mlx5_core 0005:01:00.0: 
mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9
Jan 25 07:48:36 appleton-kernel kernel: [   22.885628] mlx5_core 0005:01:00.0: 
mlx5_eq_comp_int:159:(pid 1218): Completion event for bogus CQ 0x5a5aa9
Jan 25 07:48:36 appleton-kernel kernel: [   22.885629] mlx5_core 0005:01:00.0: 
mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9
Jan 25 07:48:36 appleton-kernel kernel: [   22.885631] mlx5_core 0005:01:00.0: 
mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9


Issue found with Focal 5.4.0-96-generic

Please find attachment for syslog

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-96-generic 5.4.0-96.109
ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157
Uname: Linux 5.4.0-96-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jan 25 07:48 seq
 crw-rw 1 root audio 116, 33 Jan 25 07:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Date: Tue Jan 25 07:53:33 2022
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 004: ID 12d1:0003 Huawei Technologies Co., Ltd. 
 Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
 Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M
 |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
12M
 |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
12M
MachineType: Hisilicon D05
PciMultimedia:
 
ProcFB: 0 hibmcdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic 
root=UUID=3abb8e5a-2f46-4221-b664-cb02a273a249 ro sysrq_always_enabled
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-96-generic N/A
 linux-backports-modules-5.4.0-96-generic  N/A
 linux-firmware1.187.25
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/01/2018
dmi.bios.vendor: Huawei
dmi.bios.version: 1.50
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: BC11SPCD
dmi.board.vendor: Huawei
dmi.board.version: VER.A
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Hisilicon
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnHuawei:bvr1.50:bd06/01/2018:svnHisilicon:pnD05:pvrV100R001C00:rvnHuawei:rnBC11SPCD:rvrVER.A:cvnHisilicon:ct17:cvrTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: D05
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: V100R001C00
dmi.sys.vendor: Hisilicon

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug arm64 focal uec-images

** Attachment added: "syslog"
   https://bugs.launchpad.net/bugs/1958952/+attachment/5557240/+files/syslog

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

Title:
  ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0:
  mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ
  0x5a5aa9"

Status in linux package in Ubuntu:
  New

Bug description:
  While investigating the SRU deployment failure, I noticed the dmesg
  will be spammed with:

  Jan 25 07:48:36 appleton-kernel kernel: [   22.885627] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885628] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1218): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885629] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9
  Jan 25 07:48:36 appleton-kernel kernel: [   22.885631] mlx5_core 
0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 
0x5a5aa9

  
  Issue found with Focal 5.4.0-96-generic

  Please find attachment for syslog

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-96-generic 5.4.0-96.109
  ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157
  Uname: Linux 5.4.0-96-generic aarch64

[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds