[Kernel-packages] [Bug 1948627] [NEW] Ubuntu 22.04 Feature Request-Include support in Kernel and userspace to parse nBFT

[Reshmi Aravind]

Private bug reported:

This will enable boot from NVMe-oF/TCP. The nBFT is similar in function
to iBFT (iSCSI) and is currently being discussed in the relevant
standards bodies.

For more details:
https://www.linuxplumbersconf.org/event/7/contributions/737/attachments/531/944/LPC_2020_-_NVMe-oF_Boot_from_Ethernet_-_Final.pdf

There is a kernel patch that will expose the nBFT to user space here.
https://github.com/timberland-sig/linux/pull/1

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

** Information type changed from Public to Private

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

Title:
  Ubuntu 22.04 Feature Request-Include support in Kernel and userspace
  to parse nBFT

Status in linux package in Ubuntu:
  New

Bug description:
  This will enable boot from NVMe-oF/TCP. The nBFT is similar in
  function to iBFT (iSCSI) and is currently being discussed in the
  relevant standards bodies.

  For more details:
  
https://www.linuxplumbersconf.org/event/7/contributions/737/attachments/531/944/LPC_2020_-_NVMe-oF_Boot_from_Ethernet_-_Final.pdf

  There is a kernel patch that will expose the nBFT to user space here.
  https://github.com/timberland-sig/linux/pull/1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948627/+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 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Kent Lin]

** Tags added: cqa-verified

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

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
  [Steps to reproduce]
  1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to 
the system
  2. Boot to desktop
  3. Check if all Ethernet get IP address
  [Expected result]
  All Ethernet Port should up and runing and get the IP address.
  [Actual result]
  I225-IT Ethernet (8086:0d9f) does not work and did not get IP address
  [Failure rate]
  100%
  [Additional information]
  CID: 202109-29492
  SKU: N/A
  system-manufacturer: AAEON
  system-product-name: UPN-EHL01
  bios-version: UNEHAM0D
  CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571] (rev 01)
  kernel-version: 5.13.0-1004-intel

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1945548/+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 1948626] [NEW] Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010

[Reshmi Aravind]

Private bug reported:

NVMe-oF suffers from a well-known discovery problem that fundamentally limits 
the size of realistic deployments. To address this discovery problem, the FMDS 
working group (within nvme.org) is working on two proposals that will allow 
NVMe-oF to be managed via a “network centric” provisioning process instead of 
an “end-node centric” one.
TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will 
enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP 
Network and will prevent an end-user from needing to manually configure the IP 
Address of Discovery Controllers.
TP-8010 (this launchpad): will define the concept of a Centralized Discovery 
Controller (CDC) and will allow end-users to manage connectivity from a single 
point of management on an IP Fabric by IP Fabric basis.

Here is code that implements TP8009 and TP8010:
https://github.com/martin-belanger/nvme-stas/

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

** Information type changed from Public to Private

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

Title:
  Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client
  - TP 8010

Status in linux package in Ubuntu:
  New

Bug description:
  NVMe-oF suffers from a well-known discovery problem that fundamentally limits 
the size of realistic deployments. To address this discovery problem, the FMDS 
working group (within nvme.org) is working on two proposals that will allow 
NVMe-oF to be managed via a “network centric” provisioning process instead of 
an “end-node centric” one.
  TP-8009 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948625): will 
enable the Automated Discovery of NVMe-oF Discovery Controllers in an IP 
Network and will prevent an end-user from needing to manually configure the IP 
Address of Discovery Controllers.
  TP-8010 (this launchpad): will define the concept of a Centralized Discovery 
Controller (CDC) and will allow end-users to manage connectivity from a single 
point of management on an IP Fabric by IP Fabric basis.

  Here is code that implements TP8009 and TP8010:
  https://github.com/martin-belanger/nvme-stas/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

[Juerg Haefliger]

linux-raspi is the kernel package but this isn't a kernel problem

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

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => New

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1948044] Re: charon-systemd fails on raspberry pi systems under ubuntu 21.10

[Juerg Haefliger]

We introduced linux-modules-extra in impish and some modules moved to
that new package.

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

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

Title:
  charon-systemd fails on raspberry pi systems under ubuntu 21.10

Status in linux-raspi package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 21.10 from Ubuntu 21.04 my Strongswan
  installation fails. It seems that charon-systemd can´t be started. The
  problem occurs also when using a fresh install of the offical Ubuntu
  Server 21.10 image (from ).

  The problem doesn't exist on a VM running on an AMD64 system.

  I attach the output of journalctl -xeu strongswan.service (after
  increasing charons loglevel to 2).

  Kind regards
  Sven

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: charon-systemd 5.9.1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14
  Uname: Linux 5.13.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 21 11:54:32 2021
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: strongswan
  UpgradeStatus: Upgraded to impish on 2021-10-19 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948044/+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 1948623] [NEW] Ubuntu 22.04 Feature: Disable Kconfig CONFIG_PCI_REALLOC_ENABLE_AUTO option

[Sujith Pandel]

Private bug reported:

Coming from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934620
, request you to disable Kconfig option - CONFIG_PCI_REALLOC_ENABLE_AUTO

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

** Information type changed from Public to Private

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

Title:
  Ubuntu 22.04 Feature: Disable Kconfig CONFIG_PCI_REALLOC_ENABLE_AUTO
  option

Status in linux package in Ubuntu:
  New

Bug description:
  Coming from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934620 , request
  you to disable Kconfig option - CONFIG_PCI_REALLOC_ENABLE_AUTO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948623/+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 1845834] Re: help me

[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/1845834

Title:
  help me

Status in linux package in Ubuntu:
  Expired

Bug description:
  i don't know how to fix it, please help me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-64-generic 4.15.0-64.73
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  khansa 1996 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 17:21:45 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=193e5044-7646-4a90-9614-786527f30dfc
  InstallationDate: Installed on 2019-09-08 (21 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 14-3467
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic 
root=UUID=fc6c7aec-d46d-475e-ab32-d0278392eae9 ro locale=en_US alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-64-generic N/A
   linux-backports-modules-4.15.0-64-generic  N/A
   linux-firmware 1.173.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-09-13 (15 days ago)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.name: 09D1DR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn09D1DR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 14-3467
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845834/+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 1928512] Re: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

[Launchpad Bug Tracker]

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

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

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

Title:
  Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  My internet connection is unstable. The wireless fall down frequently and I 
noticed that there isn't the directory QCA9565 into the path /etc/firmware/ath*.
  I've run 'lspci -nnk |grep -i Wireless;lsusb' and the result was:
  6:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Dell QCA9565 / AR9565 Wireless Network Adapter [1028:020c]
  Bus 001 Device 006: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 012: ID 0cf3:0036 Qualcomm Atheros Communications 
  Bus 001 Device 004: ID 0c45:670b Microdia 
  Bus 001 Device 008: ID 046d:c535 Logitech, Inc. 
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928512/+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 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[You-Sheng Yang]

Verified both linux-firmware/focal and linux-firmware/impish.

** Tags added: verification-done-focal verification-done-impish

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

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

Status in HWE Next:
  New
Status in OEM Priority Project:
  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 Impish:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Sometimes MT7921 may not be probed due to an endless mcu reset:

[ 5.789548] mt7921 mcu reset 0
[ 5.790625] mt7921 rx type 0x7
[ 5.790625] mt7921 eid 0x1 ext_eid 0x0
[ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0

  [Fix]

  WiFi and Bluetooth firmware updates from mainline:
  * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip 
(MT7921)
  * d34196f5 linux-firmware: update firmware for MT7921 WiFi device

  [Test Case]

  This should fix the mcu reset and wireless/bluetooh devices should be
  probed successfully.

  [Where problems could occur]

  While there is explicit FW API for kernel version compatibility checking,
  this might introduce some hidden glitches that we don't know yet.

  [Other Info]

  MT7921 is supported since Impish 5.13 kernel, and Impish already has the
  latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13
  and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are
  required.

  == original bug report ==

  [Reproduce Steps]
  1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS.
  2.During OOBE, Open the settings, there is no wireless settings in the 
panel,and the wifi cannot be used,issue occurred.

  [Results]
  Expected Result:The wireless settings should be exists and wifi can be used
  Actual Result:The wireless settings not exists and wifi can not be used

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1947829/+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 1929895] Re: [EHL] Enable ISHTP

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [EHL] Enable ISHTP

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  This driver enables the OS to talk to eclite firmware on a dedicated
  low power chip over ISH Transport Protocol (ISHTP)

  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929895/+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 1929890] Re: [EHL][TGL][ADL] PMC Time-aware GPIO

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [EHL][TGL][ADL] PMC Time-aware GPIO

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  GPIO controller on CNL PCH has a new feature which allows for timed trigger 
of GPIO events.
  We should consider at least following aspects and if needed we can create 
subtasks:
  Translation of ART->System Time on input
  Any output GPIO
  Cross-timestamp and/or edge counting of input GPIOs supporting high frequency 
input
  Similar feature to input, counting output edges
  Time Aware GPIO Frequency Discipline - GPIO Frequency Adjustment
  Time Aware GPIO Output - Fire on Trigger
  Time Aware GPIO Input - Stamp on Edge Detection

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929890/+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 1929901] Re: [EHL][TGL][ADL] EDAC support

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [EHL][TGL][ADL] EDAC support

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged
Status in linux-intel package in Ubuntu:
  Fix Released
Status in linux-intel-5.13 package in Ubuntu:
  Fix Committed

Bug description:
  Description
  EDAC driver support on EHL & TGL for reporting ECC error and DIMM location

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929901/+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 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
  [Steps to reproduce]
  1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to 
the system
  2. Boot to desktop
  3. Check if all Ethernet get IP address
  [Expected result]
  All Ethernet Port should up and runing and get the IP address.
  [Actual result]
  I225-IT Ethernet (8086:0d9f) does not work and did not get IP address
  [Failure rate]
  100%
  [Additional information]
  CID: 202109-29492
  SKU: N/A
  system-manufacturer: AAEON
  system-product-name: UPN-EHL01
  bios-version: UNEHAM0D
  CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571] (rev 01)
  kernel-version: 5.13.0-1004-intel

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1945548/+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 1929902] Re: [EHL] enable USB-dw3

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [EHL] enable USB-dw3

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  Description
  Enable USB-dw3 for Elkhart Lake

  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929902/+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 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  Time Coordinated Compute (TCC)
  Pseudo SRAM interface support on top of Cache Allocation Technology

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

  ---

  [Update, 2021-08-26]
  Please find the Getting Started Guide for Intel TCC Tools here, has steps to 
download, install and verify:

  https://software.intel.com/content/www/us/en/develop/documentation/get-
  started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html

  You can find the BIOS settings to enable TCC here:

  https://software.intel.com/content/www/us/en/develop/documentation/get-
  started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure-
  intel-tcc-tools-in-bios.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929903/+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 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  The daily build containing the new kernel does not boot.  It gets
  stuck about 2 seconds into the cycle with the message "Run /init as
  init process" (see attached image file for boot message sequence.)

  System: TGL-Aaeon (CID: 202110-29509)

  Steps to reproduce:
  Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from 
https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/

  Uncompressed file with unxz -k

  Copied the .img file to my secondary USB drive.

  Boot 20.04 LTS from primary USB drive.

  Select Try Ubuntu

  Wipe out /dev/sda (primary storage)

  Use dd to copy the image from secondary USB drive to /dev/sda

  Reboot, removing USB drives when prompted.

  Expected Result:
  System should boot Ubuntu Desktop with kernel 5.13-1006

  Actual Result:
  System hangs 2 seconds into the boot cycle with
  "Run /init as init process"

  Reproducibility: 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1946223/+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 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform

[Pierre Equoy]

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [EHL][Graphic]Removing force probe protection from EHL platform

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  New
Status in The Focal Fossa:
  New
Status in linux-intel source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  The graphic driver i915 must be mounted manually instead of automatically.

  
  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  https://anongit.freedesktop.org/git/drm-tip.git

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938298/+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 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [EHL][Graphic]Removing force probe protection from EHL platform

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  New
Status in The Focal Fossa:
  New
Status in linux-intel source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  The graphic driver i915 must be mounted manually instead of automatically.

  
  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  https://anongit.freedesktop.org/git/drm-tip.git

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938298/+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 1936903] Re: CDTS Network (Ethernet) failures

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  CDTS Network (Ethernet) failures

Status in intel:
  New
Status in intel lookout-canyon series:
  New
Status in Ubuntu:
  Incomplete
Status in linux-intel package in Ubuntu:
  New

Bug description:
  [Summary]Some networking tests fail

  [Steps to reproduce]Run Manual Non-Device Networking Tests
  $ sudo snap install checkbox20
  $ sudo snap install cdts --classic --channel=20.04/stable
  $ cdts.checkbox-cli
  (X) Networking tests (manual)
  [X] + Non-device specific networking tests

  [Expected result]100% pass

  [Actual result]
  networking/info_device1_enp0s30f4 - skipped by tester (no second ethernet 
port on this board)
  networking/info_device2_UNKNOWN - failed by tester (should not have UNKNOWN 
devices)

  [Failure rate]100%

  [Additional information]
  CID: 202106-28175
  SKU:
  system-manufacturer: Intel Corporation
  system-product-name: Tiger Lake Client Platform
  bios-version: TGLIFUI1.R00.3455.A03.2011281547
  CPU: Genuine Intel(R) CPU  @ 2.60GHz (16x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9a60]
  kernel-version: 5.11.0-1009-intel

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936903/+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 1943524] Re: [EHL] Intel ishtp VNIC driver

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [EHL] Intel ishtp VNIC driver

Status in intel:
  New
Status in intel lookout-canyon series:
  New
Status in linux-intel-5.13 package in Ubuntu:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  The driver enables a virtual network interface for communicating with a 
dedicated low power chip over ISHTP

  Hardware: ElkhartLake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.13-yocto-210727T062416Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1943524/+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 1938413] Re: [ehl] Shutdown hangs on board

[Pierre Equoy]

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

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

Title:
  [ehl] Shutdown hangs on board

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  [Summary]Go to Power -> Shutdown and the screen goes blank, but the
  system does not shut down.  You cannot recover and have to perform a
  hard reboot.

  [Steps to reproduce]
  1. Boot up Ubuntu
  2. Power -> Shutdown (click ok)

  [Expected result]
  System should cleanly shut down.

  [Actual result]
  Screen blanks with a blinking cursor, the system does not shut down, the fan 
is still on.  System is unresponsive, forcing you to do a hard reset.

  [Failure rate]100%

  [Additional information]
  CID: 20215-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

  
  [Stage]
  Device froze, issue reported and logs collected right after a reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938413/+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 1938408] Re: [ehl] board does not support soft reboot

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

** Changed in: intel/lookout-canyon
   Status: New => Fix Committed

** Changed in: intel/lookout-canyon
Milestone: None => sprint2

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

Title:
  [ehl] board does not support soft reboot

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  [Summary]Telling the EHL board to reboot from within Ubuntu causes it
  to hang, forcing you to do a hard reboot.

  [Steps to reproduce]
  1. Open terminal window.
  2. $ reboot

  [Expected result]
  System should gracefullyl reboot.

  [Actual result]
  Screen goes blank except for a cursor.  System does not reboot. You must hard 
reboot (pull the plug)

  [Failure rate]100%

  [Additional information]
  CID: 202105-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938408/+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 1946304] Re: amdgpu: Add initial firmware for navi24 Beige Goby

[You-Sheng Yang]

Tested on same device but with QS CPU reworked.

** 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/1946304

Title:
  amdgpu: Add initial firmware for navi24 Beige Goby

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  New AMD Beige Goby/Navi24 GPU takes new firmware blobs.

  [Fix]

  Upstream commit 62fd279be67c ("amdgpu: Add initial firmware for Beige
  Goby").

  [Test Case]

  Apply firmware patch and boot with kernel >= v5.14, amdgpu should probe
  successfully.

  [Where problems could occur]

  New hardware. Expecting issues for external monitor hotplug, power
  consumption, etc.

  [Other Info]

  This change is already applied in upstream linux-firmware repo, and since
  it depends on kernel >= v5.14, only Focal is nominated for oem-5.14 here.

  == original bug report ==

  - This GPU is needed for AMD R21M-P50-50
  - amdgpu upstream driver already landed kernel v5.14.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
 [git.kernel.org]
  /* BEIGE_GOBY */
  {0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},

  - linux-firmware is being under reviewed in
  https://lore.kernel.org/linux-
  
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946304/+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 1929895] Re: [EHL] Enable ISHTP

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [EHL] Enable ISHTP

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  This driver enables the OS to talk to eclite firmware on a dedicated
  low power chip over ISH Transport Protocol (ISHTP)

  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929895/+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 1929890] Re: [EHL][TGL][ADL] PMC Time-aware GPIO

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [EHL][TGL][ADL] PMC Time-aware GPIO

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  GPIO controller on CNL PCH has a new feature which allows for timed trigger 
of GPIO events.
  We should consider at least following aspects and if needed we can create 
subtasks:
  Translation of ART->System Time on input
  Any output GPIO
  Cross-timestamp and/or edge counting of input GPIOs supporting high frequency 
input
  Similar feature to input, counting output edges
  Time Aware GPIO Frequency Discipline - GPIO Frequency Adjustment
  Time Aware GPIO Output - Fire on Trigger
  Time Aware GPIO Input - Stamp on Edge Detection

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929890/+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 1929902] Re: [EHL] enable USB-dw3

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [EHL] enable USB-dw3

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  Description
  Enable USB-dw3 for Elkhart Lake

  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929902/+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 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [TGL][ADL] Enable CET(Control-flow Enforcement Technology)

Status in intel:
  New
Status in intel lookout-canyon series:
  New
Status in linux-intel package in Ubuntu:
  Triaged
Status in linux-intel source package in Focal:
  New

Bug description:
  Description
  Enable Tiger Lake ROP CET(Control-flow Enforcement Technology)
  An upcoming Intel® processor family feature that counters 
return/jump-oriented programming (ROP) attacks

  Hardware: Tiger Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929889/+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 1938413] Re: [ehl] Shutdown hangs on board

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [ehl] Shutdown hangs on board

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  [Summary]Go to Power -> Shutdown and the screen goes blank, but the
  system does not shut down.  You cannot recover and have to perform a
  hard reboot.

  [Steps to reproduce]
  1. Boot up Ubuntu
  2. Power -> Shutdown (click ok)

  [Expected result]
  System should cleanly shut down.

  [Actual result]
  Screen blanks with a blinking cursor, the system does not shut down, the fan 
is still on.  System is unresponsive, forcing you to do a hard reset.

  [Failure rate]100%

  [Additional information]
  CID: 20215-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

  
  [Stage]
  Device froze, issue reported and logs collected right after a reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938413/+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 1929901] Re: [EHL][TGL][ADL] EDAC support

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [EHL][TGL][ADL] EDAC support

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-intel package in Ubuntu:
  Fix Released
Status in linux-intel-5.13 package in Ubuntu:
  Fix Committed

Bug description:
  Description
  EDAC driver support on EHL & TGL for reporting ECC error and DIMM location

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929901/+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 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  Time Coordinated Compute (TCC)
  Pseudo SRAM interface support on top of Cache Allocation Technology

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

  ---

  [Update, 2021-08-26]
  Please find the Getting Started Guide for Intel TCC Tools here, has steps to 
download, install and verify:

  https://software.intel.com/content/www/us/en/develop/documentation/get-
  started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html

  You can find the BIOS settings to enable TCC here:

  https://software.intel.com/content/www/us/en/develop/documentation/get-
  started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure-
  intel-tcc-tools-in-bios.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1929903/+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 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  New
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
  [Steps to reproduce]
  1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to 
the system
  2. Boot to desktop
  3. Check if all Ethernet get IP address
  [Expected result]
  All Ethernet Port should up and runing and get the IP address.
  [Actual result]
  I225-IT Ethernet (8086:0d9f) does not work and did not get IP address
  [Failure rate]
  100%
  [Additional information]
  CID: 202109-29492
  SKU: N/A
  system-manufacturer: AAEON
  system-product-name: UPN-EHL01
  bios-version: UNEHAM0D
  CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571] (rev 01)
  kernel-version: 5.13.0-1004-intel

  [Stage]
  Issue reported and logs collected right after it happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1945548/+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 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

[Pierre Equoy]

** Also affects: intel/lookout-canyon
   Importance: Undecided
   Status: New

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

Title:
  [iotg][tgl][tgl-aaeon] 20211006 image does not boot

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  New
Status in linux-intel-5.13 package in Ubuntu:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  The daily build containing the new kernel does not boot.  It gets
  stuck about 2 seconds into the cycle with the message "Run /init as
  init process" (see attached image file for boot message sequence.)

  System: TGL-Aaeon (CID: 202110-29509)

  Steps to reproduce:
  Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from 
https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/

  Uncompressed file with unxz -k

  Copied the .img file to my secondary USB drive.

  Boot 20.04 LTS from primary USB drive.

  Select Try Ubuntu

  Wipe out /dev/sda (primary storage)

  Use dd to copy the image from secondary USB drive to /dev/sda

  Reboot, removing USB drives when prompted.

  Expected Result:
  System should boot Ubuntu Desktop with kernel 5.13-1006

  Actual Result:
  System hangs 2 seconds into the boot cycle with
  "Run /init as init process"

  Reproducibility: 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1946223/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Danni Setiawan]

I have the same problem with my Thinkpad E14 Gen 2 Intel 1135G7, I
cannot boot at all with kernel 5.13.0-20-generic. Disabling trackpoint,
trackpad doesn't work. Switch back to 5.11.0-38 and everything is work.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  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.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1948382] Re: package linux-headers-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-38-generic/scripts/mod/empty.d

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-headers-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-5.11.0-38-generic/scripts/mod/empty.dwo.dpkg-new': Operation
  not permitted

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

Bug description:
  Software update kernel issue

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.11.0-38-generic 5.11.0-38.42~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Oct 21 10:19:03 2021
  DuplicateSignature:
   package:linux-headers-5.11.0-38-generic:5.11.0-38.42~20.04.1
   Unpacking linux-modules-5.11.0-38-generic (5.11.0-38.42~20.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-w2x7e3/13-linux-modules-5.11.0-38-generic_5.11.0-38.42~20.04.1_amd64.deb
 (--unpack):
unable to create new file 
'/var/lib/dpkg/info/linux-modules-5.11.0-38-generic.list-new': Operation not 
permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-5.11.0-38-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2021-03-23 (212 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-hwe-5.11
  Title: package linux-headers-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-5.11.0-38-generic/scripts/mod/empty.dwo.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1948382/+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 1948573] Re: Failure to start container “Failed to start device “eth0”: Error: Unknown device type.

[Stéphane Graber]

** Package changed: lxd (Ubuntu) => linux-raspi (Ubuntu)

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

Title:
  Failure to start container “Failed to start device “eth0”:  Error:
  Unknown device type.

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  I know probably wrong place. Tried understand where to send bug report
  but very confusing. Hopefully someone knows where to send it.

  Raspberry pi 4B, Ubuntu 21.10,

  ~lxc launch ubuntu:20.04
  ~lxc start container
  Error: Failed preparing container for start: Failed to start device “eth0”: 
Failed to create the veth interfaces veth34cbc1ee and veth84f13473: Failed to 
run: ip link add veth34cbc1ee type veth peer name veth84f13473: Error: Unknown 
device type.

  Default profile with lxdbr0

  lxc init with defaults.

  Tried different containers with the same error. Error: Unknown device
  type

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948573/+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 1948573] [NEW] Failure to start container “Failed to start device “eth0”: Error: Unknown device type.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I know probably wrong place. Tried understand where to send bug report
but very confusing. Hopefully someone knows where to send it.

Raspberry pi 4B, Ubuntu 21.10,

~lxc launch ubuntu:20.04
~lxc start container
Error: Failed preparing container for start: Failed to start device “eth0”: 
Failed to create the veth interfaces veth34cbc1ee and veth84f13473: Failed to 
run: ip link add veth34cbc1ee type veth peer name veth84f13473: Error: Unknown 
device type.

Default profile with lxdbr0

lxc init with defaults.

Tried different containers with the same error. Error: Unknown device
type

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

-- 
Failure to start container “Failed to start device “eth0”:  Error: Unknown 
device type.
https://bugs.launchpad.net/bugs/1948573
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-raspi 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 1689461] Re: bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from btd_adapter_remove_device

[Daniel van Vugt]

That is not related to this bug at all. Firstly it's the wrong program
(bt-adapter instead of bluetoothd). Secondly it doesn't mention any of
the functions this bug is about.

If you have a .crash file from Ubuntu for anything at all then please
use the 'ubuntu-bug' or 'apport-cli' to create a new bug report for it.

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

Title:
  bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from
  attio_cleanup from browse_request_cancel from device_remove from
  btd_adapter_remove_device

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/732cce930e4db100b0ec943638e1029f4655fbf9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689461/+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 1948611] Re: Second NVME drive not recognized in 5.13 kernel

[Avi Eis]

https://www.reddit.com/r/linuxhardware/comments/pyey6m/newer_kernels_do_not_detect_any_hard_drives_on/
someone else with the same issue on different hardware

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Ubuntu Kernel Bot]

This change was made by a bot.

** 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/1948611

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

** Description changed:

  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to 21.10
- it doesn't boot. Running blkid in initramfs only finds the first drive.
+ it doesn't boot on 5.13 kernel. If I manually select 5.11 in grub it
+ boots fine.
+ 
+ Running blkid in initramfs only finds the first drive.
  
  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031
  
- ubuntu-bug linux isn't letting me submit, will try to attach files after 
submitting this manually
- --- 
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  a  5963 F pulseaudio
-  /dev/snd/controlC0:  a  5963 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  a  5963 F pulseaudio
+  /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
-  linux-restricted-modules-5.11.0-37-generic N/A
-  linux-backports-modules-5.11.0-37-generic  N/A
-  linux-firmware 1.201
+  linux-restricted-modules-5.11.0-37-generic N/A
+  linux-backports-modules-5.11.0-37-generic  N/A
+  linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_dela

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1948611/+attachment/5535701/+files/AlsaInfo.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/1948611

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1948611/+attachment/5535710/+files/PaInfo.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/1948611

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

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

[Avi Eis]

apport information

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

Title:
  Second NVME drive not recognized in 5.13 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to
  21.10 it doesn't boot on 5.13 kernel. If I manually select 5.11 in
  grub it boots fine.

  Running blkid in initramfs only finds the first drive.

  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  5963 F pulseaudio
   /dev/snd/controlC0:  a  5963 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-02-20 (977 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-37-generic N/A
   linux-backports-modules-5.11.0-37-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.11.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
  UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.4
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.04
  dmi.board.name: DA770
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
  dmi.product.family: 1A583004 Razer Blade
  dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
  dmi.product.sku: RZ09-0406CE63
  dmi.product.version: 7.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948611/+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 1948611] [NEW] Second NVME drive not recognized in 5.13 kernel

[Avi Eis]

Public bug reported:

On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
the 2nd one. It works fine on 5.11 kernel, but when I upgraded to 21.10
it doesn't boot on 5.13 kernel. If I manually select 5.11 in grub it
boots fine.

Running blkid in initramfs only finds the first drive.

I found someone with what appears to be the same issue in
https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031


---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  a  5963 F pulseaudio
 /dev/snd/controlC0:  a  5963 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-02-20 (977 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-37-generic N/A
 linux-backports-modules-5.11.0-37-generic  N/A
 linux-firmware 1.201
Tags:  impish wayland-session
Uname: Linux 5.11.0-37-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Razer
dmi.bios.version: 1.04
dmi.board.name: DA770
dmi.board.vendor: Razer
dmi.board.version: 4
dmi.chassis.type: 10
dmi.chassis.vendor: Razer
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnRazer:bvr1.04:bd08/02/2021:br1.4:efr1.3:svnRazer:pnBlade17(Mid2021)-RZ09-0406:pvr7.04:skuRZ09-0406CE63:rvnRazer:rnDA770:rvr4:cvnRazer:ct10:cvr:
dmi.product.family: 1A583004 Razer Blade
dmi.product.name: Blade 17 (Mid 2021) - RZ09-0406
dmi.product.sku: RZ09-0406CE63
dmi.product.version: 7.04
dmi.sys.vendor: Razer

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


** Tags: apport-collected impish wayland-session

** Tags added: apport-collected impish wayland-session

** Description changed:

  On a Razer Blade Pro 17' 2021 model I have 2 NVME drives and boot off
  the 2nd one. It works fine on 5.11 kernel, but when I upgraded to 21.10
  it doesn't boot. Running blkid in initramfs only finds the first drive.
  
  I found someone with what appears to be the same issue in
  https://bbs.archlinux.org/viewtopic.php?pid=1996031#p1996031
  
- ubuntu-bug linux isn't letting me submit, will try to attach files after
- submitting this manually
+ ubuntu-bug linux isn't letting me submit, will try to attach files after 
submitting this manually
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu70
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  a  5963 F pulseaudio
+  /dev/snd/controlC0:  a  5963 F pulseaudio
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2019-02-20 (977 days ago)
+ InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
+ MachineType: Razer Blade 17 (Mid 2021) - RZ09-0406
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=18e8777c-1764-41e4-a19f-62476055de23 ro button.lid_init_state=open 
modprobe.blacklist=nouveau rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1 
button.lid_init_state=open modprobe.blacklist=nouveau 
rcutree.rcu_idle_gp_delay=1 rcutree.gp_init_delay=1
+ ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-37-generic N/A
+  linux-backports-modules-5.11.0-37-generic  N/A
+  linux-firmware 1.201
+ Tags:  impish wayland-session
+ Uname: Linux 5.11.0-37-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-10-15 (9 days ago)
+ UserGroups: adm bumblebee cdrom dip docker kvm libvirt lpadmin plex plugdev 
sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 08/02/2021
+ dmi.bios.release: 1.4
+ dmi.bios.vendor: Razer
+ dmi.bios.version: 1.04
+ dmi.board.name: DA770
+ dmi.board.vendor: Razer
+ dmi.boa

[Kernel-packages] [Bug 1948610] [NEW] Home directory not recognized

[mark maurer]

Public bug reported:

Used synaptic package manager to install linux-oem-20.04d kernel.  After reboot 
login worked fine, but then desktop reverted to default background and scale 
factor of 1 instead of 2.  (the new installation dialog appeared on desktop 
after login).
Nautilus was very sluggish to open.  Normal /home was not shown. 

Rebooted and removed Linus-oem-20.04d and everything is fine.

I use a ZFS zpool mirror for my /home (since 16.04 actually).  I had
great luck using the linux-oem-5.10 kernel in the past, but this time
the oem kernel is behaving differently.

I am happy to stay on standard Ubuntu kernel, but just wanted to report
this behavior.

***

lsb_release -rd
Description:Ubuntu 20.04.3 LTS

linux-oem-20.04d

expected to upgrade kernel while leaving desktop and preferences intact

instead my /home was not recognized and desktop reverted to that of a
new installation

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-oem-20.04d (not installed)
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 24 19:30:41 2021
InstallationDate: Installed on 2020-11-15 (343 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-oem-5.14
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-meta-oem-5.14 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  Home directory not recognized

Status in linux-meta-oem-5.14 package in Ubuntu:
  New

Bug description:
  Used synaptic package manager to install linux-oem-20.04d kernel.  After 
reboot login worked fine, but then desktop reverted to default background and 
scale factor of 1 instead of 2.  (the new installation dialog appeared on 
desktop after login).
  Nautilus was very sluggish to open.  Normal /home was not shown. 

  Rebooted and removed Linus-oem-20.04d and everything is fine.

  I use a ZFS zpool mirror for my /home (since 16.04 actually).  I had
  great luck using the linux-oem-5.10 kernel in the past, but this time
  the oem kernel is behaving differently.

  I am happy to stay on standard Ubuntu kernel, but just wanted to
  report this behavior.

  
***

  lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS

  linux-oem-20.04d

  expected to upgrade kernel while leaving desktop and preferences
  intact

  instead my /home was not recognized and desktop reverted to that of a
  new installation

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-oem-20.04d (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 24 19:30:41 2021
  InstallationDate: Installed on 2020-11-15 (343 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.14/+bug/1948610/+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 1948604] [NEW] package linux-firmware 1.187.19 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Hamyat]

Public bug reported:

error processing package linux-firmware

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.19
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  hamyat 1452 F pulseaudio
 /dev/snd/controlC0:  hamyat 1452 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Oct 25 05:28:48 2021
Dependencies:
 
DpkgHistoryLog:
 Start-Date: 2021-10-25  05:28:48
 Commandline: apt autoremove
 Requested-By: hamyat (1000)
DpkgTerminalLog:
 dpkg: error processing package linux-firmware (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2021-02-26 (240 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 81ST
PackageArchitecture: all
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=30ede6a9-a85e-430f-923c-572ffc1b9c8c ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
SourcePackage: linux-firmware
Title: package linux-firmware 1.187.19 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2020
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: AYCN24WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55754WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-14AST
dmi.ec.firmware.release: 1.24
dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN24WW:bd10/12/2020:br1.24:efr1.24:svnLENOVO:pn81ST:pvrLenovoIdeaPadS145-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55754WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-14AST:
dmi.product.family: IdeaPad S145-14AST
dmi.product.name: 81ST
dmi.product.sku: LENOVO_MT_81ST_BU_idea_FM_IdeaPad S145-14AST
dmi.product.version: Lenovo IdeaPad S145-14AST
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package 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/1948604

Title:
  package linux-firmware 1.187.19 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  error processing package linux-firmware

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.19
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hamyat 1452 F pulseaudio
   /dev/snd/controlC0:  hamyat 1452 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 25 05:28:48 2021
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2021-10-25  05:28:48
   Commandline: apt autoremove
   Requested-By: hamyat (1000)
  DpkgTerminalLog:
   dpkg: error processing package linux-firmware (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2021-02-26 (240 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 81ST
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=30ede6a9-a85e-430f-923c-572ffc1b9c8c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.187.19 failed to install/upgrade: package is 
in a 

[Kernel-packages] [Bug 1945309] Re: Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake GT2 [HD Graphics 520]

[Uyfar Us]

I believe the fix is already released, however, my issue persists.

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

Title:
  Screen flickering on Ubuntu 20.04 - HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520]

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

Bug description:
  I am using Ubuntu 20.04.3 LTS on my HP Spectre X360 with Intel Skylake
  GT2 [HD Graphics 520] and I am having flickering graphics.

  The problem sometimes happens showing grey flickering boxes 5-6 times
  in a minute, and sometimes it does not happen for 2-3 minutes.
  Overall, it annoys me quite a lot.

  I have tried decreasing the refresh rate from 60Hz to lower options,
  but that didn't work. Updating the drivers or purging Intel graphics
  didn't work either. I also tried a couple of stuff I saw online
  regarding /etc/X11/xorg.conf.d/.

  I do not have this issue on Windows, therefore it must be Ubuntu-
  related.

  When I set nomodeset on GRUB and update it, flickering disappears, but
  at the cost of my brightness adjuster and Night Light.

  As for package I have:

  apt-cache policy pkgname
  N: Unable to locate package pkgname

  dpkg -l |grep xserver-xorg-core
  ii xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 amd64 Xorg X server - core 
server

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 28 11:55:47 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:804e]
  InstallationDate: Installed on 2021-09-22 (5 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=c68313b0-c9ba-4714-abc0-dff5762a92b2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
  Identifier  "Intel Graphics"
  Driver  "intel"
  Option  "TearFree""true"
   EndSection
  dmi.bios.date: 12/27/2019
  dmi.bios.release: 15.54
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.54
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 804E
  dmi.board.vendor: HP
  dmi.board.version: 33.24
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 33.24
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.54:bd12/27/2019:br15.54:efr33.24:svnHP:pnHPSpectrex360Convertible:pvr:skuN7H72EA#AB8:rvnHP:rn804E:rvr33.24:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.product.sku: N7H72EA#AB8
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-1028
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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.11/+bug/1945309/+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 1948601] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** 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/1948601

Title:
  package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to
  install/upgrade: installed linux-image-4.15.0-29-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I dont know how to reinstall it

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  perojhan   1182 F pulseaudio
vicki  2139 F pulseaudio
  Date: Sun Oct 24 12:38:57 2021
  ErrorMessage: installed linux-image-4.15.0-29-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=e8c99a6b-f5cd-43e4-8576-b63239891c9c
  InstallationDate: Installed on 2018-09-03 (1146 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4dd8 Primax Electronics, Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=e148cac7-908c-46b5-ab0c-abddb75ccaf4 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3
  SourcePackage: linux
  Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: installed linux-image-4.15.0-29-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.38
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3672
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 23.4A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.38:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3672:rvr23.4A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068C11000320491620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948601/+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 1948601] [NEW] package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: installed linux-image-4.15.0-29-generic package pre-removal script subprocess return

[Sara Robbins]

Public bug reported:

I dont know how to reinstall it

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  perojhan   1182 F pulseaudio
  vicki  2139 F pulseaudio
Date: Sun Oct 24 12:38:57 2021
ErrorMessage: installed linux-image-4.15.0-29-generic package pre-removal 
script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=e8c99a6b-f5cd-43e4-8576-b63239891c9c
InstallationDate: Installed on 2018-09-03 (1146 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0461:4dd8 Primax Electronics, Ltd 
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard Presario CQ57 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=e148cac7-908c-46b5-ab0c-abddb75ccaf4 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3
SourcePackage: linux
Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to 
install/upgrade: installed linux-image-4.15.0-29-generic package pre-removal 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.38
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3672
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 23.4A
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.38:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3672:rvr23.4A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE
dmi.product.name: Presario CQ57 Notebook PC
dmi.product.version: 068C11000320491620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to
  install/upgrade: installed linux-image-4.15.0-29-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  I dont know how to reinstall it

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  perojhan   1182 F pulseaudio
vicki  2139 F pulseaudio
  Date: Sun Oct 24 12:38:57 2021
  ErrorMessage: installed linux-image-4.15.0-29-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=e8c99a6b-f5cd-43e4-8576-b63239891c9c
  InstallationDate: Installed on 2018-09-03 (1146 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4dd8 Primax Electronics, Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=e148cac7-908c-46b5-ab0c-abddb75ccaf4 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  R

[Kernel-packages] [Bug 1945043] Re: Impish: problem with bluetooth mouse: not connectable

[Norbert]

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

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

Title:
  Impish:  problem with bluetooth mouse: not connectable

Status in Ubuntu MATE:
  New
Status in blueman package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem with bluetooth mouse: not connectable
  I have a bluetooth mouse that I use regularly with Ubuntu Mate 20.04.x
  I tried the impish version of Ubuntu Mate but, using the same notebook, the 
computer cannot recognize it, in the bluetooth search, and then connect it.
  I tested the functionality of the mouse and it works with other devices as 
well. The brand of the MEMTEQ mouse.

  I downloaded the Impish Mate version of 09-25-2021 and I made a fresh 
installation. I also proceeded to update (it only updated Firefox because I 
believe all other updates were included).
  Unfortunately the indicated problem has not been solved. With the updated 
Ubuntu Mate 20.04 LTS it works. I also used another Bluetooth adapter on 
another PC and the result is the same. Hello.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1945043/+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 1933716] Re: Black screen on boot after stable update

[Mike E.]

Just updated to 5.11.0-38-generic on my ProBook 450 G6 with an i7-8565U
processor and both displays are back to working again.  On 20.04 focal.
5.11.0-37-generic did not work, so it was something that was part of the
-38 update that fixed the issue for me.

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

Title:
  Black screen on boot after stable update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system
  boots into black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-18-generic 5.11.0-18.19
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 1374 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 26 11:55:00 2021
  InstallationDate: Installed on 2021-05-02 (55 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HP HP Pavilion Laptop 15-eg0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2021
  dmi.bios.release: 15.12
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 87CB
  dmi.board.vendor: HP
  dmi.board.version: 34.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 34.27
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg0xxx
  dmi.product.sku: 2Q2T4EA#AKD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1948576/+attachment/5535538/+files/PaInfo.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/1948576

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Adam]

apport information

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948576/+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 1948576] Re: Ubuntu 21.10 latest update making problem

[Adam]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

- The fans spin at max and the system freezes after I un-suspend the
- system. That start to happen after I update the latest 21.10. I was
- happy with the 21.10 at the begging but when I update the latest
- release, got me upset. Please see attached log file.
+ The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu70
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ahmed  2282 F pulseaudio
+  /dev/snd/controlC1:  ahmed  2282 F pulseaudio
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-03-14 (224 days ago)
+ InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
+ MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-20-generic N/A
+  linux-backports-modules-5.13.0-20-generic  N/A
+  linux-firmware 1.201
+ Tags:  impish wayland-session
+ Uname: Linux 5.13.0-20-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
+ UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/20/2021
+ dmi.bios.release: 5.19
+ dmi.bios.vendor: American Megatrends International, LLC.
+ dmi.bios.version: UX363EA.306
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX363EA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
+ dmi.product.family: ZenBook Flip
+ dmi.product.name: ZenBook UX363EA_UX371EA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1948576/+attachment/5535529/+files/AlsaInfo.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/1948576

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LL

[Kernel-packages] [Bug 1948576] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1948576

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: impish

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the
  system. That start to happen after I update the latest 21.10. I was
  happy with the 21.10 at the begging but when I update the latest
  release, got me upset. Please see attached log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948576/+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 1948576] [NEW] Ubuntu 21.10 latest update making problem

[Adam]

Public bug reported:

The fans spin at max and the system freezes after I un-suspend the
system. That start to happen after I update the latest 21.10. I was
happy with the 21.10 at the begging but when I update the latest
release, got me upset. Please see attached log file.

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

** Attachment added: "log messages"
   
https://bugs.launchpad.net/bugs/1948576/+attachment/5535527/+files/log%20messages

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  New

Bug description:
  The fans spin at max and the system freezes after I un-suspend the
  system. That start to happen after I update the latest 21.10. I was
  happy with the 21.10 at the begging but when I update the latest
  release, got me upset. Please see attached log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948576/+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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Adam Niedling]

** Tags added: impish

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+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 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

[Norbert]

** Tags removed: groovy

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

Title:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

  PIONEER BD-RW   BDR-205

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:11:53 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+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 1900391] Re: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled

[Norbert]

** Tags removed: groovy

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

Title:
  EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is
  disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [4.589406] EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but 
ECC is disabled
  [4.589410] EDAC sbridge: Couldn't find mci handler
  [4.589411] EDAC sbridge: Failed to register device with error -19.

  but x79 doesn't have ecc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:19:05 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900391/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Yves Roggeman]

Exactly the same as #48 for me.
I'm working without trackpoint, thus also without any button (left, mid and 
right click) that have to be emulated with multifingers gesture, when it is 
possible.
Very annoying, especially for long distance moves for example.
Please, consider this bug with very high priority.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  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.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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