[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera

2022-11-08 Thread You-Sheng Yang
linux-firmware SRU V3:
* https://lists.ubuntu.com/archives/kernel-team/2022-November/134531.html 
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2022-November/134532.html 
(kinetic)
* https://lists.ubuntu.com/archives/kernel-team/2022-November/134533.html 
(lunar)

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

Title:
  Support Intel IPU6 MIPI camera

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Incomplete
Status in linux-firmware source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Incomplete
Status in linux-firmware source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justfication:linux-firmware]

  [Impact]

  Need new firmware updates for additional camera senesors.

  [Fix]

  Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for
  hi556/ovti02c1.

  [Test Case]

  The driver will prompt for missed firmware blobs for a given platform.

  [Where problems could occur]

  There is still no suspend support for the camera driver, and user sessions
  across system suspend have to be restarted.

  [Other Info]

  New sensors are introduced in Jammy oem kernels only, and kinetic is nominated
  for future hwe migration.

  = original bug report ==

  This is a follow-up for bug 1964983 but on different platforms that
  runs linux-oem-5.17 or newer.

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


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


[Kernel-packages] [Bug 1993223] Re: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04

2022-11-08 Thread You-Sheng Yang
SRU V2: https://lists.ubuntu.com/archives/kernel-
team/2022-November/134530.html (jammy)

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

Title:
  MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs
  firmware to be loaded by amdgpu.

  [Fix]

  5 commits from mainline firmware repository.

  [Test Case]

  Kernel dmesg should no longer dump:

amdgpu_vcn: Can't load firmware amdgpu/vcn_3_1_2.bin

  [Where problems could occur]

  New hardware support. May affect system stability.

  [Other Info]

  These firmware blobs are only referenced in linux/kinetic and linux-
  oem-6.0/jammy, and are already available in linux-firmware/kinetic, so
  only Jammy is nominated for fix here.

  == original bug report ==

  Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs
  firmware to be loaded by amdgpu.

  This firmware has been upstreamed by these commits, which are already
  part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1)

  db6db36a amdgpu: add firmware for VCN 3.1.2 IP block
  3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block
  639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block
  76589464 amdgpu: add firmware for GC 10.3.6 IP block
  427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block

  Matching kernel code for this processor is already upstreamed in 6.0
  kernel, and so this should work with OEM-6.0.

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


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


[Kernel-packages] [Bug 1990851] Re: Unable to boot 5.19.0-18 with modeset

2022-11-08 Thread Xavier Hsinyuan
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704

** This bug has been marked a duplicate of bug 1991704
   Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

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

Title:
  Unable to boot 5.19.0-18 with modeset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to `linux-image-5.19.0-18-generic`, system seems freeze
  during the boot.

  Boot to earlier 5.19 kernel, looks fine.

  And 5.19.0-18 with `nomodeset` also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-18-generic 5.19.0-18.18
  ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7
  Uname: Linux 5.19.0-18-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2004 F pipewire
    gdm2008 F wireplumber
   /dev/snd/controlC0:  gdm2008 F wireplumber
  CasperMD5CheckResult: unknown
  Date: Mon Sep 26 21:25:44 2022
  MachineType: LENOVO 82TF
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-18-generic 
root=/dev/mapper/vgroot-lvroot ro recovery nomodeset dis_ucode_ldr
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-18-generic N/A
   linux-backports-modules-5.19.0-18-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-09-07 (19 days ago)
  dmi.bios.date: 06/16/2022
  dmi.bios.release: 1.39
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JYCN39WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y9000X IAH7
  dmi.ec.firmware.release: 1.39
  dmi.modalias: 
dmi:bvnLENOVO:bvrJYCN39WW:bd06/16/2022:br1.39:efr1.39:svnLENOVO:pn82TF:pvrLegionY9000XIAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrLegionY9000XIAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionY9000XIAH7:
  dmi.product.family: Legion Y9000X IAH7
  dmi.product.name: 82TF
  dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion Y9000X IAH7
  dmi.product.version: Legion Y9000X IAH7
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera

2022-11-08 Thread You-Sheng Yang
SRU V2:
* https://lists.ubuntu.com/archives/kernel-team/2022-November/134524.html 
(linux-firmware/jammy)
* https://lists.ubuntu.com/archives/kernel-team/2022-November/134525.html 
(linux-firmware/kinetic)
* https://lists.ubuntu.com/archives/kernel-team/2022-November/134526.html 
(linux-firmware/lunar)

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: Incomplete

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

** Also affects: linux-oem-5.17 (Ubuntu Lunar)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-oem-6.0 (Ubuntu Lunar)
   Importance: Undecided
   Status: Invalid

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

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

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

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

Title:
  Support Intel IPU6 MIPI camera

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Incomplete
Status in linux-firmware source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Incomplete
Status in linux-firmware source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justfication:linux-firmware]

  [Impact]

  Need new firmware updates for additional camera senesors.

  [Fix]

  Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for
  hi556/ovti02c1.

  [Test Case]

  The driver will prompt for missed firmware blobs for a given platform.

  [Where problems could occur]

  There is still no suspend support for the camera driver, and user sessions
  across system suspend have to be restarted.

  [Other Info]

  New sensors are introduced in Jammy oem kernels only, and kinetic is nominated
  for future hwe migration.

  = original bug report ==

  This is a follow-up for bug 1964983 but on different platforms that
  runs linux-oem-5.17 or newer.

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


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


[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

2022-11-08 Thread Chaim Eliyah
Flashed two LTS install drives today both with the same issue. 2xSATA
JMicron controllers (HWRAID), /dev/sda and /dev/sdb are taking turns
throwing buffer I/O errors ("Buffer I/O error on dev sdb, logical block
0, async page read") and the system never boots. Any idea when the fix
will be in main-line?

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

Title:
  UBSAN: array-index-out-of-bounds in
  /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Something wrong with ata driver in dmesg found:

  [1.980693] kernel: 

  [1.980699] kernel: fbcon: Taking over console
  [1.980703] kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
  [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
  [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 
5.15.0-25-generic #25-Ubuntu
  [1.980716] kernel: Hardware name: System manufacturer System Product 
Name/P5Q3, BIOS 110206/11/2010
  [1.980718] kernel: Call Trace:
  [1.980721] kernel:  
  [1.980723] kernel:  show_stack+0x52/0x58
  [1.980729] kernel:  dump_stack_lvl+0x4a/0x5f
  [1.980734] kernel:  dump_stack+0x10/0x12
  [1.980736] kernel:  ubsan_epilogue+0x9/0x45
  [1.980739] kernel:  __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [1.980742] kernel:  ahci_qc_issue+0x166/0x170 [libahci]
  [1.980748] kernel:  ata_qc_issue+0x135/0x240
  [1.980752] kernel:  ata_exec_internal_sg+0x2c4/0x580
  [1.980754] kernel:  ? vprintk_default+0x1d/0x20
  [1.980759] kernel:  ata_exec_internal+0x67/0xa0
  [1.980762] kernel:  sata_pmp_read+0x8d/0xc0
  [1.980765] kernel:  sata_pmp_read_gscr+0x3c/0x90
  [1.980768] kernel:  sata_pmp_attach+0x8b/0x310
  [1.980771] kernel:  ata_eh_revalidate_and_attach+0x28c/0x4b0
  [1.980775] kernel:  ata_eh_recover+0x6b6/0xb30
  [1.980778] kernel:  ? ahci_do_hardreset+0x180/0x180 [libahci]
  [1.980783] kernel:  ? ahci_stop_engine+0xb0/0xb0 [libahci]
  [1.980787] kernel:  ? ahci_do_softreset+0x290/0x290 [libahci]
  [1.980792] kernel:  ? 
trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0
  [1.980795] kernel:  sata_pmp_eh_recover.isra.0+0x214/0x560
  [1.980799] kernel:  sata_pmp_error_handler+0x23/0x40
  [1.980802] kernel:  ahci_error_handler+0x43/0x80 [libahci]
  [1.980806] kernel:  ata_scsi_port_error_handler+0x2b1/0x600
  [1.980810] kernel:  ata_scsi_error+0x9c/0xd0
  [1.980813] kernel:  scsi_error_handler+0xa1/0x180
  [1.980817] kernel:  ? scsi_unjam_host+0x1c0/0x1c0
  [1.980820] kernel:  kthread+0x12a/0x150
  [1.980823] kernel:  ? set_kthread_struct+0x50/0x50
  [1.980826] kernel:  ret_from_fork+0x22/0x30
  [1.980831] kernel:  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene16798 F pulseaudio
   /dev/snd/pcmC0D0p:   eugene16798 F...m pulseaudio
   /dev/snd/controlC1:  eugene16798 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Apr 24 05:13:34 2022
  HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
  InstallationDate: Installed on 2019-04-13 (1106 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  IwConfig:
   lono wireless extensions.

   enp2s0no wireless extensions.

   virbr0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic 
root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis 

[Kernel-packages] [Bug 1995957] Re: Add cs35l41 firmware loading support

2022-11-08 Thread Kai-Heng Feng
** Also affects: linux-oem-6.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => Won't Fix

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

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

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

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Kinetic)
   Importance: Undecided => Low

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Importance: Undecided => Low

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

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

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

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

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

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

Title:
  Add cs35l41 firmware loading support

Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Confirmed
Status in linux-oem-5.17 source package in Jammy:
  Confirmed
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-firmware source package in Kinetic:
  Confirmed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Speakers on some laptops are rather quiet even with max volume.

  [Fix]
  Loading firmware to make cs35l41 speaker amplifier really work.

  [Test]
  With the fix applied, the speaker has become really loud as intended.

  [Where problems could occur]
  Most commits are refactoring codes on both ASoC and HDA parts, so things
  can be missed.

  Other than that, the change is strictly limited to cs35l41, so the
  regression scope is rather narrow.

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


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


[Kernel-packages] [Bug 1995618] Re: It seems to not login automatically or get X session after installing Nvidia-driver

2022-11-08 Thread Kevin Yeh
Hi Alberto
Please find the log and console-log in our test job in the attachment.

** Attachment added: "截圖 2022-11-09 上午11.18.27.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5629770/+files/%E6%88%AA%E5%9C%96%202022-11-09%20%E4%B8%8A%E5%8D%8811.18.27.png

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-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/1995618/+subscriptions


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


[Kernel-packages] [Bug 1995618] Re: It seems to not login automatically or get X session after installing Nvidia-driver

2022-11-08 Thread Kevin Yeh
** Attachment added: "ubuntu-drivers.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5629769/+files/ubuntu-drivers.log

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-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/1995618/+subscriptions


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


[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

2022-11-08 Thread Kai-Chuan Hsieh
Test the kernel and firmware-sof in proposed on
QKN6C-DVT2-C2_202211-30786. The result is failed.


** Attachment added: "sof-snd-fail.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992714/+attachment/5629768/+files/sof-snd-fail.log

** Tags removed: verification-needed-jammy
** Tags added: verification-failed-jammy

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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


[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2022-11-08 Thread Drew R.
Understood.  I'd be super happy however if I could just get a manual
script to work at least, and then I could call it a day...anything to
just get any sound.  But I've had no luck with that method, it seems to
have no effect.  (Assuming we are talking about the TO912.sh script.  I
tried to go down the whole road of setting up QEMU to record my own
verbs, in case they're different, but couldn't get QEMU to compile.  I
have a windows partition, with latest drivers, and sound works in
windows.

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: 

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

2022-11-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 1995983

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


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

2022-11-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 1995982

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

2022-11-08 Thread Germán Poo-Caamaño
I would like to add one extra data point.

I was bitten by this issue using 22.10 (Kinetic), but with Linux
5.14-oem (the one shipped with Lenovo Thinkpad X1 Gen 10th, from 22.04).

From what I read, mutter 43.0 should have handled it nicely, but it did
not. Otherwise I would not have arrived here :-)

Upgrading to Linux 5.17.0-1003-oem did work, though.

FWIW, I had some crashes with vmlinuz-5.19.0-23 at boot time and later
on, so I tried the kernel that came with the laptop (5.14.0-1054-oem).

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

Title:
  Screen sometimes can't update [Failed to post KMS update: CRTC
  property (GAMMA_LUT) not found]

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in mutter source package in Jammy:
  Fix Released

Bug description:
  Screen can't turn back on by clicking keyboard after screen off by meta + l 
key.
  Try to do VT switch can make the screen back, some error poped when I try to 
wake up screen.

  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-03-31 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Tags: wayland-session jammy third-party-packages
  Uname: Linux 5.15.0-23-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

  ==

  SRU Justification

  [Impact]
  The backlight power won't come back after the meta + l to turn off the 
display on ADL machines.

  [Fix]
  Below series of commits from v5.17 fix this issue
  1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
  17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
  e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform

  [Test]
  Verified on at least 2 different machines, the backlight is on after the 
screen dimmed with touchpad movement or key stroke.

  [Where problems could occcur]
  The patches only affect ADL-P and up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions


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


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

2022-11-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 1995985

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1994059] Re: NVME down errors after kernel update

2022-11-08 Thread BloodyIron
I'm getting NVMe problems with my OS Samsung 970 EVO Pro after updating
my Linux kernel to "5.15.0-52"

This is seriously concerning as I thought my device was failing due to a
hard-lock-up and hard reset after it was saying mounted read-only and IO
errors one time, and other times just locking up for a minute or two
then coming back.

I've had to switch back to 5.15.0-50, and this is a BREAKING CHANGE.
This needs to be P1 as this kernel is unusable with NVMe devices as far
as I can tell.

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

Title:
  NVME down errors after kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the latest kernel update (from 5.15.0-50-generic to
  5.15.0-52-generic) some NVME errors show up in dmesg like

  nvme nvme0: controller is down; will reset: CSTS=0x PCI_STATUS=0x10
  nvme :01:00.0: enabling device ( -> 0002)
  nvme nvme0: Removing after probe failure status: -19
  nvme0n1: detected capacity change from 1000215216 to 0

  (Typed from a picture, could not send actual dmesg since the machine
  freezes shortly after losing the root filesystem and no new program
  can be loaded.)

  Tried some tricks like kernel parameters
  nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off, suggested in
  the Internet to solve similar problems. It only seems to delay the
  freeze average time from 20-30 min to 120-180 min but does not solve
  the issue.

  Going back to kernel 5.15.0-50 seems to have stabilized the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  epx1175 F pipewire-media-
epx1176 F pulseaudio
   /dev/snd/seq:epx1174 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 14:57:35 2022
  InstallationDate: Installed on 2022-10-17 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XDA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash mitigations=off 
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P17CFB.044.220223.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550XDA-KH3BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLB187A0D-C01-G001-S0001+10.0.22000
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP17CFB.044.220223.HQ:bd02/23/2022:br5.19:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XDA:pvrP17CFB:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XDA-KH3BR:rvrSGLB187A0D-C01-G001-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-TGL3-PCFB:
  dmi.product.family: Notebook Plus2
  dmi.product.name: 550XDA
  dmi.product.sku: SCAI-A5A5-A5A5-TGL3-PCFB
  dmi.product.version: P17CFB
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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


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

2022-11-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 1995984

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995982] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1994059] Re: NVME down errors after kernel update

2022-11-08 Thread BloodyIron
Like honestly this kernel should be removed from the repo of available
updates.

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

Title:
  NVME down errors after kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the latest kernel update (from 5.15.0-50-generic to
  5.15.0-52-generic) some NVME errors show up in dmesg like

  nvme nvme0: controller is down; will reset: CSTS=0x PCI_STATUS=0x10
  nvme :01:00.0: enabling device ( -> 0002)
  nvme nvme0: Removing after probe failure status: -19
  nvme0n1: detected capacity change from 1000215216 to 0

  (Typed from a picture, could not send actual dmesg since the machine
  freezes shortly after losing the root filesystem and no new program
  can be loaded.)

  Tried some tricks like kernel parameters
  nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off, suggested in
  the Internet to solve similar problems. It only seems to delay the
  freeze average time from 20-30 min to 120-180 min but does not solve
  the issue.

  Going back to kernel 5.15.0-50 seems to have stabilized the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  epx1175 F pipewire-media-
epx1176 F pulseaudio
   /dev/snd/seq:epx1174 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 14:57:35 2022
  InstallationDate: Installed on 2022-10-17 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XDA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash mitigations=off 
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P17CFB.044.220223.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550XDA-KH3BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLB187A0D-C01-G001-S0001+10.0.22000
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP17CFB.044.220223.HQ:bd02/23/2022:br5.19:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XDA:pvrP17CFB:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XDA-KH3BR:rvrSGLB187A0D-C01-G001-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-TGL3-PCFB:
  dmi.product.family: Notebook Plus2
  dmi.product.name: 550XDA
  dmi.product.sku: SCAI-A5A5-A5A5-TGL3-PCFB
  dmi.product.version: P17CFB
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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


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

2022-11-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 1995981

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


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

2022-11-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 1995978

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


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

2022-11-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 1995979

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


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

2022-11-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 1995980

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


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

2022-11-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 1995962

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

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

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

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

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

Title:
  22.10 slows down Thinkpad X270 i3-6100U

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Lenovo Thinkpad X270 with i3-6100U does 2490 MIPS (via "7zz b") on
  Ubuntu 22.10. The same notebook with Ubuntu 22.04.1 does 6836 MIPS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  8 16:24:42 2022
  InstallationDate: Installed on 2022-10-12 (27 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


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

2022-11-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 1995977

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

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

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

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

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995981] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995980] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995985] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995984] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995983] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995978] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks

2022-11-08 Thread Chris MacNaughton
** Also affects: linux-azure (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

Title:
  [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks

Status in linux-azure package in Ubuntu:
  Incomplete
Status in linux-azure source package in Kinetic:
  New

Bug description:
  SRU Justification

  [Impact]

  Hypervisor only allocates interrupts to happen on a single physical
  GPU, which can lead to CPU soft locks when using PCI NVME under heavy
  load.

  Kinetic will get this patch via stable updates.

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  Hypervisor PCI driver may not load correctly. Patch did not apply
  cleanly and could lead to merge conflicts once the upstream patch is
  pulled in.

  [Other Info]

  SF: #00346549

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


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


[Kernel-packages] [Bug 1995962] Re: 22.10 slows down Thinkpad X270 i3-6100U

2022-11-08 Thread Nick Rosbrook
** Changed in: linux (Ubuntu)
   Status: Invalid => 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/1995962

Title:
  22.10 slows down Thinkpad X270 i3-6100U

Status in linux package in Ubuntu:
  New

Bug description:
  My Lenovo Thinkpad X270 with i3-6100U does 2490 MIPS (via "7zz b") on
  Ubuntu 22.10. The same notebook with Ubuntu 22.04.1 does 6836 MIPS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  8 16:24:42 2022
  InstallationDate: Installed on 2022-10-12 (27 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1995977] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995979] [NEW] T14 Gen3 AMD low Mic volume

2022-11-08 Thread Ammar Sheikh
Public bug reported:

User Reported:

I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
beta. In every distribution I tried I have the same problem: The volume
of the mic is rather low.

Mic is set to 100% but it is still low. I can boost with pulseaudio but
it's not a big difference. I own another Lenovo laptop. If I set the mic
to 100% on this old laptop it's a difference like day and night to the
T14 Gen3.

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


** Tags: sutton

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

Title:
  T14 Gen3 AMD low Mic volume

Status in linux package in Ubuntu:
  New

Bug description:
  User Reported:

  I recently got a T14 Gen3 AMD. I tried Ubuntu 20.04.5 because it is
  certified with this laptop. I also tried Ubuntu 22.10 and Fedora 37
  beta. In every distribution I tried I have the same problem: The
  volume of the mic is rather low.

  Mic is set to 100% but it is still low. I can boost with pulseaudio
  but it's not a big difference. I own another Lenovo laptop. If I set
  the mic to 100% on this old laptop it's a difference like day and
  night to the T14 Gen3.

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


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


[Kernel-packages] [Bug 1995962] Re: 22.10 slows down Thinkpad X270 i3-6100U

2022-11-08 Thread Nick Rosbrook
** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Invalid => New

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

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

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

Title:
  22.10 slows down Thinkpad X270 i3-6100U

Status in linux package in Ubuntu:
  Invalid

Bug description:
  My Lenovo Thinkpad X270 with i3-6100U does 2490 MIPS (via "7zz b") on
  Ubuntu 22.10. The same notebook with Ubuntu 22.04.1 does 6836 MIPS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  8 16:24:42 2022
  InstallationDate: Installed on 2022-10-12 (27 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1995962] [NEW] 22.10 slows down Thinkpad X270 i3-6100U

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

My Lenovo Thinkpad X270 with i3-6100U does 2490 MIPS (via "7zz b") on
Ubuntu 22.10. The same notebook with Ubuntu 22.04.1 does 6836 MIPS.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: ubuntu-release-upgrader-core 1:22.10.8
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  8 16:24:42 2022
InstallationDate: Installed on 2022-10-12 (27 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade kinetic wayland-session
-- 
22.10 slows down Thinkpad X270 i3-6100U
https://bugs.launchpad.net/bugs/1995962
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 1995968] Re: kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y (2022-10-26)

2022-11-08 Thread Juerg Haefliger
** Description changed:

- 
  Upstream raspberrypi patchset 2022-10-26
  
-   Ported from the following raspberrypi branch:
- rpi-5.19.y
-   from https://github.com/raspberrypi/linux.git
+   Ported from the following raspberrypi branch:
+ rpi-5.19.y
+   from https://github.com/raspberrypi/linux.git
+ 
+ configs: Add FSIA6B driver module
+ ARM: dts: Add nvmem node for BCM2711 bootloader public key
+ configs: Add RTC_DRV_RV3032=m
+ overlays: i2c-rtc: Add RV3032 support
+ media: i2c: imx290: Correct min HBLANK.
+ nvmem: Use NVMEM_DEVID_AUTO
+ media: i2c: imx477: Do not unconditionally adjust hblank and vblank limits
+ media: i2c: imx477: Reset hblank on mode switch
+ vc04_services: bcm2835-codec: Allow encoder_cmd on ISP and deinterlace
+ vc04_services: bcm2835-codec:  Remove redundant role check
+ media: i2c: imx477: Allow dynamic horizontal blanking control
+ overlays: Add rpi-sense-v2
+ usb: xhci: account for num_trbs_free when invalidating TDs
+ ARM: dts: Add dtparams to disable PCIe, HDMI, and SD card/eMMC
+ Revert "Add PHY_ID_BCM54213PE identifier."
+ media: i2c: imx219: make HBLANK r/w to allow longer exposures
+ drm/vc4: hdmi: Reset link on hotplug
+ drm/vc4: hdmi: Move vc4_hdmi_supports_scrambling() around
+ drm/vc4: hdmi: Switch to detect_ctx
+ drm/vc4: hdmi: Simplify the hotplug handling
+ drm/vc4: hdmi: Remove mutex in detect
+ drm/vc4: hdmi: Remove unused argument in vc4_hdmi_supports_scrambling
+ drm/vc4: hdmi: Constify drm_display_mode

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

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

Title:
  kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y
  (2022-10-26)

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Kinetic:
  New

Bug description:
  Upstream raspberrypi patchset 2022-10-26

    Ported from the following raspberrypi branch:
  rpi-5.19.y
    from https://github.com/raspberrypi/linux.git

  configs: Add FSIA6B driver module
  ARM: dts: Add nvmem node for BCM2711 bootloader public key
  configs: Add RTC_DRV_RV3032=m
  overlays: i2c-rtc: Add RV3032 support
  media: i2c: imx290: Correct min HBLANK.
  nvmem: Use NVMEM_DEVID_AUTO
  media: i2c: imx477: Do not unconditionally adjust hblank and vblank limits
  media: i2c: imx477: Reset hblank on mode switch
  vc04_services: bcm2835-codec: Allow encoder_cmd on ISP and deinterlace
  vc04_services: bcm2835-codec:  Remove redundant role check
  media: i2c: imx477: Allow dynamic horizontal blanking control
  overlays: Add rpi-sense-v2
  usb: xhci: account for num_trbs_free when invalidating TDs
  ARM: dts: Add dtparams to disable PCIe, HDMI, and SD card/eMMC
  Revert "Add PHY_ID_BCM54213PE identifier."
  media: i2c: imx219: make HBLANK r/w to allow longer exposures
  drm/vc4: hdmi: Reset link on hotplug
  drm/vc4: hdmi: Move vc4_hdmi_supports_scrambling() around
  drm/vc4: hdmi: Switch to detect_ctx
  drm/vc4: hdmi: Simplify the hotplug handling
  drm/vc4: hdmi: Remove mutex in detect
  drm/vc4: hdmi: Remove unused argument in vc4_hdmi_supports_scrambling
  drm/vc4: hdmi: Constify drm_display_mode

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


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


[Kernel-packages] [Bug 1963767] Re: [Purism Librem 13 v4] Microphone not working after suspend

2022-11-08 Thread Nazar Mokrynskyi
I don't think bug title change is correct, this is confirmed to happen
on 3 distinct laptops already in this thread.

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

Title:
  [Purism Librem 13 v4] Microphone not working after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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


[Kernel-packages] [Bug 1995798] Re: MT7921K high latency when bluetooth headset is used

2022-11-08 Thread Daniel van Vugt
2.4GHz wifi networks can and will conflict with Bluetooth which shares
similar frequencies. Try using 5GHz for the wifi network if you can.

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

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

Title:
  MT7921K high latency when bluetooth headset is used

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

Bug description:
  When I use onboard WiFi and Bluetooth headset at the same time, the
  latency goes from ~30-50ms to 200-6500ms

  Motherboard: ASUS TUF GAMING X670E-PLUS WIFI
  BIOS: 0809

  Kernels tested: Ubuntu 22.10 downstream kernel (5.19) and upstream
  6.0.[135]

  $ lsb_release -rd
  Description:  Ubuntu 22.10
  Release:  22.10

  Also made upstream kernel bz:
  https://bugzilla.kernel.org/show_bug.cgi?id=216668

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: bluez 5.65-0ubuntu1
  Uname: Linux 6.0.5-060005-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 15:44:14 2022
  InstallationDate: Installed on 2022-10-15 (22 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.5-060005-generic 
root=/dev/mapper/vg_system-lv_root_ubuntu ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2022
  dmi.bios.release: 8.9
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0809
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X670E-PLUS WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0809:bd10/23/2022:br8.9:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 10:6F:D9:DD:4A:B0  ACL MTU: 1021:6  SCO MTU: 240:8
UP RUNNING PSCAN 
RX bytes:23811976 acl:17760 sco:359584 events:24845 errors:0
TX bytes:22808883 acl:832 sco:352705 commands:4782 errors:0

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


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


[Kernel-packages] [Bug 1995783] Re: Nightlight fails after suspend

2022-11-08 Thread Daniel van Vugt
** Tags added: hybrid i915 multigpu nvidia

** Tags added: gamma suspend-resume

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  Nightlight fails after suspend

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Nightlight activates when turned on in settings but after closing the
  lid or otherwise suspending and then resuming power nightlight fails
  to change the color temperature.  Settings still indicates that
  nightlight is on.  If nightlight setting is cycled nightlight works
  again until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.154  Wed Jun 22 04:50:54 
UTC 2022
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1)
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  5 22:03:14 2022
  DistUpgraded: 2022-10-29 22:31:31,858 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/390.154, 5.15.0-52-generic, x86_64: installed
   nvidia/390.154, 5.19.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:212b]
   NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:1247] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 635M [1043:212b]
  InstallationDate: Installed on 2019-01-15 (1390 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUSTeK Computer Inc. N55SL
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=47b67201-d4ee-44d7-adec-9d457d3c9b5c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (6 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SL.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SL
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN55SL.204:bd10/24/2012:br4.6:svnASUSTeKComputerInc.:pnN55SL:pvr1.0:rvnASUSTeKComputerInc.:rnN55SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
  dmi.product.family: N
  dmi.product.name: N55SL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/mutter/+bug/1995783/+subscriptions


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


[Kernel-packages] [Bug 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks

2022-11-08 Thread John Cabaj
** Changed in: linux-azure (Ubuntu)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

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

Title:
  [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks

Status in linux-azure package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification

  [Impact]

  Hypervisor only allocates interrupts to happen on a single physical
  GPU, which can lead to CPU soft locks when using PCI NVME under heavy
  load.

  Kinetic will get this patch via stable updates.

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  Hypervisor PCI driver may not load correctly. Patch did not apply
  cleanly and could lead to merge conflicts once the upstream patch is
  pulled in.

  [Other Info]

  SF: #00346549

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


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


[Kernel-packages] [Bug 1995779] Re: Strange issues with suspend, Nvidia proprietary and X11 graphics

2022-11-08 Thread Daniel van Vugt
Do you find any evidence of Xorg crashing? Either a file in /var/crash
or in the previous boot's log? You can collect the log after rebooting:

  journalctl -b-1 > prevboot.txt

and then please attach it here.


** Tags added: jammy

** Tags added: nvidia suspend-resume

** Changed in: nvidia-graphics-drivers-520 (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  Strange issues with suspend, Nvidia proprietary and X11 graphics

Status in nvidia-graphics-drivers-520 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu:
  22.04 jammy

  Computer:
  HP Pavilion All-in-One Desktop 27-ca1xxx
  So a desktop but with a hybrid GPU setup like a laptop.

  GPU:
  NVIDIA GeForce RTX 3050 Laptop GPU
  +
  Intel(R) Graphics (ADL-S GT1)

  GPU driver:
  This happens with all Nvidia proprietary drivers tested so far, 510, 515, 520.
  I reported it on the latest.

  Kernel:
  This happens with all kernels tested so far from 5.15 to 6.0

  Desktop:
  This only happens with an X11 session! If I switch to Wayland it doesn't 
happen.

  Problem:
  When you suspend the computer a number of strange things may happen. Lose 
connection to keyboard and mouse. Lose connection to USB-C Audio speakers. 
Stuck on black VT terminal screen. Sometimes reproduced on first try, sometimes 
it takes 5 tries.
  Switching to Wayland allows to suspend/resume perfectly however.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1995779/+subscriptions


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


[Kernel-packages] [Bug 1995886] Re: vmxnet3: update to latest ToT

2022-11-08 Thread Tim Gardner
Ronak,

I did provide the git repo URL in #7 for you to examine what sources
went into the test kernel.

A quick check of the Jammy repo indicates that all of the patches
mentioned in #5 are included.

rtg

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

Title:
  vmxnet3: update to latest ToT

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

Bug description:
  This request is to port vmxnet3 patches to Ubuntu kernel. Below are
  the commits in order:

  vmxnet3: prepare for version 7 changes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=55f0395fcace9e675af2cbb96015ce1ae8856806

  vmxnet3: add support for capability registers
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=6f91f4ba046e5de6a6e579620b32b8ecf56873f7

  vmxnet3: add support for large passthrough BAR register
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=543fb67405410cc548a72d7a9a4087688d2f56ac

  vmxnet3: add support for out of order rx completion
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=2c5a5748105a6bb901579d365c6f93e79f282b69

  vmxnet3: add command to set ring buffer sizes
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=c7112ebd27ea0dbe4eecd5c96cad93757e34e73d

  vmxnet3: limit number of TXDs used for TSO packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=d2857b99a74b082368ee80f359372faa1d051043

  vmxnet3: use ext1 field to indicate encapsulated packet
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=60cafa0395c2bed44d13277ed328317ed16a58c0

  vmxnet3: update to version 7
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=acc38e041bd304621d4f59cea4849747d13bba9c

  vmxnet3: disable overlay offloads if UPT device does not support
  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/vmxnet3?id=a56b158a5078b8120d3d72fc9fd44efed5123b12

  vmxnet3: do not reschedule napi for rx processing
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/vmxnet3?id=5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46

  This is a request to bring latest Ubuntu LTS releases' vmxnet3 driver
  up to date with ToT Linux kernel.

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


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


[Kernel-packages] [Bug 1995968] [NEW] kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y (2022-10-26)

2022-11-08 Thread Juerg Haefliger
Public bug reported:


Upstream raspberrypi patchset 2022-10-26

  Ported from the following raspberrypi branch:
rpi-5.19.y
  from https://github.com/raspberrypi/linux.git

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

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

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

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

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

Title:
  kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y
  (2022-10-26)

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Kinetic:
  New

Bug description:
  
  Upstream raspberrypi patchset 2022-10-26

Ported from the following raspberrypi branch:
  rpi-5.19.y
from https://github.com/raspberrypi/linux.git

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


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


[Kernel-packages] [Bug 1963767] Re: [Purism Librem 13 v4] Microphone not working after suspend

2022-11-08 Thread Daniel van Vugt
** Summary changed:

- Microphone not working after suspend
+ [Purism Librem 13 v4] Microphone not working after suspend

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

Title:
  [Purism Librem 13 v4] Microphone not working after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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


[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1

2022-11-08 Thread Chris Halse Rogers
Ok. So, sorry about all the back and forth. Partially this is because
I'm more familiar with thermald than others on the SRU team, and so
don't necessarily make things explicit that should be.

At a high level, what the SRU team (in general, so that *I* don't have
to be the single point of failure) is looking for is:

*) What is the scope of potential regressions - what hardware *could* this 
effect, what possible effects could it have
  - The answer to “what hardware” is: the list of CPUIDs in 
tdh_engine.cpp:id_table. This is SandyBridge onwards
  - The answer to “what effects” is: temperature throttling problems - either 
reduced performance of CPU (and GPU?) due to unnecessary throttling, or 
instability due to not controlling temperatures 

*) What is the scope of *upstream* support - what systems do *they* test on, 
and expect to continue to work.
  - Relatedly: what testing does upstream do
  - What do we do if upstream doesn't test on hardware that we support (ie: 
*we* care about all the hardware)

*) What is the process we are going to use to verify that upstream doesn't drop 
support for systems?
  - Upstream doesn't seem to make it very easy to identify this
  - eg: the current SRU includes dropping the MSR poking support. What process 
do we/will we have to catch such cases?

*) What is the process for testing that an upload does not regress
  - The [Test Case] above is good for systems with KBL or newer processors
  - thermald also supports systems from SandyBridge onwards - how are we 
testing these? These are still supported by Ubuntu; we need a testing system 
more than “maybe users will report regressions”, particularly since it's not 
necessarily going to be clear to users that “my system got slower” is related 
to the thermald update.

Most of those questions are covered above, I think, but some could do
with your input.

Particularly the SandyBridge+ question is an important one to answer.

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

Title:
  Upgrade thermald to 2.5.1

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Incomplete

Bug description:
  [Justification]
  The purpose of this bug is that prevent the regression in the future.
  The automatic test scripts are better for the future SRU and is still on the 
planning.

  [Test case]
  For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests 
will be run on machines in the CI lab:

  1. Run stress-ng, and observe the temperature/frequency/power with s-tui
    - Temperatures should stay just below trip values
    - Power/performance profiles should stay roughly the same between old 
thermald and new thermald (unless specifically expected eg: to fix 
premature/insufficient throttling)
  2. check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
    - this depends on if acpi_thermal_rel exist.
    - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
   could be landed in etc/thermald/.
    - if not, the user-defined xml could be created, then jump to (3).
    - run thermald with --loglevel=debug, and compare the log with xml.auto 
file. check if the configuration could be parsed correctly.
  3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
    - run thermald with --loglevel=debug, and compare the log with xml files.
    - if parsed correctly, the configurations from XML files would appear in 
the log.

  4. Run unit tests, the scripts are under test folder, using emul_temp to 
simulate the High temperatue and check thermald would throttle CPU through the 
related cooling device.
    - rapl.sh
    - intel_pstate.sh
    - powerclamp.sh
    - processor.sh
  5. check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
  6. check if system would be throttled even the temperature is under the 
trip-points.

  [ Where problems could occur ]
  since the PL1 min/max is introduced, we may face the edge case in the future.

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


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


[Kernel-packages] [Bug 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks

2022-11-08 Thread John Cabaj
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

Title:
  [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks

Status in linux-azure package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification

  [Impact]

  Hypervisor only allocates interrupts to happen on a single physical
  GPU, which can lead to CPU soft locks when using PCI NVME under heavy
  load.

  Kinetic will get this patch via stable updates.

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  Hypervisor PCI driver may not load correctly. Patch did not apply
  cleanly and could lead to merge conflicts once the upstream patch is
  pulled in.

  [Other Info]

  SF: #00346549

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


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


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

2022-11-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 1995957

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

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

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

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

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

Title:
  Add cs35l41 firmware loading support

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  New

Bug description:
  [Impact]
  Speakers on some laptops are rather quiet even with max volume.

  [Fix]
  Loading firmware to make cs35l41 speaker amplifier really work.

  [Test]
  With the fix applied, the speaker has become really loud as intended.

  [Where problems could occur]
  Most commits are refactoring codes on both ASoC and HDA parts, so things
  can be missed.

  Other than that, the change is strictly limited to cs35l41, so the
  regression scope is rather narrow.

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


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


[Kernel-packages] [Bug 1995957] [NEW] Add cs35l41 firmware loading support

2022-11-08 Thread Kai-Heng Feng
Public bug reported:

[Impact]
Speakers on some laptops are rather quiet even with max volume.

[Fix]
Loading firmware to make cs35l41 speaker amplifier really work.

[Test]
With the fix applied, the speaker has become really loud as intended.

[Where problems could occur]
Most commits are refactoring codes on both ASoC and HDA parts, so things
can be missed.

Other than that, the change is strictly limited to cs35l41, so the
regression scope is rather narrow.

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

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

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

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

Title:
  Add cs35l41 firmware loading support

Status in linux package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  New

Bug description:
  [Impact]
  Speakers on some laptops are rather quiet even with max volume.

  [Fix]
  Loading firmware to make cs35l41 speaker amplifier really work.

  [Test]
  With the fix applied, the speaker has become really loud as intended.

  [Where problems could occur]
  Most commits are refactoring codes on both ASoC and HDA parts, so things
  can be missed.

  Other than that, the change is strictly limited to cs35l41, so the
  regression scope is rather narrow.

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


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


[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault in Kinetic Kudu

2022-11-08 Thread Timo Aaltonen
** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

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

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

Title:
  amdgpu no-retry page fault in Kinetic Kudu

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 
154558
  Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin!
  Nov 03 16:35:55 laptop kernel: [drm] free PSP 

[Kernel-packages] [Bug 1995956] [NEW] amdgpu no-retry page fault in Kinetic Kudu

2022-11-08 Thread Kuba Pawlak
Public bug reported:

When using Skype in snap, amdgpu crashed, resulting in black screen and
unresponsive system.

Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
Affected laptop is T14 with Ryzen 5850U.

Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page starting 
at address 0x80010142c000 from IH client 0x12 (VMC)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page starting 
at address 0x80010142d000 from IH client 0x12 (VMC)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page starting 
at address 0x80010142c000 from IH client 0x12 (VMC)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page starting 
at address 0x80010142d000 from IH client 0x12 (VMC)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 
0x0
Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0


This happens in a loop and eventually leads to GPU reset, which fails.

Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
sdma0 timeout, signaled seq=211509, emitted seq=211512
Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 
154558
Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin!
Nov 03 16:35:55 laptop kernel: [drm] free PSP TMR buffer
Nov 03 16:35:55 laptop kernel: CPU: 15 PID: 141579 Comm: kworker/u32:1 Tainted: 
GW 5.19.0-23-generic #24-Ubuntu
Nov 03 16:35:55 laptop kernel: Hardware name: LENOVO 20XK002HPB/20XK002HPB, 
BIOS R1MET49W (1.19 ) 06/27/2022
Nov 03 16:35:55 laptop kernel: Workqueue: amdgpu-reset-dev 
drm_sched_job_timedout [gpu_sched]
Nov 03 16:35:55 laptop kernel: Call Trace:
Nov 03 16:35:55 laptop kernel:  
Nov 03 16:35:55 laptop kernel:  show_stack+0x4e/0x61
Nov 03 16:35:55 laptop kernel:  dump_stack_lvl+0x4a/0x6d
Nov 03 16:35:55 laptop kernel:  dump_stack+0x10/0x18
Nov 03 16:35:55 laptop kernel:  

[Kernel-packages] [Bug 1995004] Re: Increase stability with connection tracking offload

2022-11-08 Thread Stefan Bader
** Also affects: linux-bluefield (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-bluefield (Ubuntu Focal)
 Assignee: (unassigned) => Bodong Wang (bodong-wang)

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

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

Title:
  Increase stability with connection tracking offload

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

Bug description:
  * Explain the bug(s)

  Currently qdisc ingress handling (sch_handle_ingress()) doesn't
  set a return value and it is left to the old return value of
  the caller (__netif_receive_skb_core()) which is RX drop, so if
  the packet is consumed, caller will stop and return this value
  as if the packet was dropped.

  Also, include set of patches to increase stability with connection
  tracking offload, including reduced cpu load and possible deadlock on
  cleanup.

  * What it could break.

  Packet on egress tc rule forwarding to a ingress tc rule will drop.
  High cpu load. Possible deadlock on cleanup.

  * How to test

  Run connection tracking hw offload scenario with millions of flows,
  check cpu load, test cleanup and readd scenarios.

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


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


[Kernel-packages] [Bug 1995296] Re: mlx-bootctl: support icm carveout eeprom region read/write

2022-11-08 Thread Stefan Bader
** Also affects: linux-bluefield (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => Asmaa Mnebhi (asmaam)

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

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

Title:
  mlx-bootctl: support icm carveout eeprom region read/write

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  The BlueField-3 ICM carveout feature will enable NIC FW to bypass the SMMU 
block to access DRAM memory.
  The amount of memory accessible by FW will be controlled by ARM. This patch 
enables setting the size of the large ICM carveout from userspace. The max size 
is 1TB, has a granularity of 128MB and will be passed
  and printed in hex. The size unit is MB.

  [Fix]

  * Support SMC calls to control the large ICM carveout size.

  [Test Case]

  * Only valid testing on BlueField-3 real hardware.
  * set the region size from sysfs and NIC FW will test that it has access to 
the entire region requested.

  [Regression Potential]

  * This code doesn't really have a negative impact on the functionality of the 
mlxbf-bootctl driver itself but could be a risk for the overall boot if not 
used/tested properly.
  * memory region requested is too large, adn linux cannot boot as a result. 
The memory allocated for the ICM carveout cannot be accessed by linux.
  * the icmc size is not passed properly to NIC FW

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


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


[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855

2022-11-08 Thread Timo Aaltonen
** Changed in: linux-oem-5.17 (Ubuntu)
   Status: In Progress => Invalid

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: In Progress => Invalid

** Changed in: linux-oem-6.0 (Ubuntu)
   Status: In Progress => Invalid

** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: In Progress => Invalid

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

Title:
  Fix ath11k deadlock on WCN6855

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  ath11k is in deadlock when stress reboot or suspend on WCN6855.
  sometimes kernel hang.

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

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


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


[Kernel-packages] [Bug 1995580] Re: load of value 8 is not a valid value for type '_Bool'

2022-11-08 Thread Timo Aaltonen
I'm assuming you are using 22.10 and somehow installed oem-5.17 by hand.
It was supposed to be removed from the archive before release.

It won't get any updates in 22.10, so best to use the generic kernel
which is newer anyway

** Changed in: linux-oem-5.17 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  load of value 8 is not a valid value for type '_Bool'

Status in linux-oem-5.17 package in Ubuntu:
  Won't Fix

Bug description:
  Getting a call trace below with the 5.17.0-1003-oem OEM kernel.

  HW: Lenovo 21D4000HUS

  WNIC: 04:00.0 Network controller: Qualcomm QCNFA765 Wireless Network
  Adapter (rev 01)

  
  ~$ uname -r
  5.17.0-1003-oem

  ноя 03 10:22:47 dz16 kernel: wlp4s0: send auth to aa:46:8d:38:07:9d (try 1/3)
  ноя 03 10:22:47 dz16 kernel: 

  ноя 03 10:22:47 dz16 kernel: UBSAN: invalid-load in 
/build/linux-oem-5.17-vTcPy2/linux-oem-5.17-5.17.0/net/mac80211/status.c:1164:21
  ноя 03 10:22:47 dz16 kernel: load of value 8 is not a valid value for type 
'_Bool'
  ноя 03 10:22:47 dz16 kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 
5.17.0-1003-oem #3-Ubuntu
  ноя 03 10:22:47 dz16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, 
BIOS N3GET42W (1.22 ) 09/06/2022
  ноя 03 10:22:47 dz16 kernel: Call Trace:
  ноя 03 10:22:47 dz16 kernel:  
  ноя 03 10:22:47 dz16 kernel:  show_stack+0x52/0x58
  ноя 03 10:22:47 dz16 kernel:  dump_stack_lvl+0x4c/0x63
  ноя 03 10:22:47 dz16 kernel:  dump_stack+0x10/0x12
  ноя 03 10:22:47 dz16 kernel:  ubsan_epilogue+0x9/0x45
  ноя 03 10:22:47 dz16 kernel:  __ubsan_handle_load_invalid_value.cold+0x44/0x49
  ноя 03 10:22:47 dz16 kernel:  ieee80211_tx_status_ext.cold+0x4e/0x5f 
[mac80211]
  ноя 03 10:22:47 dz16 kernel:  ieee80211_tx_status+0x7d/0xa0 [mac80211]
  ноя 03 10:22:47 dz16 kernel:  ieee80211_tasklet_handler+0xa2/0xd0 [mac80211]
  ноя 03 10:22:47 dz16 kernel:  tasklet_action_common.constprop.0+0xc0/0xf0
  ноя 03 10:22:47 dz16 kernel:  tasklet_action+0x22/0x30
  ноя 03 10:22:47 dz16 kernel:  __do_softirq+0xd9/0x315
  ноя 03 10:22:47 dz16 kernel:  __irq_exit_rcu+0x87/0xb0
  ноя 03 10:22:47 dz16 kernel:  irq_exit_rcu+0xe/0x10
  ноя 03 10:22:47 dz16 kernel:  common_interrupt+0x8a/0xa0
  ноя 03 10:22:47 dz16 kernel:  
  ноя 03 10:22:47 dz16 kernel:  
  ноя 03 10:22:47 dz16 kernel:  asm_common_interrupt+0x1e/0x40
  ноя 03 10:22:47 dz16 kernel: RIP: 0010:cpuidle_enter_state+0xec/0x630
  ноя 03 10:22:47 dz16 kernel: Code: ff e8 a8 ee 6a ff 80 7d d0 00 74 17 9c 58 
0f 1f 44 00 00 f6 c4 02 0f 85 3c 03 00 00 31 ff e8 3b c4 72 ff fb 66 0f 1f 44 
00 00 <45> 85 f6 0f 88 73 01 00 00 4d 63 ee 49 8>
  ноя 03 10:22:47 dz16 kernel: RSP: 0018:a571001ffe28 EFLAGS: 0246
  ноя 03 10:22:47 dz16 kernel: RAX: 94e422071340 RBX: 94dddb0e8400 RCX: 
0005a1d2ec47
  ноя 03 10:22:47 dz16 kernel: RDX: 0005a20ff50b RSI: 0005a1d2ec47 RDI: 

  ноя 03 10:22:47 dz16 kernel: RBP: a571001ffe78 R08: 0005a1d2f24e R09: 
000aae60
  ноя 03 10:22:47 dz16 kernel: R10: 0004 R11: 071c71c71c71c71c R12: 
a60f6020
  ноя 03 10:22:47 dz16 kernel: R13: 0003 R14: 0003 R15: 
0005a1d2f24e
  ноя 03 10:22:47 dz16 kernel:  ? cpuidle_enter_state+0xc8/0x630
  ноя 03 10:22:47 dz16 kernel:  cpuidle_enter+0x2e/0x40
  ноя 03 10:22:47 dz16 kernel:  cpuidle_idle_call+0x13e/0x1d0
  ноя 03 10:22:47 dz16 kernel:  do_idle+0x83/0xf0
  ноя 03 10:22:47 dz16 kernel:  cpu_startup_entry+0x20/0x30
  ноя 03 10:22:47 dz16 kernel:  start_secondary+0x12a/0x180
  ноя 03 10:22:47 dz16 kernel:  secondary_startup_64_no_verify+0xd5/0xdb
  ноя 03 10:22:47 dz16 kernel:  
  ноя 03 10:22:47 dz16 kernel: 


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


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


[Kernel-packages] [Bug 1995148] Re: mlxbf_gige: need to add BlueField-3 support

2022-11-08 Thread Stefan Bader
** Also affects: linux-bluefield (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => David Thompson (dthompso-98)

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

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

Title:
  mlxbf_gige: need to add BlueField-3 support

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
  support the BlueField-3 SoC.  The "mlxbf_gige" driver which
  supports BlueField-2 SoC currently will be extended to include
  the BlueField-3 support.

  [Fix]
  The BlueField-3 support will be provided in the form of a set
  of 4 patches, to be sent in as a pull request. 

  [Test Case]
  BlueField-2: Boot platform and bring up "oob_net0" interface properly
   Test that network traffic works properly
  BlueField-3: Tested in simulator platforms and early silicon

  [Regression Potential]
  Since this is initial support there is chance of regression
  on BlueField-2 platforms, but it's been tested there.

  [Other]
  n/a

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


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


[Kernel-packages] [Bug 1930082] Re: systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F

2022-11-08 Thread Juerg Haefliger
Time to turn off ADT testing for raspi kernels since it adds no real
value.

** Changed in: linux-raspi (Ubuntu)
   Status: New => Won't Fix

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

Title:
  systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F

Status in linux-raspi package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-raspi/5.11.0-1009.10 on hirsute. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.

  Testing failed on Hirsute/raspi:
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/s/systemd/20210528_100011_6f6f0@/log.gz

  Testing failed on Groovy/raspi:
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/s/systemd/20210528_084522_9b779@/log.gz

  Testing failed on Focal/raspi:
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/s/systemd/20210528_092727_7c33b@/log.gz

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


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


[Kernel-packages] [Bug 1961076] Re: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1

2022-11-08 Thread Kleber Sacilotto de Souza
Found again with linux-meta-hwe-5.4/5.4.0.132.148~18.04.109 only with
ppc64el:

https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/ppc64el/l/linux-hwe-5.4/20221105_134608_3ac96@/log.gz

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

Title:
  linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-
  hwe-5.4/5.4.0-100.113~18.04.1

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in linux-hwe-5.4 source package in Bionic:
  New

Bug description:
  The 'dev-shm' stress-ng test is failing with bionic/linux-hwe-5.4
  5.4.0-100.113~18.04.1 on ADT, only on ppc64el.

  Testing failed on:
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux-hwe-5.4/20220216_115416_c1d6c@/log.gz

  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] stress-ng 0.13.11 
g48be8ff4ffc4
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] system: Linux autopkgtest 
5.4.0-100-generic #113~18.04.1-Ubuntu SMP Mon Feb 7 15:02:55 UTC 2022 ppc64le
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] RAM total: 7.9G, RAM free: 
3.3G, swap free: 1023.9M
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 processors online, 4 
processors configured
  11:35:08 DEBUG| [stdout] stress-ng: info:  [26897] setting to a 5 second run 
per stressor
  11:35:08 DEBUG| [stdout] stress-ng: info:  [26897] dispatching hogs: 4 dev-shm
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: using 
cache maximum level L1
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: shared 
cache buffer size: 32K
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] starting stressors
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: started 
[26899] (instance 0)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: started 
[26900] (instance 1)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: started 
[26901] (instance 2)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: started 
[26902] (instance 3)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 stressors started
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: 
assuming killed by OOM killer, restarting again (instance 0)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: 
assuming killed by OOM killer, restarting again (instance 3)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: 
assuming killed by OOM killer, restarting again (instance 2)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: 
assuming killed by OOM killer, restarting again (instance 1)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] 
(stress-ng-dev-shm) terminated on signal: 9 (Killed)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] 
(stress-ng-dev-shm) was killed by the OOM killer
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] terminated
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] 
(stress-ng-dev-shm) terminated on signal: 9 (Killed)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] 
(stress-ng-dev-shm) was possibly killed by the OOM killer
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] terminated
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: exited 
[26901] (instance 2)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26901] terminated
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] 
(stress-ng-dev-shm) terminated on signal: 9 (Killed)
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] 
(stress-ng-dev-shm) was killed by the OOM killer
  11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] terminated
  11:35:08 DEBUG| [stdout] stress-ng: info:  [26897] successful run completed 
in 5.06s
  11:35:08 DEBUG| [stdout] stress-ng: fail:  [26897] dev_shm instance 0 
corrupted bogo-ops counter, 14 vs 0
  11:35:08 DEBUG| [stdout] stress-ng: fail:  [26897] dev_shm instance 0 hash 
error in bogo-ops counter and run flag, 2146579844 vs 0
  11:35:08 DEBUG| [stdout] stress-ng: fail:  [26897] dev_shm instance 1 
corrupted bogo-ops counter, 13 vs 0
  11:35:08 DEBUG| [stdout] stress-ng: fail:  [26897] dev_shm instance 1 hash 
error in bogo-ops counter and run flag, 1093487894 vs 0
  11:35:08 DEBUG| [stdout] stress-ng: fail:  [26897] dev_shm instance 3 
corrupted bogo-ops counter, 13 vs 0
  11:35:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process
  11:35:08 DEBUG| [stdout] stress-ng: fail:  [26897] dev_shm instance 3 hash 
error in bogo-ops counter and run flag, 1093487894 vs 0
  11:35:08 DEBUG| [stdout] stress-ng: fail:  [26897] metrics-check: stressor 
metrics 

[Kernel-packages] [Bug 1995109] Re: bluefield-edac: Potentially overflowing expression

2022-11-08 Thread Stefan Bader
** Also affects: linux-bluefield (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux-bluefield (Ubuntu Focal)
 Assignee: (unassigned) => Shravan Kumar Ramani (sramani)

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

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

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => Shravan Kumar Ramani (sramani)

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

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

Title:
  bluefield-edac: Potentially overflowing expression

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

Bug description:
  SRU Justification:

  [Impact]
  Potential integer overflow in men_ctrl_idx detected by static tool analyser.

  [Fix]
  Declare as type u64 instead of type int

  [Test Case]
  NA since the variable is read from the ACPI table

  [Regression Potential]
  Can be considered minimal

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


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


[Kernel-packages] [Bug 1930082] Re: systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F

2022-11-08 Thread Juerg Haefliger
** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F

Status in linux-raspi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-raspi/5.11.0-1009.10 on hirsute. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.

  Testing failed on Hirsute/raspi:
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/s/systemd/20210528_100011_6f6f0@/log.gz

  Testing failed on Groovy/raspi:
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/s/systemd/20210528_084522_9b779@/log.gz

  Testing failed on Focal/raspi:
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/s/systemd/20210528_092727_7c33b@/log.gz

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


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


[Kernel-packages] [Bug 1995941] Re: [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

2022-11-08 Thread Frank Heimes
Hello Nico, thanks for raising this.

The fix/patch c3f0e5fd2d33 "KVM: s390: pv: don't present the ecall interrupt 
twice" got upstream accepted with kernel v6.0, so I assume that it not only 
needs to be applied to 20.04/5.4, but also to 22.04/5.15 and 22.10/5.19.
And I've noticed that it got nice and properly tagged for upstream stable:
Cc:  # 5.7
Fixes: da24a0cc58ed ("KVM: s390: protvirt: Instruction emulation")

And with that it got already picked up and is included in:
22.04 with Ubuntu-5.15.0-53.59 (currently in jammy-proposed)
22.10 with Ubuntu-5.19.0-16.16 means already incl. in the release kernel.

So the only Ubuntu release that is affected is 20.04/focal, so I've set
that as affected target series...

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

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

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

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Triaged

Bug description:
  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the 
 SIGP external call order is delivered twice to a VCPU even
 though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
 interpretation facility, without KVM's involvement. But, if the
 receiving CPU is in enabled wait, KVM needs to wake the
 receiving CPU such that the interrupt can be delivered. Hence,
 in this case, the SIGP external call order causes an
 interception. In response, KVM only needs to wake the receiving
 VCPU. Interrupt delivery is then handled by the SIGP
 interpretation facility. 

 KVM wrongfuly assumed it also needs to request injection for 
the
 external call interrupt after the respective intercept, causing
 the interrupt to be delivered twice: once through the SIGP
 interpretation facility and once through the interrupt 
injection
 control by KVM.
  Solution:  Add appropriate special handling for 108 external call
 intercepts.
  Reproduction:  0. Apply kvm-unit-test submitted upstream 
("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
call orders in enabled wait").
 1. Run the smp_PV kvm-unit-test:
  ./run_tests.sh smp_PV
 2. Check logs/smp_PV.log. If system is affected, the following
line can be found:
  ABORT: smp: psw wait: ecall: Unexpected external call \
   interrupt (code 0x1202): on cpu 1 at 0x11958
If the system is not affected, the line should look like
this:
  PASS: smp: psw wait: ecall: received

  Preventive:yes
  Author:Nico Boehr 
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1995941/+subscriptions


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


[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

2022-11-08 Thread Arun
Hi there,
Any update on the fix please?
Thanks!

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

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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


[Kernel-packages] [Bug 1995870] Re: BUG: scheduling while atomic: ip/1210/0x00000200 on xenial/hwe rumford

2022-11-08 Thread Luke Nowakowski-Krijger
** Also affects: linux-hwe (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

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

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

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

Title:
  BUG: scheduling while atomic: ip/1210/0x0200 on xenial/hwe rumford

Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe source package in Xenial:
  New

Bug description:
  There is a bug being triggered on a udelay within the tg3 driver with
  xenial/linux-hwe 4.15.0-197.208~16.04.1 on rumford.

  This has been observed in multiple cycles during boot-testing.

  [   27.437584] BUG: scheduling while atomic: ip/1210/0x0200
  [   27.468440] Modules linked in: nls_iso8859_1 intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm_intel hpilo kvm 
irqbypass intel_cstate shpchp ioatdma dca intel_rapl_perf ipmi_si ipmi_devintf 
lpc_ich ipmi_msghandler acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 
i2c_algo_bit ses crct10dif_pclmul enclosure crc32_pclmul ttm 
ghash_clmulni_intel drm_kms_helper mlx5_core pcbc syscopyarea aesni_intel mlxfw 
sysfillrect sysimgblt aes_x86_64 fb_sys_fops tg3 devlink crypto_simd hpsa nvme 
glue_helper ptp drm cryptd pps_core nvme_core scsi_transport_sas wmi
  [   27.468491] CPU: 1 PID: 1210 Comm: ip Not tainted 4.15.0-197-generic 
#208~16.04.1-Ubuntu
  [   27.468493] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 05/21/2018
  [   27.468494] Call Trace:
  [   27.468508]  dump_stack+0x6d/0x8b
  [   27.468515]  __schedule_bug+0x54/0x70
  [   27.468519]  __schedule+0x635/0x8b0
  [   27.468522]  schedule+0x36/0x80
  [   27.468527]  schedule_hrtimeout_range_clock+0xbc/0x1b0
  [   27.468532]  ? __hrtimer_init+0x90/0x90
  [   27.468536]  schedule_hrtimeout_range+0x13/0x20
  [   27.468539]  usleep_range+0x62/0x90
  [   27.468547]  tg3_ape_event_lock+0x36/0xa0 [tg3]
  [   27.468552]  tg3_ape_driver_state_change.part.69+0xc6/0x160 [tg3]
  [   27.468557]  tg3_start+0xebc/0x10b0 [tg3]
  [   27.468563]  tg3_open+0x130/0x280 [tg3]
  [   27.468568]  __dev_open+0xd7/0x150
  [   27.468572]  __dev_change_flags+0x186/0x1c0
  [   27.468575]  dev_change_flags+0x29/0x70
  [   27.468580]  do_setlink+0x355/0xd90
  [   27.468589]  ? nla_parse+0xa7/0x120
  [   27.468592]  rtnl_newlink+0x773/0x8f0
  [   27.468597]  ? do_anonymous_page+0x24b/0x430
  [   27.468605]  ? ns_capable_common+0x2b/0x50
  [   27.468608]  ? ns_capable+0x10/0x20
  [   27.468612]  rtnetlink_rcv_msg+0x205/0x290
  [   27.468615]  ? _cond_resched+0x1a/0x50
  [   27.468620]  ? __kmalloc_node_track_caller+0x201/0x2c0
  [   27.468623]  ? rtnl_calcit.isra.25+0x100/0x100
  [   27.468627]  netlink_rcv_skb+0xd9/0x110
  [   27.468630]  rtnetlink_rcv+0x15/0x20
  [   27.468633]  netlink_unicast+0x198/0x260
  [   27.468637]  netlink_sendmsg+0x2ea/0x410
  [   27.468640]  sock_sendmsg+0x3e/0x50
  [   27.468642]  ___sys_sendmsg+0x2e9/0x300
  [   27.468646]  ? lru_cache_add_active_or_unevictable+0x36/0xb0
  [   27.468649]  ? do_anonymous_page+0x24b/0x430
  [   27.468653]  ? __handle_mm_fault+0xae7/0xc80
  [   27.468657]  __sys_sendmsg+0x54/0x90
  [   27.468659]  ? __sys_sendmsg+0x54/0x90
  [   27.468662]  SyS_sendmsg+0x12/0x20
  [   27.468667]  do_syscall_64+0x73/0x130
  [   27.468670]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
  [   27.468673] RIP: 0033:0x7f285dd57590
  [   27.468675] RSP: 002b:7ffd4370bf38 EFLAGS: 0246 ORIG_RAX: 
002e
  [   27.468678] RAX: ffda RBX: 7ffd43714040 RCX: 
7f285dd57590
  [   27.468679] RDX:  RSI: 7ffd4370bf80 RDI: 
0003
  [   27.468681] RBP: 6364ddd8 R08: 0040 R09: 
0008
  [   27.468682] R10: 05e7 R11: 0246 R12: 
7ffd4370bf80
  [   27.468683] R13:  R14: 006573a0 R15: 
7ffd43714018
  [   27.468703] NOHZ: local_softirq_pending 282

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


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


[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

2022-11-08 Thread Andrea Righi
** Also affects: linux (Ubuntu Kinetic)
   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/1993818

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  New

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant kernel: [  281.052899]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Oct 21 20:41:38 tyrant kernel: [  281.052902]  ? __x64_sys_kcmp+0x1f/0x30
  Oct 21 20:41:38 tyrant kernel: [  281.052905]  ? do_syscall_64+0x67/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052908]  ? 
sysvec_apic_timer_interrupt+0x4b/0xd0
  Oct 21 20:41:38 tyrant kernel: [  281.052911]  
entry_SYSCALL_64_after_hwframe+0x63/0xcd
  Oct 21 20:41:38 tyrant kernel: [  281.052915] RIP: 0033:0x7f5540712d8f
  Oct 21 20:41:38 tyrant kernel: [  281.052919] Code: 00 48 89 44 24 18 31 c0 
48 8d 44 24 

[Kernel-packages] [Bug 1995941] Comment bridged from LTC Bugzilla

2022-11-08 Thread bugproxy
--- Comment From boris.m...@de.ibm.com 2022-11-08 05:32 EDT---
Fix is upstream available:
Upstream-ID: c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8
Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3f0e5fd2d33d80c5a5a8b5e5d2bab2841709cc8

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in linux package in Ubuntu:
  New

Bug description:
  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the 
 SIGP external call order is delivered twice to a VCPU even
 though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
 interpretation facility, without KVM's involvement. But, if the
 receiving CPU is in enabled wait, KVM needs to wake the
 receiving CPU such that the interrupt can be delivered. Hence,
 in this case, the SIGP external call order causes an
 interception. In response, KVM only needs to wake the receiving
 VCPU. Interrupt delivery is then handled by the SIGP
 interpretation facility. 

 KVM wrongfuly assumed it also needs to request injection for 
the
 external call interrupt after the respective intercept, causing
 the interrupt to be delivered twice: once through the SIGP
 interpretation facility and once through the interrupt 
injection
 control by KVM.
  Solution:  Add appropriate special handling for 108 external call
 intercepts.
  Reproduction:  0. Apply kvm-unit-test submitted upstream 
("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
call orders in enabled wait").
 1. Run the smp_PV kvm-unit-test:
  ./run_tests.sh smp_PV
 2. Check logs/smp_PV.log. If system is affected, the following
line can be found:
  ABORT: smp: psw wait: ecall: Unexpected external call \
   interrupt (code 0x1202): on cpu 1 at 0x11958
If the system is not affected, the line should look like
this:
  PASS: smp: psw wait: ecall: received

  Preventive:yes
  Author:Nico Boehr 
  Component: kernel

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


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


[Kernel-packages] [Bug 1995618] Re: It seems to not login automatically or get X session after installing Nvidia-driver

2022-11-08 Thread Alberto Milone
Hi Kevin, the 520-open driver does not support running a desktop
environment yet. Can you attach the output of the following command,
please?

ubuntu-drivers debug

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

Title:
  It seems to not login automatically or get X session after installing
  Nvidia-driver

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-520 package in Ubuntu:
  New

Bug description:
  During SRU testing, I found some machines kept failing to run switching 
graphic card test.
  According to the output from the test run, those machines seem to not login 
automatically or can't get X session somehow. 

  Now I can't check the status of machines directly, but my guessing is
  base on the output from our test case, it showed "Can't open display
  :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ".

  I met this issue on there different machine which I can get log from
  them so far, there are other machines have this issue but I can't get
  the log.

  Our testing always use ubuntu-driver install to install nvidia-driver.

  https://certification.canonical.com/hardware/202004-27810/
  https://certification.canonical.com/hardware/202004-27811/
  https://certification.canonical.com/hardware/201904-26941/

  Kernel version:5.15.0-53-generic
  Nvidia driver: nvidia-driver-520-open

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov  3 10:55:26 2022
  InstallationDate: Installed on 2020-08-03 (821 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-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/1995618/+subscriptions


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


[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

2022-11-08 Thread Chris Halse Rogers
Hello AceLan, or anyone else affected,

Accepted firmware-sof into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.1.1-1ubuntu1.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: firmware-sof (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-kinetic

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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


[Kernel-packages] [Bug 1995941] [NEW] [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

2022-11-08 Thread bugproxy
Public bug reported:

Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
Symptom:   In a secure execution guest, the external interrupt for the 
   SIGP external call order is delivered twice to a VCPU even
   though it was only sent once.
Problem:   Under PV, external call interrupts are delivered by the SIGP
   interpretation facility, without KVM's involvement. But, if the
   receiving CPU is in enabled wait, KVM needs to wake the
   receiving CPU such that the interrupt can be delivered. Hence,
   in this case, the SIGP external call order causes an
   interception. In response, KVM only needs to wake the receiving
   VCPU. Interrupt delivery is then handled by the SIGP
   interpretation facility. 

   KVM wrongfuly assumed it also needs to request injection for the
   external call interrupt after the respective intercept, causing
   the interrupt to be delivered twice: once through the SIGP
   interpretation facility and once through the interrupt injection
   control by KVM.
Solution:  Add appropriate special handling for 108 external call
   intercepts.
Reproduction:  0. Apply kvm-unit-test submitted upstream 
  ("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
  call orders in enabled wait").
   1. Run the smp_PV kvm-unit-test:
./run_tests.sh smp_PV
   2. Check logs/smp_PV.log. If system is affected, the following
  line can be found:
ABORT: smp: psw wait: ecall: Unexpected external call \
 interrupt (code 0x1202): on cpu 1 at 0x11958
  If the system is not affected, the line should look like
  this:
PASS: smp: psw wait: ecall: received

Preventive:yes
Author:Nico Boehr 
Component: kernel

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-199408 severity-medium 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-199408 severity-medium
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW
  wait

Status in linux package in Ubuntu:
  New

Bug description:
  Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
  Symptom:   In a secure execution guest, the external interrupt for the 
 SIGP external call order is delivered twice to a VCPU even
 though it was only sent once.
  Problem:   Under PV, external call interrupts are delivered by the SIGP
 interpretation facility, without KVM's involvement. But, if the
 receiving CPU is in enabled wait, KVM needs to wake the
 receiving CPU such that the interrupt can be delivered. Hence,
 in this case, the SIGP external call order causes an
 interception. In response, KVM only needs to wake the receiving
 VCPU. Interrupt delivery is then handled by the SIGP
 interpretation facility. 

 KVM wrongfuly assumed it also needs to request injection for 
the
 external call interrupt after the respective intercept, causing
 the interrupt to be delivered twice: once through the SIGP
 interpretation facility and once through the interrupt 
injection
 control by KVM.
  Solution:  Add appropriate special handling for 108 external call
 intercepts.
  Reproduction:  0. Apply kvm-unit-test submitted upstream 
("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
call orders in enabled wait").
 1. Run the smp_PV kvm-unit-test:
  ./run_tests.sh smp_PV
 2. Check logs/smp_PV.log. If system is affected, the following
line can be found:
  ABORT: smp: psw wait: ecall: Unexpected external call \
   interrupt (code 0x1202): on cpu 1 at 0x11958
If the system is not affected, the line should look like
this:
  PASS: smp: psw wait: ecall: received

  Preventive:yes
  Author:Nico Boehr 
  Component: kernel

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1995941] [NEW] [UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait

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

Description:   KVM: PV: ext call delivered twice when receiver in PSW wait
Symptom:   In a secure execution guest, the external interrupt for the 
   SIGP external call order is delivered twice to a VCPU even
   though it was only sent once.
Problem:   Under PV, external call interrupts are delivered by the SIGP
   interpretation facility, without KVM's involvement. But, if the
   receiving CPU is in enabled wait, KVM needs to wake the
   receiving CPU such that the interrupt can be delivered. Hence,
   in this case, the SIGP external call order causes an
   interception. In response, KVM only needs to wake the receiving
   VCPU. Interrupt delivery is then handled by the SIGP
   interpretation facility. 

   KVM wrongfuly assumed it also needs to request injection for the
   external call interrupt after the respective intercept, causing
   the interrupt to be delivered twice: once through the SIGP
   interpretation facility and once through the interrupt injection
   control by KVM.
Solution:  Add appropriate special handling for 108 external call
   intercepts.
Reproduction:  0. Apply kvm-unit-test submitted upstream 
  ("[kvm-unit-tests PATCH v1 0/4] s390x: add tests for SIGP
  call orders in enabled wait").
   1. Run the smp_PV kvm-unit-test:
./run_tests.sh smp_PV
   2. Check logs/smp_PV.log. If system is affected, the following
  line can be found:
ABORT: smp: psw wait: ecall: Unexpected external call \
 interrupt (code 0x1202): on cpu 1 at 0x11958
  If the system is not affected, the line should look like
  this:
PASS: smp: psw wait: ecall: received

Preventive:yes
Author:Nico Boehr 
Component: kernel

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-199408 severity-medium 
targetmilestone-inin---
-- 
[UBUNTU 20.04] KVM: PV: ext call delivered twice when receiver in PSW wait
https://bugs.launchpad.net/bugs/1995941
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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2022-11-08 Thread PowerKiKi
It's been a while. Since then I upgraded to Xubuntu 22.04 (not fresh
install), and I am running kernel 5.15.0, which is supposed to contains
my patch according to tags on
https://github.com/torvalds/linux/commit/8bcea6cb2cbc1f749e574954569323dec5e2920e.

So I expect the issue to be solved, but unfortunately it is still not
solved. I still use the manual script that runs a few hundreds `sudo
hda-verb ...` to enable sound on my speakers.

I am afraid I cannot offer much guidance, neither to Aurélien, nor to
Drew R. :-/

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F 

[Kernel-packages] [Bug 1982833] Re: Bump (kernel) '-mtune' to z16 / arch14 with 23.04

2022-11-08 Thread Matthias Klose
fixed in lunar for gcc-11 and gcc-12

** Also affects: gcc-11 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gcc-11 (Ubuntu)
   Status: New => Fix Released

** Changed in: gcc-12 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Bump (kernel) '-mtune' to z16 / arch14 with 23.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in gcc-12 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Consider to bump the kernel '-mtune' to z16 (equals arch14), starting
  with 23.04.

  Discuss with IBM Z team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982833/+subscriptions


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


[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

2022-11-08 Thread Chris Halse Rogers
Hello AceLan, or anyone else affected,

Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4 in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: firmware-sof (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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