[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

2022-11-29 Thread AceLan Kao
6.0.0-1008.8 has been verified by ODM with different platforms.

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

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

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

Status in HWE Next:
  New
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:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
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
Status in linux 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:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  The patch is not finalized, so submit SRU to OEM kernels only, and
  will submit to other series kernels once the patch is accepted by
  upstream.

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

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


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


[Kernel-packages] [Bug 1914774] Re: Some derivative kernel tools packages don't depend on linux-tools-common

2022-11-29 Thread Juerg Haefliger
** Also affects: linux-ibm-5.4 (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: linux-meta-hwe-5.4 (Ubuntu)

** No longer affects: linux-meta-hwe-5.4 (Ubuntu Bionic)

** Changed in: linux-ibm-5.4 (Ubuntu Bionic)
   Status: New => Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

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

** No longer affects: linux-hwe-5.4 (Ubuntu Focal)

** No longer affects: linux-hwe-5.4 (Ubuntu Jammy)

** No longer affects: linux-hwe-5.4 (Ubuntu Kinetic)

** No longer affects: linux-ibm-5.4 (Ubuntu Focal)

** No longer affects: linux-ibm-5.4 (Ubuntu Jammy)

** No longer affects: linux-ibm-5.4 (Ubuntu Kinetic)

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

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

Title:
  Some derivative kernel tools packages don't depend on linux-tools-
  common

Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux-ibm package in Ubuntu:
  Invalid
Status in linux-ibm-5.4 package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  New
Status in linux-ibm-5.4 source package in Bionic:
  Confirmed
Status in linux-ibm source package in Focal:
  New
Status in linux-ibm source package in Jammy:
  New
Status in linux-ibm source package in Kinetic:
  New

Bug description:
  [Impact]

  Installing the tools package for some kernels, like linux-tools-
  generic-hwe-18.04, does not install linux-tools-common because of a
  missing dependency. This results in missing /usr/bin/* wrapper scripts
  that call the version dependent binaries (like cpupower).

  [Test Case]

  Install like linux-tools-generic-hwe-18.04 on bionic and:
  $ cpupower
  cpupower: command not found

  
  [Fix]

  Add linux-tools-common as a dependency.

  
  [Regression Potential]

  The fix results in an additional package being installed. If something
  goes wrong this would manifest itself as a package installation error.

  
  [Original Description]

  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1997213] Re: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add

2022-11-29 Thread xiaochun Lee
Hi, Ubuntu
Is there any update?

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

Title:
  [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized  by "lsblk"
  after hot add

Status in linux package in Ubuntu:
  Confirmed

Bug description:
Description:
After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA 
disk to the Onboard AHCI controller in our system by plugging a SATA disk into 
the SATA slot, However, the OS can not recognize the added disks, both running 
command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these 
disks we added before, and there isn't any log show up in /var/log/syslog after 
adding this SATA disks.

Produce Steps:
 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic)
 2. Boot into OS
 3. Hot plug a SATA disk into SATA slot in the front bay
 4. wait and observe whether the disks are show up by command "lsblk"


Configuration:
Systems:Lenovo SR655, AMD GENOA platform
OS:ubuntu-22.04-live-server-amd64.iso

CPU:AMD EPYC 9654 96-Core Processor *1
Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12

storage:
  7MM Drive 0-1:7.68TB 7MM NVMe SSD(PN:MTFDKCB7T6TFR,FW:E2MU110)
  Drive 0:240GB SATA SSD  (PN:SSS7B07725 ,FW:MQ31)
  Drive 1-2:1.92TB NVMe SSD(PN:SSDPF2KX019T1O,FW:9CV10320)
  Drive 3-4:400GB NVMe SSD(PN:SSDPF21Q400GB,FW:L0310600)
  Drive 5-8:12.0TB SATA HDD(PN:01GV193,FW:LEGNK9R5)
  Drive 9:240GB SATA SSD(PN:SSS7B07725,FW:MQ31)
  Drive 10-11:960GB SATA SSD(PN:SSS7A43198,FW:MP33)


Expected results:
OS can recognize the SATA disks we hot added in.

Actual results:
OS cannot recognize SATA disks we hot added in. 


Additional info:
 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up 
the added disks as well.
 2. Other OS like RHEL9.0 can recognize this hot added disks.

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


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


[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

2022-11-29 Thread Jean-Max Reymond
The issue has been reproduced on fully patched versions of Ubuntu 22.04
as well.

nov. 30 06:42:04 sd-170774 tomcat9[395629]: java.io.IOException: Duplicate 
accept detected. This is a known OS bug. Please consider reporting that you are 
affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298
nov. 30 06:42:04 sd-170774 tomcat9[395629]: at 
org.apache.tomcat.util.net.NioEndpoint.serverSocketAccept(NioEndpoint.java:548)
nov. 30 06:42:04 sd-170774 tomcat9[395629]: at 
org.apache.tomcat.util.net.NioEndpoint.serverSocketAccept(NioEndpoint.java:78)
nov. 30 06:42:04 sd-170774 tomcat9[395629]: at 
org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:129)
nov. 30 06:42:04 sd-170774 tomcat9[395629]: at 
java.lang.Thread.run(Thread.java:750)

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

Title:
  accept returns duplicate endpoints under load

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

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

2022-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.7

---
linux-firmware (20220329.git681281e4-0ubuntu3.7) jammy; urgency=medium

  * Add support for Intel DG2 (LP: #1971712)
- i915: Add DMC v2.07 for DG2
- i915: Add GuC v70.4.1 for DG2
- i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P
  * MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 (LP: 
#1993223)
- amdgpu: add firmware for DCN 3.1.5 IP block
- amdgpu: add firmware for GC 10.3.6 IP block
- amdgpu: add firmware for PSP 13.0.5 IP block
- amdgpu: add firmware for SDMA 5.2.6 IP block
- amdgpu: add firmware for VCN 3.1.2 IP block
  * Support Intel IPU6 MIPI camera (LP: #1987595)
- SAUCE: intel-ipu6: update ipu6ep firmware
- SAUCE: intel-ivsc: support more sensors
- SAUCE: intel-ivsc: add more firmware
  * Realtek 8852c WiFi/BT firmware support (LP: #1995046)
- rtw89: 8852c: add new firmware v0.27.20.0 for RTL8852C
- rtw89: 8852c: update fw to v0.27.36.0
- rtw89: 8852c: update fw to v0.27.42.0
- rtw89: 8852c: update fw to v0.27.56.0
- rtw89: 8852c: update fw to v0.27.56.1
- rtl_bt: Add firmware and config files for RTL8852C
- rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33
- rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A
  * Add cs35l41 firmware loading support (LP: #1995957)
- linux-firmware: Add firmware for Cirrus CS35L41
- linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops

 -- Juerg Haefliger   Wed, 16 Nov 2022
15:59:19 +0100

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Released
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:
  Fix Released
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:
  Fix Committed
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:
  Fix Released
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-29 Thread Timo Aaltonen
** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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
Status in linux source package in Jammy:
  Fix Committed

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 Version
  dmi.modalias: 

[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.7

---
linux-firmware (20220329.git681281e4-0ubuntu3.7) jammy; urgency=medium

  * Add support for Intel DG2 (LP: #1971712)
- i915: Add DMC v2.07 for DG2
- i915: Add GuC v70.4.1 for DG2
- i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P
  * MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 (LP: 
#1993223)
- amdgpu: add firmware for DCN 3.1.5 IP block
- amdgpu: add firmware for GC 10.3.6 IP block
- amdgpu: add firmware for PSP 13.0.5 IP block
- amdgpu: add firmware for SDMA 5.2.6 IP block
- amdgpu: add firmware for VCN 3.1.2 IP block
  * Support Intel IPU6 MIPI camera (LP: #1987595)
- SAUCE: intel-ipu6: update ipu6ep firmware
- SAUCE: intel-ivsc: support more sensors
- SAUCE: intel-ivsc: add more firmware
  * Realtek 8852c WiFi/BT firmware support (LP: #1995046)
- rtw89: 8852c: add new firmware v0.27.20.0 for RTL8852C
- rtw89: 8852c: update fw to v0.27.36.0
- rtw89: 8852c: update fw to v0.27.42.0
- rtw89: 8852c: update fw to v0.27.56.0
- rtw89: 8852c: update fw to v0.27.56.1
- rtl_bt: Add firmware and config files for RTL8852C
- rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33
- rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A
  * Add cs35l41 firmware loading support (LP: #1995957)
- linux-firmware: Add firmware for Cirrus CS35L41
- linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops

 -- Juerg Haefliger   Wed, 16 Nov 2022
15:59:19 +0100

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Add support for Intel DG2

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

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


-- 
Mailing list: https://launchpad.net/~kernel-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] Update Released

2022-11-29 Thread Timo Aaltonen
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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:
  Fix Released
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:
  Fix Released
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:
  Fix Committed
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:
  Fix Released
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] Update Released

2022-11-29 Thread Timo Aaltonen
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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:
  Fix Released
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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)

2022-11-29 Thread Timo Aaltonen
** Tags added: verification-needed-jammy

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

Title:
   Fibocom WWAN FM350-GL suspend error (notebook not suspend)

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

Bug description:
  [SRU Justification]

  [Impact]

  Fibocom WWAN FM350-GL equipped platform fails to suspend.

  [Fix]

  Full t7xx driver is still under development and some of them have
  already accepted and merged in mainline kernel. The following commits
  are once in the mainline and are reverted in v6.0:

    d20ef656f994 net: wwan: t7xx: Add AP CLDMA
    007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
    140424d90165 net: wwan: t7xx: PCIe reset rescan
    87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and
     coredump collection

  The first patch implemented the other AP-CLDMA, and with that applied,
  platforms in question may suspend and resume normally as every bits are in 
position.

  However, while these patches had been reverted for another revision
  that is still being worked on by the hardware vendor, a minimum,
  sauced patch is created to work-around this first to meet project
  schedules, and will be reverted and superseded with a final, mainline
  landing revision.

  [Test Case]

  Trigger suspend and there should be no more suspend errors from t7xx:

    mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
    mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
    mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
    mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  [Where problems could occur]

  The t7xx driver is still incomplete and we're staging aforementioned 4
  patches in internal experimental kernels for development use.

  [Other Info]

  This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0
  are nominated for fix.

  == original bug report ==

  Hi,
  I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module 
mtk_t7xx . Power management for this modem is bad. When the notebook goes to 
sleep/suspend, kernel module mtk_t7xx return an error:

  mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
  mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110
  mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110
  mtk_t7xx :58:00.0: PM: failed to suspend async: error -110

  So power management failed to suspend:
  PM: Some devices failed to suspend, or early wake event detected

  And the notebook not suspend and wake up again.
  It must be this module, because if I remove the module first (modprobe -r), 
the laptop goes to sleep and wakes up normally.
  However, after reinserting the module, the modem no longer appears in the 
system.

  Expected state: sleep occurs when the device is put to sleep -
  including the modem. When you wake up, you will wake up, including
  activating the modem and logging into the operator's network.

  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  lspci -v:
  58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
  Subsystem: Device 1cf8:3500
  Flags: bus master, fast devsel, latency 0, IRQ 17
  Memory at 601e80 (64-bit, prefetchable) [size=32K]
  Memory at 5e80 (64-bit, non-prefetchable) [size=8M]
  Memory at 601e00 (64-bit, prefetchable) [size=8M]
  Capabilities: [80] Express Endpoint, MSI 00
  Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
  Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
  Capabilities: [f8] Power Management version 3
  Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 
Len=008 
  Capabilities: [108] Latency Tolerance Reporting
  Capabilities: [110] L1 PM Substates
  Capabilities: [200] Advanced Error Reporting
  Capabilities: [300] Secondary PCI Express
  Kernel driver in use: mtk_t7xx
  Kernel modules: mtk_t7xx

  lshw:
  *-generic
  description: Wireless controller
  product: MEDIATEK Corp.
  vendor: MEDIATEK Corp.
  physical id: 0
  bus info: pci@:58:00.0
  version: 01
  width: 64 

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

2022-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.7

---
linux-firmware (20220329.git681281e4-0ubuntu3.7) jammy; urgency=medium

  * Add support for Intel DG2 (LP: #1971712)
- i915: Add DMC v2.07 for DG2
- i915: Add GuC v70.4.1 for DG2
- i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P
  * MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 (LP: 
#1993223)
- amdgpu: add firmware for DCN 3.1.5 IP block
- amdgpu: add firmware for GC 10.3.6 IP block
- amdgpu: add firmware for PSP 13.0.5 IP block
- amdgpu: add firmware for SDMA 5.2.6 IP block
- amdgpu: add firmware for VCN 3.1.2 IP block
  * Support Intel IPU6 MIPI camera (LP: #1987595)
- SAUCE: intel-ipu6: update ipu6ep firmware
- SAUCE: intel-ivsc: support more sensors
- SAUCE: intel-ivsc: add more firmware
  * Realtek 8852c WiFi/BT firmware support (LP: #1995046)
- rtw89: 8852c: add new firmware v0.27.20.0 for RTL8852C
- rtw89: 8852c: update fw to v0.27.36.0
- rtw89: 8852c: update fw to v0.27.42.0
- rtw89: 8852c: update fw to v0.27.56.0
- rtw89: 8852c: update fw to v0.27.56.1
- rtl_bt: Add firmware and config files for RTL8852C
- rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33
- rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A
  * Add cs35l41 firmware loading support (LP: #1995957)
- linux-firmware: Add firmware for Cirrus CS35L41
- linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops

 -- Juerg Haefliger   Wed, 16 Nov 2022
15:59:19 +0100

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Released
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 1993240] Re: amd_sfh modprobe fails when no sensor reported from AMD MP2

2022-11-29 Thread Timo Aaltonen
** Tags added: verification-needed-jammy

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

Title:
  amd_sfh modprobe fails when no sensor reported from AMD MP2

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

Bug description:
  [SRU Justification]

  [Impact]

  Some AMD platforms might not have sensor reported from MP2 controller,
  and that fails device init.

  [Fix]

  Two commits targeting v6.1 release in mainline kernel.

  [Test Case]

  On such platforms, driver loading should be bailed out with:

$ sudo dmesg | grep amd_sfh1_1_hid_client_init
[ 1.204896] pcie_mp2_amd :62:00.7: amd_sfh1_1_hid_client_init failed

  [Where problems could occur]

  This skips driver loading against ineffective hardware only.

  [Other Info]

  While this targets oem-6.0 and above, and is already in mainline
  v6.1-rc1, only oem-6.0 is nominated for fix.

  == original bug report ==

  Fix amd_sfh to make each sensor with proper initialization & resource
  allocation during MP2 loaded.

  To be in v6.1

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=68266bdcceec10ea364e62c63732cd6fe5a256a8

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/drivers/hid/amd-sfh-
  hid?h=next-20221010=beb18bb22cd4fb88648bb2925d56f36131c1ac21

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


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


[Kernel-packages] [Bug 1993242] Re: Fix a race condition with AMD PMF and Thinkpad-ACPI

2022-11-29 Thread Timo Aaltonen
** Tags added: verification-needed-jammy

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

Title:
  Fix a race condition with AMD PMF and Thinkpad-ACPI

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Triaged
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Depending on module load order there is a possibility that the AMT mode
  selected initially by PMF will be incorrect if thinkpad_acpi has loaded
  first.

  [Fix]

  To avoid this issue adjust the initialization order in the PMF driver.
  Commit 22ee98cb696e ("platform/x86/amd/pmf: install notify handler after
  acpi init") takes the work, but it depends on two more commits that were
  tagged as fixes for commits landed in bug 1987670.

  [Test Case]

  1. blacklist both amd-pmf and thinkpad-acpi
  2. load thinkpad-acpi first
  3. Load amd-pmf with dynamic debugging enabled

  [Where problems could occur]

  The first two parts are trivial, and the third one may have to receive
  tests to find out if it has some other interference due to the load
  order.

  [Other Info]

  AMD PMF targets oem-6.0 or above and has included in v6.1-rc1.

  == original bug report ==

  Depending on module load order there is a possibility that the AMT
  mode selected initially by PMF will be incorrect if thinkpad_acpi has
  loaded first.

  To avoid this issue adjust the initialization order in the PMF driver.

  
https://github.com/torvalds/linux/commit/22ee98cb696e95b05a188756d479d382d93559ef

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


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


[Kernel-packages] [Bug 1995046] Update Released

2022-11-29 Thread Timo Aaltonen
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Realtek 8852c WiFi/BT firmware support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add
  both FW & config file to get it work with oem-6.0.

  WiFi: rtw8852c

rtw89_8852ce :02:00.0: enabling device ( -> 0003)
rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin 
failed with error -2
rtw89_8852ce :02:00.0: failed to request firmware
rtw89_8852ce :02:00.0: failed to wait firmware completion
rtw89_8852ce :02:00.0: failed to setup chip information
rtw89_8852ce: probe of :02:00.0 failed with error -22

  BT: rtl8852cu

Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin
Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found

  [Fix]

  rtw89/rtw8852c_fw.bin and rtl_bt/rtl8852cu_fw.bin are required. Kinetic
  has already 5 commits out of 8.

  [Test Case]

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

  [Where problems could occur]

  New device to be supported for Jammy oem-6.0. May cause system stability
  issues or power consumption performance.

  [Other Info]

  This device is supported since v5.19, so only Jammy (for oem-6.0) and
  Kinetic are nominated for fix.

  == original bug report ==

  Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to
  add both FW & config file to get it work with oem-6.0.

  WiFi: rtw8852c
  [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003)
  [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for 
rtw89/rtw8852c_fw.bin failed with error -2
  [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware
  [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion
  [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information
  [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5

  BT: rtl8852cu
  [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin
  [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not 
found

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90

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


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


[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device

2022-11-29 Thread Timo Aaltonen
** Tags added: verification-needed-jammy

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

Title:
  Add some ACPI device IDs for Intel HID device

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged
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:
  New
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  New
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]
  Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake

  [Fix]
  ACPI devices IDs are add the the related Intel HID devices on these platforms 
can work.

  [Test]
  Verified the Intel HID events can work such as power button for suspend and 
wake.
   
  [Where problems could occur]
  Add the ACPI device IDs for support Intel HID devices, so chance of problems 
should be low.

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


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


[Kernel-packages] [Bug 1995046] Re: Realtek 8852c WiFi/BT firmware support

2022-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.7

---
linux-firmware (20220329.git681281e4-0ubuntu3.7) jammy; urgency=medium

  * Add support for Intel DG2 (LP: #1971712)
- i915: Add DMC v2.07 for DG2
- i915: Add GuC v70.4.1 for DG2
- i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P
  * MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 (LP: 
#1993223)
- amdgpu: add firmware for DCN 3.1.5 IP block
- amdgpu: add firmware for GC 10.3.6 IP block
- amdgpu: add firmware for PSP 13.0.5 IP block
- amdgpu: add firmware for SDMA 5.2.6 IP block
- amdgpu: add firmware for VCN 3.1.2 IP block
  * Support Intel IPU6 MIPI camera (LP: #1987595)
- SAUCE: intel-ipu6: update ipu6ep firmware
- SAUCE: intel-ivsc: support more sensors
- SAUCE: intel-ivsc: add more firmware
  * Realtek 8852c WiFi/BT firmware support (LP: #1995046)
- rtw89: 8852c: add new firmware v0.27.20.0 for RTL8852C
- rtw89: 8852c: update fw to v0.27.36.0
- rtw89: 8852c: update fw to v0.27.42.0
- rtw89: 8852c: update fw to v0.27.56.0
- rtw89: 8852c: update fw to v0.27.56.1
- rtl_bt: Add firmware and config files for RTL8852C
- rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33
- rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A
  * Add cs35l41 firmware loading support (LP: #1995957)
- linux-firmware: Add firmware for Cirrus CS35L41
- linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops

 -- Juerg Haefliger   Wed, 16 Nov 2022
15:59:19 +0100

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Realtek 8852c WiFi/BT firmware support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add
  both FW & config file to get it work with oem-6.0.

  WiFi: rtw8852c

rtw89_8852ce :02:00.0: enabling device ( -> 0003)
rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin 
failed with error -2
rtw89_8852ce :02:00.0: failed to request firmware
rtw89_8852ce :02:00.0: failed to wait firmware completion
rtw89_8852ce :02:00.0: failed to setup chip information
rtw89_8852ce: probe of :02:00.0 failed with error -22

  BT: rtl8852cu

Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin
Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found

  [Fix]

  rtw89/rtw8852c_fw.bin and rtl_bt/rtl8852cu_fw.bin are required. Kinetic
  has already 5 commits out of 8.

  [Test Case]

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

  [Where problems could occur]

  New device to be supported for Jammy oem-6.0. May cause system stability
  issues or power consumption performance.

  [Other Info]

  This device is supported since v5.19, so only Jammy (for oem-6.0) and
  Kinetic are nominated for fix.

  == original bug report ==

  Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to
  add both FW & config file to get it work with oem-6.0.

  WiFi: rtw8852c
  [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003)
  [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for 
rtw89/rtw8852c_fw.bin failed with error -2
  [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware
  [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion
  [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information
  [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5

  BT: rtl8852cu
  [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin
  [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not 
found

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90

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


-- 
Mailing list: 

[Kernel-packages] [Bug 1995957] Update Released

2022-11-29 Thread Timo Aaltonen
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add cs35l41 firmware loading support

Status in HWE Next:
  New
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:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed
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/hwe-next/+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] Re: Add cs35l41 firmware loading support

2022-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.7

---
linux-firmware (20220329.git681281e4-0ubuntu3.7) jammy; urgency=medium

  * Add support for Intel DG2 (LP: #1971712)
- i915: Add DMC v2.07 for DG2
- i915: Add GuC v70.4.1 for DG2
- i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P
  * MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 (LP: 
#1993223)
- amdgpu: add firmware for DCN 3.1.5 IP block
- amdgpu: add firmware for GC 10.3.6 IP block
- amdgpu: add firmware for PSP 13.0.5 IP block
- amdgpu: add firmware for SDMA 5.2.6 IP block
- amdgpu: add firmware for VCN 3.1.2 IP block
  * Support Intel IPU6 MIPI camera (LP: #1987595)
- SAUCE: intel-ipu6: update ipu6ep firmware
- SAUCE: intel-ivsc: support more sensors
- SAUCE: intel-ivsc: add more firmware
  * Realtek 8852c WiFi/BT firmware support (LP: #1995046)
- rtw89: 8852c: add new firmware v0.27.20.0 for RTL8852C
- rtw89: 8852c: update fw to v0.27.36.0
- rtw89: 8852c: update fw to v0.27.42.0
- rtw89: 8852c: update fw to v0.27.56.0
- rtw89: 8852c: update fw to v0.27.56.1
- rtl_bt: Add firmware and config files for RTL8852C
- rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33
- rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A
  * Add cs35l41 firmware loading support (LP: #1995957)
- linux-firmware: Add firmware for Cirrus CS35L41
- linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops
- linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops

 -- Juerg Haefliger   Wed, 16 Nov 2022
15:59:19 +0100

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Add cs35l41 firmware loading support

Status in HWE Next:
  New
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:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Fix Committed
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/hwe-next/+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 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

2022-11-29 Thread Timo Aaltonen
** Tags added: verification-needed-jammy

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

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

Status in HWE Next:
  New
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:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
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
Status in linux 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:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  The patch is not finalized, so submit SRU to OEM kernels only, and
  will submit to other series kernels once the patch is accepted by
  upstream.

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

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


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


[Kernel-packages] [Bug 1995046] Re: Realtek 8852c WiFi/BT firmware support

2022-11-29 Thread Timo Aaltonen
** Tags added: verification-needed-kinetic

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

Title:
  Realtek 8852c WiFi/BT firmware support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add
  both FW & config file to get it work with oem-6.0.

  WiFi: rtw8852c

rtw89_8852ce :02:00.0: enabling device ( -> 0003)
rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin 
failed with error -2
rtw89_8852ce :02:00.0: failed to request firmware
rtw89_8852ce :02:00.0: failed to wait firmware completion
rtw89_8852ce :02:00.0: failed to setup chip information
rtw89_8852ce: probe of :02:00.0 failed with error -22

  BT: rtl8852cu

Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin
Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found

  [Fix]

  rtw89/rtw8852c_fw.bin and rtl_bt/rtl8852cu_fw.bin are required. Kinetic
  has already 5 commits out of 8.

  [Test Case]

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

  [Where problems could occur]

  New device to be supported for Jammy oem-6.0. May cause system stability
  issues or power consumption performance.

  [Other Info]

  This device is supported since v5.19, so only Jammy (for oem-6.0) and
  Kinetic are nominated for fix.

  == original bug report ==

  Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to
  add both FW & config file to get it work with oem-6.0.

  WiFi: rtw8852c
  [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003)
  [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for 
rtw89/rtw8852c_fw.bin failed with error -2
  [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware
  [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion
  [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information
  [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5

  BT: rtl8852cu
  [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin
  [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not 
found

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90

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


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


[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

2022-11-29 Thread Ketan Mukadam
Jeff, Let us know if you are hitting any further merge issues in
updating lpfc patches for Jammy. 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/1988711

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  [IMPACT/Justification]
  There are numerous bug fixes included in the more recent version of lpfc That 
Broadcom has asked to pull into Jammy and Kinetic to better support customers 
in the field who are using the GA kernel and cant or wont move to the HWE 
kernels.  These all are limited to the lpfc driver itself, no patches to core 
code are requested.

  [FIX]
  A few of these were already landed in Jammy, and all but 6 (ones landed in 
6.0 upstream) were already in Kinetic.

  b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
  71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
  b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into 
lpfc_sli_prep_abort_xri()
  ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved 
configuration
  ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
  2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF 
WQE
  0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in 
queuecommand after VMID
  35251b4d79db scsi: lpfc: Set PU field when providing D_ID in 
XMIT_ELS_RSP64_CX iocb
  f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with 
malformed user input
  4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in 
lpfc_nvme_cancel_iocb()
  1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
  2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for 
nvme_admin_async_event cmd completion
  ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for 
aborted NVMe cmds
  336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT 
topology
  b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is 
aborted
  6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after 
starget_to_rport()
  e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path 
refactoring
  24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path 
refactoring
  44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in 
lpfc_ct_reject_event()
  a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
  348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol 
independent
  ed913cf4a533 scsi: lpfc: Commonize VMID code location
  fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
  a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for 
NVMe I/O
  e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
  de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
  5099478e436f scsi: lpfc: Change VMID registration to be based on fabric 
parameters
  dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if 
lpfc_err_lost_link()
  4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in 
rscn_recovery_check()
  596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
  ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
  b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
  ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
  84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
  775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
  cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
  c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
  92bd903da12b scsi: lpfc: Fix additional reference counting in 
lpfc_bsg_rport_els()
  db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
  646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
  3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in 
lpfc_sli_prep_wqe()
  a346f28ad231 scsi: lpfc: Remove unneeded variable
  66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
  4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
  fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
  f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
  ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
  d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
  1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post 
RSCN completion
  6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in 
Fabric topology
  6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for 

[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

2022-11-29 Thread Ketan Mukadam
From: Ketan Mukadam  
Sent: Friday, November 18, 2022 10:13 AM
To: 'Jeffrey Lane' 
Subject: Ubuntu Jammy lpfc patche merges 
 
Jeff, 
 
The jammy/master-next has lot of cherry picked patches which has broken lpfc…. 
that is why it is challenging to merge patches…. Ideally all the Refactor 
patches should have been pulled together, but I see just 3 Refactor patches in 
master-next breaking the lpfc completely.  Many lpfc patches out of the lpfc 
patch-set attached in the bug 1988711, there are many duplicates already 
present in master-next…. 
 
So I was able to fix it by selectively merging patches…. I am attaching the 
list of 76 patches that you can try to merge (there could be minor merge 
conflicts that are easy to resolve).
 
There is also dependency on nvme-fc transport patches not pulled into kernel 
master-next. 
 
https://www.spinics.net/lists/linux-scsi/msg173218.html
 
Apart from these patches, the below 3 lpfc patches may have some other 
dependency, which I have not looked into….may depend on some kernel-wide 
patches. 
 
scsi-lpfc-Remove-failing-soft_wwn-support.patch
scsi-lpfc-Fix-attempted-FA-PWWN-usage-after-feature-.patch
scsi-lpfc-Remove-Menlo-Hornet-related-code.patch
 
Hope this helps!!
 
Thanks 
Ketan

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

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  [IMPACT/Justification]
  There are numerous bug fixes included in the more recent version of lpfc That 
Broadcom has asked to pull into Jammy and Kinetic to better support customers 
in the field who are using the GA kernel and cant or wont move to the HWE 
kernels.  These all are limited to the lpfc driver itself, no patches to core 
code are requested.

  [FIX]
  A few of these were already landed in Jammy, and all but 6 (ones landed in 
6.0 upstream) were already in Kinetic.

  b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
  71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
  b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into 
lpfc_sli_prep_abort_xri()
  ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved 
configuration
  ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
  2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF 
WQE
  0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in 
queuecommand after VMID
  35251b4d79db scsi: lpfc: Set PU field when providing D_ID in 
XMIT_ELS_RSP64_CX iocb
  f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with 
malformed user input
  4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in 
lpfc_nvme_cancel_iocb()
  1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
  2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for 
nvme_admin_async_event cmd completion
  ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for 
aborted NVMe cmds
  336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT 
topology
  b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is 
aborted
  6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after 
starget_to_rport()
  e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path 
refactoring
  24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path 
refactoring
  44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in 
lpfc_ct_reject_event()
  a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
  348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol 
independent
  ed913cf4a533 scsi: lpfc: Commonize VMID code location
  fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
  a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for 
NVMe I/O
  e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
  de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
  5099478e436f scsi: lpfc: Change VMID registration to be based on fabric 
parameters
  dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if 
lpfc_err_lost_link()
  4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in 
rscn_recovery_check()
  596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
  ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
  b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
  ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
  84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
  775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
  cc28fac16ab7 scsi: lpfc: Fix 

[Kernel-packages] [Bug 1958416] Re: b/linux-gcp-5.4: log_check WARNING on n2d-standard-64

2022-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-gcp/5.4.0-1096.105
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: kernel-spammed-focal-linux-gcp verification-needed-focal

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

Title:
  b/linux-gcp-5.4: log_check WARNING on n2d-standard-64

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Triaged
Status in linux-gcp source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Small SWIOTLB might cause DMA failures during High IO on GCP instances using 
SEV.

  [Test case]
  Boot n2d-standard-2 or n2d-standard-64 instances on GCP, issue a lot of IO, 
and look for DMA overflow or full swiotlb messages on dmesg.

  [Potential regression]
  Boot failures should not be discarded when SWIOTLB cannot be allocated.

  
  --

  
  ubuntu_boot log_check fails with: WARNING: CPU: 34 PID: 8648 at 
/build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 
report_addr+0x33/0x90

  From the serial console:

  [  137.928758] nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA 
mask  bus mask 0
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.928758] 
nvme :00:04.0: overflow 0x801f68b5f000+131072 of DMA mask 
 bus mask 0
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938685] 
[ cut here ]
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938691] 
WARNING: CPU: 34 PID: 8648 at 
/build/linux-gcp-5.4-zTWCml/linux-gcp-5.4-5.4.0/kernel/dma/direct.c:35 
report_addr+0x33/0x90
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938691] 
Modules linked in: ip6table_filter ip6_tables iptable_filter bpfilter 
nls_iso8859_1 input_leds pvpanic serio_raw mac_hid sch_fq_codel ib_iser rdma_cm 
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
crypto_simd cryptd glue_helper psmouse i2c_piix4 gve
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938712] 
CPU: 34 PID: 8648 Comm: apt-check Not tainted 5.4.0-1060-gcp #64~18.04.1-Ubuntu
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938712] 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 
01/01/2011
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938714] 
RIP: 0010:report_addr+0x33/0x90
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938716] 
Code: 48 83 ec 08 48 8b 87 30 02 00 00 48 89 75 f8 48 85 c0 74 26 4c 8b 00 b8 
fe ff ff ff 49 39 c0 76 0d 80 3d 47 67 b2 01 00 74 2e <0f> 0b c9 c3 48 83 bf 40 
02 00 00 00 75 e9 eb f0 80 3d 2f 67 b2 01
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938716] 
RSP: 0018:bd77cf99f4e0 EFLAGS: 00010282
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938718] 
RAX:  RBX: 9773f8b960b0 RCX: 
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938718] 
RDX:  RSI: 9753ff897448 RDI: 
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938719] 
RBP: bd77cf99f4e8 R08: 0305 R09: 0022
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938719] 
R10: 0016dfee R11: bd77cf99f218 R12: 0002
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938720] 
R13: 9753abfe9000 R14: 0001 R15: 0100
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938723] FS: 
 7f55bb523740() GS:9753ff88() knlGS:
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938723] CS: 
 0010 DS:  ES:  CR0: 80050033
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938724] 
CR2: 7f55b41d6000 CR3: 801f6be28000 CR4: 00340ee0
  Jan 19 12:54:30 b-lgcp-5-4-gcp-5-4-0-n2dstd64-boot kernel: [  137.938726] 

[Kernel-packages] [Bug 1998252] Re: Touchpad is being recognized as generic mouse

2022-11-29 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  Touchpad is being recognized as generic mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 22.04.1 yesterday in a Thinkpad E14 Gen 4 that came
  with windows 11. After having a problem with the wifi recognition,
  that I could actually fix, I had another problem. I was installing
  some apps (Telegram desktop and TexEditor) and then realized that the
  scrolling of the touchpad wasn't working. Now after consulting
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.
  and running cat /proc/bus/input/devices in the terminel, I found out
  that the Touchpad is being recognized as a Generic Mouse.

  Here some useful information:

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erg1061 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 21:24:50 2022
  InstallationDate: Installed on 2022-11-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21E30065GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=5beb974e-650d-4de8-a7d9-e44c9d3835ec ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2022
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1SET42W(1.13)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21E30065GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET42W(1.13):bd08/12/2022:br1.13:efr1.13:svnLENOVO:pn21E30065GE:pvrThinkPadE14Gen4:rvnLENOVO:rn21E30065GE:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E3_BU_Think_FM_ThinkPadE14Gen4:
  dmi.product.family: ThinkPad E14 Gen 4
  dmi.product.name: 21E30065GE
  dmi.product.sku: LENOVO_MT_21E3_BU_Think_FM_ThinkPad E14 Gen 4
  dmi.product.version: ThinkPad E14 Gen 4
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian

2022-11-29 Thread Dave Chiluk
@vorlon, I just found this ticket, and would like to report that my Intel AX211 
wifi card no longer connects via 6ghz with the linux-oem-22.04b.  It was 
working fine with the 5.15 kernel.  I suspect regulatory compliance to be the 
issue as all of the 6ghz channels show disabled when running
$ sudo iw phy0 channels.

They also are unlisted when running 
$ sudo iw reg get

I haven't figured out how to manually fix this yet.  I have tried adding
the missing iwlwifi-so-a0-gf-a0-72.ucode to /lib/firmware and it loads,
but this did not fix the issue as I expected.

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

Title:
  dependency on crda obsolete according to Debian

Status in crda package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in linux-lowlatency package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in crda source package in Jammy:
  New
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-lowlatency source package in Jammy:
  Fix Released
Status in linux-oracle source package in Jammy:
  Fix Released
Status in linux-raspi source package in Jammy:
  Fix Released
Status in crda package in Debian:
  Fix Released

Bug description:
  Debian has just removed the crda package from the archive, stating
  that it is obsolete with current kernels:

https://bugs.debian.org/1003903

  We need someone to determine if this is accurate for Ubuntu as well,
  and if so, update the kernel packaging to not depend on crda anymore
  so it can be removed.

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


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


[Kernel-packages] [Bug 1998266] Status changed to Confirmed

2022-11-29 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  LUKS not asking for password at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For the past couple of weeks I've been unable to boot properly with
  kernel 5.15.0-53.

  After the initial start screens, when LUKS is expected to appear, the
  monitor instead says "no signal" and goes to sleep. I've been able to
  unlock the drive with the recovery mode.

  When booting with kernel -52, LUKS asks for credentials as expected.

  I had had some other issues, so to rule out that those were causing
  this I reinstalled Kubuntu tonight. The issue still remains with -53,
  and LUKS works with the -43 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcus 1337 F pulseaudio
   /dev/snd/pcmC1D0p:   marcus 1337 F...m pulseaudio
   /dev/snd/controlC2:  marcus 1337 F pulseaudio
   /dev/snd/controlC0:  marcus 1337 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Nov 30 00:30:46 2022
  InstallationDate: Installed on 2022-11-29 (0 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   wg-mullvad  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4901
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-I GAMING
  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.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING: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: System manufacturer

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


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


[Kernel-packages] [Bug 1998266] [NEW] LUKS not asking for password at boot

2022-11-29 Thread 8437698
Public bug reported:

For the past couple of weeks I've been unable to boot properly with
kernel 5.15.0-53.

After the initial start screens, when LUKS is expected to appear, the
monitor instead says "no signal" and goes to sleep. I've been able to
unlock the drive with the recovery mode.

When booting with kernel -52, LUKS asks for credentials as expected.

I had had some other issues, so to rule out that those were causing this
I reinstalled Kubuntu tonight. The issue still remains with -53, and
LUKS works with the -43 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  marcus 1337 F pulseaudio
 /dev/snd/pcmC1D0p:   marcus 1337 F...m pulseaudio
 /dev/snd/controlC2:  marcus 1337 F pulseaudio
 /dev/snd/controlC0:  marcus 1337 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Nov 30 00:30:46 2022
InstallationDate: Installed on 2022-11-29 (0 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
IwConfig:
 lono wireless extensions.
 
 enp4s0no wireless extensions.
 
 wg-mullvad  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-43-generic N/A
 linux-backports-modules-5.15.0-43-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.6
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4901
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B450-I GAMING
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.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING: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: System manufacturer

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


** Tags: amd64 apport-bug jammy

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

Title:
  LUKS not asking for password at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  For the past couple of weeks I've been unable to boot properly with
  kernel 5.15.0-53.

  After the initial start screens, when LUKS is expected to appear, the
  monitor instead says "no signal" and goes to sleep. I've been able to
  unlock the drive with the recovery mode.

  When booting with kernel -52, LUKS asks for credentials as expected.

  I had had some other issues, so to rule out that those were causing
  this I reinstalled Kubuntu tonight. The issue still remains with -53,
  and LUKS works with the -43 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marcus 1337 F pulseaudio
   /dev/snd/pcmC1D0p:   marcus 1337 F...m pulseaudio
   /dev/snd/controlC2:  marcus 1337 F pulseaudio
   /dev/snd/controlC0:  marcus 1337 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Nov 30 00:30:46 2022
  InstallationDate: Installed on 2022-11-29 (0 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   wg-mullvad  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.15.0.57.55)

2022-11-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta (5.15.0.57.55) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.6 (amd64, s390x)
initramfs-tools/0.140ubuntu13 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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


[Kernel-packages] [Bug 1993609] Update Released

2022-11-29 Thread Brian Murray
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux-firmware: add sdio firmware for qca9377 wifi module

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

Bug description:
  This firmware is already in the linux-firmware of upstream and jammy

  [Impact]
  We have a UC20 project to enable the qca9377 sdio wifi on a imx6ull
  board, without this firmware the ath10k-sdio wifi driver will fail to
  initialize and the wifi can't work.

  [Fix]
  Backport 1 patch from upstream linux-firmware.

  [Test]
  Install the patched linux-firmware and boot the kernel on that board,
  the ath10k-sdio.ko could find and load the firmware successfully and
  the wifi function worked well.

  
  [Where problems could occur]
  The patch is from upstream and Jammy already has this patch, this patch
  just adds new files to existing firmware, the regression possibility is
  very low

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


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


[Kernel-packages] [Bug 1993609] Re: linux-firmware: add sdio firmware for qca9377 wifi module

2022-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware - 1.187.35

---
linux-firmware (1.187.35) focal; urgency=medium

  * linux-firmware: add sdio firmware for qca9377 wifi module (LP: #1993609)
- ath10k: add SDIO firmware for QCA9377 WiFi

 -- Juerg Haefliger   Wed, 16 Nov 2022
14:39:03 +0100

** Changed in: linux-firmware (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  linux-firmware: add sdio firmware for qca9377 wifi module

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

Bug description:
  This firmware is already in the linux-firmware of upstream and jammy

  [Impact]
  We have a UC20 project to enable the qca9377 sdio wifi on a imx6ull
  board, without this firmware the ath10k-sdio wifi driver will fail to
  initialize and the wifi can't work.

  [Fix]
  Backport 1 patch from upstream linux-firmware.

  [Test]
  Install the patched linux-firmware and boot the kernel on that board,
  the ath10k-sdio.ko could find and load the firmware successfully and
  the wifi function worked well.

  
  [Where problems could occur]
  The patch is from upstream and Jammy already has this patch, this patch
  just adds new files to existing firmware, the regression possibility is
  very low

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


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


[Kernel-packages] [Bug 1998252] Status changed to Confirmed

2022-11-29 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Touchpad is being recognized as generic mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 22.04.1 yesterday in a Thinkpad E14 Gen 4 that came
  with windows 11. After having a problem with the wifi recognition,
  that I could actually fix, I had another problem. I was installing
  some apps (Telegram desktop and TexEditor) and then realized that the
  scrolling of the touchpad wasn't working. Now after consulting
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.
  and running cat /proc/bus/input/devices in the terminel, I found out
  that the Touchpad is being recognized as a Generic Mouse.

  Here some useful information:

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erg1061 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 21:24:50 2022
  InstallationDate: Installed on 2022-11-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21E30065GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=5beb974e-650d-4de8-a7d9-e44c9d3835ec ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2022
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1SET42W(1.13)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21E30065GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET42W(1.13):bd08/12/2022:br1.13:efr1.13:svnLENOVO:pn21E30065GE:pvrThinkPadE14Gen4:rvnLENOVO:rn21E30065GE:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E3_BU_Think_FM_ThinkPadE14Gen4:
  dmi.product.family: ThinkPad E14 Gen 4
  dmi.product.name: 21E30065GE
  dmi.product.sku: LENOVO_MT_21E3_BU_Think_FM_ThinkPad E14 Gen 4
  dmi.product.version: ThinkPad E14 Gen 4
  dmi.sys.vendor: LENOVO

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


-- 
Mailing list: https://launchpad.net/~kernel-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-29 Thread Tim Gardner
** Changed in: linux (Ubuntu Kinetic)
   Status: Fix Committed => In Progress

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in firmware-sof source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  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 1998252] [NEW] Touchpad is being recognized as generic mouse

2022-11-29 Thread Esteban Rivas-Grajales
Public bug reported:

I installed Ubuntu 22.04.1 yesterday in a Thinkpad E14 Gen 4 that came
with windows 11. After having a problem with the wifi recognition, that
I could actually fix, I had another problem. I was installing some apps
(Telegram desktop and TexEditor) and then realized that the scrolling of
the touchpad wasn't working. Now after consulting
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.
and running cat /proc/bus/input/devices in the terminel, I found out
that the Touchpad is being recognized as a Generic Mouse.

Here some useful information:

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  erg1061 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 29 21:24:50 2022
InstallationDate: Installed on 2022-11-29 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 21E30065GE
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=5beb974e-650d-4de8-a7d9-e44c9d3835ec ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-43-generic N/A
 linux-backports-modules-5.15.0-43-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2022
dmi.bios.release: 1.13
dmi.bios.vendor: LENOVO
dmi.bios.version: R1SET42W(1.13)
dmi.board.asset.tag: Not Available
dmi.board.name: 21E30065GE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias: 
dmi:bvnLENOVO:bvrR1SET42W(1.13):bd08/12/2022:br1.13:efr1.13:svnLENOVO:pn21E30065GE:pvrThinkPadE14Gen4:rvnLENOVO:rn21E30065GE:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E3_BU_Think_FM_ThinkPadE14Gen4:
dmi.product.family: ThinkPad E14 Gen 4
dmi.product.name: 21E30065GE
dmi.product.sku: LENOVO_MT_21E3_BU_Think_FM_ThinkPad E14 Gen 4
dmi.product.version: ThinkPad E14 Gen 4
dmi.sys.vendor: LENOVO

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


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

** Patch added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1998252/+attachment/5633204/+files/lspci-vnvn.log

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

Title:
  Touchpad is being recognized as generic mouse

Status in linux package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 22.04.1 yesterday in a Thinkpad E14 Gen 4 that came
  with windows 11. After having a problem with the wifi recognition,
  that I could actually fix, I had another problem. I was installing
  some apps (Telegram desktop and TexEditor) and then realized that the
  scrolling of the touchpad wasn't working. Now after consulting
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.
  and running cat /proc/bus/input/devices in the terminel, I found out
  that the Touchpad is being recognized as a Generic Mouse.

  Here some useful information:

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  erg1061 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 21:24:50 2022
  InstallationDate: Installed on 2022-11-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21E30065GE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic 
root=UUID=5beb974e-650d-4de8-a7d9-e44c9d3835ec ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2022
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 

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

2022-11-29 Thread Adrien Nader
Jeremy, there are duplicate firmware files. Replacing duplicates with
symlinks is probably the easiest and most efficient way to improve the
situation.

I get the following:

> % jdupes -mrS /lib/firmware
> Scanning: 2830 files, 286 items (in 1 specified)
> 405 duplicate files (in 212 sets), occupying 37 MB

With "jdupes -rl", "tar c /lib/firmware | zstd -1" drops from 428MB to
411MB. The effect on initrds is maybe slightly lower iirc but it's still
noticeable and it should be very easy and safe for us.

I can't tell exactly how many more people will be able to boot with that
change but I think the cost is small enough that it's worth trying.
Worst case, every kernel update is faster.

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

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

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

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

   * Some real cases from OEM projects:

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

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

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

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

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

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

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

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

  [Test Plan]

   * detailed instructions how to reproduce the bug:

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

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

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

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

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

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

  And then update-initramfs

   * After applying my patches, the issue is gone.

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

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

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

  All working well.

  [Where problems could occur]

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

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

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

[Kernel-packages] [Bug 1998248] [NEW] #define TASK_COMM_LEN 16 effects killall

2022-11-29 Thread K M
Public bug reported:

I think this define is meaning killall in
https://gitlab.com/psmisc/psmisc/-/issues/45 uses the wrong prcoess name
length

As referenced here
https://gitlab.com/psmisc/psmisc/-/blob/master/src/comm.h

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

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

Title:
  #define TASK_COMM_LEN 16 effects killall

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

Bug description:
  I think this define is meaning killall in
  https://gitlab.com/psmisc/psmisc/-/issues/45 uses the wrong prcoess
  name length

  As referenced here
  https://gitlab.com/psmisc/psmisc/-/blob/master/src/comm.h

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


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


[Kernel-packages] [Bug 1994987] Re: Azure: RMB Patch to backport on the Azure Linux Images

2022-11-29 Thread Tim Gardner
** Changed in: linux-azure (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Azure: RMB Patch to backport on the Azure Linux Images

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  MANA driver is not conforming to the HW specification in one small
  instance.

  This request from Azure LSG team to backport the rmb patch to be
  backported in all the azure images.
  (https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/ethernet/microsoft/mana?id=6fd2c68da55c552f86e401ebe40c4a619025ef69)

  Jammy and Kinetic will get this patch via stable updates.

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  At worst there might be a small performance impact.

  [Other Info]

  SF: #00346991

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


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


[Kernel-packages] [Bug 1914774] Re: Some derivative kernels don't depend on linux-tools-common

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

+ [Impact]
+ 
+ Installing the tools package for some kernels, like linux-tools-generic-
+ hwe-18.04, does not install linux-tools-common because of a missing
+ dependency. This results in missing /usr/bin/* wrapper scripts that call
+ the version dependent binaries (like cpupower).
+ 
+ [Test Case]
+ 
+ Install like linux-tools-generic-hwe-18.04 on bionic and:
+ $ cpupower
+ cpupower: command not found
+ 
+ 
+ [Fix]
+ 
+ Add linux-tools-common as a dependency.
+ 
+ 
+ [Regression Potential]
+ 
+ The fix results in an additional package being installed. If something
+ goes wrong this would manifest itself as a package installation error.
+ 
+ 
+ [Original Description]
+ 
  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

** Summary changed:

- Some derivative kernels don't depend on linux-tools-common
+ Some derivative kernel tools packages don't depend on linux-tools-common

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

Title:
  Some derivative kernel tools packages don't depend on linux-tools-
  common

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux-meta-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  Installing the tools package for some kernels, like linux-tools-
  generic-hwe-18.04, does not install linux-tools-common because of a
  missing dependency. This results in missing /usr/bin/* wrapper scripts
  that call the version dependent binaries (like cpupower).

  [Test Case]

  Install like linux-tools-generic-hwe-18.04 on bionic and:
  $ cpupower
  cpupower: command not found

  
  [Fix]

  Add linux-tools-common as a dependency.

  
  [Regression Potential]

  The fix results in an additional package being installed. If something
  goes wrong this would manifest itself as a package installation error.

  
  [Original Description]

  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

2022-11-29 Thread Juerg Haefliger
** Also affects: linux-meta-hwe-5.4 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Summary changed:

- HWE kernels do not ship linux-tools packages
+ Some derivative kernels don't depend on linux-tools-common

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

Title:
  Some derivative kernel tools packages don't depend on linux-tools-
  common

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux-meta-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  Installing the tools package for some kernels, like linux-tools-
  generic-hwe-18.04, does not install linux-tools-common because of a
  missing dependency. This results in missing /usr/bin/* wrapper scripts
  that call the version dependent binaries (like cpupower).

  [Test Case]

  Install like linux-tools-generic-hwe-18.04 on bionic and:
  $ cpupower
  cpupower: command not found

  
  [Fix]

  Add linux-tools-common as a dependency.

  
  [Regression Potential]

  The fix results in an additional package being installed. If something
  goes wrong this would manifest itself as a package installation error.

  
  [Original Description]

  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1998244] [NEW] kselftest net/fib_nexthop_nongw.sh fails

2022-11-29 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

18272   03:33:07 DEBUG| Persistent state client._record_indent now set 
to 2
18273   03:33:07 DEBUG| Persistent state 
client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh', 
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
18274   03:33:07 DEBUG| Waiting for pid 58525 for 2700 
seconds
18275   03:33:07 WARNI| System python is too old, crash 
handling disabled
18276   03:33:07 DEBUG| Running 'make run_tests -C net 
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
18277   03:33:07 DEBUG| [stdout] make: Entering 
directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18278   03:33:07 DEBUG| [stdout] make 
--no-builtin-rules ARCH=x86 -C ../../../.. headers_install
18279   03:33:07 DEBUG| [stdout] make[1]: Entering 
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18280   03:33:08 DEBUG| [stdout]   INSTALL ./usr/include
18281   03:33:08 DEBUG| [stdout] make[1]: Leaving 
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18282   03:33:08 DEBUG| [stdout] TAP version 13
18283   03:33:08 DEBUG| [stdout] 1..1
18284   03:33:08 DEBUG| [stdout] # selftests: net: 
fib_nexthop_nongw.sh
18285   03:33:08 DEBUG| [stdout] # Error: Unknown 
device type.
18286   03:33:08 DEBUG| [stdout] # Cannot find device 
"eth0"
18287   03:33:08 DEBUG| [stdout] # Cannot find device 
"eth0"
18288   03:33:08 DEBUG| [stdout] # TEST: nexthop: get 
route with nexthop without gw[ OK ]
18289   03:33:18 DEBUG| [stdout] # TEST: nexthop: ping 
through nexthop without gw  [FAIL]
18290   03:33:18 DEBUG| [stdout] not ok 1 selftests: 
net: fib_nexthop_nongw.sh # exit=1
18291   03:33:18 DEBUG| [stdout] make: Leaving 
directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'

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

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

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

** Summary changed:

- fib_nexthop_nongw.sh
+ kselftest net/fib_nexthop_nongw.sh fails

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

Title:
  kselftest net/fib_nexthop_nongw.sh fails

Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Jammy:
  New

Bug description:
  18272 03:33:07 DEBUG| Persistent state client._record_indent 
now set to 2
18273   03:33:07 DEBUG| Persistent state 
client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh', 
'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh')
18274   03:33:07 DEBUG| Waiting for pid 58525 for 2700 
seconds
18275   03:33:07 WARNI| System python is too old, crash 
handling disabled
18276   03:33:07 DEBUG| Running 'make run_tests -C net 
TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
18277   03:33:07 DEBUG| [stdout] make: Entering 
directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
18278   03:33:07 DEBUG| [stdout] make 
--no-builtin-rules ARCH=x86 -C ../../../.. headers_install
18279   03:33:07 DEBUG| [stdout] make[1]: Entering 
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18280   03:33:08 DEBUG| [stdout]   INSTALL ./usr/include
18281   03:33:08 DEBUG| [stdout] make[1]: Leaving 
directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18282   03:33:08 DEBUG| [stdout] TAP version 13
18283   03:33:08 DEBUG| [stdout] 1..1
18284   03:33:08 DEBUG| [stdout] # selftests: net: 
fib_nexthop_nongw.sh
18285   03:33:08 DEBUG| [stdout] # Error: Unknown 
device type.
18286   03:33:08 DEBUG| [stdout] # Cannot find device 
"eth0"
18287   03:33:08 DEBUG| [stdout] # Cannot find device 
"eth0"
18288   03:33:08 DEBUG| [stdout] # TEST: nexthop: get 
route with 

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

2022-11-29 Thread Brian Murray
** Description changed:

+ [Workaround]
+ 
+ Some workarounds have been suggested in
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125
+ 
  [Impact]
  
   * In some cases, if the users’ initramfs grow bigger, then it’ll likely
  not be able to be loaded by grub2.
  
   * Some real cases from OEM projects:
  
  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts
  the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the
  gfxpayload=auto will remain to use 4K resolution since it’s what EFI
  POST passed.
  
  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:
  
  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```
  
  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:
  
  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```
  
  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
  
  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.
  
   * When users grown the initramfs, then probably will get initramfs not
  found which really annoyed and impact the user experience (system not
  able to boot).
  
  [Test Plan]
  
   * detailed instructions how to reproduce the bug:
  
  1. Any method to grow the initramfs, such as install nvidia-driver.
  
  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:
  
  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh
  
  PREREQ=""
  
  prereqs()
  {
  echo "$PREREQ"
  }
  
  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac
  
  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```
  
  And then update-initramfs
  
   * After applying my patches, the issue is gone.
  
   * I did also test my test grubx64.efi in:
  
  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel
  
  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel
  
  All working well.
  
  [Where problems could occur]
  
  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.
  
  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also
  
  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```
  
  If everything works as expected, then i386 should working good.
  
  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB
  memory region and never be able to access.
  
  [Other Info]
  
   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058
  
   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
  
   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
  
   * Test source code: https://github.com/os369510/grub2/tree/lp1842320
  
   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  `/var/cache/pbuilder/build/276481/build/grub2-2.06/obj/monolithic/grub-
  efi-amd64/grubx64.efi`
  
   * My build command: `sudo PBSHELL=1 pbuilder build --hookdir ~/hook-dir
  ubuntu-grub/grub2_2.06-2ubuntu7+jeremydev2.dsc 2>&1 | tee build.log`
  
   * My qemu command: `qemu-system-x86_64 -bios
  edk2/Build/OvmfX64/DEBUG_GCC5/FV/OVMF.fd -hda Templates/grub.qcow2 -m 6G
  -vga cirrus -smp 8 -machine 

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

2022-11-29 Thread Craig Hesling
Ah, didn't realize Debian had a different limit. Thanks @juliank.

@anourzad, I'm not sure I would want to start adding custom steps to the
kernel update path. I'm much more inclined to add an /etc option for a
supported automatic mechanism, like compression or module selection.

@adrien-n, great notes in #125, I'm sure this will help others.

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

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

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

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

   * Some real cases from OEM projects:

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

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

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

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

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

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

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

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

  [Test Plan]

   * detailed instructions how to reproduce the bug:

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

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

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

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

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

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

  And then update-initramfs

   * After applying my patches, the issue is gone.

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

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

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

  All working well.

  [Where problems could occur]

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

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

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

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

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

  [Other Info]

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

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

   * Test grubx64.efi:
  

[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

2022-11-29 Thread Sven Kieske
so, we seem to have a dependency problem here, no?

for reference, this is fixed by:

apt install linux-tools-common

but why was "linux-tools-common" not installed as a part of "linux-
tools-generic-hwe-18.04"?

this is the dependency chain:

root@ceph-osd03:~# apt-cache depends linux-tools-generic-hwe-18.04
linux-tools-generic-hwe-18.04
  Depends: linux-tools-5.4.0-132-generic
root@ceph-osd03:~# apt-cache depends linux-tools-5.4.0-132-generic
linux-tools-5.4.0-132-generic
  Depends: linux-hwe-5.4-tools-5.4.0-132
root@ceph-osd03:~# apt-cache depends linux-hwe-5.4-tools-5.4.0-132
linux-hwe-5.4-tools-5.4.0-132
  Depends: libc6
  Depends: libcap2
  Depends: libdw1
  Depends: libelf1
  Depends: liblzma5
  Depends: libnuma1
  Depends: libpci3
  Depends: libslang2
  Depends: libssl1.1
  Depends: libudev1
  Depends: libunwind8
  Depends: zlib1g
  Depends: linux-hwe-5.4-tools-common
root@ceph-osd03:~# apt-cache depends linux-hwe-5.4-tools-common
linux-hwe-5.4-tools-common
  Depends: lsb-release
root@ceph-osd03:~# dpkg -S linux-hwe-5.4-tools-common
linux-hwe-5.4-tools-common: /usr/share/doc/linux-hwe-5.4-tools-common
linux-hwe-5.4-tools-common: /usr/share/doc/linux-hwe-5.4-tools-common/copyright
linux-hwe-5.4-tools-common: 
/usr/share/doc/linux-hwe-5.4-tools-common/changelog.Debian.gz

nothing installs /usr/bin/cpupower (that is, "linux-tools-common").

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid

Bug description:
  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.19.0.27.24)

2022-11-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta (5.19.0.27.24) for kinetic 
have finished running.
The following regressions have been reported in tests triggered by the package:

dropbear/2022.82-4 (arm64)
network-manager/1.40.0-1ubuntu2 (amd64)
systemd/251.4-1ubuntu7 (amd64, ppc64el, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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


[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

2022-11-29 Thread Juerg Haefliger
$ dpkg -S /usr/bin/cpupower 
linux-tools-common: /usr/bin/cpupower


** Changed in: linux-meta-hwe-5.4 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid

Bug description:
  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

2022-11-29 Thread Sven Kieske
** Changed in: linux-meta-hwe-5.4 (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid

Bug description:
  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

2022-11-29 Thread Sven Kieske
also:

 cpupower --help
bash: cpupower: command not found

type cpupower
-su: type: cpupower: not found

command cpupower
-su: cpupower: command not found


/usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower
Usage:  cpupower [-d|--debug] [-c|--cpu cpulist ]  []
Supported commands are:
frequency-info
frequency-set
idle-info
idle-set
set
info
monitor
help

Not all commands can make use of the -c cpulist option.

Use 'cpupower help ' for getting help for above commands.

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

2022-11-29 Thread Sven Kieske
I'm sorry, but can you show me your $PATH?

According to: https://packages.ubuntu.com/bionic-updates/amd64/linux-
tools-5.4.0-132-generic/filelist

cpupower get's installed into the following path:

/usr/lib/linux-tools/5.4.0-132-generic/cpupower

which seems to be a symlink, according to my system, to:

ls -lashin /usr/lib/linux-tools/5.4.0-132-generic/cpupower
2546080 0 lrwxrwxrwx 1 0 0 44 Oct 24 15:52 
/usr/lib/linux-tools/5.4.0-132-generic/cpupower -> 
../../linux-hwe-5.4-tools-5.4.0-132/cpupower

ls -lashin /usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower 
2546021 292K -rwxr-xr-x 1 0 0 290K Oct 24 15:52 
/usr/lib/linux-hwe-5.4-tools-5.4.0-132/cpupower

but if I'm not terribly mistaken /usr/lib/ is on no default $PATH, see
this system:

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

or also these answers, neither contain /usr/lib/ in $PATH?

https://askubuntu.com/questions/386629/what-are-the-default-path-values

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1988470] Re: System runs into emergency mode if SSD is missing

2022-11-29 Thread Juerg Haefliger
That's probably new behavior in 22.04. Looks like a mount timeout on
20.04 doesn't drop into maintenance mode whereas 22.04 does. Try adding
'nofail' to the mount option in /etc/fstab, i.e.,

UUID=b0b81501-45ab-4a56-a5dc-480782ebedf8 /media/WORK ext4
defaults,nofail 0 2

In any case this is not a kernel problem so marking the bug as
'invalid'.

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

Title:
  System runs into emergency mode if SSD is missing

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  I have M.2 SSD, attached to USB3 port. Everything worked fine in 20.04LTS. I 
could detach the drive, then boot the system, and it ran correctly in UI mode 
with desktop, etc.
  I have another behavior after upgrade to 22.04LTS with 5.15.0.1013 core. Now 
the system boots into emergency mode with command prompt, if SSD is detached. 
SSD linking is defined in the /etc/fstab.
  System works fine if SSD is attached to USB3 port before power is on. Also I 
can attach SDD when the system is in the command prompt mode (see above) then 
reboot from the command line, then system will boot the GUI.

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


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


[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

2022-11-29 Thread Sven Kieske
apport-collect is not installed on this system.

I added some manually collected logs. If you need further debug data,
please specify what exactly you need and I will try to provide it.

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

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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


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

2022-11-29 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 1998224

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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


[Kernel-packages] [Bug 1998224] [NEW] pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

2022-11-29 Thread Sven Kieske
Public bug reported:

situation: ubuntu 18.04 server install on a supermicro x64 host.

hot plug NVME ssd into NVME U.2 HotSwap Slot.

problem: hot plug does not work/ nvme is not recognised.

how to test:

echo 1 > /sys/bus/pci/rescan

dmesg output:

[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
[Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io  
size 0x1000]

Kernel Version:

5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux

hardware information: tried with micron and intel NVME, e.g:

INTEL SSDPE2KE016T8

after a reboot, the NVME is recognized, so there is no hardware problem.

if you need additional debug information, feel free to ask.

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

** Attachment added: "lspci Output"
   
https://bugs.launchpad.net/bugs/1998224/+attachment/5633192/+files/lspci-vnvn.log

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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


[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

2022-11-29 Thread Sven Kieske
** Attachment added: "Kernel Version"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+attachment/5633193/+files/version.log

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

Title:
  pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  situation: ubuntu 18.04 server install on a supermicro x64 host.

  hot plug NVME ssd into NVME U.2 HotSwap Slot.

  problem: hot plug does not work/ nvme is not recognised.

  how to test:

  echo 1 > /sys/bus/pci/rescan

  dmesg output:

  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io  
0x1000-0x0fff] to [bus 41] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io  
0x1000-0x0fff] to [bus 42] add_size 1000
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign 
[io  size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io  
size 0x1000]
  [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign 
[io  size 0x1000]

  Kernel Version:

  5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022
  x86_64 x86_64 x86_64 GNU/Linux

  hardware information: tried with micron and intel NVME, e.g:

  INTEL SSDPE2KE016T8

  after a reboot, the NVME is recognized, so there is no hardware
  problem.

  if you need additional debug information, feel free to ask.

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


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.19.0.1015.12)

2022-11-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta-aws (5.19.0.1015.12) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/unknown (arm64)
systemd/251.4-1ubuntu7 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-meta-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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


[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control

2022-11-29 Thread Timo Aaltonen
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  Mediatek WLAN RZ616(MT7922) SAR table control

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

Bug description:
  [Impact]
  In order to make sure the amount of RF energy being absorbed by our bodies is 
safe according to the FCC’s guidelines, products must undergo and pass SAR 
testing.

  [Fix]
  Add ACPI SAR table control to pass the testing.

  [Test]
  the unit is 0.5dBm in following:

  Without the SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 40 40 40 40 40 40 40 40
  HT20 (user) : 40 40 40 40 40 40 40 40
  HT40 (user) : 40 40 40 40 40 40 40 40 
40
  VHT20 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT40 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT80 (user): 40 40 40 40 40 40 40 40 
40 40  0  0
  VHT160 (user)   : 40 40 40 40 40 40 40 40 
40 40  0  0
  HE26 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE52 (user) : 40 40 40 40 40 40 40 40 
40 40 40 40
  HE106 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE242 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE484 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996 (user): 40 40 40 40 40 40 40 40 
40 40 40 40
  HE996x2 (user)  : 40 40 40 40 40 40 40 40 
40 40 40 40

  After enabled SAR table control:
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user
  CCK (user)  :N.AN.AN.AN.A
  OFDM (user) : 26 26 26 26 26 26 26 26
  HT20 (user) : 26 26 26 26 26 26 26 26
  HT40 (user) : 26 26 26 26 26 26 26 26 
26
  VHT20 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT40 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT80 (user): 26 26 26 26 26 26 26 26 
26 26  0  0
  VHT160 (user)   : 26 26 26 26 26 26 26 26 
26 26  0  0
  HE26 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE52 (user) : 26 26 26 26 26 26 26 26 
26 26 26 26
  HE106 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE242 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE484 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE996 (user): 26 26 26 26 26 26 26 26 
26 26 26 26
  HE996x2 (user)  : 26 26 26 26 26 26 26 26 
26 26 26 26

  Also done stress test with iperf, all works fine.

  [Where problems could occur]
  It may break mt7922 driver.

  These commits are already in oem-6.0 and unstable.

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


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


[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU

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

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

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

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: linux-oem-5.14 (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/1998106

Title:
  Fix AMD-PState driver for Genoa CPU

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  During AMD Genoa development, the datacenter team identified
  performance regressions that were root caused in the amd-pstate
  driver. A first round of fixes already landed upstream (v6.1-rc7) in
  the amd-pstate driver, and should be backported to all the affected
  kernels.

  [Fix]

  Backport the upstream amd-pstate fixes:

  https://lore.kernel.org/linux-
  
pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a

  [Regression potential]

  Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a
  single driver (amd-pstate) and the new mode (passive) is disabled by
  default.

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


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


[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic

2022-11-29 Thread Graham Inggs
Sponsored with minor changes, as discussed with Adrien:
kinetic -> lunar
dropped debian/changelog.in delta

** Changed in: strace (Ubuntu)
   Status: In Progress => Fix Committed

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

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

Title:
  FTBFS on kinetic

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

Bug description:
  As can be seen in [1], strace FTBFS in kinetic: this is caused by the
  kernel headers (linux-libc-dev) which do not define F_GETLK64 and
  other on 64b builds because the kernel contains a bogus commit
  (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
  fcntl.h"). This commit actually did the opposite of what it was
  supposed to do, namely defining those macros even on 64b builds. There
  is an attempt here to fix this which was not merged yet:
  
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/

  [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
  amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz

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


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


[Kernel-packages] [Bug 1995320] Re: [amdgpu] intermittent green static

2022-11-29 Thread Kai Groner
The issue eventually occurred with the bleeding edge mesa, but it took a
week.

I've since reverted to the kinetic mesa and tried mainline 5.18 and 5.17
kernels, but the issue continues to appear with those kernels.

For now I'm just running the jammy kernel, since that seems to work
without static. I still sometimes see one screen freeze up entirely.
Playing a video seems to fix that pretty reliably.

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

Title:
  [amdgpu] intermittent green static

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

Bug description:
  After upgrading from 22.04 to 22.10 I've been seeing some display
  glitches.

  - green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
  - firefox not refreshing when full screen video plays (separate windows, 
separate screens)

  I would guess I probably have the wrong package here, but there's no
  way for me to tell if it's mesa, the kernel, gnome-shell, or something
  else.

  Radeon 6700XT
  Dual displays
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 21:46:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1231 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2019-06-18 (1232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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


[Kernel-packages] [Bug 1993665] Re: Update the 470-server NVIDIA driver

2022-11-29 Thread Francis Ginther
The A100 is down with some hardware issues and there is no ETA when it
will be up again. Given that the testing passed on the DGX2 and the A100
is having hardware issues which quite likely impacted the testing, I'm
going to consider the kinetic testing as verified.

** Tags removed: verification-failed-kinetic
** Tags added: verification-done-kinetic

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

Title:
  Update the 470-server NVIDIA driver

Status in fabric-manager-470 package in Ubuntu:
  In Progress
Status in libnvidia-nscq-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Kinetic:
  In Progress
Status in libnvidia-nscq-470 source package in Kinetic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Kinetic:
  In Progress

Bug description:
  
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+subscriptions


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


[Kernel-packages] [Bug 1992211] Re: Focal update: v5.4.213 upstream stable release

2022-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.4.0-136.153 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: kernel-spammed-focal-linux

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

Title:
  Focal update: v5.4.213 upstream stable release

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

Bug description:
  SRU Justification

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

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

  efi: capsule-loader: Fix use-after-free in efi_capsule_write
  wifi: iwlegacy: 4965: corrected fix for potential off-by-one overflow in 
il4965_rs_fill_link_cmd()
  fs: only do a memory barrier for the first set_buffer_uptodate()
  Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"
  net: dp83822: disable false carrier interrupt
  drm/msm/dsi: fix the inconsistent indenting
  drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
  platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
  iio: adc: mcp3911: make use of the sign bit
  ieee802154/adf7242: defer destroy_workqueue call
  wifi: cfg80211: debugfs: fix return type in ht40allow_map_read()
  Revert "xhci: turn off port power in shutdown"
  net: sched: tbf: don't call qdisc_put() while holding tree lock
  ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler
  kcm: fix strp_init() order and cleanup
  sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb
  tcp: annotate data-race around challenge_timestamp
  Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb"
  net/smc: Remove redundant refcount increase
  serial: fsl_lpuart: RS485 RTS polariy is inverse
  staging: rtl8712: fix use after free bugs
  powerpc: align syscall table for ppc32
  vt: Clear selection before changing the font
  tty: serial: lpuart: disable flow control while waiting for the transmit 
engine to complete
  Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
  iio: adc: mcp3911: use correct formula for AD conversion
  misc: fastrpc: fix memory corruption on probe
  misc: fastrpc: fix memory corruption on open
  USB: serial: ftdi_sio: add Omron CS1W-CIF31 device id
  binder: fix UAF of ref->proc caused by race condition
  usb: dwc3: qcom: fix use-after-free on runtime-PM wakeup
  drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported"
  clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops
  Revert "clk: core: Honor CLK_OPS_PARENT_ENABLE for clk gate ops"
  clk: core: Fix runtime PM sequence in clk_core_unprepare()
  Input: rk805-pwrkey - fix module autoloading
  clk: bcm: rpi: Fix error handling of raspberrypi_fw_get_rate
  hwmon: (gpio-fan) Fix array out of bounds access
  gpio: pca953x: Add mutex_lock for regcache sync in PM
  thunderbolt: Use the actual buffer in tb_async_error()
  xhci: Add grace period after xHC start to prevent premature runtime suspend.
  USB: serial: cp210x: add Decagon UCA device id
  USB: serial: option: add support for OPPO R11 diag port
  USB: serial: option: add Quectel EM060K modem
  USB: serial: option: add support for Cinterion MV32-WA/WB RmNet mode
  usb: typec: altmodes/displayport: correct pin assignment for UFP receptacles
  usb: dwc2: fix wrong order of phy_power_on and phy_init
  USB: cdc-acm: Add Icom PMR F3400 support (0c26:0020)
  usb-storage: Add ignore-residue quirk for NXP PN7462AU
  s390/hugetlb: fix prepare_hugepage_range() check for 2 GB hugepages
  s390: fix nospec table alignments
  USB: core: Prevent nested device-reset calls
  usb: gadget: mass_storage: Fix cdrom data transfers on MAC-OS
  driver core: Don't probe devices after bus_type.match() probe deferral
  wifi: mac80211: Don't finalize CSA in IBSS mode if state is disconnected
  net: mac802154: Fix a condition in the receive path
  ALSA: seq: oss: Fix data-race for max_midi_devs access
  ALSA: seq: Fix data-race at module auto-loading
  drm/i915/glk: ECS Liva Q2 needs 

[Kernel-packages] [Bug 1993196] Re: Focal update: v5.4.214 upstream stable release

2022-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.4.0-136.153 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: kernel-spammed-focal-linux

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

Title:
  Focal update: v5.4.214 upstream stable release

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

Bug description:
  SRU Justification

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

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

  drm/msm/rd: Fix FIFO-full deadlock
  HID: ishtp-hid-clientHID: ishtp-hid-client: Fix comment typo
  hid: intel-ish-hid: ishtp: Fix ishtp client sending disordered message
  tg3: Disable tg3 device on system reboot to avoid triggering AER
  ieee802154: cc2520: add rc code in cc2520_tx()
  Input: iforce - add support for Boeder Force Feedback Wheel
  nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()
  perf/arm_pmu_platform: fix tests for platform_get_irq() failure
  platform/x86: acer-wmi: Acer Aspire One AOD270/Packard Bell Dot keymap fixes
  usb: storage: Add ASUS <0x0b05:0x1932> to IGNORE_UAS
  mm: Fix TLB flush for not-first PFNMAP mappings in unmap_region()
  net: dp83822: disable rx error interrupt
  soc: fsl: select FSL_GUTS driver for DPIO
  tracefs: Only clobber mode/uid/gid on remount if asked
  Linux 5.4.214
  UBUNTU: Upstream stable to v5.4.214

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


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


[Kernel-packages] [Bug 1993203] Re: Focal update: v5.4.215 upstream stable release

2022-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.4.0-136.153 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: kernel-spammed-focal-linux

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

Title:
  Focal update: v5.4.215 upstream stable release

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

Bug description:
  SRU Justification

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

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

  of: fdt: fix off-by-one error in unflatten_dt_nodes()
  NFSv4: Turn off open-by-filehandle and NFS re-export for NFSv4.0
  gpio: mpc8xxx: Fix support for IRQ_TYPE_LEVEL_LOW flow_type in mpc85xx
  drm/meson: Correct OSD1 global alpha value
  drm/meson: Fix OSD1 RGB to YCbCr coefficient
  parisc: ccio-dma: Add missing iounmap in error path in ccio_probe()
  ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC
  task_stack, x86/cea: Force-inline stack helpers
  tracing: hold caller_addr to hardirq_{enable,disable}_ip
  cifs: revalidate mapping when doing direct writes
  cifs: don't send down the destination address to sendmsg for a SOCK_STREAM
  MAINTAINERS: add Chandan as xfs maintainer for 5.4.y
  iomap: iomap that extends beyond EOF should be marked dirty
  ASoC: nau8824: Fix semaphore unbalance at error paths
  regulator: pfuze100: Fix the global-out-of-bounds access in 
pfuze100_regulator_probe()
  rxrpc: Fix local destruction being repeated
  rxrpc: Fix calc of resend age
  ALSA: hda/sigmatel: Keep power up while beep is enabled
  ALSA: hda/tegra: Align BDL entry to 4KB boundary
  net: usb: qmi_wwan: add Quectel RM520N
  afs: Return -EAGAIN, not -EREMOTEIO, when a file already locked
  MIPS: OCTEON: irq: Fix octeon_irq_force_ciu_mapping()
  mksysmap: Fix the mismatch of 'L0' symbols in System.map
  video: fbdev: pxa3xx-gcu: Fix integer overflow in pxa3xx_gcu_write
  cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()
  ALSA: hda/sigmatel: Fix unused variable warning for beep power change
  usb: dwc3: gadget: Avoid starting DWC3 gadget during UDC unbind
  usb: dwc3: Issue core soft reset before enabling run/stop
  usb: dwc3: gadget: Prevent repeat pullup()
  usb: dwc3: gadget: Refactor pullup()
  usb: dwc3: gadget: Don't modify GEVNTCOUNT in pullup()
  usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop
  usb: xhci-mtk: get the microframe boundary for ESIT
  usb: xhci-mtk: add only one extra CS for FS/LS INTR
  usb: xhci-mtk: use @sch_tt to check whether need do TT schedule
  usb: xhci-mtk: add a function to (un)load bandwidth info
  usb: xhci-mtk: add some schedule error number
  usb: xhci-mtk: allow multiple Start-Split in a microframe
  usb: xhci-mtk: relax TT periodic bandwidth allocation
  wifi: mac80211: Fix UAF in ieee80211_scan_rx()
  tty/serial: atmel: RS485 & ISO7816: wait for TXRDY before sending data
  serial: atmel: remove redundant assignment in rs485_config
  tty: serial: atmel: Preserve previous USART mode if RS485 disabled
  usb: add quirks for Lenovo OneLink+ Dock
  usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
  usb: cdns3: fix issue with rearming ISO OUT endpoint
  Revert "usb: add quirks for Lenovo OneLink+ Dock"
  Revert "usb: gadget: udc-xilinx: replace memcpy with memcpy_toio"
  USB: core: Fix RST error in hub.c
  USB: serial: option: add Quectel BG95 0x0203 composition
  USB: serial: option: add Quectel RM520N
  ALSA: hda/tegra: set depop delay for tegra
  ALSA: hda: add Intel 5 Series / 3400 PCI DID
  ALSA: hda/realtek: Add quirk for Huawei WRT-WX9
  ALSA: hda/realtek: Re-arrange quirk table entries
  ALSA: hda/realtek: Add pincfg for ASUS G513 HP jack
  ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack
  ALSA: hda/realtek: Add quirk for ASUS GA503R laptop
  ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5530 laptop
  efi: libstub: check Shim mode using MokSBStateRT
  mm/slub: fix to return errno if kmalloc() fails
  

[Kernel-packages] [Bug 1995526] Re: Focal update: v5.4.216 upstream stable release

2022-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.4.0-136.153 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: kernel-spammed-focal-linux

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

Title:
  Focal update: v5.4.216 upstream stable release

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

Bug description:
  SRU Justification

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

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

  uas: add no-uas quirk for Hiksemi usb_disk
  usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
  uas: ignore UAS for Thinkplus chips
  net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
  clk: ingenic-tcu: Properly enable registers before accessing timers
  ARM: dts: integrator: Tag PCI host with device_type
  ntfs: fix BUG_ON in ntfs_lookup_inode_by_name()
  libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205
  mmc: moxart: fix 4-bit bus width and remove 8-bit bus width
  mm/page_alloc: fix race condition between build_all_zonelists and page 
allocation
  mm: prevent page_frag_alloc() from corrupting the memory
  mm/migrate_device.c: flush TLB while holding PTL
  mm: fix madivse_pageout mishandling on non-LRU page
  media: dvb_vb2: fix possible out of bound access
  ARM: dts: Move am33xx and am43xx mmc nodes to sdhci-omap driver
  ARM: dts: am33xx: Fix MMCHS0 dma properties
  soc: sunxi: sram: Actually claim SRAM regions
  soc: sunxi: sram: Prevent the driver from being unbound
  soc: sunxi_sram: Make use of the helper function 
devm_platform_ioremap_resource()
  soc: sunxi: sram: Fix probe function ordering issues
  soc: sunxi: sram: Fix debugfs info for A64 SRAM C
  Revert "drm: bridge: analogix/dp: add panel prepare/unprepare in 
suspend/resume time"
  Input: melfas_mip4 - fix return value check in mip4_probe()
  usbnet: Fix memory leak in usbnet_disconnect()
  nvme: add new line after variable declatation
  nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices
  selftests: Fix the if conditions of in test_extra_filter()
  clk: imx: imx6sx: remove the SET_RATE_PARENT flag for QSPI clocks
  clk: iproc: Do not rely on node name for correct PLL setup
  Linux 5.4.216
  UBUNTU: Upstream stable to v5.4.216

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


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


[Kernel-packages] [Bug 1995528] Re: Focal update: v5.4.217 upstream stable release

2022-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.4.0-136.153 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: kernel-spammed-focal-linux

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

Title:
  Focal update: v5.4.217 upstream stable release

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

Bug description:
  SRU Justification

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

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

  xfs: fix misuse of the XFS_ATTR_INCOMPLETE flag
  xfs: introduce XFS_MAX_FILEOFF
  xfs: truncate should remove all blocks, not just to the end of the page cache
  xfs: fix s_maxbytes computation on 32-bit kernels
  xfs: fix IOCB_NOWAIT handling in xfs_file_dio_aio_read
  xfs: refactor remote attr value buffer invalidation
  xfs: fix memory corruption during remote attr value buffer invalidation
  xfs: move incore structures out of xfs_da_format.h
  xfs: streamline xfs_attr3_leaf_inactive
  xfs: fix uninitialized variable in xfs_attr3_leaf_inactive
  xfs: remove unused variable 'done'
  Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
  docs: update mediator information in CoC docs
  Linux 5.4.217
  UBUNTU: Upstream stable to v5.4.217

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


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


[Kernel-packages] [Bug 1995530] Re: Focal update: v5.4.218 upstream stable release

2022-11-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.4.0-136.153 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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


** Tags added: kernel-spammed-focal-linux

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

Title:
  Focal update: v5.4.218 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mm: pagewalk: Fix race between unmap and page walker
  perf tools: Fixup get_current_dir_name() compilation
  firmware: arm_scmi: Add SCMI PM driver remove routine
  dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
  dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API 
failure
  ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
  scsi: qedf: Fix a UAF bug in __qedf_probe()
  net/ieee802154: fix uninit value bug in dgram_sendmsg
  um: Cleanup syscall_handler_t cast in syscalls_32.h
  um: Cleanup compiler warning in arch/x86/um/tls_32.c
  arch: um: Mark the stack non-executable to fix a binutils warning
  usb: mon: make mmapped memory read only
  USB: serial: ftdi_sio: fix 300 bps rate for SIO
  mmc: core: Replace with already defined values for readability
  mmc: core: Terminate infinite loop in SD-UHS voltage switch
  rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
  nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
  nilfs2: fix leak of nilfs_root in case of writer thread creation failure
  nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
  ceph: don't truncate file in atomic_open
  random: clamp credited irq bits to maximum mixed
  ALSA: hda: Fix position reporting on Poulsbo
  efi: Correct Macmini DMI match in uefi cert quirk
  USB: serial: qcserial: add new usb-id for Dell branded EM7455
  random: restore O_NONBLOCK support
  random: avoid reading two cache lines on irq randomness
  random: use expired timer rather than wq for mixing fast pool
  Input: xpad - add supported devices as contributed on github
  Input: xpad - fix wireless 360 controller breaking after suspend
  Linux 5.4.218
  UBUNTU: Upstream stable to v5.4.218

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


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.15.0.54.54)

2022-11-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta (5.15.0.54.54) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.6 (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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


[Kernel-packages] [Bug 1914774] Re: HWE kernels do not ship linux-tools packages

2022-11-29 Thread Juerg Haefliger
Works for me:

$ sudo apt install linux-tools-generic-hwe-18.04
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.15.0-144 linux-headers-4.15.0-144-generic 
linux-image-4.15.0-144-generic linux-modules-4.15.0-144-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  linux-hwe-5.4-tools-5.4.0-132 linux-hwe-5.4-tools-common 
linux-tools-5.4.0-132-generic
The following NEW packages will be installed:
  linux-hwe-5.4-tools-5.4.0-132 linux-hwe-5.4-tools-common 
linux-tools-5.4.0-132-generic linux-tools-generic-hwe-18.04
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 5270 kB of archives.
After this operation, 25.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y

$ cpupower 
Usage:  cpupower [-d|--debug] [-c|--cpu cpulist ]  []
Supported commands are:
frequency-info
frequency-set
idle-info
idle-set
set
info
monitor
help

Not all commands can make use of the -c cpulist option.

Use 'cpupower help ' for getting help for above commands.

$ uname -r
5.4.0-132-generic


** Changed in: linux-meta-hwe-5.4 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  HWE kernels do not ship linux-tools packages

Status in linux-meta-hwe-5.4 package in Ubuntu:
  Invalid

Bug description:
  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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


[Kernel-packages] [Bug 1997151] Re: The volume from the microphone is very weak

2022-11-29 Thread Kai-Heng Feng
If USB microphone also has this issue I think something in userspace
caused it.

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

Title:
  The volume from the microphone is very weak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The missing gain can be estimated to about 1000 (30dB) using the program 
"Audacity".
  It does not matter whether the internal microphone, a microphone on the 
headset via the jack plug or a USB microphone is used.

  In the audio system settings a inactiv "Card Renoir Radeon High
  Definition Audio Controller" is shown.

  Ubuntu 5.15.0-53.59-generic 5.15.64
  https://linux-hardware.org/?probe=124d4a2353

  grep "Codec:" /proc/asound/card*/codec*
  /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI
  /proc/asound/card1/codec#0:Codec: Realtek ALC236

  Logfiles in the appendix!

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


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


[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-11-29 Thread Timo Aaltonen
no, plans have changed I'm afraid, but there might be something else
which I can't disclose right now

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

Title:
  Add support for Intel DG2

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

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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


[Kernel-packages] [Bug 1979352] Re: system frozen after sleep

2022-11-29 Thread Dougal
29th November 2022
I am on Ubuntu Studio 22.10 installed within the last week and I find the bug 
where the system is frozen when waking from sleep is still there.
As reported previously logs cannot be collected because no user input works.
I believe after all this time using Ubuntu I have to consider using another 
distro. I seriously regret having to consider this but because of the nature of 
what I use my computers for I need a system that still responds after sleeping 
or hibernating.
If I shutdown proper there is no problem.
I have not seen a solution to this posted.

Once again thank you to all the developers involved but, I cannot wait
any longer. I believe two years is more than a reasonable amount of time
to wait for any bug fix that affects the whole system operation.

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

Title:
  system frozen after sleep

Status in Ubuntu MATE:
  Incomplete
Status in acpid package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC
  2022 x86_64 x86_64 x86_64 GNU/Linux

  This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly 
but, at that time it was only apparent when I was using video ripping software 
on separate laptops and only when the machines became idle once the ripping 
program had finished.
  I don't think this bug was ever fixed and so I'm returning to it because I 
left my laptop in sleep mode over meal time to come back to a frozen system. I 
was not using the video ripping program this time, just surfing the Net. No 
other program was open.

  I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has
  happened when using an old Dell 1530 laptop.

  I do not believe I am unique in having this bug as someone has a
  similar bug when they have minimised Google Chrome and their system
  had went to sleep. I was also using Chrome this time but, as I have
  already said I was having this happen using another program and not
  using Chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+subscriptions


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


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

2022-11-29 Thread jeremyszu
Is it possible if we have an overwrite in debian/rule by using something
like DEB_BUILD_ARCH to specify higher compression rate for amd64?

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

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

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

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

   * Some real cases from OEM projects:

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

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

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

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

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

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

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

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

  [Test Plan]

   * detailed instructions how to reproduce the bug:

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

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

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

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

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

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

  And then update-initramfs

   * After applying my patches, the issue is gone.

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

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

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

  All working well.

  [Where problems could occur]

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

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

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

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

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

  [Other Info]

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

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

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

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

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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.19.0.24.23)

2022-11-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta (5.19.0.24.23) for kinetic 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/251.4-1ubuntu7 (amd64, ppc64el, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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


[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel

2022-11-29 Thread Alfonso Sanchez-Beato
Changing to confirmed as I cannot run the apport command in the system
where this was found.

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

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

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

Title:
  Please add support for Qualcomm IPC Router in 5.4 focal kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The modemmanager debian package in focal was recently upgraded to 1.18
  (apparently the jammy version was backported). This version has broken
  some Qualcomm modems as it start to require the Qualcomm IPC Router
  for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix
  this we need these options enabled in the focal kernel:

  CONFIG_QRTR=m
  CONFIG_QRTR_SMD=m
  CONFIG_QRTR_TUN=m
  CONFIG_QRTR_MHI=m

  The options are already enabled in more modern Ubuntu kernel, i.e.
  5.17.

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


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.19.0.24.23)

2022-11-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta (5.19.0.24.23) for kinetic 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/251.4-1ubuntu7 (arm64, amd64, ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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


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

2022-11-29 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 1998194

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

Title:
  Please add support for Qualcomm IPC Router in 5.4 focal kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The modemmanager debian package in focal was recently upgraded to 1.18
  (apparently the jammy version was backported). This version has broken
  some Qualcomm modems as it start to require the Qualcomm IPC Router
  for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix
  this we need these options enabled in the focal kernel:

  CONFIG_QRTR=m
  CONFIG_QRTR_SMD=m
  CONFIG_QRTR_TUN=m
  CONFIG_QRTR_MHI=m

  The options are already enabled in more modern Ubuntu kernel, i.e.
  5.17.

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


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


[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it

2022-11-29 Thread Christian Ehrhardt 
Bionic was already reset for other reasons at the end of march this year.
Jammy was already reset for other reasons in January this year.
Kinetic was already reset for other reasons in May this year (and Lunar is 
based on that).

Only Focal was left open and is now queued.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1998184

Title:
  fanatic tests spawn latest LTS but isn't compatible with it

Status in ubuntu-fan package in Ubuntu:
  New
Status in ubuntu-fan source package in Bionic:
  New
Status in ubuntu-fan source package in Focal:
  New
Status in ubuntu-fan source package in Jammy:
  New
Status in ubuntu-fan source package in Kinetic:
  New
Status in ubuntu-fan source package in Lunar:
  New

Bug description:
  This breaks all ubuntu-fan autopkgtest since Jammy was released in
  April 2022.

  Miriam found it while checking an autopkgtest regression in bug
  1995260

  Summary:
  - the tests in test_local_lxd hardcode to "lts"
  local series='lts'
  - due to that we always test the latest (good) but are now incompatible :-/
  - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the 
old name
  - Jammy comes without systemd-resolve
  We now face:
  - bionic: systemd-resolved
  - focal: systemd-resolved + resolvectl
  - jammy: resolvectl
  - due to that all tests fail nowadays with:

  
  ...
  /bin/sh: 29: systemd-resolve: not found
  slave: waiting for systemd resolver...
  /bin/sh: 29: systemd-resolve: not found
  slave: waiting for systemd resolver...
  ...
  slave: systemd-resolve failure!

  
  Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping 
it is kernel-packages that owns this so I'll subscribe them right away - these 
tests will block everything depending on it.
  Therefore let us mask the current version from proposed migration.

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


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


[Kernel-packages] [Bug 1998194] [NEW] Please add support for Qualcomm IPC Router in 5.4 focal kernel

2022-11-29 Thread Alfonso Sanchez-Beato
Public bug reported:

The modemmanager debian package in focal was recently upgraded to 1.18
(apparently the jammy version was backported). This version has broken
some Qualcomm modems as it start to require the Qualcomm IPC Router for
them, which drivers are not enabled in Ubuntu kernel 5.4. To fix this we
need these options enabled in the focal kernel:

CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m

The options are already enabled in more modern Ubuntu kernel, i.e. 5.17.

** Affects: linux (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/1998194

Title:
  Please add support for Qualcomm IPC Router in 5.4 focal kernel

Status in linux package in Ubuntu:
  New

Bug description:
  The modemmanager debian package in focal was recently upgraded to 1.18
  (apparently the jammy version was backported). This version has broken
  some Qualcomm modems as it start to require the Qualcomm IPC Router
  for them, which drivers are not enabled in Ubuntu kernel 5.4. To fix
  this we need these options enabled in the focal kernel:

  CONFIG_QRTR=m
  CONFIG_QRTR_SMD=m
  CONFIG_QRTR_TUN=m
  CONFIG_QRTR_MHI=m

  The options are already enabled in more modern Ubuntu kernel, i.e.
  5.17.

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


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


[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it

2022-11-29 Thread Christian Ehrhardt 
I was lost in old habits when providing MRs for hints, sorry.
This doesn't need hints to land, since it is broken in release due to external 
changes a set of baseline runs with migration-reference/0 will work just as 
much and be less effort.

Scheduling those now ...


P.S. That will unblock the test flaws, but the problem itself is still present 
and needs to be fixed in ubuntu-fan - until then there will be no test coverage.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1998184

Title:
  fanatic tests spawn latest LTS but isn't compatible with it

Status in ubuntu-fan package in Ubuntu:
  New
Status in ubuntu-fan source package in Bionic:
  New
Status in ubuntu-fan source package in Focal:
  New
Status in ubuntu-fan source package in Jammy:
  New
Status in ubuntu-fan source package in Kinetic:
  New
Status in ubuntu-fan source package in Lunar:
  New

Bug description:
  This breaks all ubuntu-fan autopkgtest since Jammy was released in
  April 2022.

  Miriam found it while checking an autopkgtest regression in bug
  1995260

  Summary:
  - the tests in test_local_lxd hardcode to "lts"
  local series='lts'
  - due to that we always test the latest (good) but are now incompatible :-/
  - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the 
old name
  - Jammy comes without systemd-resolve
  We now face:
  - bionic: systemd-resolved
  - focal: systemd-resolved + resolvectl
  - jammy: resolvectl
  - due to that all tests fail nowadays with:

  
  ...
  /bin/sh: 29: systemd-resolve: not found
  slave: waiting for systemd resolver...
  /bin/sh: 29: systemd-resolve: not found
  slave: waiting for systemd resolver...
  ...
  slave: systemd-resolve failure!

  
  Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping 
it is kernel-packages that owns this so I'll subscribe them right away - these 
tests will block everything depending on it.
  Therefore let us mask the current version from proposed migration.

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


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.19.0.1012.11)

2022-11-29 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta-aws (5.19.0.1012.11) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/251.4-1ubuntu7 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#linux-meta-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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


[Kernel-packages] [Bug 1861295] Re: [Apple 05ac:8290] Bluetooth not working

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

- Bluetooth not working
+ [Apple 05ac:8290] Bluetooth not working

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

Title:
  [Apple 05ac:8290] Bluetooth not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 19.10 on this Macbook Pro a couple of weeks ago.
  Bluetooth was working during the first days, but now it won't work
  anymore.

  Here is the output of dmesg | grep -i blue, showing some errors that
  might be interesting:

  > dmesg | grep -i blue
  [1.562871] usb 1-3: Product: Bluetooth USB Host Controller
  [2.104835] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0003/input/input10
  [2.164582] hid-generic 0003:05AC:8290.0003: input,hidraw2: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [2.164685] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0004/input/input11
  [2.164761] hid-generic 0003:05AC:8290.0004: input,hidraw3: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [3.605086] Bluetooth: Core ver 2.22
  [3.605103] Bluetooth: HCI device and connection manager initialized
  [3.605107] Bluetooth: HCI socket layer initialized
  [3.605109] Bluetooth: L2CAP socket layer initialized
  [3.605112] Bluetooth: SCO socket layer initialized
  [5.720427] Bluetooth: hci0: command 0x0c03 tx timeout
  [6.637120] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.637122] Bluetooth: BNEP filters: protocol multicast
  [6.637126] Bluetooth: BNEP socket layer initialized
  [   13.876494] Bluetooth: hci0: BCM: Reset failed (-110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-26-generic 5.3.0-26.28
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maurizio   1377 F pulseaudio
   /dev/snd/controlC0:  maurizio   1377 F pulseaudio
   /dev/snd/controlC1:  maurizio   1377 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 29 14:16:01 2020
  InstallationDate: Installed on 2020-01-23 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Apple Inc. MacBookPro12,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=adc45397-ab6d-4a20-8795-b9e7f3d733b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 188.0.0.0.0
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvr188.0.0.0.0:bd10/30/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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


[Kernel-packages] [Bug 1892012] Re: [Intel 9560] Bluetooth doesn't turn on

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

- Bluetooth doesn't turn on
+ [Intel 9560] Bluetooth doesn't turn on

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

Title:
  [Intel 9560] Bluetooth doesn't turn on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UPDATE
  ==

  I tried another kernel (`5.4.0-40-generic` and it didn't worked.
  Trying to reboot (and get back to the latest kernel) it didn't shutdown, so I 
hard shutdown it, and restart with the `5.4.0-42-generic`.

  And now, it works.
  I hope the logs below may help you to find out what happened, and help others 
to fix their issue if it's similar to this one.

  ---

  
  Hello,

  For now, everything worked fine, until this morning when Bluetooth
  stop working.

  Ubuntu 20.04

  **What expected to happen :** Bluetooth turn on on start, and if it's
  off it turns on when I turn it on.

  **What happens :** it doesn't turn on.

  ```
   $ dmesg | grep -i blue
  [2.433133] Bluetooth: Core ver 2.22
  [2.433147] Bluetooth: HCI device and connection manager initialized
  [2.433149] Bluetooth: HCI socket layer initialized
  [2.433151] Bluetooth: L2CAP socket layer initialized
  [2.433153] Bluetooth: SCO socket layer initialized
  [3.559082] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.559083] Bluetooth: BNEP filters: protocol multicast
  [3.559088] Bluetooth: BNEP socket layer initialized
  [4.456149] Bluetooth: hci0: command 0xfc05 tx timeout
  [4.456167] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  ```

  Last `/var/log/dpkg.log` logs (previous were from 3 days ago)
  ```
  2020-08-18 01:06:02 startup archives unpack
  2020-08-18 01:06:03 install python3-blessings:all  1.6-3
  2020-08-18 01:06:03 status half-installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 install python3-pynvml:amd64  7.352.0-3
  2020-08-18 01:06:03 status half-installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 install gpustat:all  0.6.0-1
  2020-08-18 01:06:03 status half-installed gpustat:all 0.6.0-1
  2020-08-18 01:06:03 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:03 startup packages configure
  2020-08-18 01:06:03 configure python3-blessings:all 1.6-3 
  2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status half-configured python3-blessings:all 1.6-3
  2020-08-18 01:06:03 status installed python3-blessings:all 1.6-3
  2020-08-18 01:06:03 configure python3-pynvml:amd64 7.352.0-3 
  2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:03 status half-configured python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 status installed python3-pynvml:amd64 7.352.0-3
  2020-08-18 01:06:04 configure gpustat:all 0.6.0-1 
  2020-08-18 01:06:04 status unpacked gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status half-configured gpustat:all 0.6.0-1
  2020-08-18 01:06:04 status installed gpustat:all 0.6.0-1

  ```

  ```
   $ dpkg -l | grep -i blue
  ii  bluez 5.53-0ubuntu3   
  amd64Bluetooth tools and daemons
  ii  bluez-cups5.53-0ubuntu3   
  amd64Bluetooth printer driver for CUPS
  ii  bluez-obexd   5.53-0ubuntu3   
  amd64bluez obex daemon
  ii  gir1.2-gnomebluetooth-1.0:amd64   3.34.1-1
  amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth   3.34.1-1
  amd64GNOME Bluetooth tools
  ii  libbluetooth3:amd64   5.53-0ubuntu3   
  amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd643.34.1-1
  amd64GNOME Bluetooth tools - support library
  ii  libkf5bluezqt-data5.68.0-0ubuntu1 
  all  data files for bluez-qt
  ii  libkf5bluezqt6:amd64  5.68.0-0ubuntu1 
  amd64Qt wrapper for bluez
  ii  node-bluebird 3.5.1+dfsg2-2build1 
  all  Fully featured Promises/A+ implementation for Node.js
  ii  pulseaudio-module-bluetooth   1:13.99.1-1ubuntu3.5
  amd64Bluetooth module for PulseAudio sound server
  ii  qml-module-org-kde-bluezqt:amd64  5.68.0-0ubuntu1 
  amd64QML wrapper for bluez
  ```

  ```
   $ sudo service bluetooth status
  [sudo] password for brieucdug:
  ● bluetooth.service - Bluetooth 

[Kernel-packages] [Bug 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

2022-11-29 Thread Daniel van Vugt
** No longer affects: bluez (Ubuntu)

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.

  inxi -EbA

  System:
    Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
    Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
    Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
    Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
    Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
    Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
    Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
    Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
    Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

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


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


[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it

2022-11-29 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1998184

Title:
  fanatic tests spawn latest LTS but isn't compatible with it

Status in ubuntu-fan package in Ubuntu:
  New
Status in ubuntu-fan source package in Bionic:
  New
Status in ubuntu-fan source package in Focal:
  New
Status in ubuntu-fan source package in Jammy:
  New
Status in ubuntu-fan source package in Kinetic:
  New
Status in ubuntu-fan source package in Lunar:
  New

Bug description:
  This breaks all ubuntu-fan autopkgtest since Jammy was released in
  April 2022.

  Miriam found it while checking an autopkgtest regression in bug
  1995260

  Summary:
  - the tests in test_local_lxd hardcode to "lts"
  local series='lts'
  - due to that we always test the latest (good) but are now incompatible :-/
  - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the 
old name
  - Jammy comes without systemd-resolve
  We now face:
  - bionic: systemd-resolved
  - focal: systemd-resolved + resolvectl
  - jammy: resolvectl
  - due to that all tests fail nowadays with:

  
  ...
  /bin/sh: 29: systemd-resolve: not found
  slave: waiting for systemd resolver...
  /bin/sh: 29: systemd-resolve: not found
  slave: waiting for systemd resolver...
  ...
  slave: systemd-resolve failure!

  
  Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping 
it is kernel-packages that owns this so I'll subscribe them right away - these 
tests will block everything depending on it.
  Therefore let us mask the current version from proposed migration.

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


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


[Kernel-packages] [Bug 1995021] Re: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash

2022-11-29 Thread Arild Johnsen
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Boot and shutdown take several minutes. "watchdog: BUG: soft lockup -
  CPU#0 stuck for 26s!" followed by nvidia kernel crash

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

Bug description:
  My system has been running smoothly until Kernel 5.15.0-50 (and
  5.15.0-52) was installed. Now boot and shutdown take several minutes.
  I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown
  run witout delay with the Nouveau and Nvidia 390 drivers but the
  OpenCl is unavailable

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


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


[Kernel-packages] [Bug 1995320] Re: [amdgpu] intermittent green static

2022-11-29 Thread Timo Aaltonen
"radeonsi: invalidate L2 when using dcc stores" is in mesa 22.2.0, and
thus in kinetic, so that's not what is missing

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

Title:
  [amdgpu] intermittent green static

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

Bug description:
  After upgrading from 22.04 to 22.10 I've been seeing some display
  glitches.

  - green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
  - firefox not refreshing when full screen video plays (separate windows, 
separate screens)

  I would guess I probably have the wrong package here, but there's no
  way for me to tell if it's mesa, the kernel, gnome-shell, or something
  else.

  Radeon 6700XT
  Dual displays
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 21:46:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1231 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2019-06-18 (1232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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