[Kernel-packages] [Bug 1983625] Re: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter.

2022-08-10 Thread Awais Tanveer
** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1983625

Title:
  5.15.0-1013-oracle: Unable to boot large memory SEV guest without
  setting swiotlb parameter.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When launching a SEV Ubuntu22.04 guest with e.g. memory > 16876M, Ubuntu 
kernel
  5.15.0-1013-oracle panics unless swiotlb=262144 is specified on guest kernel
  parameters. It seems that the kernel tries to adjust swiotlb buffer size but
  can not do that and crashes. With a memory size such as 8G, the guest boots 
fine.

  HOST INFO

  Host type : OCI Bare-Metal Server
  Server/Machine: ORACLE SERVER E2-2c
  CPU model : AMD EPYC 7742 64-Core Processor
  Architecture  : x86_64
  Hostname  : atanveer-amd-sme
  OS: Oracle Linux Server release 7.9
  Kernel: 5.4.17-2136.309.4.el7uek.x86_64 #2 SMP Tue Jun 28 17:35:13 
PDT 2022
  Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-18.oci.el7)
  OVMF/AAVMF: OVMF-1.6.3-1.el7.noarch

  Qemu command to launch SEV guest:

  /bin/qemu-system-x86_64 -name OL22.04-uefi \
  -machine q35 \
  -enable-kvm \
  -cpu host,+host-phys-bits \
  -m 16877M \
  -smp 8,maxcpus=240 \
  -D ./22.04-uefi.log \
  -nodefaults \
  -monitor stdio \
  -vnc 0.0.0.0:0,to=999 \
  -vga std \
  -drive 
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 \
  -drive file=OVMF_VARS.pure-efi.fd.ol22.04,index=1,if=pflash,format=raw \
  -device 
virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true \
  -drive 
file=Ubuntu-22.04-2022.06.16-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 \
  -device ide-hd,drive=local_disk0,id=local_disk1,bootindex=0 \
  -qmp tcp:127.0.0.1:3334,server,nowait \
  -serial telnet:127.0.0.1:,server,nowait \
  -device virtio-rng-pci,disable-legacy=on,iommu_platform=true \
  -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1 \
  -machine memory-encryption=sev0

  Console log:

  [0.005025] software IO TLB: SWIOTLB bounce buffer size adjusted to 1011MB
  [0.033881] kvm-guest: KVM setup pv remote TLB flush
  [0.054931] software IO TLB: Cannot allocate buffer
  [0.248933] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.249582] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.317440] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.317440] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [0.424952] iommu: DMA domain TLB invalidation policy: lazy mode
  [0.570923] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [0.571669] software IO TLB: No low mem
  .
  .
  .
  .
  [1.233515] ata1: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010100 
irq 28
  [1.234985] ata2: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010180 
irq 28
  [1.236464] ata3: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010200 
irq 28
  [1.237863] ata4: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010280 
irq 28
  [1.239257] ata5: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010300 
irq 28
  [1.240659] ata6: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010380 
irq 28
  [1.555165] ata5: SATA link down (SStatus 0 SControl 300)
  [1.556661] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [1.558232] ata2: SATA link down (SStatus 0 SControl 300)
  [1.559728] ata4: SATA link down (SStatus 0 SControl 300)
  [1.560996] ata3: SATA link down (SStatus 0 SControl 300)
  [1.562134] ata1: SATA link down (SStatus 0 SControl 300)
  [1.563566] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, 
err_mask=0x80)
  [6.911450] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.912906] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, 
err_mask=0x80)
  [   12.288045] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [   12.289904] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, 
err_mask=0x80)
  [   17.663548] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [  242.883993] INFO: task kworker/u480:0:9 blocked for more than 120 seconds.
  [  242.885619]   Not tainted 5.15.0-1013-oracle #17-Ubuntu
  [  242.886743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.888198] task:kworker/u480:0  state:D stack:0 pid:9 ppid: 2 
flags:0x4000
  [  242.889703] Workqueue: events_unbound async_run_entry_fn
  [  242.890882] Call Trace:
  [  242.891727]  

  
  Full console log is attached.

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


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

[Kernel-packages] [Bug 1983625] Re: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter.

2022-08-10 Thread Awais Tanveer
Can not run apport-collect logs since the SEV guest instance fails to
boot.

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

Title:
  5.15.0-1013-oracle: Unable to boot large memory SEV guest without
  setting swiotlb parameter.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When launching a SEV Ubuntu22.04 guest with e.g. memory > 16876M, Ubuntu 
kernel
  5.15.0-1013-oracle panics unless swiotlb=262144 is specified on guest kernel
  parameters. It seems that the kernel tries to adjust swiotlb buffer size but
  can not do that and crashes. With a memory size such as 8G, the guest boots 
fine.

  HOST INFO

  Host type : OCI Bare-Metal Server
  Server/Machine: ORACLE SERVER E2-2c
  CPU model : AMD EPYC 7742 64-Core Processor
  Architecture  : x86_64
  Hostname  : atanveer-amd-sme
  OS: Oracle Linux Server release 7.9
  Kernel: 5.4.17-2136.309.4.el7uek.x86_64 #2 SMP Tue Jun 28 17:35:13 
PDT 2022
  Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-18.oci.el7)
  OVMF/AAVMF: OVMF-1.6.3-1.el7.noarch

  Qemu command to launch SEV guest:

  /bin/qemu-system-x86_64 -name OL22.04-uefi \
  -machine q35 \
  -enable-kvm \
  -cpu host,+host-phys-bits \
  -m 16877M \
  -smp 8,maxcpus=240 \
  -D ./22.04-uefi.log \
  -nodefaults \
  -monitor stdio \
  -vnc 0.0.0.0:0,to=999 \
  -vga std \
  -drive 
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 \
  -drive file=OVMF_VARS.pure-efi.fd.ol22.04,index=1,if=pflash,format=raw \
  -device 
virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true \
  -drive 
file=Ubuntu-22.04-2022.06.16-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 \
  -device ide-hd,drive=local_disk0,id=local_disk1,bootindex=0 \
  -qmp tcp:127.0.0.1:3334,server,nowait \
  -serial telnet:127.0.0.1:,server,nowait \
  -device virtio-rng-pci,disable-legacy=on,iommu_platform=true \
  -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1 \
  -machine memory-encryption=sev0

  Console log:

  [0.005025] software IO TLB: SWIOTLB bounce buffer size adjusted to 1011MB
  [0.033881] kvm-guest: KVM setup pv remote TLB flush
  [0.054931] software IO TLB: Cannot allocate buffer
  [0.248933] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.249582] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.317440] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.317440] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [0.424952] iommu: DMA domain TLB invalidation policy: lazy mode
  [0.570923] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [0.571669] software IO TLB: No low mem
  .
  .
  .
  .
  [1.233515] ata1: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010100 
irq 28
  [1.234985] ata2: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010180 
irq 28
  [1.236464] ata3: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010200 
irq 28
  [1.237863] ata4: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010280 
irq 28
  [1.239257] ata5: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010300 
irq 28
  [1.240659] ata6: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010380 
irq 28
  [1.555165] ata5: SATA link down (SStatus 0 SControl 300)
  [1.556661] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [1.558232] ata2: SATA link down (SStatus 0 SControl 300)
  [1.559728] ata4: SATA link down (SStatus 0 SControl 300)
  [1.560996] ata3: SATA link down (SStatus 0 SControl 300)
  [1.562134] ata1: SATA link down (SStatus 0 SControl 300)
  [1.563566] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, 
err_mask=0x80)
  [6.911450] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [6.912906] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, 
err_mask=0x80)
  [   12.288045] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [   12.289904] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, 
err_mask=0x80)
  [   17.663548] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
  [  242.883993] INFO: task kworker/u480:0:9 blocked for more than 120 seconds.
  [  242.885619]   Not tainted 5.15.0-1013-oracle #17-Ubuntu
  [  242.886743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.888198] task:kworker/u480:0  state:D stack:0 pid:9 ppid: 2 
flags:0x4000
  [  242.889703] Workqueue: events_unbound async_run_entry_fn
  [  242.890882] Call Trace:
  [  242.891727]  

  
  Full console log is attached.

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


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

[Kernel-packages] [Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)

2022-08-10 Thread Roxnny A Barrios C
Hello, I currently have the same problem with Kernel 5.15 when
installing Ubuntu 22.04.

My laptop is an Hp ENVY x360 Convertible 15-eu0xxx.

I have secure boot disabled in the bios and I have been unable to
install Ubuntu 22.04.

In version 20.04 a successful installation was made but it is not
installed with the wireless network drivers.

If I try to update the kernel while it is in version 20.04 after the
installation I start to have boot problems.

So far I haven't tried the installation again and I really hope that the
problem will be solved as soon as possible.

** Attachment added: "these are the logs from the ubuntu terminal when the 
installation process is running.  I accessed it by pressing esc."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+attachment/5607744/+files/Ubuntu%20kernel%205.15%20Hp%20ENVY%20x360%20Convertible%2015-eu0xxx.mp4

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

Title:
  Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7
  3700U)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu-22.04-desktop-amd64.iso live cd does not boot on a HP ENVY
  X360 notebook (Ryzen 7 3700U).

  Model:
  HP ENVY X360
  13-ar0777ng
  9YN58EA#ABD

  After a few minutes the screen simply switches to black. No
  possibility to get a console by pressing CTRL-ALT-F1, F2, ...

  I removed the boot options "quiet splash" and recorded the boot via video.
  (just ask if you need the full video)
  I attach a significantly looking screenshot from that video, showing a kernel 
bug message.

  
  Currently the notebook runs with Ubuntu-20.04 using the Linux-5.11 HWE kernel.
  But suspend to memory isn't working.
  Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+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 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)

2022-08-10 Thread Bjorn Helgaas
I don't know what's in the 5.18.10-76051810-generic kernel (I assume that's 
v5.18 + some Ubuntu patches).  The upstream fixes for this went into v5.19: 
https://git.kernel.org/linus/3cc30140dbe2
I think v5.18 + the following patches (which somebody added in the "Bug 
Description" at the very beginning of this report) should work:

a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved 
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions

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

Title:
  touchpad and touchscreen doesn't work at all on ACER Spin 5
  (SP513-54N)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Won't Fix
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  E820 reserved retire memory window, and make other hot-added devices unable 
to get the required memory window.

  [Fix]
  It only can be fixed by a list of quirk to mark those machines out, and 
requires below commits from v5.19-rc1 and v5.19-rc3

  a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 
regions"
  d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
  fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved 
regions
  4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
  31bf0f433325 x86: Log resource clipping for E820 regions
  93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions

  [Test]
  Verified by the bug reporter.

  [Where problems could occur]
  The 6 commits are all clean cherry-picked, and the sixth commit reverts the 
third commit which are the 2 commits that do real functional changes.
  a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for 
E820 regions\"")
  4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
  The fourth and and fifth commits introduce a new quirk to ignore E820 
reserved regions and the quirk only affects the listed machines.
  Drivers that operates E820 table may fail if we ignore the E820 regions, but 
it should have no impact on the listed consumer PCs.

  ===

  Touchpad is not working at all on ACER Spin 5 SP513-54N.

  According to
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
  I am creating this kernel bug issue.

  There are more issues, too, like touchscreen not working and Ubuntu
  not installable - see here if interrested
  https://askubuntu.com/questions/1251719/

  I would like to run Ubuntu on this machine and I am willing to help
  with any debug or kernel tweaking... Please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4195 F pulseaudio
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 10:44:58 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  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=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.00
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.00
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.00
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1984488] [NEW] creating dummy network interface fails

2022-08-10 Thread Tim Sedlmeyer
Public bug reported:

The kernel module needed for dummy network interfaces was moved from the
linux-modules-5.15.0 package to the linux-modules-extras-5.15.0 package
with kernel release 1013 kernel update. This caused certain services
which usually bind to a dummy interface on my system to stop working
after the kernel upgrade. Moving kernel modules to the optional extras
package post major release is probably not wise since it can
unexpectedly break systems using that major release.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-modules-5.15.0-1013-raspi 5.15.0-1013.15
ProcVersionSignature: Ubuntu 5.15.0-1013.15-raspi 5.15.39
Uname: Linux 5.15.0-1013-raspi aarch64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Wed Aug 10 20:52:13 2022
ImageMediaBuild: 20210819.1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-raspi
UpgradeStatus: Upgraded to jammy on 2022-05-15 (87 days ago)

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


** Tags: apport-bug arm64 arm64-image jammy raspi-image uec-images

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

Title:
  creating dummy network interface fails

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  The kernel module needed for dummy network interfaces was moved from
  the linux-modules-5.15.0 package to the linux-modules-extras-5.15.0
  package with kernel release 1013 kernel update. This caused certain
  services which usually bind to a dummy interface on my system to stop
  working after the kernel upgrade. Moving kernel modules to the
  optional extras package post major release is probably not wise since
  it can unexpectedly break systems using that major release.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-5.15.0-1013-raspi 5.15.0-1013.15
  ProcVersionSignature: Ubuntu 5.15.0-1013.15-raspi 5.15.39
  Uname: Linux 5.15.0-1013-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Aug 10 20:52:13 2022
  ImageMediaBuild: 20210819.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-raspi
  UpgradeStatus: Upgraded to jammy on 2022-05-15 (87 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1984488/+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 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)

2022-08-10 Thread Ubuntu Foundations Team Bug Bot
The attachment
"amd64-microcode_3.20220411.1-3.202204.11.1ubuntu1.debdiff" seems to be
a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable
  (non-free)

Status in amd64-microcode package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2
  to 3.20220411.1ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+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 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)

2022-08-10 Thread crysman
Still does not work without pci=nocrs on 22.04 (jammy), up-to-date
5.18.10-76051810-generic - what does it mean? It had been working on
5.15 generic and on 5.18 not any more?

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

Title:
  touchpad and touchscreen doesn't work at all on ACER Spin 5
  (SP513-54N)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Won't Fix
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  E820 reserved retire memory window, and make other hot-added devices unable 
to get the required memory window.

  [Fix]
  It only can be fixed by a list of quirk to mark those machines out, and 
requires below commits from v5.19-rc1 and v5.19-rc3

  a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 
regions"
  d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
  fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved 
regions
  4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
  31bf0f433325 x86: Log resource clipping for E820 regions
  93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions

  [Test]
  Verified by the bug reporter.

  [Where problems could occur]
  The 6 commits are all clean cherry-picked, and the sixth commit reverts the 
third commit which are the 2 commits that do real functional changes.
  a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for 
E820 regions\"")
  4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
  The fourth and and fifth commits introduce a new quirk to ignore E820 
reserved regions and the quirk only affects the listed machines.
  Drivers that operates E820 table may fail if we ignore the E820 regions, but 
it should have no impact on the listed consumer PCs.

  ===

  Touchpad is not working at all on ACER Spin 5 SP513-54N.

  According to
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
  I am creating this kernel bug issue.

  There are more issues, too, like touchscreen not working and Ubuntu
  not installable - see here if interrested
  https://askubuntu.com/questions/1251719/

  I would like to run Ubuntu on this machine and I am willing to help
  with any debug or kernel tweaking... Please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4195 F pulseaudio
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 10:44:58 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  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=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.00
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.00
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.00
  dmi.sys.vendor: Acer

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

2022-08-10 Thread 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/1984440

Title:
  System lag induces mouse lag and keyboard multistroke

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was used to use 20.04 where the problem did not appear.
  I installed 22.04 from scratch (not a reinstall) on the same machine.

  Now after a day-long session the system has lags. In particular
  - the mouse has random long lags (>1s)
  - when I type I get short keyboard lags (<1s) and the following annoying bug: 
every now and then the lag is followed by one of the keystrokes that occurred 
during the lag being repeated like 10 times (and it does not look like a 
mechanical issue)

  Room temperature right now is 30C due to long lasting heat wave in Toulouse, 
this may be related.
  However I doubt it: a system restart usually solves the problem for a few 
hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cheritat   2534 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 20:36:33 2022
  InstallationDate: Installed on 2022-07-23 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated 
Webcam HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=bb014b1b-d145-4cf1-8227-bb0e43d4a152 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2022
  dmi.bios.release: 1.26
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.26.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.26.0:bd06/09/2022:br1.26:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984440/+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 1984440] [NEW] System lag induces mouse lag and keyboard multistroke

2022-08-10 Thread Arnaud Chéritat
Public bug reported:

I was used to use 20.04 where the problem did not appear.
I installed 22.04 from scratch (not a reinstall) on the same machine.

Now after a day-long session the system has lags. In particular
- the mouse has random long lags (>1s)
- when I type I get short keyboard lags (<1s) and the following annoying bug: 
every now and then the lag is followed by one of the keystrokes that occurred 
during the lag being repeated like 10 times (and it does not look like a 
mechanical issue)

Room temperature right now is 30C due to long lasting heat wave in Toulouse, 
this may be related.
However I doubt it: a system restart usually solves the problem for a few hours.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cheritat   2534 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 10 20:36:33 2022
InstallationDate: Installed on 2022-07-23 (18 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam 
HD
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 7490
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=bb014b1b-d145-4cf1-8227-bb0e43d4a152 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-43-generic N/A
 linux-backports-modules-5.15.0-43-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2022
dmi.bios.release: 1.26
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.26.0
dmi.board.name: 0KP0FT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.26.0:bd06/09/2022:br1.26:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C:
dmi.product.family: Latitude
dmi.product.name: Latitude 7490
dmi.product.sku: 081C
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  System lag induces mouse lag and keyboard multistroke

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was used to use 20.04 where the problem did not appear.
  I installed 22.04 from scratch (not a reinstall) on the same machine.

  Now after a day-long session the system has lags. In particular
  - the mouse has random long lags (>1s)
  - when I type I get short keyboard lags (<1s) and the following annoying bug: 
every now and then the lag is followed by one of the keystrokes that occurred 
during the lag being repeated like 10 times (and it does not look like a 
mechanical issue)

  Room temperature right now is 30C due to long lasting heat wave in Toulouse, 
this may be related.
  However I doubt it: a system restart usually solves the problem for a few 
hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cheritat   2534 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 20:36:33 2022
  InstallationDate: Installed on 2022-07-23 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated 
Webcam HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=bb014b1b-d145-4cf1-8227-bb0e43d4a152 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   

[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)

2022-08-10 Thread Mario Limonciello
> For linux-firmware, adding the following to debian/remove-
firmware.list creates a deb file without AMD-SEV files:

Presumably amd64-microcode will also need some handholding with
Conflicts/Replaces to make sure that it works on upgrade as it will
probably upgrade before linux-firmware does, right?

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Mark Esler (eslerm)

** Changed in: linux-firmware (Ubuntu)
Milestone: None => ubuntu-22.10-feature-freeze

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

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

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

Title:
  Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable
  (non-free)

Status in amd64-microcode package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2
  to 3.20220411.1ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

2022-08-10 Thread Dmitry Trofimov
Verified the patch for the master-next branch. It fixes the issue
indeed, everything is OK.

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

Title:
  re-apply missing overlayfs SAUCE patch

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

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  The following script can be used to trigger the issue:
#!/bin/bash

cat > test.py << EOF
import sys

f = open("/proc/self/maps")

for l in f.readlines():
  if "python" not in l:
continue
  print(l)
  s = l.split()
  start, end = s[0].split("-")
  fname = s[-1]
  print(start, end, fname)
  break
else:
  sys.exit(1)

test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))

fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()

if fdinfo1 != fdinfo2:
  print("FAIL")
  print(test_file1)
  print(fdinfo1)
  print(test_file2)
  print(fdinfo2)
  sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python 
/mnt/test.py

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter

2022-08-10 Thread Heather Lemon
# BIONIC - Proposed testing 
-- 

# enable proposed repo 
cat 

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1984203/+attachment/5607671/+files/AudioDevicesInUse.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/1984203

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

2022-08-10 Thread Jonathan Kamens
apport information

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2019-01-02 (1316 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-46-generic N/A
   linux-backports-modules-5.15.0-46-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+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 1984203] Re: /var/run/reboot-required not created after installing new kernel

2022-08-10 Thread Jonathan Kamens
apport information

** Tags added: apport-collected

** Description changed:

  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:
  
  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 
  
  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.
  
  This seems... problematic.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2019-01-02 (1316 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ MachineType: Acer Predator G6-710
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-46-generic N/A
+  linux-backports-modules-5.15.0-46-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.3
+ Tags:  jammy
+ Uname: Linux 5.15.0-46-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 05/18/2016
+ dmi.bios.release: 5.11
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: R01-A4
+ dmi.board.name: Predator G6-710
+ dmi.board.vendor: Acer
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Acer
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
+ dmi.product.family: Acer Desktop
+ dmi.product.name: Predator G6-710
+ dmi.sys.vendor: Acer
+ modified.conffile..etc.apport.crashdb.conf: [modified]
+ mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg

[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot

2022-08-10 Thread ltkarrde
Still present in 5.15.0-46.49-lowlatency

8/10/22 7:56 AM kernel  

8/10/22 7:56 AM kernel  UBSAN: array-index-out-of-bounds in 
/build/linux-lowlatency-Q9YOeF/linux-lowlatency-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48
8/10/22 7:56 AM kernel  index 8 is out of range for type 'aq_vec_s *[8]'
8/10/22 7:56 AM kernel  CPU: 12 PID: 2172 Comm: daemon-init Not tainted 
5.15.0-46-lowlatency #49-Ubuntu
8/10/22 7:56 AM kernel  Hardware name: To Be Filled By O.E.M. X570 Creator/X570 
Creator, BIOS P3.72 05/17/2022
8/10/22 7:56 AM kernel  Call Trace:
8/10/22 7:56 AM kernel   
8/10/22 7:56 AM kernel   show_stack+0x52/0x5c
8/10/22 7:56 AM kernel   dump_stack_lvl+0x4a/0x63
8/10/22 7:56 AM kernel   dump_stack+0x10/0x16
8/10/22 7:56 AM kernel   ubsan_epilogue+0x9/0x49
8/10/22 7:56 AM kernel   __ubsan_handle_out_of_bounds.cold+0x44/0x49
8/10/22 7:56 AM kernel   ? qdisc_pkt_len_init+0x108/0x180
8/10/22 7:56 AM kernel   ? aq_vec_stop+0x72/0x80 [atlantic]
8/10/22 7:56 AM kernel   aq_nic_stop+0x1b6/0x1c0 [atlantic]
8/10/22 7:56 AM kernel   aq_ndev_set_features+0x143/0x1a0 [atlantic]
8/10/22 7:56 AM kernel   __netdev_update_features+0x184/0x820
8/10/22 7:56 AM kernel   dev_disable_lro+0x34/0x150
8/10/22 7:56 AM kernel   devinet_sysctl_forward+0x1fb/0x230
8/10/22 7:56 AM kernel   proc_sys_call_handler+0x161/0x2d0
8/10/22 7:56 AM kernel   proc_sys_write+0x13/0x20
8/10/22 7:56 AM kernel   new_sync_write+0x117/0x1b0
8/10/22 7:56 AM kernel   ? intel_pmu_cpu_starting+0x280/0x3c0
8/10/22 7:56 AM kernel   vfs_write+0x1fb/0x290
8/10/22 7:56 AM kernel   ksys_write+0x67/0xf0
8/10/22 7:56 AM kernel   __x64_sys_write+0x19/0x20
8/10/22 7:56 AM kernel   do_syscall_64+0x5c/0xc0
8/10/22 7:56 AM kernel   ? exit_to_user_mode_prepare+0x37/0xb0
8/10/22 7:56 AM kernel   ? syscall_exit_to_user_mode+0x27/0x50
8/10/22 7:56 AM kernel   ? do_syscall_64+0x69/0xc0
8/10/22 7:56 AM kernel   entry_SYSCALL_64_after_hwframe+0x61/0xcb
8/10/22 7:56 AM kernel  RIP: 0033:0x7f0adb562a6f
8/10/22 7:56 AM kernel  Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 c0 
f7 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 
<48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 5c c0 f7 ff 48
8/10/22 7:56 AM kernel  RSP: 002b:7f0a9b7fd810 EFLAGS: 0293 ORIG_RAX: 
0001
8/10/22 7:56 AM kernel  RAX: ffda RBX: 0002 RCX: 
7f0adb562a6f
8/10/22 7:56 AM kernel  RDX: 0002 RSI: 7f0adbeeb5e5 RDI: 
0013
8/10/22 7:56 AM kernel  RBP: 7f0adbeeb5e5 R08:  R09: 
0001
8/10/22 7:56 AM kernel  R10:  R11: 0293 R12: 
0013
8/10/22 7:56 AM kernel  R13: 0013 R14:  R15: 
7f0a90024b10
8/10/22 7:56 AM kernel   
8/10/22 7:56 AM kernel  


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

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

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

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 13:02:10 2022
  InstallationDate: Installed on 2019-08-07 (899 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 
vt.handoff=7
  RelatedPackageVersions:
   

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

2022-08-10 Thread 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 1984203

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

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+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 1984203] Re: /var/run/reboot-required not created after installing new kernel

2022-08-10 Thread Julian Andres Klode
** Package changed: dpkg (Ubuntu) => linux (Ubuntu)

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

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+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 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking

2022-08-10 Thread Dimitris Moraitidis
>in 48W

what do you mean?

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

Title:
  Lenovo T16 unable to wake up from sleep, screen blinking

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics.
  Running Ubuntu 22.04 LTS.

  Unable to wake up from sleep - the screen backlight is on, but the
  screen is solid black. After a while it starts randomly flashing with
  a login screen for about ~300ms and also each time I type a character.

  Also the "reboot" command hangs.

  Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in
  BIOS - same issue.

  Not sure if relevant, but journal log contains these lines:

  jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'stop-sigterm' timed out. Killing.
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 1908 (gnome-shell) with signal SIGKILL.
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 9858 (pool-gnome-shel) with signal SIGKILL.
  jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write 
source OUI
  jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes 
still around after SIGKILL. Ignoring.
  jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable 
link training
  jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x60
  jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'stop-post' timed out. Terminating.
  jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x60
  jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'final-sigterm' timed out. Killing.
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 1908 (gnome-shell) with signal SIGKILL.
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 9858 (pool-gnome-shel) with signal SIGKILL.
  jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write 
source OUI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1761 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 09:22:18 2022
  InstallationDate: Installed on 2022-07-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.2
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3MET05W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1:
  dmi.product.family: ThinkPad T16 Gen 1
  dmi.product.name: 21BVCTO1WW
  dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1
  dmi.product.version: ThinkPad T16 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982679/+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 1984203] [NEW] /var/run/reboot-required not created after installing new kernel

2022-08-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
them, this resulted in /var/run/reboot-required and /var/run/reboot-
required.pkgs being created:

jik@jik-x1:~$ ls -l /var/run/reboot-required*
-rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
-rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
linux-image-5.15.0-46-generic
linux-base
jik@jik-x1:~$ 

On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
create this issue) the same kernel package was installed during the
`apt-get dist-upgrade -y` run, but /var/run/reboot-required and
/var/run/reboot-required.pkgs were NOT created.

This seems... problematic.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dpkg 1.21.1ubuntu2.1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 10 10:17:55 2022
InstallationDate: Installed on 2019-01-02 (1315 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: dpkg
UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

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


** Tags: amd64 apport-bug jammy
-- 
/var/run/reboot-required not created after installing new kernel
https://bugs.launchpad.net/bugs/1984203
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1981873] Re: ubuntu 5.15.0-41 on HP don't start

2022-08-10 Thread FAV
computer
description: Convertible
produit: HP ENVY x360 Convertible (7PV50EA#ABF)
fabricant: HP
version: Chassis Version
numéro de série: [REMOVED]
bits: 64 bits
fonctionnalités: smbios-3.2.1 dmi-3.2.1 smp vsyscall32
configuration : boot=normal chassis=convertible family=103C_5335KV HP ENVY 
x360 Convertible sku=7PV50EA#ABF uuid=[REMOVED]
  *-core
   description: Carte mère
   produit: 85DE
   fabricant: HP
   identifiant matériel: 0
   version: 41.36
   numéro de série: [REMOVED]
   emplacement: Base Board Chassis Location
 *-firmware
  description: BIOS
  fabricant: AMI
  identifiant matériel: 0
  version: F.22
  date: 11/05/2020
  taille: 64KiB
  capacité: 16MiB
  fonctionnalités: pci upgrade shadowing cdboot bootselect edd 
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard 
int14serial int17printer acpi usb smartbattery biosbootspecification netboot 
uefi
 *-memory
  description: Mémoire Système
  identifiant matériel: 10
  emplacement: Carte mère
  taille: 8GiB
*-bank:0
 description: SODIMM DDR4 Synchrone Unbuffered (Unregistered) 2400 
MHz (0,4 ns)
 produit: 4ATF51264HZ-2G3E1
 fabricant: Micron Technology
 identifiant matériel: 0
 numéro de série: [REMOVED]
 emplacement: Bottom - on board
 taille: 4GiB
 bits: 64 bits
 horloge: 2400MHz (0.4ns)
*-bank:1
 description: SODIMM DDR4 Synchrone Unbuffered (Unregistered) 2400 
MHz (0,4 ns)
 produit: 4ATF51264HZ-2G3E1
 fabricant: Micron Technology
 identifiant matériel: 1
 numéro de série: [REMOVED]
 emplacement: Bottom - on board
 taille: 4GiB
 bits: 64 bits
 horloge: 2400MHz (0.4ns)
 *-cache:0
  description: L1 cache
  identifiant matériel: 12
  emplacement: L1 - Cache
  taille: 384KiB
  capacité: 384KiB
  horloge: 1GHz (1.0ns)
  fonctionnalités: pipeline-burst internal write-back unified
  configuration : level=1
 *-cache:1
  description: L2 cache
  identifiant matériel: 13
  emplacement: L2 - Cache
  taille: 2MiB
  capacité: 2MiB
  horloge: 1GHz (1.0ns)
  fonctionnalités: pipeline-burst internal write-back unified
  configuration : level=2
 *-cache:2
  description: L3 cache
  identifiant matériel: 14
  emplacement: L3 - Cache
  taille: 4MiB
  capacité: 4MiB
  horloge: 1GHz (1.0ns)
  fonctionnalités: pipeline-burst internal write-back unified
  configuration : level=3
 *-cpu
  description: CPU
  produit: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
  fabricant: Advanced Micro Devices [AMD]
  identifiant matériel: 15
  information bus: cpu@0
  version: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
  numéro de série: [REMOVED]
  emplacement: FP5
  taille: 1412MHz
  capacité: 3700MHz
  bits: 64 bits
  horloge: 100MHz
  fonctionnalités: lm fpu fpu_exception wp vme de pse tsc msr pae mce 
cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall 
nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc 
cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 
movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic 
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext 
perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate ssbd ibpb 
vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt 
xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov succor smca sme sev sev_es cpufreq
  configuration : cores=4 enabledcores=4 threads=8
 *-pci:0
  description: Host bridge
  produit: Raven/Raven2 Root Complex
  fabricant: Advanced Micro Devices, Inc. [AMD]
  identifiant matériel: 100
  information bus: pci@:00:00.0
  version: 00
  bits: 32 bits
  horloge: 33MHz
*-generic NON-RÉCLAMÉ
 description: IOMMU
 produit: Raven/Raven2 IOMMU
 fabricant: Advanced Micro Devices, Inc. [AMD]
 identifiant matériel: 0.2
 information bus: pci@:00:00.2
 version: 00
 bits: 32 bits
 horloge: 33MHz
 fonctionnalités: msi ht bus_master cap_list
 configuration : latency=0
*-pci:0

[Kernel-packages] [Bug 1981873] Re: ubuntu 5.15.0-41 on HP don't start

2022-08-10 Thread FAV
-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981873

Title:
  ubuntu  5.15.0-41 on HP don't start

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New

Bug description:
  my HP ENVY x360 convertible 13-ar0009nf stays on the start page after
  grub since de 5.15.0-41 update of ubuntu 20.04.4 LTS

  so I started ubuntu from version 5.13.0-52 and the pc starts normally

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 16 14:23:36 2022
  InstallationDate: Installed on 2021-05-04 (437 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1981873/+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 1981873] Re: ubuntu 5.15.0-41 on HP don't start

2022-08-10 Thread FAV
the bug is still there after upgrading to 5.15.0-46

** No longer affects: linux-signed-hwe-5.13 (Ubuntu)

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

Title:
  ubuntu  5.15.0-41 on HP don't start

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New

Bug description:
  my HP ENVY x360 convertible 13-ar0009nf stays on the start page after
  grub since de 5.15.0-41 update of ubuntu 20.04.4 LTS

  so I started ubuntu from version 5.13.0-52 and the pc starts normally

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 16 14:23:36 2022
  InstallationDate: Installed on 2021-05-04 (437 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1981873/+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 1983429] Re: Ubuntu failed to boot after upgrading kernel

2022-08-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Ubuntu failed to boot after upgrading kernel

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

Bug description:
  Booting by using kernel 5.15.* failed with message like this:

  ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.SS10._PLD], AE_ALREADY_EXISTS (20210331/dswload2-326)
  ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210331/psobject-220)

  Currently, only by using kernel 5.13.0-52-generic I can boot
  successfully.

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

  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://id.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  3 09:16:14 2022
  InstallationDate: Installed on 2021-06-05 (423 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983429/+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 1983431] Re: ACPI boot errors for kernel 5.15.0 - regression from 5.13

2022-08-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ACPI boot errors for kernel 5.15.0 - regression from 5.13

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

Bug description:
  Half a page of ACPI error messages on startup.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Aug  2 20:16:37 2022
  InstallationDate: Installed on 2021-07-04 (394 days ago)
  InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983431/+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 1921477] Re: After suspend CUDA is not working any more

2022-08-10 Thread Roel
Still an issue with Driver Version 515.65.01 and Ubuntu 20.04.4. "sudo
rmmod nvidia_uvm" does work, but requires me to kill my current Jupyter
kernel.

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

Title:
  After suspend CUDA is not working any more

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

Bug description:
  After suspend the CUDA library can not get a connection to the GPU any
  more.

  There is following workaround possible:

  sudo rmmod nvidia_uvm
  sudo modprobe nvidia_uvm

  This could be automated in an event script however it is not helping
  if there are applications running already which depend on CUDA
  connection. The module will be refused to unload due to its usage
  then.

  System environment:

  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  
+-+
  | NVIDIA-SMI 460.32.03Driver Version: 460.32.03CUDA Version: 11.2 
|
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  |   |  |   MIG M. 
|
  
|===+==+==|
  |   0  GeForce GTX 1650On   | :01:00.0 Off |  N/A 
|
  | N/A   53CP5 9W /  N/A |   2015MiB /  3911MiB |  5%  Default 
|
  |   |  |  N/A 
|
  
+---+--+--+

 
  
+-+
  | Processes:  
|
  |  GPU   GI   CIPID   Type   Process name  GPU Memory 
|
  |ID   ID   Usage  
|
  
|=|
  |0   N/A  N/A  2924  G   /usr/lib/xorg/Xorg768MiB 
|
  |0   N/A  N/A  5018  G   xfwm4   2MiB 
|
  |0   N/A  N/A  8227  G   /opt/idea/jbr/bin/java  2MiB 
|
  |0   N/A  N/A255790  G   ...A= --shared-files   66MiB 
|
  |0   N/A  N/A267569C+G   jdks/openjdk-15/bin/java 1168MiB 
|
  
+-+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1921477/+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 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking

2022-08-10 Thread AaronMa
It should be fixed in 48W, but looks like it's delayed.

In the meanwhile, the potential fix:
https://patchwork.freedesktop.org/patch/msgid/20220602141850.21301-6-animesh.ma...@intel.com

You may want to try it.

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

Title:
  Lenovo T16 unable to wake up from sleep, screen blinking

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics.
  Running Ubuntu 22.04 LTS.

  Unable to wake up from sleep - the screen backlight is on, but the
  screen is solid black. After a while it starts randomly flashing with
  a login screen for about ~300ms and also each time I type a character.

  Also the "reboot" command hangs.

  Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in
  BIOS - same issue.

  Not sure if relevant, but journal log contains these lines:

  jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'stop-sigterm' timed out. Killing.
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 1908 (gnome-shell) with signal SIGKILL.
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 9858 (pool-gnome-shel) with signal SIGKILL.
  jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write 
source OUI
  jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes 
still around after SIGKILL. Ignoring.
  jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable 
link training
  jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x60
  jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'stop-post' timed out. Terminating.
  jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x60
  jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'final-sigterm' timed out. Killing.
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 1908 (gnome-shell) with signal SIGKILL.
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 9858 (pool-gnome-shel) with signal SIGKILL.
  jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write 
source OUI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1761 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 09:22:18 2022
  InstallationDate: Installed on 2022-07-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.2
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3MET05W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1:
  dmi.product.family: ThinkPad T16 Gen 1
  dmi.product.name: 21BVCTO1WW
  dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1
  dmi.product.version: ThinkPad T16 Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970957] Re: suspend problem

2022-08-10 Thread Pablo Angulo
I also had the problem occasionally, I tried kernel 5.15.0-40 but the
problem still appeared from time to time. Disabling screen lock solved
the problem, but this is functionality I miss :-(

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  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.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1979296] Re: [UBUNTU 20.04] Include patches to avoid self-detected stall with Secure Execution

2022-08-10 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [UBUNTU 20.04] Include patches to avoid self-detected stall with
  Secure Execution

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * On IBM Z secure execution environments under heavy load
 (means with over-committed resources - KVM guests)
 rcu_sched self-detected stalls can occur,
 which lead to LPAR crashes.

  [Fix]

   * 57c5df13eca4 57c5df13eca4017ed28f9375dc1d246ec0f54217 "KVM: s390:
  pv: add macros for UVC CC values"

   * 1e2aa46de526 1e2aa46de526a5adafe580bca4c25856bb06f09e "KVM: s390:
  pv: avoid stalls for kvm_s390_pv_init_vm"

   * f0a1a0615a6f f0a1a0615a6ff6d38af2c65a522698fb4bb85df6 "KVM: s390:
  pv: avoid stalls when making pages secure"

  [Test Plan]

   * An IBM z15 or LinuxONE III LPAR with FC 115 (secure execution)
 enabled is required.

   * Installation of Ubuntu Server 20.04 LTS (18.04 with hwe-5.4)
 or 22.04 LTS on top.

   * Install a kernel that incl. the above two patches/commits

   * Bring the system under high load with KVM guests.

   * Monitor dmesg for 'rcu_sched self-detected stalls' 
 and/or look for crashes.

   * Due to hardware requirements this test needs to be conducted by
  IBM.

  [Where problems could occur]

   * The definition from 57c5df13eca4 are missing in both jammy
 and focal, but shouldn't harm.

   * The change in 1e2aa46de526 only uses uv_call_sched instead
 of just uv_call, which should lead to a snappier system
 under high load, but may consume overall some more cycles.

   * With f0a1a0615a6f the uv_call_sched cannot simply replace 
 uv_call, due to locks being held.

   * Instead __uv_call is replacing uv_call, which does not loop.

   * But due to these changes of the (uv) calls,
 - in case erroneous - they may lead to wrong states,
 and even broken ultravisor calls
 and with that broken secure execution (SE).

   * As a side effect the uv might no longer loop over all pages,
 and in worst case leaving some unprotected.

   * All this is s390x-only functionality,
 that is only available on IBM z15 / LinuxONE III systems and newer,
 and only is the optional feature 'FC 115' in place,
 which is limited to 'secure-execution' workloads.

  [Other Info]

   * Patches are upstream accepted with kernel 5.16.

   * Commit 1e2aa46de526 is already included in jammy
 but 57c5df13eca4 and f0a1a0615a6f are missing.

   * Focal requires all 3 commits 57c5df13eca4, 1e2aa46de526 and
  f0a1a0615a6f.

   * Since impish is very close to it's EOL, it's not covered by this SRU.
  __

  ---Problem Description---
  rcu_sched self-detected stall with Secure Execution

  When the system is busy and additional Secure Execution guests are started, 
the LPAR crashes.
  Christian Borntraeger looked at the stack trace and identified two commits 
which should fix the issue:

  1e2aa46de526a5adafe580bca4c25856bb06f09e
  and
  f0a1a0615a6ff6d38af2c65a522698fb4bb85df6

  Please include these two fixes into 20.04, and 18.04 HWE.

  Here the stack trace:

  [592792.725078] rcu: INFO: rcu_sched self-detected stall on CPU
  [592792.725089] rcu:  4-: (2099 ticks this GP) 
idle=7d2/1/0x4002 softirq=3920041/3920042 fqs=984
  [592792.725133] (t=2100 jiffies g=26268505 q=410280)
  [592792.725135] Task dump for CPU 4:
  [592792.725137] qemu-system-s39 R running task0 2557923 1644255 0x0604
  [592792.725139] Call Trace:
  [592792.725146] ([<00566e2dcf52>] show_stack+0x7a/0xc0)
  [592792.725150] [<00566dab696c>] sched_show_task.part.0+0xdc/0x100
  [592792.725151] [<00566e2df248>] rcu_dump_cpu_stacks+0xc0/0x100
  [592792.725154] [<00566db0510c>] rcu_sched_clock_irq+0x75c/0x980
  [592792.725156] [<00566db1326c>] update_process_times+0x3c/0x80
  [592792.725160] [<00566db24fea>] tick_sched_handle.isra.0+0x4a/0x70
  [592792.725161] [<00566db2528e>] tick_sched_timer+0x5e/0xc0
  [592792.725163] [<00566db14294>] __hrtimer_run_queues+0x114/0x2f0
  [592792.725165] [<00566db14fdc>] hrtimer_interrupt+0x12c/0x2a0
  [592792.725167] [<00566da14b6a>] do_IRQ+0xaa/0xb0
  [592792.725170] [<00566e2eed08>] ext_int_handler+0x130/0x134
  [592792.725174] [<00566da2bad8>] gmap_make_secure+0x1c8/0x340
  [592792.725175] ([<00566da2b9fe>] gmap_make_secure+0xee/0x340)
  [592792.725180] [<00566da6e796>] kvm_s390_pv_unpack+0xc6/0x2b0
  [592792.725183] [<00566da535c0>] kvm_s390_handle_pv+0x390/0x580
  [592792.725184] [<00566da55b30>] kvm_arch_vm_ioctl+0x250/0x9e0
  

[Kernel-packages] [Bug 1977962] Re: [UBUNTU 21.10] s390/perf: obtain sie_block from the right address

2022-08-10 Thread Frank Heimes
** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  [UBUNTU 21.10] s390/perf: obtain sie_block from the right address

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Description:   s390/perf: obtain sie_block from the right address

  Symptom:   Read from unitialized stack memory, incorrect guest 
 perf data reported, possibly system crash.

  Problem:   When perf is instructed to record a software-based event and
 to trace the guest, i.e. using the following command:

 perf kvm --guest --guestvmlinux=endless.elf top -e cpu-clock
 
 The reported guest instruction pointer is inaccurate or
 the system may crash.

 This is caused by the sie_block being taken from empty1[0]
 in sie_block() in arch/s390/kernel/perf_event.c, but since 
 1179f170b6f0 ("s390: fix fpu restore in entry.S")
 it resides at empty1[1].

  Solution:  Obtain sie_block from the right address in sie_block().

  Reproduction:  1. Start a KVM guest executing an endless loop.
 2. Determine the instruction address of the loop.
 3. Start perf recording for any software event and trace 
the guest, for example using this command:

perf kvm --guest --guestvmlinux=endless.elf top -e
  cpu-clock

 4. The reported guest instruction addresses don't match
the loop's instruction address or the system crashes.

  Upstream-ID:   c9bfb460c3e4da2462e16b0f0b200990b36b1dd2

  BBPF Probl.ID: 198450
  Preventive:yes
  Reported:  -
  SupportTicket: -
  Reference: -
  Date:  2022-06-02
  Author:n...@linux.ibm.com
  Component: kernel
  Link:  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c9bfb460c3e4da2462e16b0f0b200990b36b1dd2

  Problem occurs / affects impish and jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977962/+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 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking

2022-08-10 Thread Fela Maslen
New BIOS has been released but doesn't fix the issue.

Do we have an ETA for this?

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

Title:
  Lenovo T16 unable to wake up from sleep, screen blinking

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics.
  Running Ubuntu 22.04 LTS.

  Unable to wake up from sleep - the screen backlight is on, but the
  screen is solid black. After a while it starts randomly flashing with
  a login screen for about ~300ms and also each time I type a character.

  Also the "reboot" command hangs.

  Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in
  BIOS - same issue.

  Not sure if relevant, but journal log contains these lines:

  jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'stop-sigterm' timed out. Killing.
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 1908 (gnome-shell) with signal SIGKILL.
  jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 9858 (pool-gnome-shel) with signal SIGKILL.
  jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write 
source OUI
  jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes 
still around after SIGKILL. Ignoring.
  jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable 
link training
  jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x60
  jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'stop-post' timed out. Terminating.
  jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x60
  jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read 
DPCD register 0x92
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 
'final-sigterm' timed out. Killing.
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 1908 (gnome-shell) with signal SIGKILL.
  jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing 
process 9858 (pool-gnome-shel) with signal SIGKILL.
  jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write 
source OUI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1761 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 09:22:18 2022
  InstallationDate: Installed on 2022-07-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.2
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3MET05W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1:
  dmi.product.family: ThinkPad T16 Gen 1
  dmi.product.name: 21BVCTO1WW
  dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1
  dmi.product.version: ThinkPad T16 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982679/+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 1978794] Re: Add support for Raptor Lake

2022-08-10 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add support for Raptor Lake

Status in HWE Next:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Comment]
  Add support for Raptor Lake on the multiple subsystems.

  [Where problems could occur]
  Low

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1978794/+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 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

2022-08-10 Thread Daniel van Vugt
Sorry I forgot to mention that you probably need to disable Secure Boot
in the BIOS in order to test those.

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980831/+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 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support

2022-08-10 Thread Sumit Saxena
Michael,

Problem is- the patch- "256bd4f23d9c scsi: mpi3mr: Return I/Os to an
unrecoverable HBA with DID_ERROR" is calling "scmd_done(scmd)" directly
whereas Ubuntu kernel expects "scmd->scsi_done(scmd)".

So the patch causing issue has to be adjusted for Ubuntu kernel as below
[scmd_done(scmd) replaced with scmd->scsi_done(scmd)]:

---
 drivers/scsi/mpi3mr/mpi3mr_os.c | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/drivers/scsi/mpi3mr/mpi3mr_os.c b/drivers/scsi/mpi3mr/mpi3mr_os.c
index 89a4918..5c57519 100644
--- a/drivers/scsi/mpi3mr/mpi3mr_os.c
+++ b/drivers/scsi/mpi3mr/mpi3mr_os.c
@@ -3996,6 +3996,12 @@ static int mpi3mr_qcmd(struct Scsi_Host *shost,
int iprio_class;
u8 is_pcie_dev = 0;
 
+   if (mrioc->unrecoverable) {
+   scmd->result = DID_ERROR << 16;
+   scmd->scsi_done(scmd);
+   goto out;
+   }
+
sdev_priv_data = scmd->device->hostdata;
if (!sdev_priv_data || !sdev_priv_data->tgt_priv_data) {
scmd->result = DID_NO_CONNECT << 16;
--

Please let me know if it works for you.

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

Title:
  [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG)
  support

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Request to include below mpi3mr driver bug fix patches in Ubuntu
  22.04.1(5.15 kernel). These patches got accepted by the upstream and
  please find the corresponding commit IDs as below:

  ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h
  dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0
  04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough
  937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs
  83959ce5204a scsi: mpi3mr: Add support for PEL commands
  eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands
  455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers 
to uapi header
  a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands
  7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support

  
  Thanks,
  Sumit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+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 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!

2022-08-10 Thread Alexandru Bolboaca
I tried to install the mainline kernel and to sign it according to
https://www.digitalpeer.com/blog/install-custom-or-mainline-kernel-on-
ubuntu, https://ubuntu.com/blog/how-to-sign-things-for-secure-boot,
https://github.com/berglh/ubuntu-sb-kernel-signing.

It seemed to work, but when I boot it says the shim signature is not
recognized, or something of the sort.

I'll try some more, but perhaps someone can point me to relevant and up-
to-date documentation? Thank you.

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2022-08-10 Thread 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/1984158

Title:
  touch pad stopped working after system was left unused for half a day.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Wireless hotkeys"
  P: Phys=hpq6001/input0
  S: Sysfs=/devices/virtual/input/input8
  U: Uniq=
  H: Handlers=rfkill kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=80 0 0 0

  I: Bus=0003 Vendor=04f2 Product=b67f Version=2667
  N: Name="HP TrueVision HD Camera: HP Tru"
  P: Phys=usb-:00:10.0-1/button
  S: Sysfs=/devices/pci:00/:00:10.0/usb2/2-1/2-1:1.0/input/input10
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA ATI HDMI HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:01.1/sound/card0/input11
  U: Uniq=
  H: Handlers=event8 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus=0019 Vendor= Product= Version=
  N: Name="HP WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input9
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=33
  B: KEY=40 0 10007 2102400 0 0
  B: MSC=10
  B: SW=20

  I: Bus= Vendor= Product= Version=
  N: Name="HD-Audio Generic Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:09.2/sound/card1/input12
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HD-Audio Generic Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:09.2/sound/card1/input13
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus=0003 Vendor=03f0 Product=094a Version=0111
  N: Name="PixArt HP USB Optical Mouse"
  P: Phys=usb-:00:10.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:10.0/usb2/2-2/2-2:1.0/0003:03F0:094A.0002/input/input14
  U: Uniq=
  H: Handlers=mouse0 event5 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=903
  B: MSC=10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  grasshopper   1460 F pulseaudio
   /dev/snd/controlC0:  grasshopper   1460 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 12:57:56 2022
  InstallationDate: Installed on 2022-08-02 (7 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP Laptop 15q-dy0xxx
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=3c681581-f7a6-492c-894e-2d629f316eae ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.release: 15.20
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  

[Kernel-packages] [Bug 1981864] Re: Jammy update: v5.15.46 upstream stable release

2022-08-10 Thread Stefan Bader
** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Jammy update: v5.15.46 upstream stable release

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

Bug description:
  SRU Justification

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

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

  binfmt_flat: do not stop relocating GOT entries prematurely on riscv
  parisc/stifb: Implement fb_is_primary_device()
  parisc/stifb: Keep track of hardware path of graphics card
  RISC-V: Mark IORESOURCE_EXCLUSIVE for reserved mem instead of IORESOURCE_BUSY
  riscv: Initialize thread pointer before calling C functions
  riscv: Fix irq_work when SMP is disabled
  riscv: Wire up memfd_secret in UAPI header
  riscv: Move alternative length validation into subsection
  ALSA: hda/realtek - Add new type for ALC245
  ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop
  ALSA: hda/realtek - Fix microphone noise on ASUS TUF B550M-PLUS
  ALSA: usb-audio: Cancel pending work at closing a MIDI substream
  USB: serial: option: add Quectel BG95 modem
  USB: new quirk for Dell Gen 2 devices
  usb: isp1760: Fix out-of-bounds array access
  usb: dwc3: gadget: Move null pinter check to proper place
  usb: core: hcd: Add support for deferring roothub registration
  fs/ntfs3: Update valid size if -EIOCBQUEUED
  fs/ntfs3: Fix fiemap + fix shrink file size (to remove preallocated space)
  fs/ntfs3: Keep preallocated only if option prealloc enabled
  fs/ntfs3: Check new size for limits
  fs/ntfs3: In function ntfs_set_acl_ex do not change inode->i_mode if called 
from function ntfs_init_acl
  fs/ntfs3: Fix some memory leaks in an error handling path of 'log_replay()'
  fs/ntfs3: Update i_ctime when xattr is added
  fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions
  cifs: fix potential double free during failed mount
  cifs: when extending a file with falloc we should make files not-sparse
  xhci: Allow host runtime PM as default for Intel Alder Lake N xHCI
  platform/x86: intel-hid: fix _DSM function index handling
  x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails
  perf/x86/intel: Fix event constraints for ICL
  x86/kexec: fix memory leak of elf header buffer
  x86/sgx: Set active memcg prior to shmem allocation
  ptrace/um: Replace PT_DTRACE with TIF_SINGLESTEP
  ptrace/xtensa: Replace PT_SINGLESTEP with TIF_SINGLESTEP
  ptrace: Reimplement PTRACE_KILL by always sending SIGKILL
  btrfs: add "0x" prefix for unsupported optional features
  btrfs: return correct error number for __extent_writepage_io()
  btrfs: repair super block num_devices automatically
  btrfs: fix the error handling for submit_extent_page() for btrfs_do_readpage()
  iommu/vt-d: Add RPLS to quirk list to skip TE disabling
  drm/vmwgfx: validate the screen formats
  drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes
  selftests/bpf: Fix vfs_link kprobe definition
  selftests/bpf: Fix parsing of prog types in UAPI hdr for bpftool sync
  mwifiex: add mutex lock for call in mwifiex_dfs_chan_sw_work_queue
  b43legacy: Fix assigning negative value to unsigned variable
  b43: Fix assigning negative value to unsigned variable
  ipw2x00: Fix potential NULL dereference in libipw_xmit()
  ipv6: fix locking issues with loops over idev->addr_list
  fbcon: Consistently protect deferred_takeover with console_lock()
  x86/platform/uv: Update TSC sync state for UV5
  ACPICA: Avoid cache flush inside virtual machines
  mac80211: minstrel_ht: fix where rate stats are stored (fixes debugfs output)
  drm/komeda: return early if drm_universal_plane_init() fails.
  drm/amd/display: Disabling Z10 on DCN31
  rcu-tasks: Fix race in schedule and flush work
  rcu: Make TASKS_RUDE_RCU select IRQ_WORK
  sfc: ef10: Fix assigning negative value to unsigned variable
  ALSA: jack: Access input_dev under mutex
  spi: spi-rspi: Remove setting {src,dst}_{addr,addr_width} based on DMA 
direction
  tools/power turbostat: fix ICX DRAM power numbers
  scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg()
  scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock
  scsi: lpfc: Fix call trace observed during I/O with CMF enabled
  cpuidle: PSCI: Improve support for suspend-to-RAM for PSCI OSI mode
  drm/amd/pm: fix double free in si_parse_power_table()
  

[Kernel-packages] [Bug 1984158] [NEW] touch pad stopped working after system was left unused for half a day.

2022-08-10 Thread Sphoorthy Nadimpalli
Public bug reported:

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
U: Uniq=
H: Handlers=event1 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef 
fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
U: Uniq=
H: Handlers=kbd event4 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus=0019 Vendor= Product= Version=
N: Name="Wireless hotkeys"
P: Phys=hpq6001/input0
S: Sysfs=/devices/virtual/input/input8
U: Uniq=
H: Handlers=rfkill kbd event6 
B: PROP=0
B: EV=3
B: KEY=80 0 0 0

I: Bus=0003 Vendor=04f2 Product=b67f Version=2667
N: Name="HP TrueVision HD Camera: HP Tru"
P: Phys=usb-:00:10.0-1/button
S: Sysfs=/devices/pci:00/:00:10.0/usb2/2-1/2-1:1.0/input/input10
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA ATI HDMI HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:01.1/sound/card0/input11
U: Uniq=
H: Handlers=event8 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0019 Vendor= Product= Version=
N: Name="HP WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input9
U: Uniq=
H: Handlers=kbd event9 
B: PROP=0
B: EV=33
B: KEY=40 0 10007 2102400 0 0
B: MSC=10
B: SW=20

I: Bus= Vendor= Product= Version=
N: Name="HD-Audio Generic Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:09.2/sound/card1/input12
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HD-Audio Generic Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:09.2/sound/card1/input13
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0003 Vendor=03f0 Product=094a Version=0111
N: Name="PixArt HP USB Optical Mouse"
P: Phys=usb-:00:10.0-2/input0
S: 
Sysfs=/devices/pci:00/:00:10.0/usb2/2-2/2-2:1.0/0003:03F0:094A.0002/input/input14
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=0
B: EV=17
B: KEY=7 0 0 0 0
B: REL=903
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  grasshopper   1460 F pulseaudio
 /dev/snd/controlC0:  grasshopper   1460 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 10 12:57:56 2022
InstallationDate: Installed on 2022-08-02 (7 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: HP HP Laptop 15q-dy0xxx
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=3c681581-f7a6-492c-894e-2d629f316eae ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-43-generic N/A
 linux-backports-modules-5.15.0-43-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2019
dmi.bios.release: 15.20
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84AC
dmi.board.vendor: HP
dmi.board.version: 85.24
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 85.24
dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd05/15/2019:br15.20:efr85.24:svnHP:pnHPLaptop15q-dy0xxx:pvrType1ProductConfigId:rvnHP:rn84AC:rvr85.24:cvnHP:ct10:cvrChassisVersion:sku6AL29PA#ACJ:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15q-dy0xxx
dmi.product.sku: 6AL29PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug