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

[Simon B]

Hi, 
I have been experiencing the same problem for several days. I have to press 
escape when I launch my laptop, to display its screen correctly. Otherwise, as 
mentioned before, I get a multicolored snow. If my screen goes to sleep, it 
also happens. 
I use a Tuxedo computer Pulse, with a Ryzen 7 4800h. Under Kubuntu.

-- 
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 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot

[Sigmund Ørjavik]

reverted to 5.13.0-28-generic from impish and aqc107 is still broken. is
this caused by some updated firmware blob in jammy?

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

Title:
  Aquantia GbE LAN driver causes UBSAN error during kernel boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The undefined behaviour sanitiser picks up an array-index-out-of-
  bounds in the aquantia atlantic driver. The NIC is (I think) built
  into my gigabyte motherboard
  (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME-
  rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to
  22.04 (or at least dmesg didn't previously complain).

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 13:02:10 2022
  InstallationDate: Installed on 2019-08-07 (899 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 
vt.handoff=7
  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: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+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 1958286] Re: mt7921e 0000:02:00.0: PM: failed to resume async: error -110

[Kai-Chuan Hsieh]

Run 100 time reboot stress on WMVD5-DVT2-A1, no chip reset, wifi/bt
works normally.

kernel: 5.14.0-1020-oem
bios: 1.2.0

** Tags added: verification-done-focal

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

Title:
  mt7921e :02:00.0: PM: failed to resume async: error -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  
  [Impact]

  Mediatek MT7921 may fail to resume from runtime suspend can cause chip
  reset.

mt7921e :02:00.0: PM: failed to resume async: error -110
mt7921e :02:00.0: chip reset

  [Fix]

  This is fixed with both bluetooth and WiFi firmware upgrade to
  upstream commit 094d7adc1136 ("linux-firmware: update firmware for
  MT7921 WiFi device") and commit 1e744b85cd4c ("linux-firmware: update
  firmware for mediatek bluetooth chip(MT7921)").

  [Test Case]

  This can be triggered by checkbox warm reset stress test:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  This imports fixes requiring both kernel driver and proprietary firmware
  updates, the firmware part might cause instability or so.

  [Other Info]

  This affects all kernels supporting MT7921, which means F/H/I/J.

  == original bug report ==

  [Summary]
  Boot into Ubuntu desktop, MT7921 shows IP is obtained, however there is no 
response from gateway pings, neither is 8.8.8.8.

  kernel: [ 588.893227] mt7921e :02:00.0: PM: failed to resume async: error 
-110
  kernel: [ 588.893236] mt7921e :02:00.0: chip reset

  [Reproduce Steps]
  1. Boot into Ubuntu desktop
  2. Check if MT7921 obtains IP, ping gateway and ping 8.8.8.8
  3. No response, need to do cold boot to recover
  4. The issue is easily be seen after warm reset stress, I locally test warm 
reset stress for 100 times

  [Results]
  Expected: Has traffic and response by ping
  Actual: No response

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1958286/+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 1952667] Re: XPS 9575 auto switch L-R audio when in tent mode (when laptop is updside down)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  XPS 9575 auto switch L-R audio when in tent mode (when laptop is
  updside down)

Status in linux package in Ubuntu:
  Expired

Bug description:
  When the XPS 9575 laptop is upside down the in-built gyroscope rotates
  the screen, as correct and expected. However the Audio output is not
  rotated/switched.

  This means, for instance, when listening to spatially orientated audio
  such as in games, i.e. first person shooters, the audio is the wrong
  way around. i.e. gunfire sounds like it is coming from the left, when
  in fact it is to the right, which leads to disorientation.

  A test has been conducted with the laptop the right way up and this
  has been compared to the laptop flipped upside down in tent mode, and
  the audio was identified to be the wrong way around when in tent mode.

  It is believed that the gyroscope must be linked to the audio drivers
  to flip the audio output when upside down. Although some software may
  be able to work around this issue, rotating the laptop on the fly is
  not possible without adjusting such settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952667/+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 1870597] Re: libinput says "your system is too slow"

[Angel D. Segarra]

I'm getting spammed by libinput messages about the system being slow. A
couple of patches in libinput were merged to master about  month ago
that rate limits some messages that previously were not, and should at
least stop the spamming of messages, if you use a wireless mouse for
example the journal gets flooded if you're doing a lot of mouse
movements.

Please consider backporting these.

https://gitlab.freedesktop.org/libinput/libinput/-/commit/a1e9150210abda0d3dd41127330cd7985d29957d
https://gitlab.freedesktop.org/libinput/libinput/-/commit/64a49d18b948a5b8ac88da9207689af356a081cf

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

Title:
  libinput says "your system is too slow"

Status in GNOME Shell:
  Unknown
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  During the freeze, the output of the install had a message from "gdm-
  x-session" saying "your system is too slow".

  To reproduce:
  1. Launch the Ubuntu installer
  2. Begin the installation process
  3. When the installation process begins, move the cursor around
  4. Notice how the PC freezes and drops mouse events

  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  gnome-shell:
Installed: 3.36.0-2ubuntu2
Candidate: 3.36.0-2ubuntu2
Version table:
   *** 3.36.0-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.442
  Date: Fri Apr  3 14:24:21 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Inspiron 5570
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed quiet splash ---
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/gnome-shell/+bug/1870597/+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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

[James Ferguson]

Note I reported this on a Thinkpad X13 Gen 1; Ryzen 7 4750U; [AMD/ATI]
Renoir [1002:1636] (rev d1) graphics.

On X13 Gen 2; Ryzen 7, 5850U; [AMD/ATI] Device [1002:1638] (rev d1)
graphics, the problem *does not* occur.

-- 
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 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[John McGee]

** Description changed:

- **UPDATE 1,28/2022, 1500 PST**
+ **UPDATE 1/28/2022, 1500 PST**
  
  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System Info
  outputs to attached comments below, as well as all the other output
  reports for the terminal commands I was recommended to execute.
  
- The second/newer set of automatic report outputs attached in comments
- below reports and info are from terminal command outputs while running
- Linux Mint 20.3 with Cinnamon DE on kernel 5.13.0-27. The first/older
- set was from the reports while I was still using kernel 5.11.0-46.
- Sorry.  Told you I was new to this...
+ The first/older set of automatic report outputs and info attached in the
+ comments below are from terminal command outputs while running Linux
+ Mint 20.3 with Cinnamon DE while I was still using kernel 5.11.0-46;
+ they should probably be ignored (I'm unable to delete them). The
+ second/newer set of automatic report outputs attached are from terminal
+ command outputs while running Linux Mint 20.3 with Cinnamon DE on kernel
+ 5.13.0-27. Sorry. I Told you I was new to this...
  
  **End of text update**
  
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but if
  I'm not it's because of unfamiliarity and general ignorance.  I beg for
  your patience and understanding.
  
  For the listed kernels in the summary line (kernels 5.13.0-21, -22, -23,
  -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are met:
  
  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input
  
  AND
  
  2)  The "Mirror" selection is toggled in the Display Manager GUI
  
  OR
  
  3)  The HDMI cable is removed from the HDMI port/USB-C hub
  
  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest any
  of the described screen crash issues listed above. That is to say, the
  laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.
  
  Thanks.  Please advise if I may be of any further assistance.
  
  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the 

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

[John McGee]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558102/+files/CRDA.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] Lspci.txt

[John McGee]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558105/+files/Lspci.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] UdevDb.txt

[John McGee]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558117/+files/UdevDb.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] CurrentDmesg.txt

[John McGee]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558103/+files/CurrentDmesg.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] ProcModules.txt

[John McGee]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558114/+files/ProcModules.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] Lsusb-v.txt

[John McGee]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558109/+files/Lsusb-v.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] ProcCpuinfoMinimal.txt

[John McGee]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558111/+files/ProcCpuinfoMinimal.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] ProcInterrupts.txt

[John McGee]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558113/+files/ProcInterrupts.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] ProcEnviron.txt

[John McGee]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558112/+files/ProcEnviron.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] WifiSyslog.txt

[John McGee]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558118/+files/WifiSyslog.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] PulseList.txt

[John McGee]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558115/+files/PulseList.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] Lsusb.txt

[John McGee]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558107/+files/Lsusb.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] IwConfig.txt

[John McGee]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558104/+files/IwConfig.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] Lspci-vt.txt

[John McGee]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558106/+files/Lspci-vt.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] ProcCpuinfo.txt

[John McGee]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558110/+files/ProcCpuinfo.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] acpidump.txt

[John McGee]

apport information

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

** Description changed:

  **UPDATE 1,28/2022, 1500 PST**
  
  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System Info
  outputs to attached comments below, as well as all the other output
  reports for the terminal commands I was recommended to execute.
  
- The reports and info are from terminal command outputs while running
- Linux Mint 20.3 with Cinnamon DE on kernel 5.13.0-27.
+ The second/newer set of automatic report outputs attached in comments
+ below reports and info are from terminal command outputs while running
+ Linux Mint 20.3 with Cinnamon DE on kernel 5.13.0-27. The first/older
+ set was from the reports while I was still using kernel 5.11.0-46.
+ Sorry.  Told you I was new to this...
+ 
+ **End of text update**
  
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but if
  I'm not it's because of unfamiliarity and general ignorance.  I beg for
  your patience and understanding.
  
  For the listed kernels in the summary line (kernels 5.13.0-21, -22, -23,
  -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are met:
  
  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input
  
  AND
  
  2)  The "Mirror" selection is toggled in the Display Manager GUI
  
  OR
  
  3)  The HDMI cable is removed from the HDMI port/USB-C hub
  
  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest any
  of the described screen crash issues listed above. That is to say, the
  laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.
  
  Thanks.  Please advise if I may be of any further assistance.
  
  Very Respectfully,
  John McGee
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  chief  1204 F pulseaudio
-  /dev/snd/controlC2:  chief  1204 F pulseaudio
-  /dev/snd/controlC0:  chief  1204 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  chief  1204 F pulseaudio
+  /dev/snd/controlC2:  chief  1204 F pulseaudio
+  /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
-  linux-restricted-modules-5.13.0-27-generic N/A
-  linux-backports-modules-5.13.0-27-generic  N/A
-  linux-firmware 1.187.25
+  linux-restricted-modules-5.13.0-27-generic N/A
+  linux-backports-modules-5.13.0-27-generic  N/A
+  linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug 

[Kernel-packages] [Bug 1959348] Lsusb-t.txt

[John McGee]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558108/+files/Lsusb-t.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] RfKill.txt

[John McGee]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558116/+files/RfKill.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  New

Bug description:
  **UPDATE 1/28/2022, 1500 PST**

  I have edited the original posting to keep the description of the
  problem only in the body of the report. I have moved all the System
  Info outputs to attached comments below, as well as all the other
  output reports for the terminal commands I was recommended to execute.

  The first/older set of automatic report outputs and info attached in
  the comments below are from terminal command outputs while running
  Linux Mint 20.3 with Cinnamon DE while I was still using kernel
  5.11.0-46; they should probably be ignored (I'm unable to delete
  them). The second/newer set of automatic report outputs attached are
  from terminal command outputs while running Linux Mint 20.3 with
  Cinnamon DE on kernel 5.13.0-27. Sorry. I Told you I was new to
  this...

  **End of text update**

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 with Cinnamon DE on kernel 5.11.0-46.

  Thanks.  Please advise if I may be of any further assistance.

  Very Respectfully,
  John McGee
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chief  1204 F pulseaudio
   /dev/snd/controlC2:  chief  1204 F pulseaudio
   /dev/snd/controlC0:  chief  1204 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-01-26 (1 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=57f15d2c-512b-4441-b8e0-d7586091add5 ro quiet splash
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.187.25
  Tags:  una
  Uname: Linux 5.13.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/13/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd05/13/2021:br1.10:efr1.6:svnAcer:pnSwiftSF314-42:pvrV1.10:rvnRO:rnKona_RN:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959348/+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 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[John McGee]

apport information

** Description changed:

+ **UPDATE 1,28/2022, 1500 PST**
+ 
+ I have edited the original posting to keep the description of the
+ problem only in the body of the report. I have moved all the System Info
+ outputs to attached comments below, as well as all the other output
+ reports for the terminal commands I was recommended to execute.
+ 
+ The reports and info are from terminal command outputs while running
+ Linux Mint 20.3 with Cinnamon DE on kernel 5.13.0-27.
+ 
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but if
  I'm not it's because of unfamiliarity and general ignorance.  I beg for
  your patience and understanding.
  
  For the listed kernels in the summary line (kernels 5.13.0-21, -22, -23,
  -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are met:
  
  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input
  
  AND
  
  2)  The "Mirror" selection is toggled in the Display Manager GUI
  
  OR
  
  3)  The HDMI cable is removed from the HDMI port/USB-C hub
  
  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest any
  of the described screen crash issues listed above. That is to say, the
  laptop and peripheral HDMI display run stably/without issue while
- running Linux Mint 20.3 kernel 5.11.0-46
- 
- For your diagnostic consideration:
- 
- System Info:
- [code]
- System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
-    wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
- Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

-    Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
- Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
-    model: LGC AP18C8K serial:  status: Discharging
- CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
-    arch: Zen rev: 1 L2 cache: 4096 KiB
-    flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
-    Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
-    4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
- Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
-    bus ID: 03:00.0 chip ID: 1002:1636
-    Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
-    resolution: 1920x1080~60Hz, 1920x1080~60Hz
-    OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
-    direct render: Yes
- Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
-    bus ID: 03:00.1 chip ID: 1002:1637
-    Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
-    vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
-    chip ID: 1022:15e2
-    Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
-    v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
-    Sound Server: ALSA v: k5.11.0-46-generic
- Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
-    chip ID: 8086:2723
-    IF: wlp1s0 state: up mac: 
- Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
-    ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
-    speed: 31.6 Gb/s lanes: 4 serial: 
- Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
- USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
-    Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
-    Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
-    Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
-    Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
-    rev: 2.0 chip ID: 1c7a:0575
-    Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
-    driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
-    Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
- Sensors:   System 

[Kernel-packages] [Bug 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[John McGee]

sudo lspci -vnvn > lspci-vnvn.log:
No reports/outputs listed from that command

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

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
     Fan Speeds (RPM): N/A
  Repos: No active 

[Kernel-packages] [Bug 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[John McGee]

cat /proc/version_signature > version.log:
No reports/outputs listed from that command

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

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
     Fan Speeds (RPM): N/A
  Repos: No 

[Kernel-packages] [Bug 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[John McGee]

System:Kernel: 5.13.0-27-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
   wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 
 
   Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021 
Battery:   ID-1: BAT1 charge: 34.3 Wh condition: 49.2/47.8 Wh (103%) volts: 
11.6/11.2 
   model: LGC AP18C8K serial:  status: Discharging 
CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 
64 type: MCP 
   arch: Zen rev: 1 L2 cache: 4096 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31937 
   Speed: 1248 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1248 2: 
1248 3: 1325 
   4: 2495 5: 2495 6: 1927 7: 1664 8: 1251 
Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu v: 
kernel 
   bus ID: 03:00.0 chip ID: 1002:1636 
   Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa 
   resolution: 1920x1080~60Hz, 1920x1080~60Hz 
   OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 21.0.3 
compat-v: 3.1 
   direct render: Yes 
Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel v: 
kernel 
   bus ID: 03:00.1 chip ID: 1002:1637 
   Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
   vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel bus 
ID: 03:00.5 
   chip ID: 1022:15e2 
   Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel 
   v: kernel bus ID: 03:00.6 chip ID: 1022:15e3 
   Sound Server: ALSA v: k5.13.0-27-generic 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0 
   chip ID: 8086:2723 
   IF: wlp1s0 state: up mac:  
   Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: 
r8152 
   bus ID: 2-1.3:3 chip ID: 0bda:8153 
   IF: enx002432197538 state: down mac:  
Drives:Local Storage: total: 931.51 GiB used: 29.37 GiB (3.2%) 
   ID-1: /dev/nvme0n1 vendor: Western Digital model: WDBRPG0010BNC-WRSN 
size: 931.51 GiB 
   speed: 31.6 Gb/s lanes: 4 serial:  
Partition: ID-1: / size: 183.37 GiB used: 29.34 GiB (16.0%) fs: ext4 dev: 
/dev/nvme0n1p5 
USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 
1d6b:0002 
   Hub: 1-1:2 info: Genesys Logic 4-port hub ports: 4 rev: 2.1 chip ID: 
05e3:0610 
   Hub: 1-1.4:4 info: Terminus ports: 4 rev: 2.0 chip ID: 1a40:0801 
   Device-1: 1-1.4.2:6 info: Microdia type: Keyboard,Mouse driver: 
hid-generic,usbhid 
   rev: 1.1 chip ID: 0c45:3451 
   Device-2: 1-4:9 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029 
   Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip ID: 
1d6b:0003 
   Hub: 2-1:2 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.1 chip ID: 
05e3:0626 
   Device-3: 2-1.3:3 info: Realtek RTL8153 Gigabit Ethernet Adapter 
type: Network 
   driver: r8152 rev: 3.0 chip ID: 0bda:8153 
   Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 
1d6b:0002 
   Device-4: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A 
   rev: 2.0 chip ID: 1c7a:0575 
   Device-5: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse 
   driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2 
   Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip ID: 
1d6b:0003 
Sensors:   System Temperatures: cpu: 36.1 C mobo: N/A gpu: amdgpu temp: 35 C 
   Fan Speeds (RPM): N/A 
Repos: No active apt repos in: /etc/apt/sources.list 
   Active apt repos in: 
/etc/apt/sources.list.d/brave-browser-release.list 
   1: deb 
[signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] 
https: //brave-browser-apt-release.s3.brave.com/ stable main
   Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
   1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable 
main
   Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
   1: deb https: //mirrors.sonic.net/mint/packages una main upstream 
import backport
   2: deb http: //mirrors.accretive-networks.net/ubuntu focal main 
restricted universe multiverse
   3: deb http: //mirrors.accretive-networks.net/ubuntu focal-updates 
main restricted universe multiverse
   4: deb http: //mirrors.accretive-networks.net/ubuntu focal-backports 
main restricted universe multiverse
   5: deb http: //security.ubuntu.com/ubuntu/ focal-security main 
restricted universe multiverse
   

[Kernel-packages] [Bug 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[John McGee]

** Description changed:

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but if
  I'm not it's because of unfamiliarity and general ignorance.  I beg for
  your patience and understanding.
  
  For the listed kernels in the summary line (kernels 5.13.0-21, -22, -23,
  -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are met:
  
  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input
  
  AND
  
  2)  The "Mirror" selection is toggled in the Display Manager GUI
  
  OR
  
  3)  The HDMI cable is removed from the HDMI port/USB-C hub
  
  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest any
  of the described screen crash issues listed above. That is to say, the
  laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46
  
  For your diagnostic consideration:
  
  System Info:
  [code]
- System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
-wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
- Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 
 
-Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021 
- Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2 
-model: LGC AP18C8K serial:  status: Discharging 
- CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP 
-arch: Zen rev: 1 L2 cache: 4096 KiB 
-flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938 
-Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396 
-4: 1397 5: 1908 6: 1761 7: 1736 8: 2286 
- Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel 
-bus ID: 03:00.0 chip ID: 1002:1636 
-Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa 
-resolution: 1920x1080~60Hz, 1920x1080~60Hz 
-OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1 
-direct render: Yes 
- Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel 
-bus ID: 03:00.1 chip ID: 1002:1637 
-Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
-vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5 
-chip ID: 1022:15e2 
-Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel 
-v: kernel bus ID: 03:00.6 chip ID: 1022:15e3 
-Sound Server: ALSA v: k5.11.0-46-generic 
- Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0 
-chip ID: 8086:2723 
-IF: wlp1s0 state: up mac:  
- Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%) 
-ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB 
-speed: 31.6 Gb/s lanes: 4 serial:  
- Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5 
- USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002 
-Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029 
-Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003 
-Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002 
-Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A 
-rev: 2.0 chip ID: 1c7a:0575 
-Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse 
-driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2 
-Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003 
- Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C 
-Fan Speeds (RPM): N/A 
- Repos: No active apt repos in: /etc/apt/sources.list 
-Active apt repos in: 
/etc/apt/sources.list.d/brave-browser-release.list 
-1: deb 
[signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] 
https: //brave-browser-apt-release.s3.brave.com/ stable main
-Active apt repos in: 

[Kernel-packages] [Bug 1959348] Lsusb-t.txt

[John McGee]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558088/+files/Lsusb-t.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
 

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

[John McGee]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558096/+files/RfKill.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
    

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

[John McGee]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558099/+files/acpidump.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 

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

[John McGee]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558085/+files/Lspci.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
  

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

[John McGee]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558089/+files/Lsusb-v.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
 

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

[John McGee]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558093/+files/ProcInterrupts.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: 

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

[John McGee]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558092/+files/ProcEnviron.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu 

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

[John McGee]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558095/+files/PulseList.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 

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

[John McGee]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558097/+files/UdevDb.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
    

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

[John McGee]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558086/+files/Lspci-vt.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 

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

[John McGee]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558090/+files/ProcCpuinfo.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu 

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

[John McGee]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558094/+files/ProcModules.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu 

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

[John McGee]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558098/+files/WifiSyslog.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 

[Kernel-packages] [Bug 1959348] Lsusb.txt

[John McGee]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558087/+files/Lsusb.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
  

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

[John McGee]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558091/+files/ProcCpuinfoMinimal.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A 

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

[John McGee]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1959348/+attachment/5558082/+files/CRDA.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C
    

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

[John McGee]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558084/+files/IwConfig.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 

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

[John McGee]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1959348/+attachment/5558083/+files/CurrentDmesg.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/1959348

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7
     wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 

     Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2
     model: LGC AP18C8K serial:  status: Discharging
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP
     arch: Zen rev: 1 L2 cache: 4096 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938
     Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396
     4: 1397 5: 1908 6: 1761 7: 1736 8: 2286
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel
     bus ID: 03:00.0 chip ID: 1002:1636
     Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa
     resolution: 1920x1080~60Hz, 1920x1080~60Hz
     OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1
     direct render: Yes
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel
     bus ID: 03:00.1 chip ID: 1002:1637
     Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
     vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5
     chip ID: 1022:15e2
     Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
     v: kernel bus ID: 03:00.6 chip ID: 1022:15e3
     Sound Server: ALSA v: k5.11.0-46-generic
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0
     chip ID: 8086:2723
     IF: wlp1s0 state: up mac: 
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%)
     ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB
     speed: 31.6 Gb/s lanes: 4 serial: 
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029
     Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
     Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002
     Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A
     rev: 2.0 chip ID: 1c7a:0575
     Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse
     driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2
     Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu 

[Kernel-packages] [Bug 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[John McGee]

apport information

** Tags added: apport-collected una

** Description changed:

  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but if
  I'm not it's because of unfamiliarity and general ignorance.  I beg for
  your patience and understanding.
  
  For the listed kernels in the summary line (kernels 5.13.0-21, -22, -23,
  -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are met:
  
  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input
  
  AND
  
  2)  The "Mirror" selection is toggled in the Display Manager GUI
  
  OR
  
  3)  The HDMI cable is removed from the HDMI port/USB-C hub
  
  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest any
  of the described screen crash issues listed above. That is to say, the
  laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46
  
  For your diagnostic consideration:
  
  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 
 
 Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021 
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2 
 model: LGC AP18C8K serial:  status: Discharging 
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP 
 arch: Zen rev: 1 L2 cache: 4096 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938 
 Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396 
 4: 1397 5: 1908 6: 1761 7: 1736 8: 2286 
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel 
 bus ID: 03:00.0 chip ID: 1002:1636 
 Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa 
 resolution: 1920x1080~60Hz, 1920x1080~60Hz 
 OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1 
 direct render: Yes 
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel 
 bus ID: 03:00.1 chip ID: 1002:1637 
 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
 vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5 
 chip ID: 1022:15e2 
 Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel 
 v: kernel bus ID: 03:00.6 chip ID: 1022:15e3 
 Sound Server: ALSA v: k5.11.0-46-generic 
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0 
 chip ID: 8086:2723 
 IF: wlp1s0 state: up mac:  
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%) 
 ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB 
 speed: 31.6 Gb/s lanes: 4 serial:  
  Partition: ID-1: / size: 183.37 GiB used: 28.03 GiB (15.3%) fs: ext4 dev: 
/dev/nvme0n1p5 
  USB:   Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002 
 Device-1: 1-4:6 info: Intel type: Bluetooth driver: btusb rev: 2.0 
chip ID: 8087:0029 
 Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003 
 Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip 
ID: 1d6b:0002 
 Device-2: 3-1:2 info: LighTuning EgisTec EH575 type:  driver: N/A 
 rev: 2.0 chip ID: 1c7a:0575 
 Device-3: 3-4:3 info: Microsoft Notebook Optical Mouse with Tilt 
Wheel type: Mouse 
 driver: hid-generic,usbhid rev: 2.0 chip ID: 045e:00d2 
 Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 chip 
ID: 1d6b:0003 
  Sensors:   System Temperatures: cpu: 41.8 C mobo: N/A gpu: amdgpu temp: 40 C 
 Fan Speeds (RPM): N/A 
  Repos: No active apt repos in: /etc/apt/sources.list 
 Active apt repos in: 
/etc/apt/sources.list.d/brave-browser-release.list 
 1: deb 
[signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] 
https: 

[Kernel-packages] [Bug 1935082] Re: [MIR] egl-wayland

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-495 -
495.46-0ubuntu3

---
nvidia-graphics-drivers-495 (495.46-0ubuntu3) jammy; urgency=medium

  * debian/templates/libnvidia-gl-flavour.{install|links}.in:
Include libnvidia-vulkan-producer.so now that
libnvidia-egl-wayland1 is in main (LP: #1935082).
  * debian/templates/control.in:
- Add build dependency on libnvidia-egl-wayland1.

 -- Alberto Milone   Wed, 26 Jan 2022
16:56:33 +0100

** Changed in: nvidia-graphics-drivers-495 (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [MIR] egl-wayland

Status in egl-wayland package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in egl-wayland source package in Impish:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Impish:
  Won't Fix
Status in nvidia-graphics-drivers-495 source package in Impish:
  Won't Fix

Bug description:
  MIR Template:

  [Availability]
  Already available in universe now for impish with the minimum required 1.1.7 
version.

  [Rationale]
  Past nvidia driver releases are in restricted.  If the 470 release follows 
the pattern and ultimately ends up in restricted it will suffer a performance 
penalty when used with Xwayland unless egl-wayland version 1.1.7 (or later) 
from outside the main+restricted repository set (universe) has also been 
installed.

  [Security]
  No search results found for CVS, oss-security.
  No Ubuntu CVE results for egl-wayland or variations thereof.
  The egl-wayland package installs a library with mode 0644 for use by the 
nvidia egl driver.
  While this does not seem to present security issues of its own, the library 
will be loaded and used by the nvidia egl driver and may therefore share any 
security concerns applicable to that driver.

  [Quality assurance]
  Once installed, use of egl-wayland by the nvidia egl driver is automatic, the 
single configuration file 
(/usr/share/egl/egl_external_platform.d/10_nvidia_wayland.json) installed by 
the egl-wayland package makes that happen.
  There is no configuration or other end user interaction.  The package itself 
does not have any UI of its own.
  The current universe version of the package comes from the upstream Debian 
package.
  There is a debian/watch file present.

  [Dependencies]
  The required dependencies (libc6, libwayland-client, libwayland-server) are 
already present in main.

  [Standards compliance]
  Appears to comply with both the FHS and Debian Policy standards.  The 
"/usr/share/egl/egl_external_platform.d/" directory is not specifically 
mentioned by those standards, but that directory location is required by the 
installed "10_nvidia_wayland.json" file in order for the nvidia egl driver to 
load the library that the egl-wayland package installs.

  [Maintenance]
  The egl-wayland package is a small package with few dependencies that is 
already being maintained upstream by Debian.
  Since it only installs a library and a config file and does not have any of 
its own UI, there are no i18n or l10n support issues.

  [Background information]

  The libnvidia-gl 470 drivers have been officially released as of
  2021-07-19 and have since become available in multiverse.

  The libnvidia-gl 470 release notes discuss performance under xwayland
  here:

  


  Quoting from those release notes:

  > The following are necessary to enable accelerated rendering on
  > Xwayland with the NVIDIA driver:
  >
  > * DRM KMS must be enabled. See Chapter 35, Direct Rendering Manager
  >   Kernel Modesetting (DRM KMS) for details.
  >
  > * The installed copy of Xwayland should be a build from the master
  >   branch of https://gitlab.freedesktop.org/xorg/xserver at least
  >   as recent as commit c468d34c. Note that if this requirement is
  >   not satisfied, the NVIDIA GPU can still be used for rendering,
  >   however it will fall back to a suboptimal path for presentation
  >   resulting in degraded performance.
  >
  > * libxcb version 1.13 or later must be present.
  >
  > * egl-wayland version 1.1.7 or later must be present (if installed
  >   separately from the the NVIDIA driver).
  >
  > * If using the GNOME desktop environment, kms-modifiers must be
  >   enabled through gsettings. This can be done with the following
  >   command:
  > gsettings set org.gnome.mutter experimental-features [\"kms-modifiers\"]

  The first item is easily accomplished with something like this:

  /etc/modprobe.d/nvidia-drm.conf:
  options nvidia-drm 

[Kernel-packages] [Bug 1935082] Re: [MIR] egl-wayland

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470 -
470.86-0ubuntu2

---
nvidia-graphics-drivers-470 (470.86-0ubuntu2) jammy; urgency=medium

  * debian/templates/control.in,
debian/templates/libnvidia-gl-flavour.install.in,
debian/templates/libnvidia-gl-flavour.links.in:
- Add libnvidia-vulkan-producer.so and build depend on
  libnvidia-egl-wayland1 (LP: #1935082).

 -- Alberto Milone   Wed, 26 Jan 2022
17:20:50 +0100

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

Title:
  [MIR] egl-wayland

Status in egl-wayland package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in egl-wayland source package in Impish:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Impish:
  Won't Fix
Status in nvidia-graphics-drivers-495 source package in Impish:
  Won't Fix

Bug description:
  MIR Template:

  [Availability]
  Already available in universe now for impish with the minimum required 1.1.7 
version.

  [Rationale]
  Past nvidia driver releases are in restricted.  If the 470 release follows 
the pattern and ultimately ends up in restricted it will suffer a performance 
penalty when used with Xwayland unless egl-wayland version 1.1.7 (or later) 
from outside the main+restricted repository set (universe) has also been 
installed.

  [Security]
  No search results found for CVS, oss-security.
  No Ubuntu CVE results for egl-wayland or variations thereof.
  The egl-wayland package installs a library with mode 0644 for use by the 
nvidia egl driver.
  While this does not seem to present security issues of its own, the library 
will be loaded and used by the nvidia egl driver and may therefore share any 
security concerns applicable to that driver.

  [Quality assurance]
  Once installed, use of egl-wayland by the nvidia egl driver is automatic, the 
single configuration file 
(/usr/share/egl/egl_external_platform.d/10_nvidia_wayland.json) installed by 
the egl-wayland package makes that happen.
  There is no configuration or other end user interaction.  The package itself 
does not have any UI of its own.
  The current universe version of the package comes from the upstream Debian 
package.
  There is a debian/watch file present.

  [Dependencies]
  The required dependencies (libc6, libwayland-client, libwayland-server) are 
already present in main.

  [Standards compliance]
  Appears to comply with both the FHS and Debian Policy standards.  The 
"/usr/share/egl/egl_external_platform.d/" directory is not specifically 
mentioned by those standards, but that directory location is required by the 
installed "10_nvidia_wayland.json" file in order for the nvidia egl driver to 
load the library that the egl-wayland package installs.

  [Maintenance]
  The egl-wayland package is a small package with few dependencies that is 
already being maintained upstream by Debian.
  Since it only installs a library and a config file and does not have any of 
its own UI, there are no i18n or l10n support issues.

  [Background information]

  The libnvidia-gl 470 drivers have been officially released as of
  2021-07-19 and have since become available in multiverse.

  The libnvidia-gl 470 release notes discuss performance under xwayland
  here:

  


  Quoting from those release notes:

  > The following are necessary to enable accelerated rendering on
  > Xwayland with the NVIDIA driver:
  >
  > * DRM KMS must be enabled. See Chapter 35, Direct Rendering Manager
  >   Kernel Modesetting (DRM KMS) for details.
  >
  > * The installed copy of Xwayland should be a build from the master
  >   branch of https://gitlab.freedesktop.org/xorg/xserver at least
  >   as recent as commit c468d34c. Note that if this requirement is
  >   not satisfied, the NVIDIA GPU can still be used for rendering,
  >   however it will fall back to a suboptimal path for presentation
  >   resulting in degraded performance.
  >
  > * libxcb version 1.13 or later must be present.
  >
  > * egl-wayland version 1.1.7 or later must be present (if installed
  >   separately from the the NVIDIA driver).
  >
  > * If using the GNOME desktop environment, kms-modifiers must be
  >   enabled through gsettings. This can be done with the following
  >   command:
  > gsettings set org.gnome.mutter experimental-features [\"kms-modifiers\"]

  The first item is easily accomplished with something like this:

  /etc/modprobe.d/nvidia-drm.conf:
  options nvidia-drm modeset=1

  For the second item, commit 763f4fb278 in the freedesktop.org xserver
  repository cherry-picks commit c468d34c (and an associated, not
  mentioned, but also required commit) and is first 

[Kernel-packages] [Bug 1959367] Re: Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

[Marco Ciampa]

Also I am not sure of from which version the problem did show up since
it was not me that did the upgrade that triggered the problem. If you
can grab one of those hp laptops that seems that they are _very_ common
(my friend bough it from Mediaworld) perhaps you can bisect and find the
point when exactly this problem arose. I also thought that the wifi
kernel module could be blamed of all this because of the strange
behaviour of the drivers dialog that reports that it does not work but
actually it seems to work fine... strange hu?

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

Title:
  Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some days ago I helped one of my friends who bough an HP laptop
  (15-dw1069nl ... Intel i7-10510U - nvidia GM108M(GeForce MX130)). I
  installed Ubuntu 20.04 on it without problems (not checked every
  details thought). He said that the problem happened after an update.
  After a few secs after it boots, it freezes. No way to do anything. I
  tried myself ... it happens even in the emergency console (i.e.
  without X...)! I tried reinstalling Ubuntu 20.04 myself. Yes, it fixes
  it...but true, until the next update! After the update... count 1 to 5
  after the boot and it is completely frozen.

  For the time being I resolved installing an oem kernel version 
(linux-image-oem-20.04d -> linux-image-5.14.0-1020-oem and fixed nvidia driver 
after install of package linux-oem-20.04d which installed the missing kernel 
headers files...
  BTW:

  - the driver panel says that wifi does not work (RTL 8169) but actually 
it works flawlessly
  - the screen brightness keys do not work (but the sound keys do work). 
It's probably only the keys, since using the cursor, luckily, you can regulate 
the screen backlight. xev report no key press at all...

  I am reporting this mainly for a heads up to the Ubuntu dev folks because I, 
somehow - but I do not know exactly how - resolved, and probably the same 
problems happen to the whole hp 15-sw10xx series...
  Please note that I have not direct access to that machine. So I may can 
additional tests in the future but not easily/immediately.

  lsb_release -d
  Description:  Ubuntu 20.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959367/+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 1959367] Re: Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

[Marco Ciampa]

I tried a few, with the same results (5.4.0-96-generic and
5.13.0-27-generic signed and unsigned for sure). I started to think that
it was because of something external of the kernel when I noticed that
with the "oem" series of kernels the problem just vanished. I tried some
of the "oem" series but it seems that all works right away. Hope this
has some meaning for you...

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

Title:
  Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some days ago I helped one of my friends who bough an HP laptop
  (15-dw1069nl ... Intel i7-10510U - nvidia GM108M(GeForce MX130)). I
  installed Ubuntu 20.04 on it without problems (not checked every
  details thought). He said that the problem happened after an update.
  After a few secs after it boots, it freezes. No way to do anything. I
  tried myself ... it happens even in the emergency console (i.e.
  without X...)! I tried reinstalling Ubuntu 20.04 myself. Yes, it fixes
  it...but true, until the next update! After the update... count 1 to 5
  after the boot and it is completely frozen.

  For the time being I resolved installing an oem kernel version 
(linux-image-oem-20.04d -> linux-image-5.14.0-1020-oem and fixed nvidia driver 
after install of package linux-oem-20.04d which installed the missing kernel 
headers files...
  BTW:

  - the driver panel says that wifi does not work (RTL 8169) but actually 
it works flawlessly
  - the screen brightness keys do not work (but the sound keys do work). 
It's probably only the keys, since using the cursor, luckily, you can regulate 
the screen backlight. xev report no key press at all...

  I am reporting this mainly for a heads up to the Ubuntu dev folks because I, 
somehow - but I do not know exactly how - resolved, and probably the same 
problems happen to the whole hp 15-sw10xx series...
  Please note that I have not direct access to that machine. So I may can 
additional tests in the future but not easily/immediately.

  lsb_release -d
  Description:  Ubuntu 20.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959367/+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 1935082] Re: [MIR] egl-wayland

[Steve Langasek]

Override component to main
egl-wayland 1:1.1.9-1.1 in jammy: universe/misc -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy amd64: 
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy arm64: 
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy armhf: 
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy i386: 
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy ppc64el: 
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy riscv64: 
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy s390x: 
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland1 1:1.1.9-1.1 in jammy amd64: universe/libs/optional/100% 
-> main
libnvidia-egl-wayland1 1:1.1.9-1.1 in jammy arm64: universe/libs/optional/100% 
-> main
libnvidia-egl-wayland1 1:1.1.9-1.1 in jammy armhf: universe/libs/optional/100% 
-> main
libnvidia-egl-wayland1 1:1.1.9-1.1 in jammy i386: universe/libs/optional/100% 
-> main
libnvidia-egl-wayland1 1:1.1.9-1.1 in jammy ppc64el: 
universe/libs/optional/100% -> main
libnvidia-egl-wayland1 1:1.1.9-1.1 in jammy riscv64: 
universe/libs/optional/100% -> main
libnvidia-egl-wayland1 1:1.1.9-1.1 in jammy s390x: universe/libs/optional/100% 
-> main


** Changed in: egl-wayland (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: egl-wayland (Ubuntu Impish)
   Status: New => Won't Fix

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish)
   Status: In Progress => Won't Fix

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Impish)
   Status: In Progress => Won't Fix

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

Title:
  [MIR] egl-wayland

Status in egl-wayland package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in egl-wayland source package in Impish:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Impish:
  Won't Fix
Status in nvidia-graphics-drivers-495 source package in Impish:
  Won't Fix

Bug description:
  MIR Template:

  [Availability]
  Already available in universe now for impish with the minimum required 1.1.7 
version.

  [Rationale]
  Past nvidia driver releases are in restricted.  If the 470 release follows 
the pattern and ultimately ends up in restricted it will suffer a performance 
penalty when used with Xwayland unless egl-wayland version 1.1.7 (or later) 
from outside the main+restricted repository set (universe) has also been 
installed.

  [Security]
  No search results found for CVS, oss-security.
  No Ubuntu CVE results for egl-wayland or variations thereof.
  The egl-wayland package installs a library with mode 0644 for use by the 
nvidia egl driver.
  While this does not seem to present security issues of its own, the library 
will be loaded and used by the nvidia egl driver and may therefore share any 
security concerns applicable to that driver.

  [Quality assurance]
  Once installed, use of egl-wayland by the nvidia egl driver is automatic, the 
single configuration file 
(/usr/share/egl/egl_external_platform.d/10_nvidia_wayland.json) installed by 
the egl-wayland package makes that happen.
  There is no configuration or other end user interaction.  The package itself 
does not have any UI of its own.
  The current universe version of the package comes from the upstream Debian 
package.
  There is a debian/watch file present.

  [Dependencies]
  The required dependencies (libc6, libwayland-client, libwayland-server) are 
already present in main.

  [Standards compliance]
  Appears to comply with both the FHS and Debian Policy standards.  The 
"/usr/share/egl/egl_external_platform.d/" directory is not specifically 
mentioned by those standards, but that directory location is required by the 
installed "10_nvidia_wayland.json" file in order for the nvidia egl driver to 
load the library that the egl-wayland package installs.

  [Maintenance]
  The egl-wayland package is a small package with few dependencies that is 
already being maintained upstream by Debian.
  Since it only installs a library and a config file and does not have any of 
its own UI, there are no i18n or l10n support issues.

  [Background information]

  The libnvidia-gl 470 drivers have been officially released as of
  2021-07-19 and have since become available in multiverse.

  The libnvidia-gl 470 release notes discuss performance under xwayland
  here:

  


  Quoting from those release notes:

  > The following are necessary to enable accelerated rendering on
  > Xwayland with the NVIDIA driver:
  >
  > 

[Kernel-packages] [Bug 1959173] Re: Vulnerability in af_packet handling

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-gke/5.4.0-1061.64
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

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

Title:
  Vulnerability in af_packet handling

Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-gke source package in Focal:
  In Progress

Bug description:
  CVE-2021-22600

  A vulnerability, which was classified as critical, was found in Linux
  Kernel. Affected is the function packet_set_ring of the file
  net/packet/af_packet.c. The manipulation with an unknown input leads
  to a memory corruption vulnerability. This is going to have an impact
  on confidentiality, integrity, and availability.

  The weakness was released 01/26/2022. The advisory is shared for
  download at git.kernel.org. This vulnerability is traded as
  CVE-2021-22600 since 01/05/2021. The exploitability is told to be
  easy. It is possible to launch the attack remotely. A authentication
  is required for exploitation. There are known technical details, but
  no exploit is available. The current price for an exploit might be
  approx. USD $5k-$25k (estimation calculated on 01/26/2022).

  Applying a patch is able to eliminate this problem. The fix is
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755

  More information at:
  https://partnerissuetracker.corp.google.com/issues/215427453

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1959173/+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 1959437] [NEW] Focal update: v5.4.171 upstream stable release

[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:

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

f2fs: quota: fix potential deadlock
Input: touchscreen - Fix backport of a02dcde595f7cbd240ccd64de96034ad91cffc40
selftests: x86: fix [-Wstringop-overread] warn in test_process_vm_readv()
tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
tracing: Tag trace_percpu_buffer as a percpu pointer
ieee802154: atusb: fix uninit value in atusb_set_extended_addr
iavf: Fix limit of total number of queues to active queues of VF
RDMA/core: Don't infoleak GRH fields
RDMA/uverbs: Check for null return of kmalloc_array
mac80211: initialize variable have_higher_than_11mbit
i40e: fix use-after-free in i40e_sync_filters_subtask()
i40e: Fix for displaying message regarding NVM version
i40e: Fix incorrect netdev's real number of RX/TX queues
ipv4: Check attribute length for RTA_GATEWAY in multipath route
ipv4: Check attribute length for RTA_FLOW in multipath route
ipv6: Check attribute length for RTA_GATEWAY in multipath route
ipv6: Check attribute length for RTA_GATEWAY when deleting multipath route
lwtunnel: Validate RTA_ENCAP_TYPE attribute length
batman-adv: mcast: don't send link-local multicast to mcast routers
sch_qfq: prevent shift-out-of-bounds in qfq_init_qdisc
net: phy: micrel: set soft_reset callback to genphy_soft_reset for KSZ8081
power: supply: core: Break capacity loop
power: reset: ltc2952: Fix use of floating point literals
rndis_host: support Hytera digital radios
phonet: refcount leak in pep_sock_accep
ipv6: Continue processing multipath route even if gateway attribute is invalid
ipv6: Do cleanup if attribute validation fails in multipath route
usb: mtu3: fix interval value for intr and isoc
scsi: libiscsi: Fix UAF in iscsi_conn_get_param()/iscsi_conn_teardown()
ip6_vti: initialize __ip6_tnl_parm struct in vti6_siocdevprivate
net: udp: fix alignment problem in udp4_seq_show()
atlantic: Fix buff_ring OOB in aq_ring_rx_clean
mISDN: change function names to avoid conflicts
Linux 5.4.171
UBUNTU: upstream stable to v5.4.171

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

** Affects: linux (Ubuntu Focal)
 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 Focal)
   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:
+    v5.4.171 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.171 upstream stable release
-from git://git.kernel.org/
+ f2fs: quota: fix potential deadlock
+ Input: touchscreen - Fix backport of a02dcde595f7cbd240ccd64de96034ad91cffc40
+ selftests: x86: fix [-Wstringop-overread] warn in test_process_vm_readv()
+ tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
+ tracing: Tag trace_percpu_buffer as a percpu pointer
+ ieee802154: atusb: fix uninit value in atusb_set_extended_addr
+ iavf: Fix limit of total number of queues to active queues of VF
+ RDMA/core: Don't infoleak GRH fields
+ RDMA/uverbs: Check for null return of kmalloc_array
+ mac80211: initialize variable have_higher_than_11mbit
+ i40e: fix use-after-free in i40e_sync_filters_subtask()
+ i40e: Fix for displaying message regarding NVM version
+ i40e: Fix incorrect netdev's real number of RX/TX queues
+ ipv4: Check attribute length for RTA_GATEWAY in multipath route
+ ipv4: Check attribute length for RTA_FLOW in multipath route
+ ipv6: Check 

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Henry Wertz]

I don't think this patch is intended to fix suspend/resume bug, that's
not the problem I was seeing at any rate.  That said...

Does this bug apply to GCP kernel?  I'm assuming GCP is "Google Cloud
Platform", so I'm not sure they are even using affected hardware.  AMD
CPUs are fairly power-efficient, so I could see Google using them, but
probably not the ones with built-in GPU (in favor of getting ones with
more CPU cores instead).  I assume if they want to support CUDA-style
workloads they'd thrown some monster GPUs into their "GPU compute" cloud
systems.  (That said, that all means for the use case of GCP kernel, it
should be fine either way, apply or not apply this patch.)

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

[Mariusz]

I made a experiment and I can confirm static noise after waking from
suspend.


@jamesf My device model is Lenovo Ideapad 320. You can update your post.


I will copy my other post since we are tracking this bug here:  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'.

Then you can follow instructions in post #15 to boot with Linux 5.11.0
by default.

-- 
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] [Bug 1935082] Re: [MIR] egl-wayland

[Alberto Milone]

** Also affects: egl-wayland (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470 (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-495 (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Impish)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Impish)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [MIR] egl-wayland

Status in egl-wayland package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress
Status in egl-wayland source package in Impish:
  New
Status in nvidia-graphics-drivers-470 source package in Impish:
  In Progress
Status in nvidia-graphics-drivers-495 source package in Impish:
  In Progress

Bug description:
  MIR Template:

  [Availability]
  Already available in universe now for impish with the minimum required 1.1.7 
version.

  [Rationale]
  Past nvidia driver releases are in restricted.  If the 470 release follows 
the pattern and ultimately ends up in restricted it will suffer a performance 
penalty when used with Xwayland unless egl-wayland version 1.1.7 (or later) 
from outside the main+restricted repository set (universe) has also been 
installed.

  [Security]
  No search results found for CVS, oss-security.
  No Ubuntu CVE results for egl-wayland or variations thereof.
  The egl-wayland package installs a library with mode 0644 for use by the 
nvidia egl driver.
  While this does not seem to present security issues of its own, the library 
will be loaded and used by the nvidia egl driver and may therefore share any 
security concerns applicable to that driver.

  [Quality assurance]
  Once installed, use of egl-wayland by the nvidia egl driver is automatic, the 
single configuration file 
(/usr/share/egl/egl_external_platform.d/10_nvidia_wayland.json) installed by 
the egl-wayland package makes that happen.
  There is no configuration or other end user interaction.  The package itself 
does not have any UI of its own.
  The current universe version of the package comes from the upstream Debian 
package.
  There is a debian/watch file present.

  [Dependencies]
  The required dependencies (libc6, libwayland-client, libwayland-server) are 
already present in main.

  [Standards compliance]
  Appears to comply with both the FHS and Debian Policy standards.  The 
"/usr/share/egl/egl_external_platform.d/" directory is not specifically 
mentioned by those standards, but that directory location is required by the 
installed "10_nvidia_wayland.json" file in order for the nvidia egl driver to 
load the library that the egl-wayland package installs.

  [Maintenance]
  The egl-wayland package is a small package with few dependencies that is 
already being maintained upstream by Debian.
  Since it only installs a library and a config file and does not have any of 
its own UI, there are no i18n or l10n support issues.

  [Background information]

  The libnvidia-gl 470 drivers have been officially released as of
  2021-07-19 and have since become available in multiverse.

  The libnvidia-gl 470 release notes discuss performance under xwayland
  here:

  


  Quoting from those release notes:

  > The following are necessary to enable accelerated rendering on
  > Xwayland with the NVIDIA driver:
  >
  > * DRM KMS must be enabled. See Chapter 35, Direct Rendering Manager
  >   Kernel Modesetting (DRM KMS) for details.
  >
  > * The installed copy of Xwayland should be a build from the master
  >   branch of https://gitlab.freedesktop.org/xorg/xserver at least
  >   as recent as commit c468d34c. Note that if this requirement is
  >   not satisfied, the NVIDIA GPU can still be used for rendering,
  >   however it will fall back to a suboptimal path for presentation
  >   resulting in degraded performance.
  >
  > * libxcb version 1.13 or later must be present.
  >
  > * egl-wayland version 1.1.7 or later must be present (if installed
  >   separately from the the NVIDIA driver).
  >
  > * If using the GNOME desktop environment, kms-modifiers must be
  >   enabled through gsettings. This can be 

[Kernel-packages] [Bug 1959424] [NEW] ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime

[Krzysztof Kozlowski]

Public bug reported:

d2021.10.26/jammy/linux-realtime/5.15.0-1004.4, only on node 
appleton-kernel.arm64, hangs (timeouts) on ubuntu_kernel_selftests / 
ftrace:ftracetest test:

01:28:34 DEBUG| [stdout] # === Ftrace unit tests ===
01:28:34 DEBUG| [stdout] # [1] Basic trace file check[PASS]
01:28:38 DEBUG| [stdout] # [2] Basic test for tracers[PASS]
01:28:38 DEBUG| [stdout] # [3] Basic trace clock test[PASS]
01:28:38 DEBUG| [stdout] # [4] Basic event tracing check[PASS]
01:28:39 DEBUG| [stdout] # [5] Change the ringbuffer size[PASS]
01:28:39 DEBUG| [stdout] # [6] Snapshot and tracing setting[PASS]
01:28:40 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS]
01:28:40 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers
[UNRESOLVED]
01:28:40 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes
[UNRESOLVED]
01:28:40 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe 
events[PASS]
01:28:41 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe 
events[PASS]
01:28:41 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic 
events[PASS]
01:28:41 DEBUG| [stdout] # [13] Generic dynamic event - selective clear 
(compatibility)[PASS]
01:28:41 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event
[PASS]
01:28:42 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate 
events are caught[PASS]
01:58:36 INFO | Timer expired (1800 sec.), nuking pid 161336


The issue was not reproduced on mcdivitt36 (HP ProLiant m400 server
cartridge with AppliedMicro X-Gene 64-bit ARM).

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

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


** Tags: 5.15 jammy realtime

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

** Tags added: 5.15 jammy realtime

** Summary changed:

- ubuntu_kernel_selftests / ftrace:ftracetest fails on arm64 on Jammy realtime
+ ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime

** Description changed:

- d2021.10.26/jammy/linux-realtime/5.15.0-1004.4, only on node 
appleton-kernel.arm64, hangs on ubuntu_kernel_selftests / ftrace:ftracetest 
test:
+ d2021.10.26/jammy/linux-realtime/5.15.0-1004.4, only on node 
appleton-kernel.arm64, hangs (timeouts) on ubuntu_kernel_selftests / 
ftrace:ftracetest test:
  
  01:28:34 DEBUG| [stdout] # === Ftrace unit tests ===
  01:28:34 DEBUG| [stdout] # [1] Basic trace file check[PASS]
  01:28:38 DEBUG| [stdout] # [2] Basic test for tracers[PASS]
  01:28:38 DEBUG| [stdout] # [3] Basic trace clock test[PASS]
  01:28:38 DEBUG| [stdout] # [4] Basic event tracing check[PASS]
  01:28:39 DEBUG| [stdout] # [5] Change the ringbuffer size[PASS]
  01:28:39 DEBUG| [stdout] # [6] Snapshot and tracing setting[PASS]
  01:28:40 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS]
  01:28:40 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers   
 [UNRESOLVED]
  01:28:40 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes   
 [UNRESOLVED]
  01:28:40 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe 
events[PASS]
  01:28:41 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe 
events[PASS]
  01:28:41 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic 
events[PASS]
  01:28:41 DEBUG| [stdout] # [13] Generic dynamic event - selective clear 
(compatibility)[PASS]
  01:28:41 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event   
 [PASS]
  01:28:42 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate 
events are caught[PASS]
  01:58:36 INFO | Timer expired (1800 sec.), nuking pid 161336
  
  
  The issue was not reproduced on mcdivitt36 (HP ProLiant m400 server
  cartridge with AppliedMicro X-Gene 64-bit ARM).

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

Title:
  ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy
  realtime

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  d2021.10.26/jammy/linux-realtime/5.15.0-1004.4, only on node 
appleton-kernel.arm64, hangs (timeouts) on ubuntu_kernel_selftests / 
ftrace:ftracetest test:
  
  01:28:34 DEBUG| [stdout] # === Ftrace unit tests ===
  01:28:34 DEBUG| [stdout] # [1] Basic trace file check[PASS]
  01:28:38 DEBUG| [stdout] # [2] Basic test for tracers[PASS]
  01:28:38 DEBUG| [stdout] # [3] Basic trace clock test[PASS]
  01:28:38 DEBUG| [stdout] # [4] Basic event tracing check[PASS]
  01:28:39 DEBUG| [stdout] # [5] Change the ringbuffer size[PASS]
  01:28:39 DEBUG| [stdout] # [6] Snapshot and tracing setting[PASS]
  01:28:40 DEBUG| [stdout] # [7] 

[Kernel-packages] [Bug 1959102] Re: Kernel fails to boot in ScalingStack

[Juerg Haefliger]

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

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

Title:
  Kernel fails to boot in ScalingStack

Status in linux-raspi package in Ubuntu:
  Fix Committed
Status in linux-raspi-5.4 package in Ubuntu:
  Invalid
Status in linux-raspi-5.4 source package in Bionic:
  New
Status in linux-raspi source package in Focal:
  New
Status in linux-raspi source package in Impish:
  New
Status in linux-raspi source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  The raspi kernel fails to boot in ScalingStack which is our OpenStack
  cluster for running ADT/autopkgtest tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1959102/+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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

[Kartik Agaram]

True, I can't see anything of the underlying desktop.

-- 
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 1932329] Re: Benchmark if we can compress kernel modules

[Dimitri John Ledkov]

** Description changed:

+ --- initramfs-tools
+ 
+ [Impact]
+ 
+  * Initramfs-tools already supports compressed kernel modules. However,
+ in focal it does so inefficiently. It is always better to have a
+ compressed initramfs of uncommpressed kernel modules, than a compressed
+ initrd of compressed kernel modules. Thus when kernel module compression
+ is turned on, it is prudent for initramfs-tools to pre-uncompress kernel
+ modules when building initramfs.
+ 
+ [Test Plan]
+ 
+  * Compress all kernel modules with xz for a current kernel, check that
+ all of them have .ko.xz extension and no .ko ones available
+ 
+  * Rerun depmod
+ 
+  * Update initramfs with update-initramfs -u
+ 
+  * lsinitramfs contents and check that all kernel modules are present,
+ and are uncompressed (.ko extension)
+ 
+ [Where problems could occur]
+ 
+  * This optimization for compressed kernel modules will make initramfs
+ build time longer (due to decompression) whilst improving bootspeed
+ (overall smaller size of the initrd).
+ 
+ [Other Info]
+  
+  * Original bug report re kernel feature
+ 
+ 
  Symbol: MODULE_COMPRESS_ZSTD [=n]
  Type  : bool
  
  = Impacts to measure and observe =
  
  == Disk space ==
  
  * Inspect linux-modules-* and linux-modules-extra* deb package
  Installed-Size and Download-Size changes, i.e.
  
  $ apt show linux-modules-5.8.0-53-generic linux-modules-
  extra-5.8.0-53-generic  | grep -e Package: -e Size:
  
  Package: linux-modules-5.8.0-53-generic
  Installed-Size: 81.5 MB
  Download-Size: 15.5 MB
  
  Package: linux-modules-extra-5.8.0-53-generic
  Installed-Size: 215 MB
  Download-Size: 41.5 MB
  
  In theory, there should not be a significant change in the Download-
  size. It is desired that there is a significant reduction in Installed-
  Size. Modules take up about 300MB and normally one has upto three kernel
  version installed, resulting in about of 1GB of disk space that one
  constantly pays for.
  
  == Boot Speed ==
  
  In theory, boot speed may either improve or regress. It depends if disk
  IO is slower than decompression speed, meaning loading compressed
  modules is faster.
  
  Also one has to observe the changes in the initrd size. zstd(zstd)
  compression may result in slight growth, which shouldn't impact boot
  speed too much.
  
  = Outcomes =
  
  If installed size savings can be achieved without regressing bootspeed
  we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default.

** Description changed:

  --- initramfs-tools
  
  [Impact]
  
-  * Initramfs-tools already supports compressed kernel modules. However,
+  * Initramfs-tools already supports compressed kernel modules. However,
  in focal it does so inefficiently. It is always better to have a
  compressed initramfs of uncommpressed kernel modules, than a compressed
  initrd of compressed kernel modules. Thus when kernel module compression
  is turned on, it is prudent for initramfs-tools to pre-uncompress kernel
  modules when building initramfs.
  
  [Test Plan]
  
-  * Compress all kernel modules with xz for a current kernel, check that
+  * Compress all kernel modules with xz for a current kernel, check that
  all of them have .ko.xz extension and no .ko ones available
  
-  * Rerun depmod
+  * Rerun depmod
  
-  * Update initramfs with update-initramfs -u
+  * Update initramfs with update-initramfs -u
  
-  * lsinitramfs contents and check that all kernel modules are present,
+  * lsinitramfs contents and check that all kernel modules are present,
  and are uncompressed (.ko extension)
  
  [Where problems could occur]
  
-  * This optimization for compressed kernel modules will make initramfs
+  * This optimization for compressed kernel modules will make initramfs
  build time longer (due to decompression) whilst improving bootspeed
  (overall smaller size of the initrd).
  
  [Other Info]
-  
-  * Original bug report re kernel feature
  
+  * Original bug report re kernel feature
+ 
+ --- linux
  
  Symbol: MODULE_COMPRESS_ZSTD [=n]
  Type  : bool
  
  = Impacts to measure and observe =
  
  == Disk space ==
  
  * Inspect linux-modules-* and linux-modules-extra* deb package
  Installed-Size and Download-Size changes, i.e.
  
  $ apt show linux-modules-5.8.0-53-generic linux-modules-
  extra-5.8.0-53-generic  | grep -e Package: -e Size:
  
  Package: linux-modules-5.8.0-53-generic
  Installed-Size: 81.5 MB
  Download-Size: 15.5 MB
  
  Package: linux-modules-extra-5.8.0-53-generic
  Installed-Size: 215 MB
  Download-Size: 41.5 MB
  
  In theory, there should not be a significant change in the Download-
  size. It is desired that there is a significant reduction in Installed-
  Size. Modules take up about 300MB and normally one has upto three kernel
  version installed, resulting in about of 1GB of disk space that one
  constantly pays for.
  
  == Boot Speed ==
  
  In theory, boot speed may either improve or regress. It depends if disk
  IO is slower than decompression speed, meaning loading 

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

[James Ferguson]

@akkartik - I assume yours was the same as my
https://bugs.launchpad.net/ubuntu/+source/linux-
hwe-5.13/+bug/1958591/+attachment/993/+files/PXL_20220119_165211771.jpg,
since we have I think identical machines.

Personally I'd have assumed anything described as "flickering" to be
different, since the underlying screen image is not even visible.  But
it could be that some of the bugs I listed separately actually saw this
"static" / "colored snow" display.  I think not everyone sees the
vertical bars on the right that we do.

-- 
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 : 

[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware

[Dimitri John Ledkov]

** Description changed:

+ -- initramfs-tools
+ 
+ [Impact]
+ 
+  * linux supports xz compressed linux-firmware which saves disk space.
+ In focal, initramfs-tools only knows how to included uncompressed
+ firmware files (even when kernel supports loading compressed ones).
+ Newer releases of linux-firmware may use compressed firmware files only,
+ in such cases it would be nice for focal's initramfs-tools to support
+ compressed firmware files in case of partial or incomplete upgrades
+ (i.e. linux-firmware force installed or upgraded, without newer
+ initramfs-tools). The proposed changes to initramfs-tools are backwards
+ and forwards compatible, they prefer to include uncompressed firmware
+ files; and if missing, include compressed firmware files in their
+ uncompressed form. Thus maintaining compatibility with any kernels,
+ irrespective of compressed/uncompressed firmware inputs.
+ 
+ [Test Plan]
+ 
+  * Compress all files shipped by linux-firmware with xz
+ 
+  * Rebuild initrd
+ 
+  * Check that all the same firmware files are still included in the
+ initramfs, in their uncompressed form as before
+ 
+ [Where problems could occur]
+ 
+  * This SRU is precautionary to prevent accidental installation of
+ compressed linux-firmware from generating incorrect initramfs. It should
+ be noted that whilst initramfs-tools would create a compatible initramfs
+ with any kernels, pre-v5.3 kernels do not support xz compressed firmware
+ files at runtime. Mixing this new initramfs with compressed firmwares
+ and pre 5.3 kernels may lead to expectations of supporting compressed
+ firmware files with them only working at initrd stage and not at
+ runtime.
+ 
+ [Other Info]
+ Original bug report
+ 
  Some facts:
-  - The linux kernel has supported loading xz compressed firmware since 5.3
-  - The size of /lib/firmware in impish is ~650Mb (and growing)
-  - The compressed size of firmware could be ~230Mb
+  - The linux kernel has supported loading xz compressed firmware since 5.3
+  - The size of /lib/firmware in impish is ~650Mb (and growing)
+  - The compressed size of firmware could be ~230Mb
  
  It would be nice to install compressed firmware to save space.
  
  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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

Title:
  compress firmware in /lib/firmware

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  New

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions


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

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

[Kartik Agaram]

I reported #1959340, and to clarify, what I see _could_ be characterized
as flickering. I called it "snow" in my report to compare it to the
reception from a TV with a terrestrial antenna. Each pixel on the screen
seems to get constantly changing rgb values.

One thing I've noticed is that the right side of my 16:9 gets _lines_
with constantly changing rgb values.

I can catch it on video if that's helpful.

-- 
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 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

[James Ferguson]

Scanning the duplicates, just to collect some info we have

Bugs mentioning or showing "Static" pattern of display at either boot or
suspend, mostly on Renoir 1636

#1959340: Thinkpad X13; [AMD/ATI] Renoir [1002:1636] (rev d1) (same hardware as 
this bug)
#1958248: HP Envy x360; [AMD/ATI] Renoir [1002:1636] (rev c2)
#1958412: VivoBook_ASUSLaptop TP420UA_TM420UA  [AMD/ATI] Device [1002:164c] 
(rev c2)
#1958631: HP Pavilion Gaming Laptop 15-ec1xxx; [AMD/ATI] Renoir [1002:1636] 
(rev c6)

"Blinking / Flickering, rather than static reported, devices other than
1636:

#1958523:  [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4]
#1958823: LENOVO 82KT IdeaPad 3 "blinking/flickering"; [AMD/ATI] Device 
[1002:164c] (rev c1)
#1958890: Ideapad 3 "Blinking/Flickering"; [AMD/ATI] Device [1002:164c] (rev c1)

While it has to be a strong probability it's all one issue, there is a
bit of a split between static on 1636 devices and blinking/flickering on
others.  Note the non-1636 bug in the "static" list seems slightly
different and the static occurs from different triggers, but then that's
hardly surprising with a different device even if it's one issue.

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

[Kernel-packages] [Bug 1959404] Re: Enable CONFIG_PCI_MSI_ARCH_FALLBACKS in Jammy realtime arm64 kernel

[Krzysztof Kozlowski]

Option cannot be selected on arm64, so Jammy/linux is also affected with
above warning.

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

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

Title:
  Enable CONFIG_PCI_MSI_ARCH_FALLBACKS in Jammy realtime arm64 kernel

Status in linux package in Ubuntu:
  Invalid

Bug description:
  CONFIG_PCI_MSI_ARCH_FALLBACKS should be selected for arm64, just like
  in J/linux.

  This causes boot warnings on arm64 xgene like:
  -
  [   28.297202] [ cut here ]
  [   28.297203] WARNING: CPU: 4 PID: 229 at include/linux/msi.h:262 
msix_capability_init+0x2e4/0x344
  [   28.297216] Modules linked in: mlx4_core(+) gpio_dwapb gpio_keys_polled 
ahci_xgene gpio_xgene_sb crct10dif_ce aes_neon_bs aes_neon_blk crypto_simd 
cryptd
  [   28.297232] CPU: 4 PID: 229 Comm: systemd-udevd Not tainted 
5.15.0-1004-realtime #4-Ubuntu
  [   28.297236] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [   28.297239] pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [   28.297243] pc : msix_capability_init+0x2e4/0x344
  [   28.297246] lr : msix_capability_init+0x140/0x344
  [   28.297250] sp : 80001458b550
  [   28.297251] x29: 80001458b550 x28:  x27: 
00102cc2
  [   28.297256] x26: 0a223000 x25: 0011 x24: 

  [   28.297260] x23: 0a2230d0 x22: 0011 x21: 
05bee700
  [   28.297264] x20:  x19: 0a223000 x18: 

  [   28.297268] x17:  x16: 0068 x15: 
800012789451
  [   28.297272] x14: fffd x13: 0a73746962204331 x12: 
8000128f7000
  [   28.297276] x11: 8000128f5000 x10: 00a13487c000 x9 : 
80001079f0dc
  [   28.297280] x8 : 09cd2c00 x7 : 0028 x6 : 
09cd2980
  [   28.297284] x5 : 0040 x4 :  x3 : 
0a223338
  [   28.297288] x2 :  x1 :  x0 : 

  [   28.297292] Call trace:
  [   28.297294]  msix_capability_init+0x2e4/0x344
  [   28.297298]  __pci_enable_msix_range+0x1d4/0x23c
  [   28.297301]  pci_enable_msix_range+0x24/0x30
  [   28.297304]  mlx4_enable_msi_x+0xd0/0x390 [mlx4_core]
  [   28.297360]  mlx4_load_one+0x578/0xe74 [mlx4_core]
  [   28.297401]  __mlx4_init_one+0x364/0x418 [mlx4_core]
  [   28.297441]  mlx4_init_one+0x2a0/0x310 [mlx4_core]
  [   28.297482]  local_pci_probe+0x4c/0xc0
  [   28.297487]  pci_device_probe+0x120/0x1c0
  [   28.297491]  really_probe+0xc4/0x470
  [   28.297499]  __driver_probe_device+0x11c/0x190
  [   28.297502]  driver_probe_device+0x48/0x110
  [   28.297505]  __driver_attach+0xd8/0x1f0
  [   28.297509]  bus_for_each_dev+0x7c/0xe0
  [   28.297512]  driver_attach+0x30/0x40
  [   28.297515]  bus_add_driver+0x154/0x250
  [   28.297518]  driver_register+0x84/0x140
  [   28.297522]  __pci_register_driver+0x58/0x6c
  [   28.297526]  mlx4_init+0x154/0x1000 [mlx4_core]
  [   28.297567]  do_one_initcall+0x50/0x2f0
  [   28.297571]  do_init_module+0x60/0x280
  [   28.297576]  load_module+0x9f0/0xbb0
  [   28.297578]  __do_sys_finit_module+0xa8/0x11c
  [   28.297581]  __arm64_sys_finit_module+0x2c/0x40
  [   28.297584]  invoke_syscall+0x78/0x100
  [   28.297589]  el0_svc_common.constprop.0+0x54/0x184
  [   28.297593]  do_el0_svc+0x34/0x9c
  [   28.297596]  el0_svc+0x30/0x150
  [   28.297603]  el0t_64_sync_handler+0xa4/0x130
  [   28.297606]  el0t_64_sync+0x1a4/0x1a8
  [   28.297609] ---[ end trace 0002 ]---
  [   31.897760] [ cut here ]
  [   31.897763] WARNING: CPU: 4 PID: 229 at include/linux/msi.h:268 
free_msi_irqs+0x6c/0x150
  [   31.897771] Modules linked in: mlx4_core(+) gpio_dwapb gpio_keys_polled 
ahci_xgene gpio_xgene_sb crct10dif_ce aes_neon_bs aes_neon_blk crypto_simd 
cryptd
  [   31.897782] CPU: 4 PID: 229 Comm: systemd-udevd Tainted: GW
 5.15.0-1004-realtime #4-Ubuntu
  [   31.897785] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [   31.897787] pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [   31.897791] pc : free_msi_irqs+0x6c/0x150
  [   31.897794] lr : msix_capability_init+0x2d0/0x344
  [   31.897797] sp : 80001458b510
  [   31.897799] x29: 80001458b510 x28:  x27: 
00102cc2
  [   31.897803] x26: 0a223000 x25: 0011 x24: 

  [   31.897807] x23: 0a2230d0 x22: 0a223000 x21: 
0a223338
  [   31.897811] x20: ffed x19: 0a2230d0 x18: 

  [   31.897815] x17:  x16: 0068 x15: 
800012789451
  [   31.897819] x14: fffd x13: 0a73746962204331 x12: 
8000128f7000
  [   31.897823] x11: 8000128f5000 x10: 00a13487c000 x9 : 
80001079f9d0
 

[Kernel-packages] [Bug 1690512] Re: shutdown/restart/suspend freezes laptop on intel graphics

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


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

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  shutdown/restart/suspend freezes laptop on intel graphics

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm not sure where to report this under, so please bear with me.
  Reporting this bug using ubuntu-bug just crashes my system if im using
  intel graphics, I had to switch to nvidia graphics just to file this
  bug report so the automatically attached log files may not be a good
  representation of the problem.

  I've attached the syslog and kern.log files below.

  PROBLEM:

  When using intel graphics:

  Whenever I close the laptop lid or restart / shutdown using GUI or
  terminal commands, it goes into a black screen with a single "_" at
  the top left corner, and hangs. Only long-pressing (hard reset) the
  power button would shut down the computer.

  However, when I use sudo prime-select nvidia to switch over to nvidia,
  everything works fine.log

  I have tried many things, and all do not work. I have attached the
  logs for /var/log/syslog and /var/log/kern.log below.

  Attempts so far:

  1)Tried installing new intel drivers from Updated kernel to 4.8 now
  missing firmware warnings --> Did not work. Issue persists

  2) Tried upgrading kernel from 4.8 to 4.10.15 --> Did not work.
  Problem got worse. Instead of the normal login screen, it gives a
  terminal login screen and hangs.

  3) Tried the fix to nvidia-prime
  https://askubuntu.com/a/884506/547039, but both the poweron.sh and
  poweroff.sh script hangs my laptop instead.

  4) Tried sudo swapoff -a && systemctl poweroff as a workaround, no
  avail.

  5) Tried changing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" Does not work
  either.

  Additional note:
  'sudo lshw -C display' on intel graphics outputs PCI(sysfs) then laptop 
freezes.

  LOG FILES:
  /var/log/syslog
  https://codeshare.io/5XOPwM

  /var/log/kern.log
  https://codeshare.io/aJp6nq

  specs:

  Intel 7700HQ, NVIDIA 1060GTX, kernel 4.8, Ubuntu 16.04

  Would really appreciate your help. Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 13 17:06:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-77-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-49-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-51-generic, x86_64: installed
   nvidia-381, 381.22, 4.8.0-51-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
   NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
  InstallationDate: Installed on 2017-03-30 (43 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 0483:374b STMicroelectronics 

[Kernel-packages] [Bug 1959404] [NEW] Enable CONFIG_PCI_MSI_ARCH_FALLBACKS in Jammy realtime arm64 kernel

[Krzysztof Kozlowski]

Public bug reported:

CONFIG_PCI_MSI_ARCH_FALLBACKS should be selected for arm64, just like in
J/linux.

This causes boot warnings on arm64 xgene like:
-
[   28.297202] [ cut here ]
[   28.297203] WARNING: CPU: 4 PID: 229 at include/linux/msi.h:262 
msix_capability_init+0x2e4/0x344
[   28.297216] Modules linked in: mlx4_core(+) gpio_dwapb gpio_keys_polled 
ahci_xgene gpio_xgene_sb crct10dif_ce aes_neon_bs aes_neon_blk crypto_simd 
cryptd
[   28.297232] CPU: 4 PID: 229 Comm: systemd-udevd Not tainted 
5.15.0-1004-realtime #4-Ubuntu
[   28.297236] Hardware name: HP ProLiant m400 Server Cartridge (DT)
[   28.297239] pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   28.297243] pc : msix_capability_init+0x2e4/0x344
[   28.297246] lr : msix_capability_init+0x140/0x344
[   28.297250] sp : 80001458b550
[   28.297251] x29: 80001458b550 x28:  x27: 00102cc2
[   28.297256] x26: 0a223000 x25: 0011 x24: 
[   28.297260] x23: 0a2230d0 x22: 0011 x21: 05bee700
[   28.297264] x20:  x19: 0a223000 x18: 
[   28.297268] x17:  x16: 0068 x15: 800012789451
[   28.297272] x14: fffd x13: 0a73746962204331 x12: 8000128f7000
[   28.297276] x11: 8000128f5000 x10: 00a13487c000 x9 : 80001079f0dc
[   28.297280] x8 : 09cd2c00 x7 : 0028 x6 : 09cd2980
[   28.297284] x5 : 0040 x4 :  x3 : 0a223338
[   28.297288] x2 :  x1 :  x0 : 
[   28.297292] Call trace:
[   28.297294]  msix_capability_init+0x2e4/0x344
[   28.297298]  __pci_enable_msix_range+0x1d4/0x23c
[   28.297301]  pci_enable_msix_range+0x24/0x30
[   28.297304]  mlx4_enable_msi_x+0xd0/0x390 [mlx4_core]
[   28.297360]  mlx4_load_one+0x578/0xe74 [mlx4_core]
[   28.297401]  __mlx4_init_one+0x364/0x418 [mlx4_core]
[   28.297441]  mlx4_init_one+0x2a0/0x310 [mlx4_core]
[   28.297482]  local_pci_probe+0x4c/0xc0
[   28.297487]  pci_device_probe+0x120/0x1c0
[   28.297491]  really_probe+0xc4/0x470
[   28.297499]  __driver_probe_device+0x11c/0x190
[   28.297502]  driver_probe_device+0x48/0x110
[   28.297505]  __driver_attach+0xd8/0x1f0
[   28.297509]  bus_for_each_dev+0x7c/0xe0
[   28.297512]  driver_attach+0x30/0x40
[   28.297515]  bus_add_driver+0x154/0x250
[   28.297518]  driver_register+0x84/0x140
[   28.297522]  __pci_register_driver+0x58/0x6c
[   28.297526]  mlx4_init+0x154/0x1000 [mlx4_core]
[   28.297567]  do_one_initcall+0x50/0x2f0
[   28.297571]  do_init_module+0x60/0x280
[   28.297576]  load_module+0x9f0/0xbb0
[   28.297578]  __do_sys_finit_module+0xa8/0x11c
[   28.297581]  __arm64_sys_finit_module+0x2c/0x40
[   28.297584]  invoke_syscall+0x78/0x100
[   28.297589]  el0_svc_common.constprop.0+0x54/0x184
[   28.297593]  do_el0_svc+0x34/0x9c
[   28.297596]  el0_svc+0x30/0x150
[   28.297603]  el0t_64_sync_handler+0xa4/0x130
[   28.297606]  el0t_64_sync+0x1a4/0x1a8
[   28.297609] ---[ end trace 0002 ]---
[   31.897760] [ cut here ]
[   31.897763] WARNING: CPU: 4 PID: 229 at include/linux/msi.h:268 
free_msi_irqs+0x6c/0x150
[   31.897771] Modules linked in: mlx4_core(+) gpio_dwapb gpio_keys_polled 
ahci_xgene gpio_xgene_sb crct10dif_ce aes_neon_bs aes_neon_blk crypto_simd 
cryptd
[   31.897782] CPU: 4 PID: 229 Comm: systemd-udevd Tainted: GW 
5.15.0-1004-realtime #4-Ubuntu
[   31.897785] Hardware name: HP ProLiant m400 Server Cartridge (DT)
[   31.897787] pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   31.897791] pc : free_msi_irqs+0x6c/0x150
[   31.897794] lr : msix_capability_init+0x2d0/0x344
[   31.897797] sp : 80001458b510
[   31.897799] x29: 80001458b510 x28:  x27: 00102cc2
[   31.897803] x26: 0a223000 x25: 0011 x24: 
[   31.897807] x23: 0a2230d0 x22: 0a223000 x21: 0a223338
[   31.897811] x20: ffed x19: 0a2230d0 x18: 
[   31.897815] x17:  x16: 0068 x15: 800012789451
[   31.897819] x14: fffd x13: 0a73746962204331 x12: 8000128f7000
[   31.897823] x11: 8000128f5000 x10: 00a13487c000 x9 : 80001079f9d0
[   31.897827] x8 : 09cd2c00 x7 : 0028 x6 : 09cd2980
[   31.897831] x5 : 0040 x4 :  x3 : 0a223338
[   31.897835] x2 :  x1 :  x0 : 
[   31.897838] Call trace:
[   31.897840]  free_msi_irqs+0x6c/0x150
[   31.897843]  msix_capability_init+0x2d0/0x344
[   31.897846]  __pci_enable_msix_range+0x1d4/0x23c
[   31.897849]  pci_enable_msix_range+0x24/0x30
[   31.897852]  mlx4_enable_msi_x+0xd0/0x390 [mlx4_core]
[   31.897899]  mlx4_load_one+0x578/0xe74 [mlx4_core]
[   31.897940]  

[Kernel-packages] [Bug 1957026] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.26 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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:
  Fix Committed
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:
  [SRU Justification]

  [Impact]

  On AMD Yellow Carp B0 platforms, S0i3 is still not working.

  [Fix]

  This denpends on a few fixes for kernel driver that are all either in
  v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed
  dmcub firmware.

  [Test Case]

  On AMD RMT CRB board,
  1. apply both kernel and firmware fixes
  2. module blacklist amd_sfh as it's still under development,
  3. trigger system suspend. Use power button to wake up the device.
  4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero

  On without any of above, the board may not cut device power during
  suspend, and/or fail to resume and leaving a blank screen, and/or s0ix
  stats remain all zeros.

  [Where problems could occur]

  So far all the patches can be cleanly applied, and they're being
  progressively proposed to linux-stable.

  [Other Info]

  For kernel driver fixes, patches for both oem-5.14 and jammy are
  necessary; for firmware, that has been available in jammy branch but
  not yet released, so only Focal will be nominated.

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 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

[Timo Aaltonen]

could you update the "where problems.." part, it doesn't make sense for
the firmware

-- 
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:
  Fix Committed
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:
  [SRU Justification]

  [Impact]

  On AMD Yellow Carp B0 platforms, S0i3 is still not working.

  [Fix]

  This denpends on a few fixes for kernel driver that are all either in
  v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed
  dmcub firmware.

  [Test Case]

  On AMD RMT CRB board,
  1. apply both kernel and firmware fixes
  2. module blacklist amd_sfh as it's still under development,
  3. trigger system suspend. Use power button to wake up the device.
  4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero

  On without any of above, the board may not cut device power during
  suspend, and/or fail to resume and leaving a blank screen, and/or s0ix
  stats remain all zeros.

  [Where problems could occur]

  So far all the patches can be cleanly applied, and they're being
  progressively proposed to linux-stable.

  [Other Info]

  For kernel driver fixes, patches for both oem-5.14 and jammy are
  necessary; for firmware, that has been available in jammy branch but
  not yet released, so only Focal will be nominated.

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 1958153] Please test proposed package

[Timo Aaltonen]

Hello AaronMa, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.26 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU][F] Add firmware of MT7922

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add firmware of MT7922 wifi and bluetooth.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  These firmware is specific for MT7922, it should be low risk.

  The firmware is already in impish and jammy, only SRU fw for focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958153/+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 1958283] Re: linux-firmware missing renoir_ta

[Timo Aaltonen]

Hello Ainar, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.26 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1958283

Title:
  linux-firmware missing renoir_ta

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  After today's update to the 5.13 kernel, my laptop's screen stopped
  working, showing random patterns instead.  The laptop is ThinkPad X13
  with an AMD GPU.

  In dmesg there was a message about amdgpu/renoir_ta.bin missing.
  Following some StackOverflow advice, I downloaded and installed linux-
  firmware_1.201_all.deb from the 21.10 repo, which has
  amdgpu/renoir_ta.bin and rebooted, which fixed my issue.

  Proposed Solution

  Add amdgpu/renoir_ta.bin to the current version of the linux-firmware
  package for 20.04 LTS.

  Additional Data

    $ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  Codename: focal

    $ uname -a
  Linux ainar-ThinkPad-X13-Gen-1 5.13.0-25-generic #26~20.04.1-Ubuntu SMP Fri 
Jan 7 16:27:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  [ Test Case ]

  See above. Kernel log shows firmware load failures for amdgpu firmware
  in combination with the OEM 5.13 kernel.

  [ Fix ]

  Kernel fixes for new amdgpu firmware have landed in linux-oem-5.13 so
  it's now safe to update amdgpu firmware on focal to match impish.

  [ Where Problems Could Occur ]

  Display issues with amdgpu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+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 1958286] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.26 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  mt7921e :02:00.0: PM: failed to resume async: error -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  
  [Impact]

  Mediatek MT7921 may fail to resume from runtime suspend can cause chip
  reset.

mt7921e :02:00.0: PM: failed to resume async: error -110
mt7921e :02:00.0: chip reset

  [Fix]

  This is fixed with both bluetooth and WiFi firmware upgrade to
  upstream commit 094d7adc1136 ("linux-firmware: update firmware for
  MT7921 WiFi device") and commit 1e744b85cd4c ("linux-firmware: update
  firmware for mediatek bluetooth chip(MT7921)").

  [Test Case]

  This can be triggered by checkbox warm reset stress test:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  This imports fixes requiring both kernel driver and proprietary firmware
  updates, the firmware part might cause instability or so.

  [Other Info]

  This affects all kernels supporting MT7921, which means F/H/I/J.

  == original bug report ==

  [Summary]
  Boot into Ubuntu desktop, MT7921 shows IP is obtained, however there is no 
response from gateway pings, neither is 8.8.8.8.

  kernel: [ 588.893227] mt7921e :02:00.0: PM: failed to resume async: error 
-110
  kernel: [ 588.893236] mt7921e :02:00.0: chip reset

  [Reproduce Steps]
  1. Boot into Ubuntu desktop
  2. Check if MT7921 obtains IP, ping gateway and ping 8.8.8.8
  3. No response, need to do cold boot to recover
  4. The issue is easily be seen after warm reset stress, I locally test warm 
reset stress for 100 times

  [Results]
  Expected: Has traffic and response by ping
  Actual: No response

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1958286/+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 1959064] Please test proposed package

[Timo Aaltonen]

Hello Hsuan-Yu, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.26 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU][F] Add mt8183 SCP firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  No driver is loaded for scp firmware on the mt8183 platform, and fw is 
missing too.

  [Fix]
  Add mt8183 SCP firmware

  [Test]
  Verified on the mt8183 platform, it can be loaded and powered up.

  [Where problems could occur]
  This firmware is specific for mt8183, it should be low risk.

  The firmware is already in impish and jammy, only SRU fw for focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959064/+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 1954300] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into impish-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.201.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  mt7921e: Failed to start WM firmware

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  MT7921 might fail at device probe at boot:

  mt7921e :03:00.0: WM Firmware Version: 01, Build Time: 
20211014150922
  IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
  mt7921e :03:00.0: Message 8002 (seq 9) timeout
  mt7921e :03:00.0: Failed to start WM firmware
  mt7921e: probe of :03:00.0 failed with error -110

  [Fix]

  Kernel fixes:
  * 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
  * 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")

  And firmware:
  * 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")

  [Test Case]

  Run checkbox reboot stress tests to try trigger this issue:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  This imports fixes requiring both kernel driver and proprietary firmware
  updates, the firmware part might cause instability or so.

  == original bug report ==

  Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware 
Version: 01, Build Time: 20211014150922
  Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
  Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up - 
1Gbps/Full - flow control rx/tx
  Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: 
link becomes ready
  Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64, 
error -110
  Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002 
(seq 9) timeout
  Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start 
WM firmware
  Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed 
with error -110

  This takes following fixes to resolve completely:
  * kernel patch:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
  * firmware:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+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 1958286] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into impish-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.201.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  mt7921e :02:00.0: PM: failed to resume async: error -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  
  [Impact]

  Mediatek MT7921 may fail to resume from runtime suspend can cause chip
  reset.

mt7921e :02:00.0: PM: failed to resume async: error -110
mt7921e :02:00.0: chip reset

  [Fix]

  This is fixed with both bluetooth and WiFi firmware upgrade to
  upstream commit 094d7adc1136 ("linux-firmware: update firmware for
  MT7921 WiFi device") and commit 1e744b85cd4c ("linux-firmware: update
  firmware for mediatek bluetooth chip(MT7921)").

  [Test Case]

  This can be triggered by checkbox warm reset stress test:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  This imports fixes requiring both kernel driver and proprietary firmware
  updates, the firmware part might cause instability or so.

  [Other Info]

  This affects all kernels supporting MT7921, which means F/H/I/J.

  == original bug report ==

  [Summary]
  Boot into Ubuntu desktop, MT7921 shows IP is obtained, however there is no 
response from gateway pings, neither is 8.8.8.8.

  kernel: [ 588.893227] mt7921e :02:00.0: PM: failed to resume async: error 
-110
  kernel: [ 588.893236] mt7921e :02:00.0: chip reset

  [Reproduce Steps]
  1. Boot into Ubuntu desktop
  2. Check if MT7921 obtains IP, ping gateway and ping 8.8.8.8
  3. No response, need to do cold boot to recover
  4. The issue is easily be seen after warm reset stress, I locally test warm 
reset stress for 100 times

  [Results]
  Expected: Has traffic and response by ping
  Actual: No response

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1958286/+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 1959367] Re: Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

[Paul White ]

Yes, I understand that but which version of the kernel is affected?
Without knowing which kernel version is causing these problems it's
impossible for the kernel team to take any action.

Unsubscribing and leaving to the kernel to team to investigate if they
decide to...

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

Title:
  Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some days ago I helped one of my friends who bough an HP laptop
  (15-dw1069nl ... Intel i7-10510U - nvidia GM108M(GeForce MX130)). I
  installed Ubuntu 20.04 on it without problems (not checked every
  details thought). He said that the problem happened after an update.
  After a few secs after it boots, it freezes. No way to do anything. I
  tried myself ... it happens even in the emergency console (i.e.
  without X...)! I tried reinstalling Ubuntu 20.04 myself. Yes, it fixes
  it...but true, until the next update! After the update... count 1 to 5
  after the boot and it is completely frozen.

  For the time being I resolved installing an oem kernel version 
(linux-image-oem-20.04d -> linux-image-5.14.0-1020-oem and fixed nvidia driver 
after install of package linux-oem-20.04d which installed the missing kernel 
headers files...
  BTW:

  - the driver panel says that wifi does not work (RTL 8169) but actually 
it works flawlessly
  - the screen brightness keys do not work (but the sound keys do work). 
It's probably only the keys, since using the cursor, luckily, you can regulate 
the screen backlight. xev report no key press at all...

  I am reporting this mainly for a heads up to the Ubuntu dev folks because I, 
somehow - but I do not know exactly how - resolved, and probably the same 
problems happen to the whole hp 15-sw10xx series...
  Please note that I have not direct access to that machine. So I may can 
additional tests in the future but not easily/immediately.

  lsb_release -d
  Description:  Ubuntu 20.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959367/+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 1959367] Re: Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

[Marco Ciampa]

Sorry but it is nearly impossible to do anything with the system. When
you update the kernel you have almost 5 seconds and then it freeze. It
is impossible to do _any_ kind of log...

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

Title:
  Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some days ago I helped one of my friends who bough an HP laptop
  (15-dw1069nl ... Intel i7-10510U - nvidia GM108M(GeForce MX130)). I
  installed Ubuntu 20.04 on it without problems (not checked every
  details thought). He said that the problem happened after an update.
  After a few secs after it boots, it freezes. No way to do anything. I
  tried myself ... it happens even in the emergency console (i.e.
  without X...)! I tried reinstalling Ubuntu 20.04 myself. Yes, it fixes
  it...but true, until the next update! After the update... count 1 to 5
  after the boot and it is completely frozen.

  For the time being I resolved installing an oem kernel version 
(linux-image-oem-20.04d -> linux-image-5.14.0-1020-oem and fixed nvidia driver 
after install of package linux-oem-20.04d which installed the missing kernel 
headers files...
  BTW:

  - the driver panel says that wifi does not work (RTL 8169) but actually 
it works flawlessly
  - the screen brightness keys do not work (but the sound keys do work). 
It's probably only the keys, since using the cursor, luckily, you can regulate 
the screen backlight. xev report no key press at all...

  I am reporting this mainly for a heads up to the Ubuntu dev folks because I, 
somehow - but I do not know exactly how - resolved, and probably the same 
problems happen to the whole hp 15-sw10xx series...
  Please note that I have not direct access to that machine. So I may can 
additional tests in the future but not easily/immediately.

  lsb_release -d
  Description:  Ubuntu 20.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959367/+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 1959367] Re: Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

[Paul White ]

** 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/1959367

Title:
  Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some days ago I helped one of my friends who bough an HP laptop
  (15-dw1069nl ... Intel i7-10510U - nvidia GM108M(GeForce MX130)). I
  installed Ubuntu 20.04 on it without problems (not checked every
  details thought). He said that the problem happened after an update.
  After a few secs after it boots, it freezes. No way to do anything. I
  tried myself ... it happens even in the emergency console (i.e.
  without X...)! I tried reinstalling Ubuntu 20.04 myself. Yes, it fixes
  it...but true, until the next update! After the update... count 1 to 5
  after the boot and it is completely frozen.

  For the time being I resolved installing an oem kernel version 
(linux-image-oem-20.04d -> linux-image-5.14.0-1020-oem and fixed nvidia driver 
after install of package linux-oem-20.04d which installed the missing kernel 
headers files...
  BTW:

  - the driver panel says that wifi does not work (RTL 8169) but actually 
it works flawlessly
  - the screen brightness keys do not work (but the sound keys do work). 
It's probably only the keys, since using the cursor, luckily, you can regulate 
the screen backlight. xev report no key press at all...

  I am reporting this mainly for a heads up to the Ubuntu dev folks because I, 
somehow - but I do not know exactly how - resolved, and probably the same 
problems happen to the whole hp 15-sw10xx series...
  Please note that I have not direct access to that machine. So I may can 
additional tests in the future but not easily/immediately.

  lsb_release -d
  Description:  Ubuntu 20.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959367/+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 1958718] Re: Crash on wake with kernel version 5.13

[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/1958718

Title:
  Crash on wake with kernel version 5.13

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

Bug description:
  With "linux-image-5.13.0-27-generic" on Ubuntu 20.04.3 LTS, my
  notebook (Thinkpad T14) crashes when waking up after being suspended.
  The screen displays what I would describe as "colourful snow" with
  some vertical stripes on the right edge of the display. The only thing
  I can do is power off the machine by holding the power button for
  several seconds and then restart.

  With "linux-image-5.11.0-46-generic", this does not happen.

  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.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 22 16:05:18 2022
  InstallationDate: Installed on 2020-12-28 (389 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  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/1958718/+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 1959367] [NEW] Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Some days ago I helped one of my friends who bough an HP laptop
(15-dw1069nl ... Intel i7-10510U - nvidia GM108M(GeForce MX130)). I
installed Ubuntu 20.04 on it without problems (not checked every details
thought). He said that the problem happened after an update. After a few
secs after it boots, it freezes. No way to do anything. I tried myself
... it happens even in the emergency console (i.e. without X...)! I
tried reinstalling Ubuntu 20.04 myself. Yes, it fixes it...but true,
until the next update! After the update... count 1 to 5 after the boot
and it is completely frozen.

For the time being I resolved installing an oem kernel version 
(linux-image-oem-20.04d -> linux-image-5.14.0-1020-oem and fixed nvidia driver 
after install of package linux-oem-20.04d which installed the missing kernel 
headers files...
BTW:

- the driver panel says that wifi does not work (RTL 8169) but actually it 
works flawlessly
- the screen brightness keys do not work (but the sound keys do work). It's 
probably only the keys, since using the cursor, luckily, you can regulate the 
screen backlight. xev report no key press at all...

I am reporting this mainly for a heads up to the Ubuntu dev folks because I, 
somehow - but I do not know exactly how - resolved, and probably the same 
problems happen to the whole hp 15-sw10xx series...
Please note that I have not direct access to that machine. So I may can 
additional tests in the future but not easily/immediately.

lsb_release -d
Description:Ubuntu 20.04.3 LTS

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


** Tags: bot-comment focal
-- 
Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl
https://bugs.launchpad.net/bugs/1959367
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 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Lukas Wiest]

Tested by installing linux-gcp-edge from the proposed repo which
installed mentioned version 5.13.0-1013.16~20.04.1

This didn't fix the suspend bug on focal with a Ryzen 7 4700U, but this gcp 
kernel seems to lack other drivers needed for my device, as my touch screen 
e.g. didn't work and the lid-close didn't even automatically trigger the 
suspend.
But for the bug we're trying to fix the behavior didn't change with this: 
triggering the suspend ends up in trying to go to suspend but then I'm left 
with a black screen, power led on and no reaction anymore.
Recognized the power led goes off shortly, like it would when entering suspend 
normally to start pulsing, but then instantly goes back to permanent on, like 
as it's immediately woken up again instead of staying asleep. But it never 
comes back to live from there.

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+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 1959216] Re: linux-azure: CONFIG_FB_EFI=y

[Tim Gardner]

** Description changed:

  SRU Justification
  
  [Impact]
  
  Secure boot instances of linux-azure require an EFI framebuffer in some
  cases in order for the VM to boot.
+ 
+ The issue was noticed in Ubuntu 18.04 linux-azure kernel, but actually
+ exists in the latest mainline kernel. The issue happens when the below
+ conditions are met:
+ 
+ hyperv_pci is built into the kernel and hyperv_fb is not, i.e., this means 
hyperv_pci loads before hyperv_fb loads.
+ CONFIG_FB_EFI is not defined, i.e., the efifb driver is not used.
+ 
+ Here is how the bug happens:
+ 
+ Linux VM starts, and vmbus_reserve_fb() reserves the VRAM [base=0xf800, 
length=8MB].
+ hyper-pci loads, gets MMIO [base=0xf880, lengh=8KB] as the bridge config 
window, and may get some other 64-bit MMIO ranges, and some 32-bit MMIO ranges 
(if needed.)
+ hyperv-fb loads, and gets MMIO [base=0xf800, lengh=8MB or a different 
length], and sets screen_info.lfb_base = 0.
+ VM panics.
+ The kdump kernel starts to run, and vmbus_reserve_fb() is not reserving 
[base=0xf800, length=8MB] due to the lfb_base==0.
+ hyperv-pci loads and gets [base=0xf800, lengh=8KB] and the host PCI VSP 
driver rejects this address as the bridge config window.
+ 
+ The crux of the problem is that Linux vmbus driver itself is unable to
+ detect the VRAM base/length (it looks like a video BIOS call is needed
+ to get this info and such a BIOS call is inappropriate or impossible in
+ hv_vmbus) and has to rely on screen_info.lfb_base (which is set by grub
+ or the kdump/kexec tool and can be reset to zero by hyperv_fb/drm).
+ 
+ Solution: Enable CONFIG_FB_EFI=y
  
  [Test Case]
  
  Microsoft tested. This config is also enabled on the master branch.
  
  [Where things could go wrong]
  
  VMs on certain instance types could fail to boot.
  
  [Other Info]
  
  SF: #00327005

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

Title:
  linux-azure: CONFIG_FB_EFI=y

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure-4.15 package in Ubuntu:
  Invalid
Status in linux-azure-5.11 package in Ubuntu:
  Invalid
Status in linux-azure-5.13 package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  In Progress
Status in linux-azure-4.15 source package in Bionic:
  In Progress
Status in linux-azure-5.11 source package in Bionic:
  Invalid
Status in linux-azure-5.13 source package in Bionic:
  Invalid
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure-4.15 source package in Focal:
  Invalid
Status in linux-azure-5.11 source package in Focal:
  In Progress
Status in linux-azure-5.13 source package in Focal:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure-4.15 source package in Impish:
  Invalid
Status in linux-azure-5.11 source package in Impish:
  Invalid
Status in linux-azure-5.13 source package in Impish:
  Invalid
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure-4.15 source package in Jammy:
  Invalid
Status in linux-azure-5.11 source package in Jammy:
  Invalid
Status in linux-azure-5.13 source package in Jammy:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Secure boot instances of linux-azure require an EFI framebuffer in
  some cases in order for the VM to boot.

  The issue was noticed in Ubuntu 18.04 linux-azure kernel, but actually
  exists in the latest mainline kernel. The issue happens when the below
  conditions are met:

  hyperv_pci is built into the kernel and hyperv_fb is not, i.e., this means 
hyperv_pci loads before hyperv_fb loads.
  CONFIG_FB_EFI is not defined, i.e., the efifb driver is not used.

  Here is how the bug happens:

  Linux VM starts, and vmbus_reserve_fb() reserves the VRAM [base=0xf800, 
length=8MB].
  hyper-pci loads, gets MMIO [base=0xf880, lengh=8KB] as the bridge config 
window, and may get some other 64-bit MMIO ranges, and some 32-bit MMIO ranges 
(if needed.)
  hyperv-fb loads, and gets MMIO [base=0xf800, lengh=8MB or a different 
length], and sets screen_info.lfb_base = 0.
  VM panics.
  The kdump kernel starts to run, and vmbus_reserve_fb() is not reserving 
[base=0xf800, length=8MB] due to the lfb_base==0.
  hyperv-pci loads and gets [base=0xf800, lengh=8KB] and the host PCI VSP 
driver rejects this address as the bridge config window.

  The crux of the problem is that Linux vmbus driver itself is unable to
  detect the VRAM base/length (it looks like a video BIOS call is needed
  to get this info and such a BIOS call is inappropriate or impossible
  in hv_vmbus) and has to rely on screen_info.lfb_base (which is set by
  grub or the kdump/kexec tool and can be reset to zero by
  hyperv_fb/drm).

  Solution: Enable CONFIG_FB_EFI=y

  [Test Case]

  Microsoft tested. This config is also enabled on the 

[Kernel-packages] [Bug 1958286] Re: mt7921e 0000:02:00.0: PM: failed to resume async: error -110

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware -
20220124.git0c6a7b3b-0ubuntu1

---
linux-firmware (20220124.git0c6a7b3b-0ubuntu1) jammy; urgency=medium

  * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286)
- Rebase to upstream commit 0c6a7b3bf728b95c8b7b95328f94335e2bb2c967
  Rebase against 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
  - QCA: Add Bluetooth default nvm file for WCN685x
  - i915: Add DMC firmware v2.14 for ADL-P
  - rtw89: 8852a: update fw to v0.13.33.0
  - cxgb4: Update firmware to revision 1.26.4.0
  - i915: Add GuC v69.0.3 for all platforms
  - rtl_bt: Update RTL8761B BT USB firmware to 0x09A9_8A6B
  - rtl_bt: Update RTL8761B BT UART firmware to 0x0CA9_8A6B
  - linux-firmware: wilc1000: update WILC1000 firmware to v15.4.1
  - linux-firmware: update frimware for mediatek bluetooth chip (MT7921)
  - bnx2x: Add FW 7.13.21.0
  - amdgpu: update green sardine PSP firmware
  - QCA: Update Bluetooth WCN685x firmware to 2.1.0-00298
  - rtw88: 8822c: Update normal firmware to v9.9.11
  - linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
  - linux-firmware: update firmware for MT7921 WiFi device
  - cnm: add chips wave521c firmware.
  - cxgb4: Update firmware to revision 1.26.6.0
  - QCA: Update Bluetooth WCN685x 2.0 firmware to 2.0.0-00609
  - QCA: Update Bluetooth WCN685x 2.1 firmware to 2.1.0-00324
  - QCA: Add Bluetooth nvm file for WCN685x
  - amdgpu: update yellow carp dmcub firmware
  - WHENCE: add missing symlink for NanoPi R1
  - linux-firmware: Update firmware file for Intel Bluetooth AX210
  - linux-firmware: Update firmware file for Intel Bluetooth AX211
  - linux-firmware: Update firmware file for Intel Bluetooth AX211
  - linux-firmware: Update firmware file for Intel Bluetooth AX201
  - linux-firmware: Update firmware file for Intel Bluetooth AX201
  - linux-firmware: Update firmware file for Intel Bluetooth 9560
  - linux-firmware: Update firmware file for Intel Bluetooth 9560
  - linux-firmware: Update firmware file for Intel Bluetooth 9462
  - linux-firmware: Update firmware file for Intel Bluetooth 9462
  - linux-firmware: add firmware for MT7916
  - iwlwifi: update 9000-family firmwares to core66-88
  - iwlwifi: add new FWs from core66-88 release
  - iwlwifi: add new FWs from core63-136 release
  - linux-firmware: update firmware for MT7915
  - linux-firmware: add marvell CPT firmware images
  - Mellanox: Add new mlxsw_spectrum firmware xx.2010.1232
  - linux-firmware: update firmware for MT7921 WiFi device
  - linux-firmware: update firmware for mediatek bluetooth chip(MT7921)
  - linux-firmware: Update firmware file for Intel Bluetooth AX201
  - linux-firmware: Update firmware file for Intel Bluetooth AX200
  - linux-firmware: Update firmware file for Intel Bluetooth 9560
  - linux-firmware: Update firmware file for Intel Bluetooth AX210
  - linux-firmware: Update firmware file for Intel Bluetooth AX211
  - linux-firmware: Update firmware file for Intel Bluetooth AX211
  - linux-firmware: Update firmware file for Intel Bluetooth AX201
  - linux-firmware: Update firmware file for Intel Bluetooth AX201
  - linux-firmware: Update firmware file for Intel Bluetooth 9560
  - linux-firmware: Update firmware file for Intel Bluetooth 9560
  - linux-firmware: Update firmware file for Intel Bluetooth 9462
  - linux-firmware: Update firmware file for Intel Bluetooth 9462
  - linux-firmware: Update firmware file for Intel Bluetooth 9260

 -- Juerg Haefliger   Fri, 28 Jan 2022 11:20:55
+0100

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

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

Title:
  mt7921e :02:00.0: PM: failed to resume async: error -110

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  
  [Impact]

  Mediatek MT7921 may fail to resume from runtime suspend can cause chip
  reset.

mt7921e :02:00.0: PM: failed to resume async: error -110
mt7921e :02:00.0: chip reset

  [Fix]

  This is fixed with both bluetooth and WiFi firmware upgrade to
  upstream commit 094d7adc1136 ("linux-firmware: update firmware for
  MT7921 WiFi device") and commit 1e744b85cd4c ("linux-firmware: update
  firmware for mediatek bluetooth chip(MT7921)").

  [Test Case]

  This 

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Lukas Wiest]

** Tags removed: verification-needed-focal
** Tags added: verification-failed-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/1956401

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+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 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled

[Laurent Bonnaud]

** Tags added: jammy

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

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1954938] Re: Include the QCA WCN 6856 v2.1 support

[You-Sheng Yang]

** Description changed:

  [SRU Justification]
  
  [Impact]
  
  WCN685x hw2.1 takes additional/updated firmware for both WiFi and
  Bluetooth function.
  
  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95
  
  [Fix]
  
  WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except
  for the directory path and a board-2.bin.
  
  For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from
  mainline are neccessary for Focal. Jammy has all of them already.
  
  For kernel, many of the prerequisite works have been committed for
  hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G
  will be turned off for the lack of userspace support, the only fix
  necessary is to correct read mask of version info register.
+ 
+ ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14
+ in bug 1939528, so only oem-5.14 has to be reverted.
  
  [Test Case]
  
  WiFi and Bluetooth devices should be up and running, pass basic
  operations.
  
  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci
  
  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai
  
  [Where problems could occur]
  
  At the time being, WCN685x WiFi 6G support will be turnef off
  deliberately due to the lack of full support in the userspace
  management tools.
  
  [Other Info]
  
  While this is a new hardware model from OEM program, it's only
  nominated for Focal oem-5.14 kernel and the coming LTS Jammy.
  
  == original bug report ==
  
  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95
  
  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci
  
  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

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

Title:
  Include the QCA WCN 6856 v2.1 support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  In Progress
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 Impish:
  Won't Fix
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WCN685x hw2.1 takes additional/updated firmware for both WiFi and
  Bluetooth function.

  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95

  [Fix]

  WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except
  for the directory path and a board-2.bin.

  For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from
  mainline are neccessary for Focal. Jammy has all of them already.

  For kernel, many of the prerequisite works have been committed for
  hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G
  will be turned off for the lack of userspace support, the only fix
  necessary is to correct read mask of version info register.

  ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14
  in bug 1939528, so only oem-5.14 has to be reverted.

  [Test Case]

  WiFi and Bluetooth devices should be up and running, pass basic
  operations.

  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

  [Where problems could occur]

  At the time being, 

[Kernel-packages] [Bug 1855338] Re: CONFIG_IO_STRICT_DEVMEM should be enabled

[Laurent Bonnaud]

*** This bug is a duplicate of bug 1959384 ***
https://bugs.launchpad.net/bugs/1959384

** This bug has been marked a duplicate of bug 1959384
   CONFIG_IO_STRICT_DEVMEM could be enabled

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

Title:
  CONFIG_IO_STRICT_DEVMEM should be enabled

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access
  of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel commandline to override this setting.

  
  This config option is recommended by the Kernel Self Protection Project[1] 
and a 2019 study performed by Capsule 8 shows that it is enabled in many other 
major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855338/+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 1959384] Re: CONFIG_IO_STRICT_DEVMEM could be enabled

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu)
   Status: New => 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/1959384

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1959384] [NEW] CONFIG_IO_STRICT_DEVMEM could be enabled

[Laurent Bonnaud]

Public bug reported:

Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access
of active io-memory ranges.

This could impact kernel debugability. In that case, you may reboot with
iomem=relaxed on the kernel command line to override this setting.

This config option is recommended by the Kernel Self Protection
Project[1] and a 2019 study performed by Capsule 8 shows that it is
enabled in many other major distro kernels[2].

[1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
[2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

In Ubuntu impish:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

In Debian 11:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
/boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

In Debian sid:

$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
/boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
/boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

** Affects: linux (Ubuntu)
 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/1959384

Title:
  CONFIG_IO_STRICT_DEVMEM could be enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu could enable CONFIG_IO_STRICT_DEVMEM to restrict userspace
  access of active io-memory ranges.

  This could impact kernel debugability. In that case, you may reboot with
  iomem=relaxed on the kernel command line to override this setting.

  This config option is recommended by the Kernel Self Protection
  Project[1] and a 2019 study performed by Capsule 8 shows that it is
  enabled in many other major distro kernels[2].

  [1] 
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
  [2] 
https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/

  In Ubuntu impish:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.13.0-27-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.13.0-27-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-generic:# CONFIG_IO_STRICT_DEVMEM is not set
  /boot/config-5.16.3-051603-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set

  In Debian 11:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.10.0-10-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.10.0-11-amd64:CONFIG_IO_STRICT_DEVMEM=y

  In Debian sid:

  $ grep CONFIG_IO_STRICT_DEVMEM /boot/config-*
  /boot/config-5.15.0-3-amd64:CONFIG_IO_STRICT_DEVMEM=y
  /boot/config-5.15.0-3-rt-amd64:CONFIG_IO_STRICT_DEVMEM=y

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959384/+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 1850105] Re: ubuntu_k8s_unit_tests failed to build with cannot find package "context"

[Po-Hsu Lin]

https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-
tests/commit/?id=e4b72827b7bf6dd402443b59e2d11a83ab3a749a


** Changed in: linux-signed-gcp (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  ubuntu_k8s_unit_tests failed to build with cannot find package
  "context"

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-signed-gcp package in Ubuntu:
  Invalid

Bug description:
  Issue found on Xenial GCP testing.

  Test failed with:
vendor/k8s.io/client-go/rest/request.go:21:2: cannot find package "context" 
in any of:

/tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/context 
(vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/tmp/kubernetes.git/_output/local/go/src/context (from $GOPATH)

  Complete test log:
   Running 'make test'
+++ [1023 18:04:28] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:30] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:31] Building go targets for linux/amd64:
cmd/libs/go2idl/deepcopy-gen
+++ [1023 18:04:41] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:41] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:41] Building go targets for linux/amd64:
cmd/libs/go2idl/defaulter-gen
+++ [1023 18:04:49] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:49] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:50] Building go targets for linux/amd64:
cmd/libs/go2idl/conversion-gen
+++ [1023 18:04:59] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:59] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:59] Building go targets for linux/amd64:
cmd/libs/go2idl/openapi-gen
Running tests for APIVersion: 
v1,apps/v1beta1,authentication.k8s.io/v1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1,authorization.k8s.io/v1beta1,autoscaling/v1,autoscaling/v2alpha1,batch/v1,batch/v2alpha1,certificates.k8s.io/v1beta1,extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,rbac.authorization.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1beta1,storage.k8s.io/v1,federation/v1beta1
+++ [1023 18:05:14] Running tests without code coverage
vendor/k8s.io/client-go/rest/request.go:21:2: cannot find package "context" 
in any of:
/tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/context 
(vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/tmp/kubernetes.git/_output/local/go/src/context (from $GOPATH)
!!! [1023 18:05:16] Call tree:
Makefile:164: recipe for target 'test' failed
!!! [1023 18:05:16] 1: hack/make-rules/test.sh:343 runTests(...)
make: *** [test] Error 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-1047-gcp 4.15.0-1047.50
  ProcVersionSignature: Ubuntu 4.15.0-1047.50-gcp 4.15.18
  Uname: Linux 4.15.0-1047-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Mon Oct 28 04:54:34 2019
  SourcePackage: linux-signed-gcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1850105/+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 1954938] Re: Include the QCA WCN 6856 v2.1 support

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127579.html 
(linux-oem-5.14/focal, linux/jammy)
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127581.html 
(linux-firmware/focal)
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127582.html 
(linux-firmware/jammy)

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ WCN685x hw2.1 takes additional/updated firmware for both WiFi and
+ Bluetooth function.
+ 
  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95
+ 
+ [Fix]
+ 
+ WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except
+ for the directory path and a board-2.bin.
+ 
+ For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from
+ mainline are neccessary for Focal. Jammy has all of them already.
+ 
+ For kernel, many of the prerequisite works have been committed for
+ hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G
+ will be turned off for the lack of userspace support, the only fix
+ necessary is to correct read mask of version info register.
+ 
+ [Test Case]
+ 
+ WiFi and Bluetooth devices should be up and running, pass basic
+ operations.
  
  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci
  
  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai
+ 
+ [Where problems could occur]
+ 
+ At the time being, WCN685x WiFi 6G support will be turnef off
+ deliberately due to the lack of full support in the userspace
+ management tools.
+ 
+ [Other Info]
+ 
+ While this is a new hardware model from OEM program, it's only
+ nominated for Focal oem-5.14 kernel and the coming LTS Jammy.
+ 
+ == original bug report ==
+ 
+ ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
+ ath11k_pci :71:00.0: enabling device ( -> 0002)
+ ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
+ ath11k_pci: probe of :71:00.0 failed with error -95
+ 
+ $ lspci -nnk|grep -A3 Network
+ :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
+ Subsystem: Foxconn International, Inc. Device [105b:e0ce]
+ Kernel driver in use: ath11k_pci
+ Kernel modules: ath11k_pci
+ 
+ $ lsusb
+ Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

** 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 Focal)
   Importance: Undecided => High

** 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 Impish)
   Status: New => Won't Fix

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

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

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

** Changed in: linux (Ubuntu Impish)
   Status: Incomplete => Won't Fix

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

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => 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/1954938

Title:
  Include the QCA WCN 6856 v2.1 support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  In Progress
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 Impish:
  Won't Fix
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WCN685x hw2.1 takes additional/updated firmware for both WiFi and
  Bluetooth function.

  ath11k_pci :71:00.0: BAR 0: assigned [mem 

[Kernel-packages] [Bug 1959110] Re: pl2303 serial adapter no longer recognized

[Severi Härkönen]

Regarding to https://www.spinics.net/lists/linux-usb/msg217773.html
should be fixed in kernel v5.13.15.

Unable to confirm since problem with libc6 dependency while installing
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.15/.

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

Title:
  pl2303 serial adapter no longer recognized

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

Bug description:
  Hi,

  After upgrading the Linux kernel to 5.13.0-27 my pl2303 device stopped
  working.

  Error from dmesg:

  jan 26 07:39:24 semalx0017 kernel: Linux version 5.13.0-27-generic 
(buildd@lgw01-amd64-045) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 
(Ubuntu 5.13.0>
  ...
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: pl2303 converter 
detected
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: unknown device type, 
please report to linux-...@vger.kernel.org

  This works fine in the previous 5.11.0-27-generic kernel.

  Probably this patch needs backporting 
  "USB: serial: pl2303: fix GC type detection"
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5721a9e0c9fb8a4bdfe0c8751377cd537d6174

  lsusb:

  Bus 003 Device 012: ID 067b:23a3 Prolific Technology, Inc. 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x067b Prolific Technology, Inc.
idProduct  0x23a3 
bcdDevice1.05
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Jan 26 15:11:11 2022
  InstallationDate: Installed on 2022-01-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  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/1959110/+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 1850105] Re: ubuntu_k8s_unit_tests failed to build with cannot find package "context"

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

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

Title:
  ubuntu_k8s_unit_tests failed to build with cannot find package
  "context"

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-signed-gcp package in Ubuntu:
  New

Bug description:
  Issue found on Xenial GCP testing.

  Test failed with:
vendor/k8s.io/client-go/rest/request.go:21:2: cannot find package "context" 
in any of:

/tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/context 
(vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/tmp/kubernetes.git/_output/local/go/src/context (from $GOPATH)

  Complete test log:
   Running 'make test'
+++ [1023 18:04:28] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:30] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:31] Building go targets for linux/amd64:
cmd/libs/go2idl/deepcopy-gen
+++ [1023 18:04:41] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:41] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:41] Building go targets for linux/amd64:
cmd/libs/go2idl/defaulter-gen
+++ [1023 18:04:49] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:49] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:50] Building go targets for linux/amd64:
cmd/libs/go2idl/conversion-gen
+++ [1023 18:04:59] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:59] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:59] Building go targets for linux/amd64:
cmd/libs/go2idl/openapi-gen
Running tests for APIVersion: 
v1,apps/v1beta1,authentication.k8s.io/v1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1,authorization.k8s.io/v1beta1,autoscaling/v1,autoscaling/v2alpha1,batch/v1,batch/v2alpha1,certificates.k8s.io/v1beta1,extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,rbac.authorization.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1beta1,storage.k8s.io/v1,federation/v1beta1
+++ [1023 18:05:14] Running tests without code coverage
vendor/k8s.io/client-go/rest/request.go:21:2: cannot find package "context" 
in any of:
/tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/context 
(vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/tmp/kubernetes.git/_output/local/go/src/context (from $GOPATH)
!!! [1023 18:05:16] Call tree:
Makefile:164: recipe for target 'test' failed
!!! [1023 18:05:16] 1: hack/make-rules/test.sh:343 runTests(...)
make: *** [test] Error 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-1047-gcp 4.15.0-1047.50
  ProcVersionSignature: Ubuntu 4.15.0-1047.50-gcp 4.15.18
  Uname: Linux 4.15.0-1047-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Mon Oct 28 04:54:34 2019
  SourcePackage: linux-signed-gcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1850105/+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 1959110] Re: pl2303 serial adapter no longer recognized

[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/1959110

Title:
  pl2303 serial adapter no longer recognized

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

Bug description:
  Hi,

  After upgrading the Linux kernel to 5.13.0-27 my pl2303 device stopped
  working.

  Error from dmesg:

  jan 26 07:39:24 semalx0017 kernel: Linux version 5.13.0-27-generic 
(buildd@lgw01-amd64-045) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 
(Ubuntu 5.13.0>
  ...
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: pl2303 converter 
detected
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: unknown device type, 
please report to linux-...@vger.kernel.org

  This works fine in the previous 5.11.0-27-generic kernel.

  Probably this patch needs backporting 
  "USB: serial: pl2303: fix GC type detection"
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5721a9e0c9fb8a4bdfe0c8751377cd537d6174

  lsusb:

  Bus 003 Device 012: ID 067b:23a3 Prolific Technology, Inc. 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x067b Prolific Technology, Inc.
idProduct  0x23a3 
bcdDevice1.05
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Jan 26 15:11:11 2022
  InstallationDate: Installed on 2022-01-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  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/1959110/+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 1959376] [NEW] Jammy update: v5.15.17 upstream stable release

[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.17 upstream stable release
   from git://git.kernel.org/


Linux 5.15.17
scripts: sphinx-pre-install: Fix ctex support on Debian
scripts: sphinx-pre-install: add required ctex dependency
lib/test_meminit: destroy cache in kmem_cache_alloc_bulk() test
bonding: Fix extraction of ports from the packet headers
mm/hmm.c: allow VM_MIXEDMAP to work with hmm_range_fault
lib82596: Fix IRQ check in sni_82596_probe
scripts/dtc: dtx_diff: remove broken example from help text
sch_api: Don't skip qdisc attach on ingress
dt-bindings: watchdog: Require samsung,syscon-phandle for Exynos7
dt-bindings: display: meson-vpu: Add missing amlogic,canvas property
dt-bindings: display: meson-dw-hdmi: add missing sound-name-prefix property
net: mscc: ocelot: fix using match before it is set
net: phy: micrel: use kszphy_suspend()/kszphy_resume for irq aware devices
net: cpsw: avoid alignment faults by taking NET_IP_ALIGN into account
net: sfp: fix high power modules without diagnostic monitoring
net: ocelot: Fix the call to switchdev_bridge_port_offload
net: ethernet: mtk_eth_soc: fix error checking in mtk_mac_config()
net: wwan: Fix MRU mismatch issue which may lead to data connection lost
bcmgenet: add WOL IRQ check
net: mscc: ocelot: don't let phylink re-enable TX PAUSE on the NPI port
net_sched: restore "mpu xxx" handling
net: ipa: fix atomic update in ipa_endpoint_replenish()
net: bonding: fix bond_xmit_broadcast return value error bug
net: fix sock_timestamping_bind_phc() to release device
arm64: dts: qcom: msm8996: drop not documented adreno properties
devlink: Remove misleading internal_flags from health reporter dump
perf probe: Fix ppc64 'perf probe add events failed' case
perf tools: Drop requirement for libstdc++.so for libopencsd check
dmaengine: at_xdmac: Fix at_xdmac_lld struct definition
dmaengine: at_xdmac: Fix lld view setting
dmaengine: at_xdmac: Fix concurrency over xfers_list
dmaengine: at_xdmac: Print debug message after realeasing the lock
dmaengine: at_xdmac: Start transfer for cyclic channels in issue_pending
dmaengine: at_xdmac: Don't start transactions at tx_submit level
perf script: Fix hex dump character output
libcxgb: Don't accidentally set RTO_ONLINK in cxgb_find_route()
gre: Don't accidentally set RTO_ONLINK in gre_fill_metadata_dst()
vdpa/mlx5: Restore cur_num_vqs in case of failure in change_num_qps()
xfrm: Don't accidentally set RTO_ONLINK in decode_session4()
iwlwifi: fix Bz NMI behaviour
netns: add schedule point in ops_exit_list()
inet: frags: annotate races around fqdir->dead and fqdir->high_thresh
taskstats: Cleanup the use of task->exit_code
virtio_ring: mark ring unused on error
vdpa/mlx5: Fix wrong configuration of virtio_version_1_0
rtc: pxa: fix null pointer dereference
HID: vivaldi: fix handling devices not using numbered reports
um: gitignore: Add kernel/capflags.c
bitops: protect find_first_{,zero}_bit properly
net: axienet: increase default TX ring size to 128
net: axienet: fix for TX busy handling
net: axienet: fix number of TX ring slots for available check
net: axienet: Fix TX ring slot available check
net: axienet: limit minimum TX ring size
net: axienet: add missing memory barriers
net: axienet: reset core on initialization prior to MDIO access
net: axienet: Wait for PhyRstCmplt after core reset
net: axienet: increase reset timeout
net/smc: Fix hung_task when removing SMC-R devices
gpio: idt3243x: Fix IRQ check in idt_gpio_probe
gpio: mpc8xxx: Fix IRQ check in mpc8xxx_probe
pinctrl/rockchip: fix gpio device creation
clk: si5341: Fix clock HW provider cleanup
clk: Emit a stern warning with writable debugfs enabled
af_unix: annote lockless accesses to unix_tot_inflight & gc_in_progress
crypto: octeontx2 - uninitialized variable in kvf_limits_store()
f2fs: fix to check available space of CP area correctly in update_ckpt_flags()
f2fs: fix to reserve space for IO align feature
f2fs: compress: fix potential deadlock of compress file
f2fs: fix to avoid panic in is_alive() if metadata is inconsistent
f2fs: fix remove page failed in invalidate compress pages
drm/vmwgfx: Remove unused compile options
drm/vmwgfx: Remove explicit transparent hugepages support
riscv: dts: microchip: mpfs: Drop empty chosen node
parisc: pdc_stable: Fix memory leak in pdcs_register_pathentries
net/fsl: xgmac_mdio: Fix incorrect iounmap when removing module
net/fsl: xgmac_mdio: Add workaround for erratum A-009885
mlx5: Don't accidentally set RTO_ONLINK before mlx5e_route_lookup_ipv4_get()
ipv4: avoid quadratic 

[Kernel-packages] [Bug 1959348] Re: Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27 Induce Laptop Screen Crash

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 1959348

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided
with Ubuntu by default, many require manual addition for some releases
of downstream OSes based on Ubuntu (eg. Linux Mint). You should check
with your distribution first.

Also note I've marked this as 'incomplete'.  On completion of the
`apport-collect` which will cause package & other details to populate
fields in this report (currently empty), the status should be returned
to "New".   If you are unable to run these using the kernels that
'crash', you can use other recent kernels, but please note that via
comment."

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

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

Title:
  Linux Mint kernels 5.13.0-21, -22, -23, -25, & -27  Induce Laptop
  Screen Crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please accept my apologies up front for any inefficiencies this format
  may induce, as I'm a very casual user who has just started to scratch
  the surface of Linux distro usage. I have read the instructions on the
  report submission page and I believe I am following the guidance, but
  if I'm not it's because of unfamiliarity and general ignorance.  I beg
  for your patience and understanding.

  For the listed kernels in the summary line (kernels 5.13.0-21, -22,
  -23, -25, and -27), my Acer Swift 3 laptop's screen crashes/reverts to
  snow/white noise immediately whenever the following conditions are
  met:

  1)  Any video peripheral is connected to the laptop via the HDMI port
  directly or through a USB-C hub with HDMI input

  AND

  2)  The "Mirror" selection is toggled in the Display Manager GUI

  OR

  3)  The HDMI cable is removed from the HDMI port/USB-C hub

  I can confirm that: 1) The HDMI cable is not the culprit because this
  issue doesn't manifest itself with Win10 or with Manjaro Linux, and 2)
  running Linux Mint 20.3 with the 5.11.0-46 kernel does not manifest
  any of the described screen crash issues listed above. That is to say,
  the laptop and peripheral HDMI display run stably/without issue while
  running Linux Mint 20.3 kernel 5.11.0-46

  For your diagnostic consideration:

  System Info:
  [code]
  System:Kernel: 5.11.0-46-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
  Machine:   Type: Laptop System: Acer product: Swift SF314-42 v: V1.10 serial: 
 
 Mobo: RO model: Kona_RN v: V1.10 serial:  UEFI: Insyde v: 
1.10 date: 05/13/2021 
  Battery:   ID-1: BAT1 charge: 15.4 Wh condition: 49.2/47.8 Wh (103%) volts: 
10.9/11.2 
 model: LGC AP18C8K serial:  status: Discharging 
  CPU:   Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics 
bits: 64 type: MCP 
 arch: Zen rev: 1 L2 cache: 4096 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 31938 
 Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
2: 1397 3: 1396 
 4: 1397 5: 1908 6: 1761 7: 1736 8: 2286 
  Graphics:  Device-1: AMD Renoir vendor: Acer Incorporated ALI driver: amdgpu 
v: kernel 
 bus ID: 03:00.0 chip ID: 1002:1636 
 Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati unloaded: 
fbdev,modesetting,vesa 
 resolution: 1920x1080~60Hz, 1920x1080~60Hz 
 OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 
21.0.3 compat-v: 3.1 
 direct render: Yes 
  Audio: Device-1: AMD vendor: Acer Incorporated ALI driver: snd_hda_intel 
v: kernel 
 bus ID: 03:00.1 chip ID: 1002:1637 
 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
 vendor: Acer Incorporated ALI driver: snd_rn_pci_acp3x v: kernel 
bus ID: 03:00.5 
 chip ID: 1022:15e2 
 Device-3: AMD Family 17h HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel 
 v: kernel bus ID: 03:00.6 chip ID: 1022:15e3 
 Sound Server: ALSA v: k5.11.0-46-generic 
  Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 
01:00.0 
 chip ID: 8086:2723 
 IF: wlp1s0 state: up mac:  
  Drives:Local Storage: total: 931.51 GiB used: 28.05 GiB (3.0%) 
 ID-1: /dev/nvme0n1 vendor: Western Digital model: 
WDBRPG0010BNC-WRSN size: 931.51 GiB 

[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support

[You-Sheng Yang]

** Description changed:

  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95
+ 
+ $ lspci -nnk|grep -A3 Network
+ :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
+ Subsystem: Foxconn International, Inc. Device [105b:e0ce]
+ Kernel driver in use: ath11k_pci
+ Kernel modules: ath11k_pci
+ 
+ $ lsusb
+ Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

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

Title:
  Include the QCA WCN 6856 v2.1 support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
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:
  New
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux-firmware source package in Impish:
  New
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95

  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954938/+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