[Kernel-packages] [Bug 1984036] [NEW] Second Monitor via HDMI flicking on and off , and green flares

2022-08-08 Thread Edward
Public bug reported:

Tired X.org, Other Nvidia Drivers, swapping and changing cables,
lowering refresh rates, swapping over the HDMI to other monitor
(ThinkVision  can not remeber) now the second monitor has the exact
same problem and the first one via DP is perfect (not a problem of the
monitor or cable of the DP port).

Need this setup for work.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-515 515.65.01-0ubuntu0.22.04.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: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  9 08:17:19 2022
InstallationDate: Installed on 2022-07-27 (12 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nvidia-graphics-drivers-515
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Second Monitor via HDMI flicking on and off ,and green flares

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

Bug description:
  Tired X.org, Other Nvidia Drivers, swapping and changing cables,
  lowering refresh rates, swapping over the HDMI to other monitor
  (ThinkVision  can not remeber) now the second monitor has the
  exact same problem and the first one via DP is perfect (not a problem
  of the monitor or cable of the DP port).

  Need this setup for work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-515 515.65.01-0ubuntu0.22.04.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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  9 08:17:19 2022
  InstallationDate: Installed on 2022-07-27 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nvidia-graphics-drivers-515
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1984036/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread Daniel van Vugt
Thanks. I still can't tell which GPU is responsible for the HDMI port
(or if there is one at all if it's internally known as one of the DP
outputs).

Please:

 1. Look in /usr/share/X11/xorg.conf.d for any custom Nvidia
configuration files. The log suggests they do exist somewhere and
contain some bogus/ignored config commands, which is suspicious.

 2. Subscribe to https://gitlab.freedesktop.org/drm/intel/-/issues/6401
in case the kernel crash in the i915 driver is the cause of this bug.

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1984034] [NEW] Backport patches needed to allow live migration under SEV

2022-08-08 Thread Khaled El Mously
Public bug reported:

https://canonical.my.salesforce.com/5004K09oeuI

Upstream (v5.16) patches needed to allow live migration of confidential
VMs.

More details in the SF case.

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

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

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

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

** No longer affects: linux-oracle (Ubuntu)

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

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

** Description changed:

- https://canonical.lightning.force.com/lightning/r/Case/5004K09oeuIQAQ/
+ https://canonical.my.salesforce.com/5004K09oeuI
  
- Upstream (v5.16 mostly) patches needed to allow live migration of
- confidential VMs.
+ Upstream (v5.16) patches needed to allow live migration of confidential
+ VMs.
  
  More details in the SF case.

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

Title:
  Backport patches needed to allow live migration under SEV

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-gcp source package in Jammy:
  New

Bug description:
  https://canonical.my.salesforce.com/5004K09oeuI

  Upstream (v5.16) patches needed to allow live migration of
  confidential VMs.

  More details in the SF case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1984034/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread stkim
** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+attachment/5607446/+files/journal.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/1983815

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread Daniel van Vugt
I would like to see a full system log from when the bug is happening in
a Xorg session. Please reproduce the bug and while it is happening, run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-08-08 Thread jeremyszu
This patch is not from upstream or rhboot but which has been submitted as a MP 
to rhboot
https://github.com/rhboot/grub2/pull/102

+0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch
+0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
+0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch
+0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch
+0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch
+0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch
+0135-Fix-4GB-memory-be-filtered-out-by-filter_memory_map.patch

0129-0134 are from rhboot.

** Patch added: "0135-Fix-4GB-memory-be-filtered-out-by-filter_memory_map.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607436/+files/0135-Fix-4GB-memory-be-filtered-out-by-filter_memory_map.patch

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-08-08 Thread jeremyszu
** Patch added: 
"0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607435/+files/0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-08-08 Thread jeremyszu
** Patch added: 
"0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607434/+files/0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-08-08 Thread jeremyszu
** Patch added: "0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607432/+files/0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-08-08 Thread jeremyszu
** Patch added: "0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607433/+files/0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-08-08 Thread jeremyszu
** Patch added: 
"0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607431/+files/0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

2022-08-08 Thread jeremyszu
As my MP from comment#69 doesn't have response from rhboot team.

Shared the debdiff here for review to consider to carry it in Ubuntu.


** Patch added: "0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607429/+files/0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  

[Kernel-packages] [Bug 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread Daniel van Vugt
Upstream bug report for the same crash:
https://gitlab.freedesktop.org/drm/intel/-/issues/6401

** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6401
   https://gitlab.freedesktop.org/drm/intel/-/issues/6401

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1971202] Re: [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works)

2022-08-08 Thread Daniel van Vugt
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  happens with both xorg and wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
  Uname: Linux 5.15.0-27-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Mon May  2 18:20:07 2022
  DistUpgraded: 2022-03-26 15:56:50,280 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. TU106M [GeForce RTX 2060 Max-Q] 
[1043:1e11]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e11]
  MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (37 days ago)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GA502IV.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA502IV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.13
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.211:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Zephyrus G15
  dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971202/+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 1934878] Re: Mute/mic LEDs no function on some HP platfroms

2022-08-08 Thread Kai-Heng Feng
Javier, please file a separate bug, thanks!

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

Title:
  Mute/mic LEDs no function on some HP platfroms

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP ProBook 630 G8 Notebook PC
  2) HP ProBook 445 G8 Notebook PC
  3) HP ProBook 450 G8 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934878/+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 1810430] Re: tpm_crb MSFT0101:00: can't request region for resource

2022-08-08 Thread Merlin
I have the same problem running AMD Ryzen Threadripper 2920X on MSI X399
SLI PLUS with kernel 5.15.0-43-generic.

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

Title:
  tpm_crb MSFT0101:00: can't request region for resource

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  New hardware (AMD Threadripper 2920x with an ASRock X399 Taichi
  motherboard) and a clean 18.04.1 install.  I purposefully turn on AMD
  fTPM in the UEFI as I would like to explore using this to secure my
  system.  However after booting with this option no /dev/tpm device
  node exists and the kernel boot output now includes the following...

  $ dmesg | grep -i tpm
  [0.00] ACPI: TPM2 0x7902E4D0 34 (v04 AMDA M I
0001 AMI  )
  [0.928120] tpm_crb MSFT0101:00: can't request region for resource [mem 
0x7943a000-0x7943afff]
  [0.928141] tpm_crb: probe of MSFT0101:00 failed with error -16
  [1.090180] ima: No TPM chip found, activating TPM-bypass! (rc=-19)

  I'm using the motherboard vendors latest issued UEFI firmware and am
  unable to locate any other examples of this issue on my hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kelvin 3554 F pulseaudio
   /dev/snd/controlC0:  kelvin 3554 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  3 17:11:03 2019
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=dc67630f-0924-11e9-b9f2-7085c2b1c052 ro amd_iommu=force_isolation 
iommu=pt transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G 
hugepages=8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: X399 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810430/+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 1984011] Missing required logs.

2022-08-08 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 1984011

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

** Changed in: linux (Ubuntu Focal)
   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/1984011

Title:
  [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]

  fNIC driver controls print messages based on the flag fnic_log_level. 
shost_printk is not controlled via this flag. This issue is resolved by using 
some of the print macros that have been defined in fnic. This has negligible 
impact.
  The resid was being set irrespective of whether we saw an underflow or not. 
It needs to be set only when we see an underflow. The impact here is negligible.
  When we don't receive link events, we could go into a loop before sending fw 
reset. The patch for the issue resolves this, and we break out of the loop.
  Prior to checking the remote port, fnic driver must check if the io_req is 
valid. If not, there could be a crash. The patch resolves this issue.

  [Fix]
  The following patches need to be pulled from upstream to update the fnic 
driver to 1.6.0.53:

  https://marc.info/?l=linux-scsi=160591061813369=2
  https://marc.info/?l=linux-scsi=160592183315837=2
  https://marc.info/?l=linux-scsi=160592283315997=2
  https://marc.info/?l=linux-scsi=160592363016122=2
  https://marc.info/?l=linux-scsi=160592616516616=2

  Here's a description of each issue:

  1. https://marc.info/?l=linux-scsi=160591061813369=2

  FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_fip_handler_timer with this print so that it can
  be controlled.

  2. https://marc.info/?l=linux-scsi=160592183315837=2

  When fnic is in TRANS ETH state, and when there are no link events, we
  must not loop before sending fw reset.

  3. https://marc.info/?l=linux-scsi=160592283315997=2

  FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_handle_link with this print so that it can be
  controlled.

  4. https://marc.info/?l=linux-scsi=160592363016122=2

  Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is
  set.

  5. https://marc.info/?l=linux-scsi=160592616516616=2

  Check for a valid io_req before we check other data.

  [Test Plan]

  Runnings IOs with multiple link flaps would be a good test case to
  validate all the patches above. It is suggested to run these IOs with
  a data integrity check. We do this as a standard practice.

  [Where problems could occur]

  The print messages are innocuous. It is not expected to run into any issues.
  Problems could occur with storage arrays that have a non-standard response.
  If the sanity test fails, there could be issues in the scsi midlayer or fnic 
driver.

  All the patches present low regression risk.

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/cisco_fnic_update

  See original description
  Add tags Tag help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984011/+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 1984011] Re: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

2022-08-08 Thread Michael Reed
Thanks for the new kernel Michael.

I've updated the kernel and verified that the new driver is present.

We're all set. Thanks for your help with this. This bug can be resolved.

** Attachment added: "modinfo output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984011/+attachment/5607407/+files/lp1984011_log.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/1984011

Title:
  [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]

  fNIC driver controls print messages based on the flag fnic_log_level. 
shost_printk is not controlled via this flag. This issue is resolved by using 
some of the print macros that have been defined in fnic. This has negligible 
impact.
  The resid was being set irrespective of whether we saw an underflow or not. 
It needs to be set only when we see an underflow. The impact here is negligible.
  When we don't receive link events, we could go into a loop before sending fw 
reset. The patch for the issue resolves this, and we break out of the loop.
  Prior to checking the remote port, fnic driver must check if the io_req is 
valid. If not, there could be a crash. The patch resolves this issue.

  [Fix]
  The following patches need to be pulled from upstream to update the fnic 
driver to 1.6.0.53:

  https://marc.info/?l=linux-scsi=160591061813369=2
  https://marc.info/?l=linux-scsi=160592183315837=2
  https://marc.info/?l=linux-scsi=160592283315997=2
  https://marc.info/?l=linux-scsi=160592363016122=2
  https://marc.info/?l=linux-scsi=160592616516616=2

  Here's a description of each issue:

  1. https://marc.info/?l=linux-scsi=160591061813369=2

  FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_fip_handler_timer with this print so that it can
  be controlled.

  2. https://marc.info/?l=linux-scsi=160592183315837=2

  When fnic is in TRANS ETH state, and when there are no link events, we
  must not loop before sending fw reset.

  3. https://marc.info/?l=linux-scsi=160592283315997=2

  FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_handle_link with this print so that it can be
  controlled.

  4. https://marc.info/?l=linux-scsi=160592363016122=2

  Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is
  set.

  5. https://marc.info/?l=linux-scsi=160592616516616=2

  Check for a valid io_req before we check other data.

  [Test Plan]

  Runnings IOs with multiple link flaps would be a good test case to
  validate all the patches above. It is suggested to run these IOs with
  a data integrity check. We do this as a standard practice.

  [Where problems could occur]

  The print messages are innocuous. It is not expected to run into any issues.
  Problems could occur with storage arrays that have a non-standard response.
  If the sanity test fails, there could be issues in the scsi midlayer or fnic 
driver.

  All the patches present low regression risk.

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/cisco_fnic_update

  See original description
  Add tags Tag help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984011/+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 1984011] Re: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

2022-08-08 Thread Michael Reed
I have updated the link with a new test kernel.

https://people.canonical.com/~mreed/cisco/lp_1978247_fnic/

After installing this test kernel you should see kernel version
5.4.0-123.139.

I installed it and verified the updated driver is present.

$ uname -a
Linux hogplum 5.4.0-123-generic #139 SMP Thu Aug 4 21:28:51 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

$ modinfo fnic
filename: /lib/modules/5.4.0-123-generic/kernel/drivers/scsi/fnic/fnic.ko
version: 1.6.0.53
license: GPL v2

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

Title:
  [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New

Bug description:
  [Impact]

  fNIC driver controls print messages based on the flag fnic_log_level. 
shost_printk is not controlled via this flag. This issue is resolved by using 
some of the print macros that have been defined in fnic. This has negligible 
impact.
  The resid was being set irrespective of whether we saw an underflow or not. 
It needs to be set only when we see an underflow. The impact here is negligible.
  When we don't receive link events, we could go into a loop before sending fw 
reset. The patch for the issue resolves this, and we break out of the loop.
  Prior to checking the remote port, fnic driver must check if the io_req is 
valid. If not, there could be a crash. The patch resolves this issue.

  [Fix]
  The following patches need to be pulled from upstream to update the fnic 
driver to 1.6.0.53:

  https://marc.info/?l=linux-scsi=160591061813369=2
  https://marc.info/?l=linux-scsi=160592183315837=2
  https://marc.info/?l=linux-scsi=160592283315997=2
  https://marc.info/?l=linux-scsi=160592363016122=2
  https://marc.info/?l=linux-scsi=160592616516616=2

  Here's a description of each issue:

  1. https://marc.info/?l=linux-scsi=160591061813369=2

  FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_fip_handler_timer with this print so that it can
  be controlled.

  2. https://marc.info/?l=linux-scsi=160592183315837=2

  When fnic is in TRANS ETH state, and when there are no link events, we
  must not loop before sending fw reset.

  3. https://marc.info/?l=linux-scsi=160592283315997=2

  FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_handle_link with this print so that it can be
  controlled.

  4. https://marc.info/?l=linux-scsi=160592363016122=2

  Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is
  set.

  5. https://marc.info/?l=linux-scsi=160592616516616=2

  Check for a valid io_req before we check other data.

  [Test Plan]

  Runnings IOs with multiple link flaps would be a good test case to
  validate all the patches above. It is suggested to run these IOs with
  a data integrity check. We do this as a standard practice.

  [Where problems could occur]

  The print messages are innocuous. It is not expected to run into any issues.
  Problems could occur with storage arrays that have a non-standard response.
  If the sanity test fails, there could be issues in the scsi midlayer or fnic 
driver.

  All the patches present low regression risk.

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/cisco_fnic_update

  See original description
  Add tags Tag help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984011/+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 1984011] [NEW] [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

2022-08-08 Thread Michael Reed
Public bug reported:

[Impact]

fNIC driver controls print messages based on the flag fnic_log_level. 
shost_printk is not controlled via this flag. This issue is resolved by using 
some of the print macros that have been defined in fnic. This has negligible 
impact.
The resid was being set irrespective of whether we saw an underflow or not. It 
needs to be set only when we see an underflow. The impact here is negligible.
When we don't receive link events, we could go into a loop before sending fw 
reset. The patch for the issue resolves this, and we break out of the loop.
Prior to checking the remote port, fnic driver must check if the io_req is 
valid. If not, there could be a crash. The patch resolves this issue.

[Fix]
The following patches need to be pulled from upstream to update the fnic driver 
to 1.6.0.53:

https://marc.info/?l=linux-scsi=160591061813369=2
https://marc.info/?l=linux-scsi=160592183315837=2
https://marc.info/?l=linux-scsi=160592283315997=2
https://marc.info/?l=linux-scsi=160592363016122=2
https://marc.info/?l=linux-scsi=160592616516616=2

Here's a description of each issue:

1. https://marc.info/?l=linux-scsi=160591061813369=2

FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace
shost_printk in fnic_fip_handler_timer with this print so that it can be
controlled.

2. https://marc.info/?l=linux-scsi=160592183315837=2

When fnic is in TRANS ETH state, and when there are no link events, we
must not loop before sending fw reset.

3. https://marc.info/?l=linux-scsi=160592283315997=2

FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace
shost_printk in fnic_handle_link with this print so that it can be
controlled.

4. https://marc.info/?l=linux-scsi=160592363016122=2

Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is set.

5. https://marc.info/?l=linux-scsi=160592616516616=2

Check for a valid io_req before we check other data.

[Test Plan]

Runnings IOs with multiple link flaps would be a good test case to
validate all the patches above. It is suggested to run these IOs with a
data integrity check. We do this as a standard practice.

[Where problems could occur]

The print messages are innocuous. It is not expected to run into any issues.
Problems could occur with storage arrays that have a non-standard response.
If the sanity test fails, there could be issues in the scsi midlayer or fnic 
driver.

All the patches present low regression risk.

[Other Info]

https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/cisco_fnic_update

See original description
Add tags Tag help

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

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

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

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

Title:
  [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New

Bug description:
  [Impact]

  fNIC driver controls print messages based on the flag fnic_log_level. 
shost_printk is not controlled via this flag. This issue is resolved by using 
some of the print macros that have been defined in fnic. This has negligible 
impact.
  The resid was being set irrespective of whether we saw an underflow or not. 
It needs to be set only when we see an underflow. The impact here is negligible.
  When we don't receive link events, we could go into a loop before sending fw 
reset. The patch for the issue resolves this, and we break out of the loop.
  Prior to checking the remote port, fnic driver must check if the io_req is 
valid. If not, there could be a crash. The patch resolves this issue.

  [Fix]
  The following patches need to be pulled from upstream to update the fnic 
driver to 1.6.0.53:

  https://marc.info/?l=linux-scsi=160591061813369=2
  https://marc.info/?l=linux-scsi=160592183315837=2
  https://marc.info/?l=linux-scsi=160592283315997=2
  https://marc.info/?l=linux-scsi=160592363016122=2
  https://marc.info/?l=linux-scsi=160592616516616=2

  Here's a description of each issue:

  1. https://marc.info/?l=linux-scsi=160591061813369=2

  FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_fip_handler_timer with this print so that it can
  be controlled.

  2. https://marc.info/?l=linux-scsi=160592183315837=2

  When fnic is in TRANS ETH state, and when there are no link events, we
  must not loop before sending fw reset.

  3. https://marc.info/?l=linux-scsi=160592283315997=2

  FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_handle_link with this print so that it can be
  controlled.

  4. https://marc.info/?l=linux-scsi=160592363016122=2

  Fix to set scsi_set_resid() only if 

[Kernel-packages] [Bug 1976228] Re: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan-scsi-bus.sh -r' command is executed

2022-08-08 Thread Michael Reed
Is this an issue on 20.04 with the 5.4 kernel or on 21.10?

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

Title:
  [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan-
  scsi-bus.sh -r' command is executed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  OS:Ubuntu 22.04 LTS
  kernel:5.15.0-33-generic
  host model:Dell PowerEdge R630
  issue description:
  After I mapped luns from array to my host, I ran 'rescan-scsi-bus.sh -r' to 
scan for luns, my host crashed and became read-only.After the KVM forcibly 
restarts the host, the host is restored to normal.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 30 08:33 seq
   crw-rw 1 root audio 116, 33 May 30 08:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-26 (4 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/14/2021
  dmi.bios.release: 2.13
  dmi.bios.version: 2.13.0
  dmi.board.name: 02C2CP
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.modalias: 
dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn02C2CP:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=:
  dmi.product.sku: SKU=NotProvided;ModelName=

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976228/+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 1982782] Re: Bionic update: upstream stable patchset 2022-07-25

2022-08-08 Thread Luke Nowakowski-Krijger
** Changed in: linux (Ubuntu Bionic)
   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/1982782

Title:
  Bionic update: upstream stable patchset 2022-07-25

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-07-25

  Ported from the following upstream stable releases:
  v4.14.283, v4.19.247
  v4.14.284, v4.19.248

     from git://git.kernel.org/

  Note: All patches from v4.14.284 and v4.19.248 had previously been
  applied.

  binfmt_flat: do not stop relocating GOT entries prematurely on riscv
  USB: serial: option: add Quectel BG95 modem
  USB: new quirk for Dell Gen 2 devices
  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: repair super block num_devices automatically
  drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes
  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()
  ACPICA: Avoid cache flush inside virtual machines
  ALSA: jack: Access input_dev under mutex
  drm/amd/pm: fix double free in si_parse_power_table()
  ath9k: fix QCA9561 PA bias level
  media: venus: hfi: avoid null dereference in deinit
  media: pci: cx23885: Fix the error handling in cx23885_initdev()
  media: cx25821: Fix the warning when removing the module
  scsi: megaraid: Fix error check return value of register_chrdev()
  drm/amd/pm: fix the compile warning
  ipv6: Don't send rs packets to the interface of ARPHRD_TUNNEL
  ASoC: dapm: Don't fold register value changes into notifications
  s390/preempt: disable __preempt_count_add() optimization for 
PROFILE_ALL_BRANCHES
  dma-debug: change allocation mode from GFP_NOWAIT to GFP_ATIOMIC
  ipmi:ssif: Check for NULL msg when handling events and messages
  rtlwifi: Use pr_warn instead of WARN_ONCE
  openrisc: start CPU timer early in boot
  nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags
  ASoC: rt5645: Fix errorenous cleanup order
  net: phy: micrel: Allow probing without .driver_data
  media: exynos4-is: Fix compile warning
  rxrpc: Return an error to sendmsg if call failed
  eth: tg3: silence the GCC 12 array-bounds warning
  ARM: dts: ox820: align interrupt controller node name with dtschema
  fs: jfs: fix possible NULL pointer dereference in dbFree()
  ARM: OMAP1: clock: Fix UART rate reporting algorithm
  fat: add ratelimit to fat*_ent_bread()
  ARM: versatile: Add missing of_node_put in dcscb_init
  ARM: dts: exynos: add atmel,24c128 fallback to Samsung EEPROM
  ARM: hisi: Add missing of_node_put after of_find_compatible_node
  PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()
  tracing: incorrect isolate_mote_t cast in mm_vmscan_lru_isolate
  powerpc/xics: fix refcount leak in icp_opal_init()
  macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled
  RDMA/hfi1: Prevent panic when SDMA is disabled
  drm: fix EDID struct for old ARM OABI format
  ath9k: fix ar9003_get_eepmisc
  ASoC: mediatek: Fix error handling in mt8173_max98090_dev_probe
  ASoC: mediatek: Fix missing of_node_put in mt2701_wm8960_machine_probe
  x86/delay: Fix the wrong asm constraint in delay_loop()
  drm/mediatek: Fix mtk_cec_mask()
  spi: spi-ti-qspi: Fix return value handling of wait_for_completion_timeout
  NFC: NULL out the dev->rfkill to prevent UAF
  efi: Add missing prototype for efi_capsule_setup_info
  HID: hid-led: fix maximum brightness for Dream Cheeky
  spi: img-spfi: Fix pm_runtime_get_sync() error checking
  ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix
  inotify: show inotify mask flags in proc fdinfo
  fsnotify: fix wrong lockdep annotations
  x86/pm: Fix false positive kmemleak report in msr_build_context()
  drm/msm/dsi: fix error checks and return values for DSI xmit functions
  drm/msm/hdmi: check return value after calling platform_get_resource_byname()
  drm/rockchip: vop: fix possible null-ptr-deref in vop_bind()
  x86: Fix return value of __setup handlers
  

[Kernel-packages] [Bug 1983756] Re: Please backport kernel patches to support thermal policy handling in OMEN laptops

2022-08-08 Thread jose
@xnox: this is what I get from the changelog of the kernel I'm currently 
running:
$ apt-get changelog linux-hwe-5.15-source-5.15.0 | grep -Ei '(omen|hp-wmi)'
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
- ALSA: hda/realtek: Add a quirk for HP OMEN 15 mute LED
- platform/x86: hp-wmi: Fix ACPI errors caused by too small buffer
- platform/x86: hp-wmi: Fix ACPI errors caused by passing 0 as input size
So. one mention of omen. but unrelated to this set of patches or to HP-WMI.


Current kernel comes directly from Ubuntu repos:
$ dpkg -l | grep '5.15.0-43'
ii  linux-headers-5.15.0-43-generic   5.15.0-43.46~20.04.1  
amd64Linux kernel headers for version 5.15.0 on 
64 bit x86 SMP
ii  linux-hwe-5.15-headers-5.15.0-43  5.15.0-43.46~20.04.1  
all  Header files related to Linux kernel 
version 5.15.0
ii  linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1  
amd64Signed kernel image generic
ii  linux-modules-5.15.0-43-generic   5.15.0-43.46~20.04.1  
amd64Linux kernel extra modules for version 
5.15.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.15.0-43-generic 5.15.0-43.46~20.04.1  
amd64Linux kernel extra modules for version 
5.15.0 on 64 bit x86 SMP

$ apt-cache showpkg linux-image-5.15.0-43-generic
Package: linux-image-5.15.0-43-generic
Versions: 
5.15.0-43.46~20.04.1 
(/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_focal-security_main_binary-amd64_Packages)
 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_focal-updates_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)
 Description Language: 
 File: 
/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_focal-security_main_binary-amd64_Packages
  MD5: 54a18b1adebc179da3c9e59a5db5fe77
...

Honestly, I don't think having to wait for new kernel releases is good
for (prospective) users.

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

Title:
  Please backport kernel patches to support thermal policy handling in
  OMEN laptops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As described in https://www.phoronix.com/news/HP-OMEN-Linux-5.16 and 
https://www.phoronix.com/news/Linux-5.18-HP-Omen-Thermal, thermal policy 
handling for OMEN laptops was added in kernel 5.16 and updated in 5.18:
  
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=4c51ba9af42dff0ef6a2ca3edcefa76f3466959e
  
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=286e937efbc7177c114e80aae9b402131e3886c1

  Please backport these kernel patches so that we can check and control
  fan speed, performance profiles and some device temps.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  $ lsb_release -rd
  Description:KDE neon User - 5.25
  Release:20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983756/+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 1984004] [NEW] Linux Firmware drops AMD RX6650 XT Performance

2022-08-08 Thread Ras
Public bug reported:

Kernel: 5.15.0-43-generic
linux-firmware: 20220329.git681281e4-0ubuntu3.3
Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based)

In e.g. the Unigine benchmark, the linux-firmware packages drops the
performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to
23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu
20.04 based).

Getting the firmware directly from git brings the performance back to about 100 
FPS:
git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
cd linux-firmware
sudo make install
sudo update-initramfs -c -k all

Re-installing the linux-firmware package causes the performance to drop
again. So there is a problem with the linux firmware at least for the RX
6650 XT, maybe for the whole RX 6000 series.

The linux-firmware package in Ubuntu 22.04 should be updated.

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

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

Title:
  Linux Firmware drops AMD RX6650 XT Performance

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Kernel: 5.15.0-43-generic
  linux-firmware: 20220329.git681281e4-0ubuntu3.3
  Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based)

  In e.g. the Unigine benchmark, the linux-firmware packages drops the
  performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to
  23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu
  20.04 based).

  Getting the firmware directly from git brings the performance back to about 
100 FPS:
  git clone 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
  cd linux-firmware
  sudo make install
  sudo update-initramfs -c -k all

  Re-installing the linux-firmware package causes the performance to
  drop again. So there is a problem with the linux firmware at least for
  the RX 6650 XT, maybe for the whole RX 6000 series.

  The linux-firmware package in Ubuntu 22.04 should be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+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 1934878] Re: Mute/mic LEDs no function on some HP platfroms

2022-08-08 Thread Javier
I am still facing this issue on a HP Probook 450 G8 with kernel
5.15.0-43-generic (Ubuntu 22.04.1).

Both mute audio (f5) and mute mic (f8) leds are always on.

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

Title:
  Mute/mic LEDs no function on some HP platfroms

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on
  1) HP ProBook 630 G8 Notebook PC
  2) HP ProBook 445 G8 Notebook PC
  3) HP ProBook 450 G8 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934878/+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 1971202] Re: [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works)

2022-08-08 Thread enorrmann
after clean install the bug is no longer present

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

Title:
  [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  happens with both xorg and wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
  Uname: Linux 5.15.0-27-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Mon May  2 18:20:07 2022
  DistUpgraded: 2022-03-26 15:56:50,280 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. TU106M [GeForce RTX 2060 Max-Q] 
[1043:1e11]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e11]
  MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (37 days ago)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GA502IV.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA502IV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.13
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.211:bd12/30/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Zephyrus G15
  dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971202/+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 1923114] Re: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy

2022-08-08 Thread Francis Ginther
** Tags added: 5.4

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

Title:
  ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write
  error: Device or resource busy

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux-azure source package in Trusty:
  New
Status in linux-azure-4.15 source package in Trusty:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-azure-4.15 source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-4.15 source package in Bionic:
  New
Status in linux-azure source package in Groovy:
  New
Status in linux-azure-4.15 source package in Groovy:
  New

Bug description:
  Test cpu-hotplug from ubuntu_kernel_selftests failed with
  bionic:linux-azure-4.15 running on a Basic A2 with 2 cores (besides
  other instance types):

  selftests: cpu-on-off-test.sh
  
  pid 28041's current affinity mask: 3
  pid 28041's new affinity mask: 1
  CPU online/offline summary:
  present_cpus = 0-1 present_max = 1
  Cpus in online state: 0-1
  Cpus in offline state: 0
  Limited scope test: one hotplug cpu
  (leaves cpu in the original state):
  online to offline to online: cpu 1
  not ok 1..1 selftests: cpu-on-off-test.sh [FAIL]
  ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy
  offline_cpu_expect_success 1: unexpected fail

  http://10.246.72.46/4.15.0-1112.124~16.04.1-azure/xenial-linux-azure-
  azure-
  
amd64-4.15.0-Basic_A2-ubuntu_kernel_selftests/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.cpu-
  hotplug/debug/ubuntu_kernel_selftests.cpu-hotplug.DEBUG.html

  The problem happens at "autotest-client-
  tests/ubuntu_kernel_selftests/cpu-on-off-test.sh" when executing:

  echo 0 > $SYSFS/devices/system/cpu/cpu$1/online

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923114/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy

2022-08-08 Thread Martin Richtarsky
@xnox: I have:

$ uname -r
5.15.0-43-generic
$ sudo zfs version
zfs-2.1.4-0ubuntu0.1
zfs-kmod-2.1.4-0ubuntu0.1

Can you confirm that the bug is not fixed there, since presumably kernel
5.15.0-43 < 5.15.0-43.46?

And is it possible to upgrade the kernel within jammy to get the fix?

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

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
  Jammy

Status in Native ZFS for Linux:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Summary]

  When running Jammy on zfs or LXD with a zfs pool on a Jammy host,
  fallocate creates a zero-sized file.

  The issue was originally found when installing mysql on LXD, where
  fallocate would create a zero-sized ib_logfile1 file. The original
  information in this bug is based on that.

  [Steps to Reproduce]

  touch foo.img
  fallocate -z -l 10M foo.img
  ls -la foo.img

  On a non-zfs Jammy system this will show something like:
  -rw-r--r-- 1 root root 10M ...

  while on zfs it will show:
  -rw-rw-r-- 1 root root 0 ...

  [Original Description]
  I came across this error when testing various mysql setups in an LXD 
container and managed to reproduce it consistently. I'm unable to reproduce on 
Ubuntu desktop or server though since the prerequisites are probably handled 
properly there.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 15 21:31:09 2022
  Dmesg:

  ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  KernLog:

  Logs.var.log.daemon.log:

  MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
  MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
   [mysqldump]
   quick
   quote-names
   max_allowed_packet   = 16M
  MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic 
links: '/etc/mysql/my.cnf'
  MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 
'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 
'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 
'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 
'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 
'public_key.pem', 'ca.pem', 'server-key.pem']
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: mysql-8.0
  Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1969247/+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 1964992] Re: ZFS ignores ARC sizes below allmem/32

2022-08-08 Thread Heitor Alves de Siqueira
Hi Robie,

You're right, the patch does essentially invert the problem. This is
still the behavior upstream, and it currently works like you mentioned:
if the user tries to set a min above the default max (ramsize/2), it
fails.

I'm working on a patch to propose upstream that should fix this. We
should be setting min/max values as a pairs else we'll run into a
similar issue as the one reported here. I'm also going to double check
other tunables to see if they exhibit similar issues, so we can avoid
further problems on those too.

For this particular LP bug, do you think we should wait until a "proper"
fix upstream? I do understand the point about breaking setups relying on
the current min/max behavior, but that will also happen when upgrading
to newer releases. My (subjective) opinion is that users trying to
reduce ZFS memory footprint are much more common than the alternative,
and for high memory systems this is currently not possible due to this
bug. What do you think?

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

Title:
  ZFS ignores ARC sizes below allmem/32

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Focal:
  Incomplete

Bug description:
  [Impact]
  ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. 
This prevents users from properly restraining ARC sizes, and can cause 
increased memory contention in some systems.

  [Test Plan]
  1. Deploy test system with ZFS storage and 32GB RAM
  2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf
     # cat /etc/modprobe.d/99-zfs-arc.conf
     options zfs zfs_arc_min=536870912
     options zfs zfs_arc_max=966367641
  3. Reboot system
  4. Verify ARC sizes through "arc_summary"
     # arc_summary | grep -A3 "ARC size"
     ARC size (current):   < 0.1 %1.3 MiB
     Target size (adaptive):   100.0 %   15.7 GiB
     Min size (hard limit):  3.2 %  512.0 MiB
     Max size (high water):   31:1   15.7 GiB

  For a 32GB test system, we should be able to set max ARC sizes below
  1GB.

  [Fix]
  This has been fixed by upstream commit:
   - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32"

  The commit has been introduced in upstream zfs-2.0.0, so it's needed
  for Bionic and Focal. Releases starting with Impish already have this
  commit by default:

  $ git describe --contains 36a6e2335c45
  zfs-2.0.0-rc1~332
  $ rmadison zfs-linux
   zfs-linux | 0.7.5-1ubuntu15| bionic  | source
   zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates  | source
   zfs-linux | 0.8.3-1ubuntu12| focal   | source
   zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
   zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates   | source
   zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed  | source
   zfs-linux | 2.0.6-1ubuntu2 | impish  | source
   zfs-linux | 2.0.6-1ubuntu2.1   | impish-updates  | source
   zfs-linux | 2.1.2-1ubuntu3 | jammy   | source

  [Regression Potential]
  The introduced commit essentially removes the limitation of setting ARC 
tunables below allmem/32, and re-arranges the order of how some of the tunables 
are parsed. Regressions would possibly show up as other tunables being ignored 
or not being set correctly due to parsing errors. We should validate whether 
other ARC related tunables are still being set correctly, and whether ZFS is 
using the set values for the ARC memory thresholds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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-08 Thread Heather Lemon
F/J kernel versions Linux focal-azure 5.15.0-1014-azure
Bionic version - 5.4.0-1086-azure

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

Title:
  Remove "ata_piix.prefer_ms_hyperv=0" parameter

Status in kdump-tools package in Ubuntu:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in kdump-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in kdump-tools source package in Focal:
  Invalid
Status in makedumpfile source package in Focal:
  Fix Committed
Status in kdump-tools source package in Impish:
  Invalid
Status in makedumpfile source package in Impish:
  Invalid
Status in kdump-tools source package in Jammy:
  In Progress
Status in makedumpfile source package in Jammy:
  Invalid
Status in kdump-tools source package in Kinetic:
  Fix Committed
Status in makedumpfile source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  Azure VM instances hit I/O error on boot causing kernel crash

  [Test Plan]

  Create Ubuntu Marketplace VM on Azure

  ```
  ssh -i .ssh/id_rsa ubuntu@ipaddr 
  ```

  Install crash dump utilities (from guide:
  https://ubuntu.com/server/docs/kernel-crash-dump)

  apt-get install kdump-tools

  Say (y) to all questions during install

  kdump-config show 
  *shows the vm is not yet ready to kdump 

  root@bionic3: kdump-config show 
   * no crashkernel= parameter in the kernel cmdline
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz
  kdump initrd: 
 /var/lib/kdump/initrd.img
  current state:Not ready to kdump

  kexec command:
no kexec command recorded

  
  Reboot the VM

  sudo su

  As root on the VM after reboot:

  kdump-config show

  kdump-config show 
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x3200
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-5.4.0-1086-azure
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure 
root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 
irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

  
  #verify kdump is on

  cat /proc/cmdline
  ... crashkernel=512M-:192M

  dmesg | grep -i crash
  [0.071660] kexec: Reserving the low 1M of memory for crashkernel
  [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System 
RAM: 4095MB)

  cat /proc/sys/kernel/sysrq
  # make sure this value is greater than 0
  #set it to 1
  sudo sysctl -w kernel.sysrq=1

  the directory of /var/crash should have no crashes yet as well.

  Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command:
  # perform crash
  sudo su
  echo c > /proc/sysrq-trigger

  After a couple of minuties 
  Open new terminal and try to ssh to azure  VM, 
  It does not succeed 

  Force a reboot of the VM through the portal or serial console 
  #kdump doesnt work and hangs indefinitely
  #force reboot VM from Azure console

  # verify package version of kdump-tool
  # verify parameter is not listed in the kdump-config show output 
  kdump-config unload
  kdump-config load 
  kdump-config show 

  kdump-config show 
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x3200
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-5.4.0-1086-azure
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure 
root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 
irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  
  #trigger another crash
  echo c > /proc/sysrq-trigger

  # open new terminal and ssh back into vm

  cd /var/crash

  #verify a dump was created 
  linux-image-5.4.0-1086-azure-202208041658.crash

  [Where Problems Could Occur]

  This change modifies the debian/rules.
  The package could fail to build properly if mistyped.

  [Other]
  Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" 
parameter.

  target series - Bionic, Focal, Jammy

  upstream patch

  https://salsa.debian.org/debian/kdump-
  

[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter

2022-08-08 Thread Heather Lemon
I've been testing the Focal/Jammy instances and no crash dump is being
generated. I'm still investigating why this is happening.

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

Title:
  Remove "ata_piix.prefer_ms_hyperv=0" parameter

Status in kdump-tools package in Ubuntu:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in kdump-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Committed
Status in kdump-tools source package in Focal:
  Invalid
Status in makedumpfile source package in Focal:
  Fix Committed
Status in kdump-tools source package in Impish:
  Invalid
Status in makedumpfile source package in Impish:
  Invalid
Status in kdump-tools source package in Jammy:
  In Progress
Status in makedumpfile source package in Jammy:
  Invalid
Status in kdump-tools source package in Kinetic:
  Fix Committed
Status in makedumpfile source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  Azure VM instances hit I/O error on boot causing kernel crash

  [Test Plan]

  Create Ubuntu Marketplace VM on Azure

  ```
  ssh -i .ssh/id_rsa ubuntu@ipaddr 
  ```

  Install crash dump utilities (from guide:
  https://ubuntu.com/server/docs/kernel-crash-dump)

  apt-get install kdump-tools

  Say (y) to all questions during install

  kdump-config show 
  *shows the vm is not yet ready to kdump 

  root@bionic3: kdump-config show 
   * no crashkernel= parameter in the kernel cmdline
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz
  kdump initrd: 
 /var/lib/kdump/initrd.img
  current state:Not ready to kdump

  kexec command:
no kexec command recorded

  
  Reboot the VM

  sudo su

  As root on the VM after reboot:

  kdump-config show

  kdump-config show 
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x3200
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-5.4.0-1086-azure
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure 
root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 
irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

  
  #verify kdump is on

  cat /proc/cmdline
  ... crashkernel=512M-:192M

  dmesg | grep -i crash
  [0.071660] kexec: Reserving the low 1M of memory for crashkernel
  [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System 
RAM: 4095MB)

  cat /proc/sys/kernel/sysrq
  # make sure this value is greater than 0
  #set it to 1
  sudo sysctl -w kernel.sysrq=1

  the directory of /var/crash should have no crashes yet as well.

  Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command:
  # perform crash
  sudo su
  echo c > /proc/sysrq-trigger

  After a couple of minuties 
  Open new terminal and try to ssh to azure  VM, 
  It does not succeed 

  Force a reboot of the VM through the portal or serial console 
  #kdump doesnt work and hangs indefinitely
  #force reboot VM from Azure console

  # verify package version of kdump-tool
  # verify parameter is not listed in the kdump-config show output 
  kdump-config unload
  kdump-config load 
  kdump-config show 

  kdump-config show 
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x3200
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-5.4.0-1086-azure
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure 
root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 
irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  
  #trigger another crash
  echo c > /proc/sysrq-trigger

  # open new terminal and ssh back into vm

  cd /var/crash

  #verify a dump was created 
  linux-image-5.4.0-1086-azure-202208041658.crash

  [Where Problems Could Occur]

  This change modifies the debian/rules.
  The package could fail to build properly if mistyped.

  [Other]
  Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" 
parameter.

  target series - Bionic, Focal, Jammy

  upstream patch

  https://salsa.debian.org/debian/kdump-
  

[Kernel-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2022-08-08 Thread Henry Spanka
I am having the same issue. Unfortunately the systems are already in
production so testing is a bit limited and the issue was not present at
first (not sure why or we didn't notice somehow).

I can confirm that I am seeing approx. 8% loss and huge latency > 1s sometimes.
Both tested with Ubuntu 18.04 and Ubuntu 20.04 with standard kernel and 
Libvirt/Openstack VMs. No difference.

Bond with LACP, bond first NIC primary and bond second NIC primary makes 
absolutely no difference.
Changed almost all NIC parameters (offloading, ring size, queues) etc., still 
same result.

My last bet was to completely remove the bond and just use the first NIC
interface. That worked and now I have stable latency and no loss.

Don't know what exactly causes this because we already replaced the NIC
with Mellanox and even had the same issue, so I am not sure if this is
an issue that happens when the BCM NIC is present but NOT USED somehow
(was installed on mainboard). But I can't do further testing now.
Removing the bond was my solution as @niveditasinghvi solution did not
work for me.

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num 

[Kernel-packages] [Bug 1969966] Re: No support for Intel Killer AX1675i

2022-08-08 Thread Juerg Haefliger
@harish-kp please do not hijack this bug report. Your problem (whatever
it is) is a different one. Please open a separate but report for that.

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

Title:
  No support for Intel Killer AX1675i

Status in backport-iwlwifi-dkms package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.

  
  I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried 
with 5.18rc1 but no change
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Dependencies: firmware-sof-signed 2.0-1ubuntu3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-26 (152 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 20220329.git681281e4-0ubuntu1
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  jammy
  Uname: Linux 5.17.4-051704-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to jammy on 2022-02-03 (83 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969966/+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 1981173] Re: Clear PCI errors left from BIOS

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  Clear PCI errors left from BIOS

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
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:
  Won't Fix
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 Committed
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:
  [Impact]
  Errors like Master Abort can be flagged before setting up PCI devices.

  [Fix]
  Clear PCI status that BIOS handed over to the OS.

  [Test]
  Using `lspci`, no more errors after boot.

  [Where problems could occur]
  If there's any driver's probe routine depends on PCI status to have 
  different behavior, this can cause some cracks. There doesn't seem to be
  any driver doing such insane thing though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981173/+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 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  intel_iommu: Fix  enable intel_iommu, Ubuntu 22.04 installation
  crashes

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
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 Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server.
  Attaching the console logs.

  Currently, it looks like disabling VT-D option in BIOS settings helps 
mitigate the issue.
  Console logs indicate something is wrong in iommu/dmar subsystem.

  [Fix]
  The IOMMU driver shares the pasid table for PCI alias devices. When the
  RID2PASID entry of the shared pasid table has been filled by the first
  device, the subsequent device will encounter the "DMAR: Setup RID2PASID
  failed" failure as the pasid entry has already been marked as present.
  As the result, the IOMMU probing process will be aborted.

  On the contrary, when any alias device is hot-removed from the system,
  for example, by writing to /sys/bus/pci/devices/.../remove, the shared
  RID2PASID will be cleared without any notifications to other devices.
  As the result, any DMAs from those rest devices are blocked.

  Sharing pasid table among PCI alias devices could save two memory pages
  for devices underneath the PCIe-to-PCI bridges. Anyway, considering that
  those devices are rare on modern platforms that support VT-d in scalable
  mode and the saved memory is negligible, it's reasonable to remove this
  part of immature code to make the driver feasible and stable.

  [Test Case]
  1. use the target machine(Intel Sapphire Rapids) and install the kernel with 
the fix.
  2. boot the target machine
  3. check dmesg if the error message exists
  [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed

  [Where problems could occur]
  After enable intel_iommu, the errors may be occurred.
  We need to figure out one by one once the related errors are triggered in the 
future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1982104/+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 1983756] Re: Please backport kernel patches to support thermal policy handling in OMEN laptops

2022-08-08 Thread Dimitri John Ledkov
it is not clear which release and which kernel is missing these features
on which hardware.


22.04.2 release is likely to ship with Kinetic's kernel, v5.19. Meaning all of 
these patches will be available on Desktop SKUs in due course.


Maybe you should contact Neon developer team about this, such that they can 
further clarify details, prepare backport patches, and submit them to the 
appropriate kernel tree, if they are needed.

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

Title:
  Please backport kernel patches to support thermal policy handling in
  OMEN laptops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As described in https://www.phoronix.com/news/HP-OMEN-Linux-5.16 and 
https://www.phoronix.com/news/Linux-5.18-HP-Omen-Thermal, thermal policy 
handling for OMEN laptops was added in kernel 5.16 and updated in 5.18:
  
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=4c51ba9af42dff0ef6a2ca3edcefa76f3466959e
  
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=286e937efbc7177c114e80aae9b402131e3886c1

  Please backport these kernel patches so that we can check and control
  fan speed, performance profiles and some device temps.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  $ lsb_release -rd
  Description:KDE neon User - 5.25
  Release:20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983756/+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 1981950] Re: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
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 Committed
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:
  [Impact]
  The system with atlantic NIC[1d6a:94c0] fails to resume from S3 and hang with 
the following errors

  Jun 7 13:13:54 ubuntu kernel: [ 116.000561] aq_nic_deinit+0xb4/0xd0 [atlantic]
  Jun 7 13:13:54 ubuntu kernel: [ 116.000566] atl_resume_common+0x6d/0x110 
[atlantic]
  Jun 7 13:13:54 ubuntu kernel: [ 116.000571] aq_pm_resume_restore+0x13/0x20 
[atlantic]
  Jun 7 13:13:54 ubuntu kernel: [ 116.000575] pci_pm_resume+0x5c/0x90
  Jun 7 13:13:54 ubuntu kernel: [ 116.000578] ? pci_pm_thaw+0x80/0x80
  Jun 7 13:13:54 ubuntu kernel: [ 116.000580] dpm_run_callback+0x4e/0x120
  Jun 7 13:13:54 ubuntu kernel: [ 116.000582] device_resume+0xad/0x200
  Jun 7 13:13:54 ubuntu kernel: [ 116.000583] async_resume+0x1e/0x40
  Jun 7 13:13:54 ubuntu kernel: [ 116.000585] async_run_entry_fn+0x33/0x120
  Jun 7 13:13:54 ubuntu kernel: [ 116.000586] process_one_work+0x220/0x3c0
  Jun 7 13:13:54 ubuntu kernel: [ 116.000588] worker_thread+0x4d/0x3f0
  Jun 7 13:13:54 ubuntu kernel: [ 116.000589] ? process_one_work+0x3c0/0x3c0
  Jun 7 13:13:54 ubuntu kernel: [ 116.000591] kthread+0x12a/0x150
  Jun 7 13:13:54 ubuntu kernel: [ 116.000592] ? set_kthread_struct+0x40/0x40
  Jun 7 13:13:54 ubuntu kernel: [ 116.000593] ret_from_fork+0x22/0x30
  Jun 7 13:13:54 ubuntu kernel: [ 116.000596] 
  Jun 7 13:13:54 ubuntu kernel: [ 116.000596] ---[ end trace 9d3fcd41d27dae25 
]---

  [Fix]
  aq_nic_deinit() has been called while suspending, so don't need to call it 
again on resuming.
  Applied below 2 commits from v5.19-rc7 fix the issue, and the 2 commits have 
been applied to stable kernel v5.10, v5.15, and v5.18.

  2e15c51fefaf net: atlantic: remove aq_nic_deinit() when resume
  0f3325076038 net: atlantic: remove deep parameter on suspend/resume functions

  [Test]
  Verified on the system with atlantic NIC[1d6a:94c0] and run S3 test for more 
than 200 times.

  [Where problems could occur]
  The 2 commits remove the redundant code, aq_nic_deinit() has been called 
while suspending, so we don't need to call it again while resuming, and this 
fix the issue. I don't think this would introduce any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981950/+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 1966010] Re: Fix audio on Zbook Studio G9

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  Fix audio on Zbook Studio G9

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The
  audio mute LEDs stop working after the said SRU.

  [Fix]
  Correcly interpret the debounce time from ACPI to gpiolib, and apply the
  correct quirk for the audio mute LEDs.

  [Where problems could occur]
  It's possible that some hardwares rely on the "wrong" debounce time to
  work, however the fix is to increase the debounce time, so it's more
  forgiving than decreasing.

  The LED fix is only applied to one system, so it's specifi and won't
  cause too much trouble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966010/+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 1972815] Re: Headset mic with Cirrus logic codec doesn't work

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  Headset mic with Cirrus logic codec doesn't work

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
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 Committed
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:
  [Impact]
  Headset mic doesn't be selected automatically after headset is plugged in.

  [Fix]
  Cirrus provides a fix for this issue
  
https://patchwork.kernel.org/project/alsa-devel/cover/20220504161236.2490532-1-sbind...@opensource.cirrus.com/

  Currently, they are included in v5.19-rc1
  ec6a8aaafbc5 ALSA: hda/cs8409: Support manual mode detection for 
CS42L429cd827381310 ALSA: hda/cs8409: Use general cs42l42 include in cs8409 hda 
driver
  7b43e6d79562 ASoC: cs42l42: Move CS42L42 register descriptions to general 
include

  
  [Test]
  Verified on the target platform, and confirmed these patches work.

  [Where problems could occur]
  These affect the mic detection on CS8409_BULLSEYE, CS8409_WARLOCK, 
CS8409_WARLOCK_MLK, CS8409_WARLOCK_MLK_DUAL_MIC, CS8409_CYBORG, and CS8409_ODIN 
platforms. Hard to tell if it introduce any regression, will keep an eye on it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1972815/+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 1942999] Re: [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address
  after hotplug tbt dock

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Confirmed

Bug description:
  SRU justification:

  [Impact]
  igc driver can not connect to network after re-plugin thunderbolt dock when
  MAC passthrough enabled in BIOS.

  [Fix]
  Wait for the MAC copy of BIOS when enabled MAC passthrough.
  Intel engineer wants a different solution and promise to discuss with 
firmware engineer.
  Due to the schedule, made this as a short term solution to fix the issue, and 
wait for the other
  fix from Intel.

  [Test]
  Verified on hardware, after hotplug the thunderbolt cable,
  Ethernet works fine.

  [Where problems could occur]
  It may break the igc driver.

  Intel still doesn't provide any solution about their approach.
  In the meantime, this patch is still the only fix.
  Re-submit it to Jammy, oem-5.17 and Unstable kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1942999/+subscriptions


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


[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

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

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

Bug description:
  [SRU Justification]

  [Impact]

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

  [Fix]

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

  [Test Case]

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

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

  [Where problems could occur]

  On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't
  support S0ix and has to be disabled. For the kernel side, the driver
  fixes addressed a few procedure errors that should be unlikely to
  introduce regressions; for the firmware side, also tested loading new
  firmware on unpatched kernels and there is no difference found yet.

  [Other Info]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions


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


[Kernel-packages] [Bug 1973104] Re: e1000e report hardware hang

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  e1000e report hardware hang

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

Bug description:
  [Impact]
  e1000e hardware unit hang after s2idle
  May 06 15:34:49 ubuntu kernel: e1000e :00:1f.6 enp0s31f6: Detected 
Hardware Unit Hang:
   TDH <1>
   TDT <5>
   next_to_use <5>
   next_to_clean <1>
     buffer_info[next_to_clean]:
   time_stamp <1000587f0>
   next_to_watch <1>
   jiffies <1000589c0>
   next_to_watch.status <0>
     MAC Status <40080283>
     PHY Status <796d>
     PHY 1000BASE-T Status <3800>
     PHY Extended Status <3000>
     PCI Status <10>

  [Fix]
  Below commits fix this issue which have been included in v5.19-rc8
  
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220508070905.1878172-1-sasha.nef...@intel.com/

  6cfa45361d3e Revert "e1000e: Fix possible HW unit hang after an s0ix exit"
  b49feacbeffc e1000e: Enable GPT clock before sending message to CSME

  
  [Test]
  Verified on the target machine, and confirmed the issue is gone.

  [Where problems could occur]
  The impact is low, it keeps the GPT clock enabled for CSME when 
e1000e_pm_resume() is called. With the new fix, the old workaround could be 
removed. I can't see this may introduce any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1973104/+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 1976438] Re: Fix sub-optimal I210 network speed

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  Fix sub-optimal I210 network speed

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
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:
  Won't Fix
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 Committed
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:
  [Impact]
  I210 may not reach maximum speed on Intel Alder Lake platforms.

  [Fix]
  Following the datasheet to ensure I210 is not in idle state when CPU is
  using PCIe link to perform TX.

  [Test] 
  With the fix applied, the I210 TX/RX speed can reach ~94x MBps.

  [Where problems could occur]
  Since this changes how hardware idles, it can slightly increase power
  consumption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1976438/+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 1980060] Re: Fix AMDGPU blank screen when Type-C DP alt is in use

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  Fix AMDGPU blank screen when Type-C DP alt is in use

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  When Type-C DP/HDMI is in use, s0ix resume renders both eDP and DP
  outputs blank.

  [Fix]
  Query the firmware to ensure the DP alt status.

  [Test]
  Suspend and resume the system, both eDP and Type-C DP/HDMI are working.

  [Where problems could occur]
  This fix only applies to certain AMD GFX with certain firmware version,
  so the scope is very limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980060/+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 1981773] Re: Make cm32181 sensor work after system suspend

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  Make cm32181 sensor work after system suspend

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
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 Committed
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:
  [Impact]
  cm32181 ambient light sensor stops working after system suspend.

  [Fix]
  Add PM support for cm32181 so it can work after system suspend.

  [Test]
  The sysfs in_illuminance_input continues to change after system suspend.

  [Where problems could occur]
  This changeset is limited to a specific device, and it already lacks PM
  support - so the worst case is that it stops working after resume like
  it always has been.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981773/+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 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

2022-08-08 Thread Timo Aaltonen
** Also affects: hwe-next
   Importance: Undecided
   Status: New

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  AMD Rembrandt: DP tunneling fails with Thunderbolt monitors

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
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:
  New
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New

Bug description:
  [Summary]
  No video output on Thunderbolt monitor.
  1. Connect monitor to DUT directly
  2. Connect monitor to DUT via Docking

  System can detect the monitor and able to change display mode but no
  output on the monitor

  [Steps to reproduce]
  1. Boot to OS
  2. Plug an external monitor via thunderbolt port

  [Expected result]
  Display on external monitor normally

  [Actual result]
  No vidoe ouput on external monitor

  [Failure rate]
  3/3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1983143/+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 1983297] Re: Additional fix for TGL + AUO panel flickering

2022-08-08 Thread Timo Aaltonen
** Changed in: hwe-next
   Status: New => Fix Committed

** Changed in: hwe-next
   Importance: Undecided => Critical

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

Title:
  Additional fix for TGL + AUO panel flickering

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact] 
  "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel"
  alone used to fix the issue on the AUO panel. But the panel starts to
  flicker like crazy on top of the new stable commits. 

  [Fix]
  Backport full fix for PSR2 selective fetch, but only enable it on TGL +
  specific AUO panel. The last three patches which enable PSR2 on ADL-P
  are dropped.

  [Test]
  Originally the backport regressed ADL + BOE panel, so this time we
  put extra effort to ensure those system are unaffected, while TGL + AUO
  panel is still fixed.
   
  [Where problems could occur]
  Most code changes only have functional impact when PSR2 selective fetch
  is enabled. Some of changes are under more general call path for
  hardware cursor rendering.

  Notes are added to describe the functional impact for each patch, so if
  regression really occurrs it's easier to spot the offending commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1983297/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy

2022-08-08 Thread Dimitri John Ledkov
Hi, the zfs userspace .deb package versions can be out of sync with the
kernel driver zfs kernel module version number. This can be seen in the
output of

$ zfs version

For example on my test system I have:

$ sudo zfs version
zfs-2.1.4-0ubuntu0.1
zfs-kmod-2.1.5-1ubuntu2


Because I have a newer kernel version, than userspace tooling (I am testing 
upgrades). Or vice versa.

This particular bug is fixed in zfs 2.1.4-0ubuntu0.1 or higher, which is
included in linux 5.15.0-43.46 or higher (or kernels based of it). Thus
without upgrading zfs packages, one can reboot into newer kernel, which
has never zfs, and things should be fine.

If anyone is having issues, please provide output of:

uname -r
sudo zfs version

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

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
  Jammy

Status in Native ZFS for Linux:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Summary]

  When running Jammy on zfs or LXD with a zfs pool on a Jammy host,
  fallocate creates a zero-sized file.

  The issue was originally found when installing mysql on LXD, where
  fallocate would create a zero-sized ib_logfile1 file. The original
  information in this bug is based on that.

  [Steps to Reproduce]

  touch foo.img
  fallocate -z -l 10M foo.img
  ls -la foo.img

  On a non-zfs Jammy system this will show something like:
  -rw-r--r-- 1 root root 10M ...

  while on zfs it will show:
  -rw-rw-r-- 1 root root 0 ...

  [Original Description]
  I came across this error when testing various mysql setups in an LXD 
container and managed to reproduce it consistently. I'm unable to reproduce on 
Ubuntu desktop or server though since the prerequisites are probably handled 
properly there.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 15 21:31:09 2022
  Dmesg:

  ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  KernLog:

  Logs.var.log.daemon.log:

  MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
  MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
   [mysqldump]
   quick
   quote-names
   max_allowed_packet   = 16M
  MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic 
links: '/etc/mysql/my.cnf'
  MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 
'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 
'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 
'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 
'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 
'public_key.pem', 'ca.pem', 'server-key.pem']
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: mysql-8.0
  Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1969247/+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 1983787] Re: USB hub only works in USB2 ports

2022-08-08 Thread James Lanham
Here is the full dmesg log during my fooling around.

** Attachment added: "dmesg-full.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+attachment/5607363/+files/dmesg-full.txt

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

Title:
  USB hub only works in USB2 ports

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

Bug description:
  I have an IOGear GUS404 USB hub/switch
  (https://www.iogear.com/product/GUS404/), which works only when
  plugged into a USB2.0 port. When plugged into a USB3.0 port, none of
  the attached peripherals work. The attached peripherals are:

  1) Corsair Vengeance K70 RGB Keyboard
  (https://www.corsair.com/us/en/Categories/Products/Gaming-
  Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical-
  Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA)

  2) Logitech G9x Mouse
  (https://www.newegg.com/logitech-g9x/p/N82E16826104261)

  3) Logitech C922 Webcam
  (https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-
  for-hd-video-streaming-black/5579380.p?skuId=5579380)

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

  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: MATE
  Date: Sun Aug  7 15:57:21 2022
  InstallationDate: Installed on 2022-06-11 (57 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1983787/+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 1983787] Re: USB hub only works in USB2 ports

2022-08-08 Thread James Lanham
Agreed that loading an older kernel might give some interesting info,
but it might not be until later this week that I can re-image my machine
and get that to you. In the meantime, here is the dmesg info, and my
observations:

At 219.322795, I disconnect from the USB2 port, plug into USB3 at 220.959698, 
and an interesting error appears at 224.531221: 
[  224.531221] usb 8-2.2: Not enough bandwidth for new device state.
[  224.531226] usb 8-2.2: can't set config #1, error -28

This is just after it tries to load the mouse, but the same error appears when 
it detects the keybaord as well. 
I did some experimenting, and it turns out if I ONLY plug the webcam into the 
hub, then it works fine in both port types. But if I ONLY plug in a standard 
plain office keyboard, then it again works only in USB2 ports. It's as if USB3 
ports don't like non 'high-speed' devices plugged into the hub. 

Here is the log from when I only have the plain office keybaord plugged into 
the hub -> USB2:
[  921.131359] usb 1-5.2: new low-speed USB device number 19 using ehci-pci
[  921.378603] usb 1-5.2: New USB device found, idVendor=03f0, idProduct=034a, 
bcdDevice= 1.21
[  921.378610] usb 1-5.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  921.378612] usb 1-5.2: Product: HP Elite USB Keyboard
[  921.378614] usb 1-5.2: Manufacturer: Chicony
[  921.387895] input: Chicony HP Elite USB Keyboard as 
/devices/pci:00/:00:12.2/usb1/1-5/1-5.2/1-5.2:1.0/0003:03F0:034A.000E/input/input39
[  921.447589] hid-generic 0003:03F0:034A.000E: input,hidraw0: USB HID v1.10 
Keyboard [Chicony HP Elite USB Keyboard] on usb-:00:12.2-5.2/input0
[  921.454660] input: Chicony HP Elite USB Keyboard System Control as 
/devices/pci:00/:00:12.2/usb1/1-5/1-5.2/1-5.2:1.1/0003:03F0:034A.000F/input/input40
[  921.511524] input: Chicony HP Elite USB Keyboard Consumer Control as 
/devices/pci:00/:00:12.2/usb1/1-5/1-5.2/1-5.2:1.1/0003:03F0:034A.000F/input/input41
[  921.511621] hid-generic 0003:03F0:034A.000F: input,hidraw1: USB HID v1.10 
Device [Chicony HP Elite USB Keyboard] on usb-:00:12.2-5.2/input1

And the same for USB3:
[  892.290826] usb 8-2.2: new low-speed USB device number 10 using xhci_hcd
[  892.554392] usb 8-2.2: New USB device found, idVendor=03f0, idProduct=034a, 
bcdDevice= 1.21
[  892.554397] usb 8-2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[  892.554400] usb 8-2.2: Product: HP Elite USB Keyboard
[  892.554401] usb 8-2.2: Manufacturer: Chicony
[  892.554542] usb 8-2.2: Not enough bandwidth for new device state.
[  892.554548] usb 8-2.2: can't set config #1, error -28

I'll include what you requested as dmesg.txt, but everything, including
my experimenting with multiple unplugs/replugs, is in dmesg-full.txt

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1983787/+attachment/5607362/+files/dmesg.txt

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

Title:
  USB hub only works in USB2 ports

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

Bug description:
  I have an IOGear GUS404 USB hub/switch
  (https://www.iogear.com/product/GUS404/), which works only when
  plugged into a USB2.0 port. When plugged into a USB3.0 port, none of
  the attached peripherals work. The attached peripherals are:

  1) Corsair Vengeance K70 RGB Keyboard
  (https://www.corsair.com/us/en/Categories/Products/Gaming-
  Keyboards/Vengeance%C2%AE-K70-RGB-%28Limited-Edition%29-Mechanical-
  Gaming-Keyboard-%E2%80%94-CHERRY%C2%AE-MX-Brown/p/CH-993-NA)

  2) Logitech G9x Mouse
  (https://www.newegg.com/logitech-g9x/p/N82E16826104261)

  3) Logitech C922 Webcam
  (https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-
  for-hd-video-streaming-black/5579380.p?skuId=5579380)

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

  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: MATE
  Date: Sun Aug  7 15:57:21 2022
  InstallationDate: Installed on 2022-06-11 (57 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1983787/+subscriptions


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

[Kernel-packages] [Bug 1983620] Re: Cannot netboot Raspberry Pi 4B with NFSv4

2022-08-08 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1954716 ***
https://bugs.launchpad.net/bugs/1954716

** This bug has been marked a duplicate of bug 1954716
   rpi nfsroot vers=4 not supported anymore?

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

Title:
  Cannot netboot Raspberry Pi 4B with NFSv4

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  I am trying to do a network boot of Ubuntu 22.04 on a Raspberry Pi 4B
  (RPi4). I had the same problem previously with Ubuntu 20.04.

  I can network boot Ubuntu using TFTP if I specify nfsroot as an NFSv3
  address. However, I then run into problems with overlayroot not
  working (see https://askubuntu.com/questions/1401854/why-doesnt-
  overlayroot-work-properly-with-a-net-booted-nfs-root-on-a-rpi4).

  I suspect overlayroot only works with NFSv4 (at least, I hope this is
  a way out of the quandary). However, when I use an NFSv4 address for
  nfsroot in cmdline.txt, I get "permissions denied" errors. Adding
  NFSv4 parameters (nfsvers=4, vers=4, rootfstype=nfs4) to cmdline.txt
  has no apparent effect: indeed, if I put in an NFSv3 address they get
  ignored completely.

  I have been working on this problem since April and have received no
  feedback at all on AskUbuntu
  (https://askubuntu.com/questions/1421606/rpi4-network-boot-
  configuration-error-or-bug), SuperUser
  (https://superuser.com/questions/1716358/how-to-netboot-a-raspberry-
  pi-with-tftp-and-nfs-on-a-synology-nas) or Launchpad (which I find
  difficult to navigate). It may not be a bug, in which case I
  apologise, but it looks like one to me and - without feedback - I have
  no way of determining whether it is or not.

  root@q-ubu:~# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1012-raspi 5.15.0-1012.14
  ProcVersionSignature: Ubuntu 5.15.0-1012.14-raspi 5.15.39
  Uname: Linux 5.15.0-1012-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Aug  4 22:34:34 2022
  ImageMediaBuild: 20220419
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=xterm-256color
   LC_CTYPE=C.UTF-8
   PATH=(custom, no user)
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1983620/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread stkim
I also try a kernel  https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-
tip/2022-08-06/amd64/.

The display is black on the xorg/wayland and mouse pointer is jumping on
the xorg session.

So, waiting a nvidia driver fix..

Thank you for reply.

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1983850] Re: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build

2022-08-08 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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

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

Bug description:
  failing to update from sofware

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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
  DKMSKernelVersion: 5.15.0-43-generic
  Date: Thu Aug  4 10:45:56 2022
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.91.03/build/common/inc/nv-time.h:208:18:
 error: ‘struct task_struct’ has no member named ‘state’; did you mean 
‘__state’?
  InstallationDate: Installed on 2021-03-24 (501 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 460.91.03-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1983850/+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-08 Thread Stefan Bader
** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** 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/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 1983850] [NEW] nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build

2022-08-08 Thread Kangembega Kangembega
Public bug reported:

failing to update from sofware

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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
DKMSKernelVersion: 5.15.0-43-generic
Date: Thu Aug  4 10:45:56 2022
Dependencies:
 
DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.91.03/build/common/inc/nv-time.h:208:18:
 error: ‘struct task_struct’ has no member named ‘state’; did you mean 
‘__state’?
InstallationDate: Installed on 2021-03-24 (501 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageVersion: 460.91.03-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.4
SourcePackage: nvidia-graphics-drivers-460
Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

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

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

Bug description:
  failing to update from sofware

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.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
  DKMSKernelVersion: 5.15.0-43-generic
  Date: Thu Aug  4 10:45:56 2022
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.91.03/build/common/inc/nv-time.h:208:18:
 error: ‘struct task_struct’ has no member named ‘state’; did you mean 
‘__state’?
  InstallationDate: Installed on 2021-03-24 (501 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 460.91.03-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1983850/+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 1896350] Re: nbd: requests can become stuck when disconnecting from server with qemu-nbd

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

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

Title:
  nbd: requests can become stuck when disconnecting from server with
  qemu-nbd

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1896350

  [Impact]

  After 2516ab1("nbd: only clear the queue on device teardown"), present
  in 4.12-rc1 onward, the ioctl NBD_CLEAR_SOCK can no longer clear
  requests currently being processed. This change was made to fix a race
  between using the NBD_CLEAR_SOCK ioctl to clear requests, and teardown
  of the device clearing requests. This worked for the most part, as
  several years ago systemd was not set up to watch nbd devices for
  changes in their state.

  But after:

  commit f82abfcda58168d9f667e2094d438763531d3fa6
  From: Tony Asleson 
  Date: Fri, 8 Feb 2019 15:47:10 -0600
  Subject: rules: watch metadata changes on nbd devices
  Link: 
https://github.com/systemd/systemd/commit/f82abfcda58168d9f667e2094d438763531d3fa6

  in systemd v242-rc1, nbd* devices were added to a udev rule to watch
  those devices for changes with the inotify subsystem. From man udev:

  > watch
  >   Watch the device node with inotify; when the node is closed after being 
  >   opened for writing, a change uevent is synthesized.
  >
  > nowatch
  >   Disable the watching of a device node with inotify.

  This changed the behaviour of device teardown, since systemd now keeps
  tabs on the device with inotify, outstanding requests cannot be
  cleared as nbd_xmit_timeout() will always return 'BLK_EH_RESET_TIMER',
  and requests get stuck, never to complete, because a disconnect has
  occurred, and never to timeout, as their timers keep being reset.

  Symptoms of this issue is that the nbd subsystem gets stuck with
  messages like:

  block nbd15: NBD_DISCONNECT
  block nbd15: Send disconnect failed -32
  ...
  block nbd15: Possible stuck request 7fcf62ba: control 
(read@523915264,24576B). Runtime 30 seconds
  ...
  block nbd15: Possible stuck request 7fcf62ba: control 
(read@523915264,24576B). Runtime 150 seconds
  ...
  INFO: task qemu-nbd:1267 blocked for more than 120 seconds.
Not tainted 5.15.0-23-generic #23-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  task:qemu-nbdstate:D stack:0 pid: 1267 ppid: 1 
flags:0x0002
  Call Trace:
   
   __schedule+0x23d/0x590
   ? call_rcu+0xe/0x10
   schedule+0x4e/0xb0
   blk_mq_freeze_queue_wait+0x69/0xa0
   ? wait_woken+0x70/0x70
   blk_mq_freeze_queue+0x1b/0x30
   nbd_add_socket+0x76/0x1f0 [nbd]
   __nbd_ioctl+0x18b/0x340 [nbd]
   ? security_capable+0x3d/0x60
   nbd_ioctl+0x81/0xb0 [nbd]
   blkdev_ioctl+0x12e/0x270
   ? __fget_files+0x86/0xc0
   block_ioctl+0x46/0x50
   __x64_sys_ioctl+0x91/0xc0
   do_syscall_64+0x5c/0xc0
   entry_SYSCALL_64_after_hwframe+0x44/0xae
   

  Additionally, in syslog you will also see systemd-udevd get stuck:

  systemd-udevd[419]: nbd15: Worker [2004] processing SEQNUM=5661 is
  taking a long time

  $ ps aux
  ...
  4191194 root D 0.1 systemd-udevd   -

  We can workaround the issue by adding a higher priority udev rule to
  not watch nbd* devices.

  $ cat << EOF >> /etc/udev/rules.d/97-nbd-device.rules
  # Disable inotify watching of change events for NBD devices
  ACTION=="add|change", KERNEL=="nbd*", OPTIONS:="nowatch"
  EOF

  $ sudo udevadm control --reload-rules
  $ sudo udevadm trigger

  [Fix]

  The fix relies on infrastructure provided by the flag
  NBD_CMD_INFLIGHT, which was introduced in 5.16, and added to in 5.19.
  We need to backport all commits related to NBD_CMD_INFLIGHT to our
  kernels for the fix to be effective.

  For Focal, Impish and Jammy:

  commit 4e6eef5dc25b528e08ac5b5f64f6ca9d9987241d
  Author: Yu Kuai 
  Date:   Thu Sep 16 17:33:44 2021 +0800
  Subject: nbd: don't handle response without a corresponding request message
  Link: 
https://github.com/torvalds/linux/commit/4e6eef5dc25b528e08ac5b5f64f6ca9d9987241d

  commit 07175cb1baf4c51051b1fbd391097e349f9a02a9
  Author: Yu Kuai 
  Date:   Thu Sep 16 17:33:45 2021 +0800
  Subject: nbd: make sure request completion won't concurrent
  Link: 
https://github.com/torvalds/linux/commit/07175cb1baf4c51051b1fbd391097e349f9a02a9

  commit 2895f1831e911ca87d4efdf43e35eb72a0c7e66e
  Author: Yu Kuai 
  Date:   Sat May 21 15:37:46 2022 +0800
  Subject: nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed
  Link: 

[Kernel-packages] [Bug 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread stkim
I test kernel in https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.19/amd64/.

xorg session, additionally mouse is lagged.

[0.00] Linux version 5.19.0-051900-generic (kernel@sita) 
(x86_64-linux-gnu-gcc-11 (Ubuntu 11.3.0-5ubuntu1) 11.3.0, GNU ld (GNU Binutils 
for Ubuntu) 2.38.90.20220713) #202207312230 SMP PREEMPT_DYNAMIC Sun Jul 31 
22:34:11 UTC 2022
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-051900-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Hygon HygonGenuine
[0.00]   Centaur CentaurHauls
[0.00]   zhaoxin   Shanghai  
[0.00] x86/split lock detection: #AC: crashing the kernel on kernel 
split_locks and warning on user-space split_locks
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User 
registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:8
[0.00] x86/fpu: Enabled xstate features 0x207, context size is 840 
bytes, using 'compacted' format.
[0.00] signal: max sigframe size: 3632
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x8bb6efff] usable
[0.00] BIOS-e820: [mem 0x8bb6f000-0x90b2efff] reserved
[0.00] BIOS-e820: [mem 0x90b2f000-0x9172efff] ACPI NVS
[0.00] BIOS-e820: [mem 0x9172f000-0x917fefff] ACPI data
[0.00] BIOS-e820: [mem 0x917ff000-0x917f] usable
[0.00] BIOS-e820: [mem 0x9180-0x95ff] reserved
[0.00] BIOS-e820: [mem 0x97e0-0x97ff] reserved
[0.00] BIOS-e820: [mem 0x9880-0xa07f] reserved
[0.00] BIOS-e820: [mem 0xc000-0xcfff] reserved
[0.00] BIOS-e820: [mem 0xfed2-0xfed7] reserved
[0.00] BIOS-e820: [mem 0x0001-0x000c5f7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.70 by Lenovo
[0.00] efi: ACPI=0x917fe000 ACPI 2.0=0x917fe014 TPMFinalLog=0x9168e000 
SMBIOS=0x8d8af000 SMBIOS 3.0=0x8d8a2000 MEMATTR=0x8665c018 ESRT=0x86bae018 
MOKvar=0x8665f000 RNG=0x8da2e418 TPMEventLog=0x5de81018 
[0.00] efi: seeding entropy pool
[0.00] random: crng init done
[0.00] SMBIOS 3.4.0 present.
[0.00] DMI: LENOVO 21BVCTO1WW/21BVCTO1WW, BIOS N3BET46W (1.24 ) 
06/07/2022
[0.00] tsc: Detected 2500.000 MHz processor
[0.00] tsc: Detected 2496.000 MHz TSC
[0.06] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.09] e820: remove [mem 0x000a-0x000f] usable
[0.17] last_pfn = 0xc5f800 max_arch_pfn = 0x4
[0.000342] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.001603] total RAM covered: 63936M
[0.001737] Found optimal setting for mtrr clean up
[0.001738]  gran_size: 64K  chunk_size: 128Mnum_reg: 7  lose 
cover RAM: 0G
[0.002525] e820: update [mem 0x9c00-0x] usable ==> reserved
[0.002530] last_pfn = 0x91800 max_arch_pfn = 0x4
[0.012287] esrt: Reserving ESRT space from 0x86bae018 to 
0x86bae2d0.
[0.012293] e820: update [mem 0x86bae000-0x86baefff] usable ==> reserved
[0.012307] e820: update [mem 0x8665f000-0x8665] usable ==> reserved
[0.012328] Using GB pages for direct mapping
[0.012697] Secure boot disabled
[0.012697] RAMDISK: [mem 0x360d5000-0x3a35afff]
[0.012704] ACPI: Early table checksum verification disabled
[0.012707] ACPI: RSDP 0x917FE014 24 (v02 LENOVO)
[0.012713] ACPI: XSDT 0x917FC188 000144 (v01 LENOVO TP-N3B   
1240 PTEC 0002)
[0.012721] ACPI: FACP 0x8D891000 000114 (v06 LENOVO TP-N3B   
1240 PTEC 0002)
[0.012728] ACPI: DSDT 0x8D843000 0493FA (v02 LENOVO ICL  
0002  0113)
[0.012732] ACPI: FACS 0x91673000 40
[0.012736] ACPI: SSDT 0x8D94A000 00038C (v02 LENOVO Pmax_Dev 
0001 INTL 20200717)
[0.012741] ACPI: SSDT 0x8D932000 005D0B (v02 LENOVO CpuSsdt  
3000 INTL 20200717)
[0.012745] ACPI: SSDT 0x8D931000 00059B (v02 LENOVO CtdpB
1000 INTL 20200717)
[0.012749] ACPI: SSDT 0x8D8C2000 003203 (v02 LENOVO DptfTabl 
1000 INTL 20200717)
[

[Kernel-packages] [Bug 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread stkim
I test kernel in https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.19/amd64/.

wayland session, additionally mouse is normal.

[0.00] Linux version 5.19.0-051900-generic (kernel@sita) 
(x86_64-linux-gnu-gcc-11 (Ubuntu 11.3.0-5ubuntu1) 11.3.0, GNU ld (GNU Binutils 
for Ubuntu) 2.38.90.20220713) #202207312230 SMP PREEMPT_DYNAMIC Sun Jul 31 
22:34:11 UTC 2022
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-051900-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Hygon HygonGenuine
[0.00]   Centaur CentaurHauls
[0.00]   zhaoxin   Shanghai  
[0.00] x86/split lock detection: #AC: crashing the kernel on kernel 
split_locks and warning on user-space split_locks
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User 
registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:8
[0.00] x86/fpu: Enabled xstate features 0x207, context size is 840 
bytes, using 'compacted' format.
[0.00] signal: max sigframe size: 3632
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x8bb6efff] usable
[0.00] BIOS-e820: [mem 0x8bb6f000-0x90b2efff] reserved
[0.00] BIOS-e820: [mem 0x90b2f000-0x9172efff] ACPI NVS
[0.00] BIOS-e820: [mem 0x9172f000-0x917fefff] ACPI data
[0.00] BIOS-e820: [mem 0x917ff000-0x917f] usable
[0.00] BIOS-e820: [mem 0x9180-0x95ff] reserved
[0.00] BIOS-e820: [mem 0x97e0-0x97ff] reserved
[0.00] BIOS-e820: [mem 0x9880-0xa07f] reserved
[0.00] BIOS-e820: [mem 0xc000-0xcfff] reserved
[0.00] BIOS-e820: [mem 0xfed2-0xfed7] reserved
[0.00] BIOS-e820: [mem 0x0001-0x000c5f7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.70 by Lenovo
[0.00] efi: ACPI=0x917fe000 ACPI 2.0=0x917fe014 TPMFinalLog=0x9168e000 
SMBIOS=0x8d8af000 SMBIOS 3.0=0x8d8a2000 MEMATTR=0x8665c018 ESRT=0x86bae018 
MOKvar=0x8665f000 RNG=0x8da2e418 TPMEventLog=0x5de81018 
[0.00] efi: seeding entropy pool
[0.00] random: crng init done
[0.00] SMBIOS 3.4.0 present.
[0.00] DMI: LENOVO 21BVCTO1WW/21BVCTO1WW, BIOS N3BET46W (1.24 ) 
06/07/2022
[0.00] tsc: Detected 2500.000 MHz processor
[0.00] tsc: Detected 2496.000 MHz TSC
[0.06] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.09] e820: remove [mem 0x000a-0x000f] usable
[0.17] last_pfn = 0xc5f800 max_arch_pfn = 0x4
[0.000338] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.001626] total RAM covered: 63936M
[0.001758] Found optimal setting for mtrr clean up
[0.001759]  gran_size: 64K  chunk_size: 128Mnum_reg: 7  lose 
cover RAM: 0G
[0.002507] e820: update [mem 0x9c00-0x] usable ==> reserved
[0.002511] last_pfn = 0x91800 max_arch_pfn = 0x4
[0.011230] esrt: Reserving ESRT space from 0x86bae018 to 
0x86bae2d0.
[0.011235] e820: update [mem 0x86bae000-0x86baefff] usable ==> reserved
[0.011249] e820: update [mem 0x8665f000-0x8665] usable ==> reserved
[0.011271] Using GB pages for direct mapping
[0.011682] Secure boot disabled
[0.011682] RAMDISK: [mem 0x360d5000-0x3a35afff]
[0.011689] ACPI: Early table checksum verification disabled
[0.011693] ACPI: RSDP 0x917FE014 24 (v02 LENOVO)
[0.011698] ACPI: XSDT 0x917FC188 000144 (v01 LENOVO TP-N3B   
1240 PTEC 0002)
[0.011706] ACPI: FACP 0x8D891000 000114 (v06 LENOVO TP-N3B   
1240 PTEC 0002)
[0.011714] ACPI: DSDT 0x8D843000 0493FA (v02 LENOVO ICL  
0002  0113)
[0.011718] ACPI: FACS 0x91673000 40
[0.011722] ACPI: SSDT 0x8D94A000 00038C (v02 LENOVO Pmax_Dev 
0001 INTL 20200717)
[0.011726] ACPI: SSDT 0x8D932000 005D0B (v02 LENOVO CpuSsdt  
3000 INTL 20200717)
[0.011730] ACPI: SSDT 0x8D931000 00059B (v02 LENOVO CtdpB
1000 INTL 20200717)
[0.011735] ACPI: SSDT 0x8D8C2000 003203 (v02 LENOVO DptfTabl 
1000 INTL 20200717)
[

[Kernel-packages] [Bug 1983291] Re: Update firmware for DCN316/GFX1037

2022-08-08 Thread Juerg Haefliger
** Tags added: kern-4119

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

Title:
  Update firmware for DCN316/GFX1037

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Jammy already has firmware for upcoming product with GFX1037 and DCN316.  
However this firmware has some stability problems under stress and it should be 
updated to latest on linux-firmware.git to support systems that will take this 
firmware.

  [Fix]
  Upgrade following binaries:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122

  [Test]
  Verify suspend/resume works.
  Verify that accelerated graphics works.
  Verify video playback works.

  [Where problems could occur]
  Firmware is only loaded to product with GFX1037/DCN316
  This isn't yet on the market and regressions are not possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983291/+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 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices

2022-08-08 Thread Kinga Tanska
Hi,

Should I submit new bug for Jammy? I don't see this release in this bug,
but it should be fixed there too.

Kinga Tanska

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

Title:
  [VROC] Kernel does not contain fixes for iostat for md devices

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.13 source package in Focal:
  In Progress
Status in linux source package in Impish:
  Won't Fix
Status in linux-hwe-5.13 source package in Impish:
  Invalid

Bug description:
  Hello,

  I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does
  not contain fixes for IO statistics for md devices. IO statistics for
  md devices were added to kernel 5.10
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d)
  but then bug for double fault was reported and this patch was reverted
  by Guoqing Jiang
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8).

  Guoqing Jiang added series of patches which fixes problem and adds IO stats 
for md devices on top on the revert patch:
  - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f)
  - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b)

  I checked that kernel used in ubuntu 22.04 contains only patch with revert - 
iostat does not report for md devices 
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang)
  Please consider adding series of patches described above.

  Regards,
  Kinga Tanska

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+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 1983193] Re: Internet connectivity through AR8131 Gigabit Ethernet breaks

2022-08-08 Thread Juerg Haefliger
So this is no longer an issue?

** Tags added: kern-4118

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

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

Title:
  Internet connectivity through AR8131 Gigabit Ethernet breaks

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  20220329.git681281e4-0ubuntu3.3 (later referenced as *3) for linux-
  firmware breaks internet connectivity/there is no internet
  connectivity through AR8131 Gigabit Ethernet interface.

  Using the installed package prior to this update,
  20220329.git681281e4-0ubuntu1 (later referenced as *1), does not cause
  an issue.

  Ubuntu release: 22.04

  When I installed *3, rebooted the next day and internet was no longer
  available.  Checked with the the internet service provider, and
  connected the ethernet cable to a separate matchine and had
  connectivity.  A boot with live Ubuntu 22.04 USB showed no
  connectivity issues (which I assume is using *1).  Reinstalled a fresh
  Ubuntu 22.04 and held back *3.3 and now have internet.

  The only other update made on the day of the update of *3 was
  wireless-regdb.  This package was not held back when I reinstalled
  Ubuntu 22.04, seems to be causing no issue.

  **Update** Tried going to *3 package today and internet connectivity
  works. Maybe there was corruption but received no messages of same the
  day of the original upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983193/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread Daniel van Vugt
No problem. It's likely that legacy KMS is still using some atomic KMS
code in the kernel so the crash would keep happening...

If that's really the cause of this bug then the solution will be to try a newer 
kernel like:
  https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2022-08-06/amd64/
or
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/amd64/

If however the i915 crash is not the cause of the black screen (like if
the HDMI port is wired to the Nvidia GPU) then we might be waiting for
an Nvidia driver fix.

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread stkim
I put "=0" on the end.

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0


reboot -> login xog session ==> still external monitor is black.

[0.00] Linux version 5.15.0-43-generic (buildd@lcy02-amd64-076) (gcc 
(Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) 
#46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 (Ubuntu 5.15.0-43.46-generic 
5.15.39)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Hygon HygonGenuine
[0.00]   Centaur CentaurHauls
[0.00]   zhaoxin   Shanghai  
[0.00] x86/split lock detection: #AC: crashing the kernel on kernel 
split_locks and warning on user-space split_locks
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User 
registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:8
[0.00] x86/fpu: Enabled xstate features 0x207, context size is 840 
bytes, using 'compacted' format.
[0.00] signal: max sigframe size: 3632
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x8bb6efff] usable
[0.00] BIOS-e820: [mem 0x8bb6f000-0x90b2efff] reserved
[0.00] BIOS-e820: [mem 0x90b2f000-0x9172efff] ACPI NVS
[0.00] BIOS-e820: [mem 0x9172f000-0x917fefff] ACPI data
[0.00] BIOS-e820: [mem 0x917ff000-0x917f] usable
[0.00] BIOS-e820: [mem 0x9180-0x95ff] reserved
[0.00] BIOS-e820: [mem 0x97e0-0x97ff] reserved
[0.00] BIOS-e820: [mem 0x9880-0xa07f] reserved
[0.00] BIOS-e820: [mem 0xc000-0xcfff] reserved
[0.00] BIOS-e820: [mem 0xfed2-0xfed7] reserved
[0.00] BIOS-e820: [mem 0x0001-0x000c5f7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.70 by Lenovo
[0.00] efi: ACPI=0x917fe000 ACPI 2.0=0x917fe014 TPMFinalLog=0x9168e000 
SMBIOS=0x8d8af000 SMBIOS 3.0=0x8d8a2000 MEMATTR=0x8665c018 ESRT=0x86bae018 
MOKvar=0x8665f000 RNG=0x8da2e418 TPMEventLog=0x5de81018 
[0.00] efi: seeding entropy pool
[0.00] random: fast init done
[0.00] secureboot: Secure boot disabled
[0.00] SMBIOS 3.4.0 present.
[0.00] DMI: LENOVO 21BVCTO1WW/21BVCTO1WW, BIOS N3BET46W (1.24 ) 
06/07/2022
[0.00] tsc: Detected 2500.000 MHz processor
[0.00] tsc: Detected 2496.000 MHz TSC
[0.07] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.10] e820: remove [mem 0x000a-0x000f] usable
[0.17] last_pfn = 0xc5f800 max_arch_pfn = 0x4
[0.000333] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.002579] total RAM covered: 63936M
[0.002708] Found optimal setting for mtrr clean up
[0.002709]  gran_size: 64K  chunk_size: 128Mnum_reg: 7  lose 
cover RAM: 0G
[0.003419] e820: update [mem 0x9c00-0x] usable ==> reserved
[0.003424] last_pfn = 0x91800 max_arch_pfn = 0x4
[0.011505] esrt: Reserving ESRT space from 0x86bae018 to 
0x86bae2d0.
[0.011511] e820: update [mem 0x86bae000-0x86baefff] usable ==> reserved
[0.011523] e820: update [mem 0x8665f000-0x8665] usable ==> reserved
[0.011542] Using GB pages for direct mapping
[0.012021] secureboot: Secure boot disabled
[0.012022] RAMDISK: [mem 0x367e4000-0x3a35afff]
[0.012029] ACPI: Early table checksum verification disabled
[0.012033] ACPI: RSDP 0x917FE014 24 (v02 LENOVO)
[0.012039] ACPI: XSDT 0x917FC188 000144 (v01 LENOVO TP-N3B   
1240 PTEC 0002)
[0.012047] ACPI: FACP 0x8D891000 000114 (v06 LENOVO TP-N3B   
1240 PTEC 0002)
[0.012054] ACPI: DSDT 0x8D843000 0493FA (v02 LENOVO ICL  
0002  0113)
[0.012059] ACPI: FACS 0x91673000 40
[0.012063] ACPI: SSDT 0x8D94A000 00038C (v02 LENOVO Pmax_Dev 
0001 INTL 20200717)
[0.012067] ACPI: SSDT 0x8D932000 005D0B (v02 LENOVO CpuSsdt  
3000 INTL 20200717)
[0.012071] ACPI: SSDT 0x8D931000 00059B 

[Kernel-packages] [Bug 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread Daniel van Vugt
Please also try logging into a Xorg session. You can do that by
selecting 'Ubuntu on Xorg' on the login screen. If that option is not
available then it may be called just '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/1983815

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread Daniel van Vugt
That's showing the same crash. Did you remember to put "=0" on the end?

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread stkim
add MUTTER_DEBUG_ENABLE_ATOMIC_KMS to /etc/environment
after reboot, still monitor is not displayed.

[0.00] Linux version 5.15.0-43-generic (buildd@lcy02-amd64-076) (gcc 
(Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) 
#46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 (Ubuntu 5.15.0-43.46-generic 
5.15.39)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Hygon HygonGenuine
[0.00]   Centaur CentaurHauls
[0.00]   zhaoxin   Shanghai  
[0.00] x86/split lock detection: #AC: crashing the kernel on kernel 
split_locks and warning on user-space split_locks
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User 
registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:8
[0.00] x86/fpu: Enabled xstate features 0x207, context size is 840 
bytes, using 'compacted' format.
[0.00] signal: max sigframe size: 3632
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x8bb6efff] usable
[0.00] BIOS-e820: [mem 0x8bb6f000-0x90b2efff] reserved
[0.00] BIOS-e820: [mem 0x90b2f000-0x9172efff] ACPI NVS
[0.00] BIOS-e820: [mem 0x9172f000-0x917fefff] ACPI data
[0.00] BIOS-e820: [mem 0x917ff000-0x917f] usable
[0.00] BIOS-e820: [mem 0x9180-0x95ff] reserved
[0.00] BIOS-e820: [mem 0x97e0-0x97ff] reserved
[0.00] BIOS-e820: [mem 0x9880-0xa07f] reserved
[0.00] BIOS-e820: [mem 0xc000-0xcfff] reserved
[0.00] BIOS-e820: [mem 0xfed2-0xfed7] reserved
[0.00] BIOS-e820: [mem 0x0001-0x000c5f7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.70 by Lenovo
[0.00] efi: ACPI=0x917fe000 ACPI 2.0=0x917fe014 TPMFinalLog=0x9168e000 
SMBIOS=0x8d8af000 SMBIOS 3.0=0x8d8a2000 MEMATTR=0x8665c018 ESRT=0x86bae018 
MOKvar=0x8665f000 RNG=0x8da2e418 TPMEventLog=0x5de81018 
[0.00] efi: seeding entropy pool
[0.00] random: fast init done
[0.00] secureboot: Secure boot disabled
[0.00] SMBIOS 3.4.0 present.
[0.00] DMI: LENOVO 21BVCTO1WW/21BVCTO1WW, BIOS N3BET46W (1.24 ) 
06/07/2022
[0.00] tsc: Detected 2500.000 MHz processor
[0.00] tsc: Detected 2496.000 MHz TSC
[0.07] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.10] e820: remove [mem 0x000a-0x000f] usable
[0.17] last_pfn = 0xc5f800 max_arch_pfn = 0x4
[0.000322] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.002604] total RAM covered: 63936M
[0.002732] Found optimal setting for mtrr clean up
[0.002733]  gran_size: 64K  chunk_size: 128Mnum_reg: 7  lose 
cover RAM: 0G
[0.003463] e820: update [mem 0x9c00-0x] usable ==> reserved
[0.003471] last_pfn = 0x91800 max_arch_pfn = 0x4
[0.011626] esrt: Reserving ESRT space from 0x86bae018 to 
0x86bae2d0.
[0.011633] e820: update [mem 0x86bae000-0x86baefff] usable ==> reserved
[0.011645] e820: update [mem 0x8665f000-0x8665] usable ==> reserved
[0.011663] Using GB pages for direct mapping
[0.012047] secureboot: Secure boot disabled
[0.012048] RAMDISK: [mem 0x367e4000-0x3a35afff]
[0.012055] ACPI: Early table checksum verification disabled
[0.012060] ACPI: RSDP 0x917FE014 24 (v02 LENOVO)
[0.012066] ACPI: XSDT 0x917FC188 000144 (v01 LENOVO TP-N3B   
1240 PTEC 0002)
[0.012074] ACPI: FACP 0x8D891000 000114 (v06 LENOVO TP-N3B   
1240 PTEC 0002)
[0.012081] ACPI: DSDT 0x8D843000 0493FA (v02 LENOVO ICL  
0002  0113)
[0.012086] ACPI: FACS 0x91673000 40
[0.012090] ACPI: SSDT 0x8D94A000 00038C (v02 LENOVO Pmax_Dev 
0001 INTL 20200717)
[0.012094] ACPI: SSDT 0x8D932000 005D0B (v02 LENOVO CpuSsdt  
3000 INTL 20200717)
[0.012098] ACPI: SSDT 0x8D931000 00059B (v02 LENOVO CtdpB
1000 INTL 20200717)
[0.012102] ACPI: SSDT 0x8D8C2000 003203 (v02 LENOVO DptfTabl 
1000 

[Kernel-packages] [Bug 1983815] Re: no detection of the hdmi display moinitor

2022-08-08 Thread Daniel van Vugt
Thanks for the bug report. This may be caused by:

 * The Intel kernel graphics crash mentioned in CurrentDmesg.txt
 * An Nvidia driver problem (if the HDMI port is wired to the Nvidia GPU)
 * Something else

Firstly, to see if we can stop the Intel graphics crash from happening
please try adding this to /etc/environment:

  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

and then reboot.


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

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

** Tags added: hyb i915 nvidia rid

** Tags removed: hyb rid
** Tags added: hybrid

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

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: New => Incomplete

** Tags added: multimonitor

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

Title:
  no detection of the hdmi display moinitor

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Incomplete

Bug description:
  In the windows, hdmi display monitor work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  8 16:27:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e9]
 Subsystem: Lenovo Device [17aa:22e9]
  InstallationDate: Installed on 2022-08-07 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 21BVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3BET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983815/+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 1983815] [NEW] no detection of the hdmi display moinitor

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

In the windows, hdmi display monitor work.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..03.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 14:00:58 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  8 16:27:14 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:22e9]
   Subsystem: Lenovo Device [17aa:22e9]
InstallationDate: Installed on 2022-08-07 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: LENOVO 21BVCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=240545ce-be3b-4291-87da-1fe7a719dca4 ro text
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2022
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: N3BET46W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21BVCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.12
dmi.modalias: 
dmi:bvnLENOVO:bvrN3BET46W(1.24):bd06/07/2022:br1.24:efr1.12:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrSDK0T76530WIN: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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu
-- 
no detection of the hdmi display moinitor
https://bugs.launchpad.net/bugs/1983815
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 1978530] Re: [8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless card

2022-08-08 Thread You-Sheng Yang
Mark WONTFIX per
https://bugs.launchpad.net/somerville/+bug/1964897/comments/21.

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Incomplete => Won't Fix

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: Incomplete => Won't Fix

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: Incomplete => Won't Fix

** Changed in: hwe-next
   Status: New => Won't Fix

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  [8086:7af0][8086:40c4] Missing support for Intel AX204 NGW wireless
  card

Status in HWE Next:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Won't Fix
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Kinetic:
  Won't Fix
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  The Intel AX204 NGW wireless card was enabled by:
  * WiFi:
- commit ac4790dcd0ff ("iwlwifi: pcie: add support for MS devices"):
  * 
https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220129105618.a82ca9207ace.I38aa0acfb7846b179027b6f87f5f88f8e4177f63@changeid/
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac4790dcd0ffede2085a54ab12a4b70a48789215
  * Bluetooth:
- commit 2ca57c809926 ("Bluetooth: btusb: Add support for Intel Madison 
Peak (MsP2) device")
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2ca57c8099268001f41aa158cac92838daed323e

  The wifi/bluetooth firmware is not yet available.

  However, while the prereleased firmware has FW API 73, and v5.17 has
  FW API 69, v5.18/5.19 have 72, we'll have the same problem as bug
  1969434 tried to solve, and linux-modules-iwlwifi shall be used if
  back porting iwlwifi FW API continues to be unrealistic and/or
  unstable.

  We have verified current backport-iwlwifi-dkms based on upstream
  revision 9858 has FW API 73 and is able to load prereleased
  wifi/bluetooth firmware. So the pending work might fall on linux-
  firmware only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1978530/+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