[Kernel-packages] [Bug 2062135] Re: Add Cirrus Logic CS35L56 amplifier support

[Chris Chiu]

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

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

Title:
  Add Cirrus Logic CS35L56 amplifier support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  Add a driver for the Cirrus Logic CS35L56 amplifier. This is not a standalone 
HDA device; it provides control of the CS35L56 for systems that use a 
combination of an HDA codec and CS35L56 amplifiers with audio routed through 
the HDA codec. If it's not enabled on HDA codec with this amplifier, there will 
be no sound if play audio via built-in speaker.

  [Fix]
  Backport the CS35L56 driver from kernel 6.9-rc

  [Test Case]
  1. Install the kernel w/ CS35L56 driver enabled 
  2. Install the linux-firmware with latest CS35l56 supported
  3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK

  [Where problems could occur]
  Only affects models which have CS35L56 amplifier. Should be no risk to others.

  
=

  SRU Jusitification for linux-firmware

  [Impact]
  No sound if no CS35L56 firmware even the driver is enabled in Linux kernel.

  [Fix]
  Add release FW binary of CS35L56 to linux-firmware

  [Test Case]
  1. Install the kernel w/ CS35L56 driver enabled 
  2. Install the linux-firmware with latest CS35l56 supported
  3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK

  [Where problems could occur]
  New firmware is only loaded by the CS35L56, we only need to verify it on the 
target platform.

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


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

[Kernel-packages] [Bug 2063399] Re: Add support for Quectel EM160R-GL modem

[AaronMa]

** Also affects: hwe-next/mantic
   Importance: Undecided
   Status: New

** Also affects: hwe-next/jammy
   Importance: Undecided
   Status: New

** No longer affects: hwe-next/jammy

** No longer affects: hwe-next/mantic

** Also affects: hwe-next/jammy
   Importance: Undecided
   Status: New

** Also affects: hwe-next/mantic
   Importance: Undecided
   Status: New

** No longer affects: hwe-next/jammy

** No longer affects: hwe-next/mantic

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

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

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

** Changed in: linux-oem-6.5 (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: hwe-next
 Assignee: (unassigned) => Atlas Yu (pseudoc)

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux-oem-6.5 (Ubuntu Mantic)
   Importance: Undecided => High

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

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

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

** Changed in: linux (Ubuntu Mantic)
   Importance: Undecided => High

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

Title:
  Add support for Quectel EM160R-GL modem

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  In Progress

Bug description:
  [Impact]

  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * The commit only introduces a PID, it won't impact devices which are
  supported originally.

  [Other Info]

  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

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


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

[Kernel-packages] [Bug 2052663] Re: fabric-manager-535 setup fails during install on Grace/Hopper arm64 system running noble

[Mitchell Augustin]

This bug no longer appears to be reproducible on noble with the 6.8
generic kernels, so I have marked it as resolved.

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

Title:
  fabric-manager-535 setup fails during install on Grace/Hopper arm64
  system running noble

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released

Bug description:
  This error occurs on both the standard and largemem variants of the latest 
Noble server build of Ubuntu:
  Ubuntu Noble Numbat (development branch) (GNU/Linux 6.6.0-14-generic-64k 
aarch64) (iso link: 
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20240207.1/noble-live-server-arm64+largemem.iso)
  Ubuntu Noble Numbat (development branch) (GNU/Linux 6.6.0-14-generic aarch64) 
(iso link: 
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20240207/noble-live-server-arm64.iso)
  CPU/GPU: Nvidia Grace/Hopper

  lsb_release -rd: 
  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  Kernel versions affected:
  GNU/Linux 6.6.0-14-generic-64k aarch64
  GNU/Linux 6.6.0-14-generic aarch64

  Package version: nvidia-fabricmanager-535 (535.154.05-0ubuntu1 arm64)

  Expected behavior: Package starts as expected during post-install
  setup steps

  Actual behavior:
  On our grace/hopper system running noble, when installing 
nvidia-fabricmanager-535, the installation froze at 60% twice, along with all 
ssh processes. I am also unable to ssh back into the system after this happens.

  This is the last output I see from my installer shell:
  + apt install -y nvidia-fabricmanager-535
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
nvidia-fabricmanager-535
  0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
  Need to get 1795 kB of archives.
  After this operation, 8679 kB of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports noble/multiverse arm64 
nvidia-fabricmanager-535 arm64 535.154.05-0ubuntu1 [1795 kB]
  Fetched 1795 kB in 1s (2439 kB/s)
  Selecting previously unselected package nvidia-fabricmanager-535.
  (Reading database ... 103745 files and directories currently installed.)
  Preparing to unpack 
.../nvidia-fabricmanager-535_535.154.05-0ubuntu1_arm64.deb ...
  Unpacking nvidia-fabricmanager-535 (535.154.05-0ubuntu1) ...
  Setting up nvidia-fabricmanager-535 (535.154.05-0ubuntu1) ...
  Created symlink 
/etc/systemd/system/multi-user.target.wants/nvidia-fabricmanager.service → 
/lib/systemd/system/nvidia-fabricmanager.service.

  Progress: [ 60%]
  
[#...]

  
  This does not appear to cause a panic/reboot, as I can still interact with 
the console, and it even appears that the apt process is still running in ps 
aux (although it doesn't seem to progress). However, I observe the following 
output in the console that I believe may be related:
  [ 1453.814597] watchdog: BUG: soft lockup - CPU#16 stuck for 670s! 
[(udev-worker):33269]
  [ 1477.814602] watchdog: BUG: soft lockup - CPU#16 stuck for 693s! 
[(udev-worker):33269]
  [ 1501.814606] watchdog: BUG: soft lockup - CPU#16 stuck for 715s! 
[(udev-worker):33269]
  [ 1525.814611] watchdog: BUG: soft lockup - CPU#16 stuck for 738s! 
[(udev-worker):33269]
  [ 1579.666718] rcu: INFO: rcu_preempt detected expedited stalls on 
CPUs/tasks: { 17-...D } 240893 ji
  ffies s: 653 root: 0x2/.
  [ 1579.678114] rcu: blocking rcu_node structures (internal RCU debug): 
l=1:15-29:0x4/.
  [ 1597.814625] watchdog: BUG: soft lockup - CPU#16 stuck for 805s! 
[(udev-worker):33269]
  [ 1621.814630] watchdog: BUG: soft lockup - CPU#16 stuck for 827s! 
[(udev-worker):33269]
  [ 1630.562655] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
  [ 1630.568973] rcu:   17-...0: (1 GPs behind) idle=2444/1/0x4000 
softirq=13696/13700 f
  qs=126842
  [ 1630.578665] rcu:hardirqs   softirqs   csw/system
  [ 1630.584381] rcu:number:0  00
  [ 1630.590109] rcu:   cputime:0  00   ==> 
1110384(ms)
  [ 1630.597458] rcu:   (detected by 20, t=285099 jiffies, g=74061, q=113266 
ncpus=72)

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


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

[Kernel-packages] [Bug 2063399] [NEW] Add support for Quectel EM160R-GL modem

[Atlas Yu]

Public bug reported:

[Impact]

* Add support for Quectel EM160R-GL modem, so the device could be
properly probed.

[Test Plan]

* Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
use` is mht-pci-generic.

[Where problems could occur]

* The commit only introduces a PID, it won't impact devices which are
supported originally.

[Other Info]

* Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
* Lenovo with this device will be enabled by linux-oem-6.5.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

** Description changed:

  [Impact]
  
  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
- The commit only introduces a PID, it won't impact devices which are
+ * The commit only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

** Also affects: hwe-next
   Importance: Undecided
   Status: New

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

Title:
  Add support for Quectel EM160R-GL modem

Status in HWE Next:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New

Bug description:
  [Impact]

  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * The commit only introduces a PID, it won't impact devices which are
  supported originally.

  [Other Info]

  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

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


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

[Kernel-packages] [Bug 2052663] Re: fabric-manager-535 setup fails during install on Grace/Hopper arm64 system running noble

[Mitchell Augustin]

** Changed in: fabric-manager-535 (Ubuntu)
 Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin)

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
 Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin)

** Changed in: fabric-manager-535 (Ubuntu)
   Status: New => Fix Released

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

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
   Status: New => Fix Released

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

Title:
  fabric-manager-535 setup fails during install on Grace/Hopper arm64
  system running noble

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released

Bug description:
  This error occurs on both the standard and largemem variants of the latest 
Noble server build of Ubuntu:
  Ubuntu Noble Numbat (development branch) (GNU/Linux 6.6.0-14-generic-64k 
aarch64) (iso link: 
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20240207.1/noble-live-server-arm64+largemem.iso)
  Ubuntu Noble Numbat (development branch) (GNU/Linux 6.6.0-14-generic aarch64) 
(iso link: 
https://cdimage.ubuntu.com/ubuntu-server/daily-live/20240207/noble-live-server-arm64.iso)
  CPU/GPU: Nvidia Grace/Hopper

  lsb_release -rd: 
  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  Kernel versions affected:
  GNU/Linux 6.6.0-14-generic-64k aarch64
  GNU/Linux 6.6.0-14-generic aarch64

  Package version: nvidia-fabricmanager-535 (535.154.05-0ubuntu1 arm64)

  Expected behavior: Package starts as expected during post-install
  setup steps

  Actual behavior:
  On our grace/hopper system running noble, when installing 
nvidia-fabricmanager-535, the installation froze at 60% twice, along with all 
ssh processes. I am also unable to ssh back into the system after this happens.

  This is the last output I see from my installer shell:
  + apt install -y nvidia-fabricmanager-535
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
nvidia-fabricmanager-535
  0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
  Need to get 1795 kB of archives.
  After this operation, 8679 kB of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports noble/multiverse arm64 
nvidia-fabricmanager-535 arm64 535.154.05-0ubuntu1 [1795 kB]
  Fetched 1795 kB in 1s (2439 kB/s)
  Selecting previously unselected package nvidia-fabricmanager-535.
  (Reading database ... 103745 files and directories currently installed.)
  Preparing to unpack 
.../nvidia-fabricmanager-535_535.154.05-0ubuntu1_arm64.deb ...
  Unpacking nvidia-fabricmanager-535 (535.154.05-0ubuntu1) ...
  Setting up nvidia-fabricmanager-535 (535.154.05-0ubuntu1) ...
  Created symlink 
/etc/systemd/system/multi-user.target.wants/nvidia-fabricmanager.service → 
/lib/systemd/system/nvidia-fabricmanager.service.

  Progress: [ 60%]
  
[#...]

  
  This does not appear to cause a panic/reboot, as I can still interact with 
the console, and it even appears that the apt process is still running in ps 
aux (although it doesn't seem to progress). However, I observe the following 
output in the console that I believe may be related:
  [ 1453.814597] watchdog: BUG: soft lockup - CPU#16 stuck for 670s! 
[(udev-worker):33269]
  [ 1477.814602] watchdog: BUG: soft lockup - CPU#16 stuck for 693s! 
[(udev-worker):33269]
  [ 1501.814606] watchdog: BUG: soft lockup - CPU#16 stuck for 715s! 
[(udev-worker):33269]
  [ 1525.814611] watchdog: BUG: soft lockup - CPU#16 stuck for 738s! 
[(udev-worker):33269]
  [ 1579.666718] rcu: INFO: rcu_preempt detected expedited stalls on 
CPUs/tasks: { 17-...D } 240893 ji
  ffies s: 653 root: 0x2/.
  [ 1579.678114] rcu: blocking rcu_node structures (internal RCU debug): 
l=1:15-29:0x4/.
  [ 1597.814625] watchdog: BUG: soft lockup - CPU#16 stuck for 805s! 
[(udev-worker):33269]
  [ 1621.814630] watchdog: BUG: soft lockup - CPU#16 stuck for 827s! 
[(udev-worker):33269]
  [ 1630.562655] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
  [ 1630.568973] rcu:   17-...0: (1 GPs behind) idle=2444/1/0x4000 
softirq=13696/13700 f
  qs=126842
  [ 1630.578665] rcu:hardirqs   softirqs   csw/system
  [ 1630.584381] rcu:number:0  00
  [ 1630.590109] rcu:   cputime:0  00   ==> 
1110384(ms)
  [ 1630.597458] rcu:   

[Kernel-packages] [Bug 2063308] Re: lenovo p1g5 suspend issues with docking stations

[AaronMa]

In legacy S3, TBT controller can't resume to D0 status.

It should be related to TBT/BIOS firmware.

Log attached.

** Attachment added: "p1g5-s3-tbt-fail-resume-dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+attachment/5770127/+files/p1g5-s3-tbt-fail-resume-dmesg.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/2063308

Title:
  lenovo p1g5 suspend issues with docking stations

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery

  Hello,
  We are having trouble with our lenovo p1 laptops docking stations. When 
waking from suspend on Ubuntu with a docking station is an issue for some users 
even with Intel AMT disabled in BIOS.
  The exact steps to reproduce are as follows:
  1) Suspend/sleep the laptop
  2) Plug the docking station into the laptop
  3) Wake the laptop

  The sleep settings in BIOS are set to Linux S3. Docking station
  issues, such as Ethernet not working after waking, do not occur with
  Windows/Linux sleep settings, but the laptop doesn't properly suspend
  processes in Windows/Linux sleep mode and will overheat the laptop
  when in an enclosed space such as a bag. Linux S3 is the only way
  we've found laptops to not overheat after suspending, but we that
  makes the dock inoperable after waking from suspend.

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


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

[Kernel-packages] [Bug 2063308] Re: lenovo p1g5 suspend issues with docking stations

[AaronMa]

BIOS N3JET33W (1.17 ), EC N3JHT22W, ME fw 1.25.1932
BIOS N3JET38W (1.22 ), EC N3JHT24W, ME fw 1.25.1932

Both Legacy S3 and s2idle power consumption are 1.1w.

After update ME fw to 1.27.2176 via fwupdmgr.
s2idle power consumption is increased to 2.2w.

ME fw details:
21DFZA2YUS
│
└─Intel Management Engine:
  │   Device ID:  632acf4927c0b5fb53519d6beed3b60adb73f1d5
  │   Previous version:   1.25.1932
  │   Update State:   Success
  │   Last modified:  2024-04-25 02:09
  │   GUID:   2d9ea625-256b-7882-2103-da49b102ef33
  │   Device Flags:   • Internal device
  │   • Updatable
  │   • System requires external power source
  │   • Supported on remote server
  │   • Needs a reboot after installation
  │   • Device is usable for the duration of the update
  │ 
  └─ThinkPad P1 Gen5 X1 Extreme Gen5 dTBT Vpro:
New version:  1.27.2176
Remote ID:lvfs
Release ID:   83203
Summary:  Lenovo Lenovo ThinkPad P1 Gen5 X1 Extreme Gen5 
Corporate ME Firmware
License:  Proprietary
Size: 13.3 MB
Created:  2024-02-21
Urgency:  High
Details:  
https://pcsupport.lenovo.com/de/en/search?query=N3JRO11W
Vendor:   Lenovo
Description:  
Lenovo ThinkPad P1 Gen5 X1 Extreme Gen5 Corporate ME Firmware

For dTBT Vpro (SWG Vpro System)

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

Title:
  lenovo p1g5 suspend issues with docking stations

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery

  Hello,
  We are having trouble with our lenovo p1 laptops docking stations. When 
waking from suspend on Ubuntu with a docking station is an issue for some users 
even with Intel AMT disabled in BIOS.
  The exact steps to reproduce are as follows:
  1) Suspend/sleep the laptop
  2) Plug the docking station into the laptop
  3) Wake the laptop

  The sleep settings in BIOS are set to Linux S3. Docking station
  issues, such as Ethernet not working after waking, do not occur with
  Windows/Linux sleep settings, but the laptop doesn't properly suspend
  processes in Windows/Linux sleep mode and will overheat the laptop
  when in an enclosed space such as a bag. Linux S3 is the only way
  we've found laptops to not overheat after suspending, but we that
  makes the dock inoperable after waking from suspend.

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


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

[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

seems 6.6.x has this in addition for apply the "thermal: trip: Drop
redundant trips check from for_each_thermal_trip()"

thermal: core: Rework and rename __for_each_thermal_trip()

Rework the currently unused __for_each_thermal_trip() to pass original
pointers to struct thermal_trip objects to the callback, so it can be
used for updating trip data (e.g. temperatures), rename it to
for_each_thermal_trip() and make it available to modular drivers.

Suggested-by: Daniel Lezcano 
Signed-off-by: Rafael J. Wysocki 

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

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are no journal logs existed when it boot with the 6.5.0-33
  kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

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


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

[Kernel-packages] [Bug 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver

[Chris Chiu]

** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5

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

Title:
  Fix random HuC/GuC initialization failure of Intel i915 driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.8 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux-oem-6.8 source package in Jammy:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid
Status in linux-oem-6.8 source package in Noble:
  New

Bug description:
  [Impact]
  i915 error can sometimes be found in kernel message when booting the machine 
w/ power unplugged
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5)
  kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, 
declaring it wedged!
  The GPU won't work with this failure

  [Fix]
  Backport the upatream fix for allowing slow HuC loading. 

  [Test]
  1. Unplug the power of the laptop and make sure it's charged by battery
  2. Cold boot or Warm boot the machine and check the GuC init fail message.
  3. Go to settings - > about --> graphics to make sure the GPU information is 
correct every boot.

  [Where problems could occur]
  Simply increase the loading time of HuC still get a working system. Should be 
low risk of regression.

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


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

[Kernel-packages] [Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[J K]

If I choose Xorg then I still get that bug

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

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2024
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1UET46W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21B4S4QB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76465 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.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
  dmi.product.family: ThinkPad L13 Gen 3
  dmi.product.name: 21B4S4QB00
  dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
  dmi.product.version: ThinkPad L13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

here is i915 failed to boot in the same way. you can see the i915 kernel
driver does not finish until much after sddm starts

** Attachment added: "i915-fail-boot.txt"
   
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770118/+files/i915-fail-boot.txt

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

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  New
Status in SDDM:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

here is i915 with a successfull boot. the i915 driver finishes starting
before sddm starts.

** Attachment added: "i915-successfull-boot.txt"
   
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770119/+files/i915-successfull-boot.txt

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

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  New
Status in SDDM:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

I am hitting this on i915 as well with the same 50-75% frequency.

I think this need to be upgraded to critical status (at least for non
GDM login managers where no mitigation exists) and potentially release
blocker depending on how widespread this issue is.

Devices I have confirmed affected by this:
AMD Framework 13
HP Spectre X360

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

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  New
Status in SDDM:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2037335] Re: kernel leaking TCP_MEM

[Launchpad Bug Tracker]

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

** Changed in: linux-meta-aws-6.2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  kernel leaking TCP_MEM

Status in linux-meta-aws-6.2 package in Ubuntu:
  Confirmed

Bug description:
  We are running our Kafka brokers on Jammy on ARM64. Previous they were
  on kernel version 5.15.0-1028-aws, but a few weeks ago we built a new
  AMI and it picked up 6.2.0-1009-aws, and we have also upgraded to
  6.2.0-1012-aws and found the same problem.

  What we expected to happen:
  TCP memory (TCP_MEM) to fluctuate but stay relatively low (on a busy 
production broker running 5.15.0-1028-aws, we average 1900 pages over a 24 hour 
period)

  What happened instead:
  TCP memory (TCP_MEM) continues to rise until hitting the limit (1.5 million 
pages as configured currently). At this point, the broker is no longer able to 
properly create new connections and we start seeing "kernel: TCP: out of memory 
-- consider tuning tcp_mem" in dmesg output. If allowed to continue, the broker 
will eventually isolate itself from the rest of the cluster since it can't talk 
to the other brokers.

  Attached is a graph of the average TCP memory usage per kernel version
  for our production environment over the past 24 hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-aws 6.2.0.1012.12~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-1012.12~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1012-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-east-1
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Sep 25 20:56:02 2023
  Ec2AMI: ami-0b9c5aafc5b2a4725
  Ec2AMIManifest: (unknown)
  Ec2Architecture: arm64
  Ec2AvailabilityZone: us-east-1b
  Ec2Imageid: ami-0b9c5aafc5b2a4725
  Ec2InstanceType: im4gn.4xlarge
  Ec2Instancetype: im4gn.4xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-east-1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-aws-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws-6.2/+bug/2037335/+subscriptions


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

[Kernel-packages] [Bug 2037335] Re: kernel leaking TCP_MEM

[Terra Field]

Thank you, that is great to hear!

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

Title:
  kernel leaking TCP_MEM

Status in linux-meta-aws-6.2 package in Ubuntu:
  Confirmed

Bug description:
  We are running our Kafka brokers on Jammy on ARM64. Previous they were
  on kernel version 5.15.0-1028-aws, but a few weeks ago we built a new
  AMI and it picked up 6.2.0-1009-aws, and we have also upgraded to
  6.2.0-1012-aws and found the same problem.

  What we expected to happen:
  TCP memory (TCP_MEM) to fluctuate but stay relatively low (on a busy 
production broker running 5.15.0-1028-aws, we average 1900 pages over a 24 hour 
period)

  What happened instead:
  TCP memory (TCP_MEM) continues to rise until hitting the limit (1.5 million 
pages as configured currently). At this point, the broker is no longer able to 
properly create new connections and we start seeing "kernel: TCP: out of memory 
-- consider tuning tcp_mem" in dmesg output. If allowed to continue, the broker 
will eventually isolate itself from the rest of the cluster since it can't talk 
to the other brokers.

  Attached is a graph of the average TCP memory usage per kernel version
  for our production environment over the past 24 hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-aws 6.2.0.1012.12~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-1012.12~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1012-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-east-1
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Sep 25 20:56:02 2023
  Ec2AMI: ami-0b9c5aafc5b2a4725
  Ec2AMIManifest: (unknown)
  Ec2Architecture: arm64
  Ec2AvailabilityZone: us-east-1b
  Ec2Imageid: ami-0b9c5aafc5b2a4725
  Ec2InstanceType: im4gn.4xlarge
  Ec2Instancetype: im4gn.4xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-east-1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-aws-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws-6.2/+bug/2037335/+subscriptions


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[Mario Limonciello]

For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.

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

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  New
Status in SDDM:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2058752] Re: ath11k high jitter and packet loss when operating in 802.11ax mode

[Andrea Ieri]

unfortunately the problem is not actually gone in noble. I have upgraded
to the beta and are having significant but intermittent problems. On
6.8.0-31-generic I get periods of normal traffic mixed with 100% packet
loss for some seconds. This looks as follows:

64 bytes from 192.168.16.77: icmp_seq=2622 ttl=64 time=2.47 ms
64 bytes from 192.168.16.77: icmp_seq=2623 ttl=64 time=2.80 ms
64 bytes from 192.168.16.77: icmp_seq=2624 ttl=64 time=2.77 ms
>From 192.168.16.231 icmp_seq=2637 Destination Host Unreachable
>From 192.168.16.231 icmp_seq=2638 Destination Host Unreachable
>From 192.168.16.231 icmp_seq=2639 Destination Host Unreachable
>From 192.168.16.231 icmp_seq=2640 Destination Host Unreachable
>From 192.168.16.231 icmp_seq=2644 Destination Host Unreachable
>From 192.168.16.231 icmp_seq=2645 Destination Host Unreachable
64 bytes from 192.168.16.77: icmp_seq=2646 ttl=64 time=162 ms
64 bytes from 192.168.16.77: icmp_seq=2647 ttl=64 time=1.95 ms
64 bytes from 192.168.16.77: icmp_seq=2648 ttl=64 time=44.3 ms
64 bytes from 192.168.16.77: icmp_seq=2649 ttl=64 time=143 ms
64 bytes from 192.168.16.77: icmp_seq=2650 ttl=64 time=2.37 ms
64 bytes from 192.168.16.77: icmp_seq=2651 ttl=64 time=151 ms
64 bytes from 192.168.16.77: icmp_seq=2652 ttl=64 time=2.69 ms
64 bytes from 192.168.16.77: icmp_seq=2653 ttl=64 time=6.66 ms
64 bytes from 192.168.16.77: icmp_seq=2654 ttl=64 time=47.2 ms
64 bytes from 192.168.16.77: icmp_seq=2655 ttl=64 time=40.1 ms
64 bytes from 192.168.16.77: icmp_seq=2656 ttl=64 time=44.9 ms
64 bytes from 192.168.16.77: icmp_seq=2657 ttl=64 time=1583 ms
64 bytes from 192.168.16.77: icmp_seq=2658 ttl=64 time=560 ms
64 bytes from 192.168.16.77: icmp_seq=2659 ttl=64 time=1506 ms
64 bytes from 192.168.16.77: icmp_seq=2660 ttl=64 time=457 ms
64 bytes from 192.168.16.77: icmp_seq=2661 ttl=64 time=809 ms
64 bytes from 192.168.16.77: icmp_seq=2662 ttl=64 time=3014 ms
64 bytes from 192.168.16.77: icmp_seq=2663 ttl=64 time=2005 ms
64 bytes from 192.168.16.77: icmp_seq=2664 ttl=64 time=982 ms
64 bytes from 192.168.16.77: icmp_seq=2665 ttl=64 time=2.47 ms
64 bytes from 192.168.16.77: icmp_seq=2666 ttl=64 time=2471 ms
64 bytes from 192.168.16.77: icmp_seq=2667 ttl=64 time=1464 ms
64 bytes from 192.168.16.77: icmp_seq=2668 ttl=64 time=440 ms
64 bytes from 192.168.16.77: icmp_seq=2669 ttl=64 time=54.2 ms
64 bytes from 192.168.16.77: icmp_seq=2670 ttl=64 time=2.35 ms


If I find some time I'll try rerunning the same test from windows.

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

Title:
  ath11k high jitter and packet loss when operating in 802.11ax mode

Status in linux package in Ubuntu:
  New

Bug description:
  On 6.5.0-26-generic, my QCNFA765 cannot really operate in 802.11ax
  mode.

  I have a Thinkpad P16s Gen 2 with a (soldered, sadly) QCNFA765 card, which 
uses the ath11k driver.
  I also have a Ruckus R650 AP, which supports wifi6.

  Connecting the two and pinging the AP yields the following:

  ```
  64 bytes from 192.168.16.77: icmp_seq=45 ttl=64 time=22.4 ms
  64 bytes from 192.168.16.77: icmp_seq=46 ttl=64 time=29.6 ms
  64 bytes from 192.168.16.77: icmp_seq=47 ttl=64 time=26.8 ms
  64 bytes from 192.168.16.77: icmp_seq=48 ttl=64 time=2174 ms
  64 bytes from 192.168.16.77: icmp_seq=49 ttl=64 time=1158 ms
  64 bytes from 192.168.16.77: icmp_seq=50 ttl=64 time=130 ms
  64 bytes from 192.168.16.77: icmp_seq=51 ttl=64 time=503 ms
  64 bytes from 192.168.16.77: icmp_seq=54 ttl=64 time=1832 ms
  64 bytes from 192.168.16.77: icmp_seq=55 ttl=64 time=808 ms
  64 bytes from 192.168.16.77: icmp_seq=56 ttl=64 time=9.32 ms
  64 bytes from 192.168.16.77: icmp_seq=57 ttl=64 time=2.11 ms
  64 bytes from 192.168.16.77: icmp_seq=58 ttl=64 time=25.6 ms
  64 bytes from 192.168.16.77: icmp_seq=59 ttl=64 time=30.9 ms
  64 bytes from 192.168.16.77: icmp_seq=60 ttl=64 time=95.6 ms
  ^C
  --- 192.168.16.77 ping statistics ---
  60 packets transmitted, 55 received, 8.3% packet loss, time 59273ms
  rtt min/avg/max/mdev = 2.105/275.084/2344.792/560.334 ms, pipe 3
  ```

  Those periodic bursts of >1s latency make some webpages fail to load
  and videochats unusable.

  No interference is present in my channel of choice.

  Nothing interesting is printed in dmesg while the above occurs.

  The above does not happen if:
  * I disable wifi 6 in the AP
  * I ping a wifi 5 AP (I also have an older R710, which is a 802.11ac AP)
  * I ping the R650 in wifi 6 mode from a AX210 on kernel 6.2
  * I ping the R650 from a completely different OS and device (e.g. Android)

  I'll test with a 24.04 daily image next.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: 

[Kernel-packages] [Bug 2063376] Re: linux-source-6.5.0 will install kernel 6.5.13

[Gero Schwäricke]

** Tags added: jammy

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

Title:
  linux-source-6.5.0 will install kernel 6.5.13

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

Bug description:
  Hi,

  As the summary suggests, when I install linux-source-6.5.0 it will
  actually install the 6.5.13 kernel sources. Querying

apt show linux-source-6.5.0

  reports:

[...]
Description: Linux kernel source for version 6.5.0 with Ubuntu patches
 This package provides the source code for the Linux kernel version
 6.5.0.
[...]

  So providing 6.5.13 seems like a bug to me. But it's my first time
  trying to build a kernel module for Debian myself, so I'm quite unsure
  what's happening here. Any pointers welcome.

  Here's what I did:

sudo su
apt install linux-source-6.5.0
cd /usr/src
tar xjf linux-source-6.5.0.tar.bz2
head linux-source-6.5.0/Makefile

  which shows:

# SPDX-License-Identifier: GPL-2.0
VERSION = 6
PATCHLEVEL = 5
SUBLEVEL = 13
EXTRAVERSION =
NAME = Hurr durr I'ma ninja sloth

# *DOCUMENTATION*
# To see a list of typical targets execute "make help"
# More info can be located in ./README

  I don't know how or why this happens, but I found the following in
  dmesg

$ dmesg | grep 6.5.13
[0.00] Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
14:39:20 UTC 2 (Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13)

  If I'm decyphering this correctly my running 6.5.0 kernel was build on
  a machine running 6.5.13. Is it possible that this machine by accident
  uploaded it's own kernel source tree rather than the built kernel's?

$ lsb_release -rd
Description:Linux Mint 21.3
Release:21.3

$ apt-cache policy linux-source-6.5.0
linux-source-6.5.0:
  Installed: 6.5.0-28.29~22.04.1
  Candidate: 6.5.0-28.29~22.04.1
  Version table:
 *** 6.5.0-28.29~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
100 /var/lib/dpkg/status
 6.5.0-27.28~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-26.26~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-25.25~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-21.21~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-18.18~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-17.17~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-15.15~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 

[Kernel-packages] [Bug 2063376] [NEW] linux-source-6.5.0 will install kernel 6.5.13

[Gero Schwäricke]

Public bug reported:

Hi,

As the summary suggests, when I install linux-source-6.5.0 it will
actually install the 6.5.13 kernel sources. Querying

  apt show linux-source-6.5.0

reports:

  [...]
  Description: Linux kernel source for version 6.5.0 with Ubuntu patches
   This package provides the source code for the Linux kernel version
   6.5.0.
  [...]

So providing 6.5.13 seems like a bug to me. But it's my first time
trying to build a kernel module for Debian myself, so I'm quite unsure
what's happening here. Any pointers welcome.

Here's what I did:

  sudo su
  apt install linux-source-6.5.0
  cd /usr/src
  tar xjf linux-source-6.5.0.tar.bz2
  head linux-source-6.5.0/Makefile

which shows:

  # SPDX-License-Identifier: GPL-2.0
  VERSION = 6
  PATCHLEVEL = 5
  SUBLEVEL = 13
  EXTRAVERSION =
  NAME = Hurr durr I'ma ninja sloth
  
  # *DOCUMENTATION*
  # To see a list of typical targets execute "make help"
  # More info can be located in ./README

I don't know how or why this happens, but I found the following in dmesg

  $ dmesg | grep 6.5.13
  [0.00] Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
14:39:20 UTC 2 (Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13)

If I'm decyphering this correctly my running 6.5.0 kernel was build on a
machine running 6.5.13. Is it possible that this machine by accident
uploaded it's own kernel source tree rather than the built kernel's?

  $ lsb_release -rd
  Description:  Linux Mint 21.3
  Release:  21.3

  $ apt-cache policy linux-source-6.5.0
  linux-source-6.5.0:
Installed: 6.5.0-28.29~22.04.1
Candidate: 6.5.0-28.29~22.04.1
Version table:
   *** 6.5.0-28.29~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
  100 /var/lib/dpkg/status
   6.5.0-27.28~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   6.5.0-26.26~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   6.5.0-25.25~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   6.5.0-21.21~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   6.5.0-18.18~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   6.5.0-17.17~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   6.5.0-15.15~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
   6.5.0-14.14~22.04.1 500
  500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
  500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages

Best,
Gero

** Affects: 

[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2062667

** Tags added: iso-testing

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

** Changed in: sddm
   Status: Unknown => New

** Changed in: plymouth
   Status: Unknown => 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/2063143

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  New
Status in SDDM:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

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

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

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

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

** Changed in: protection-domain-mapper (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Dave Jones]

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Kernel-packages] [Bug 2063337] Re: RM: noble linux-meta/linux-restricted-modules incorrectly expressing -oem-24.04 variants

[Andy Whitcroft]

+ remove-package -y -m Bad variant --binary --architecture amd64 
linux-cloud-tools-generic-oem-24.04 linux-cloud-tools-virtual-oem-24.04 
linux-generic-oem-24.04 linux-headers-generic-oem-24.04 
linux-headers-virtual-oem-24.04 linux-image-extra-virtual-oem-24.04 
linux-image-generic-oem-24.04 linux-image-uc-generic-oem-24.04 
linux-image-virtual-oem-24.04 linux-modules-ipu6-generic-oem-24.04 
linux-modules-ivsc-generic-oem-24.04 linux-modules-iwlwifi-generic-oem-24.04 
linux-tools-generic-oem-24.04 linux-tools-virtual-oem-24.04 
linux-virtual-oem-24.04
Removing packages from noble:
linux-cloud-tools-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-cloud-tools-virtual-oem-24.04 6.8.0-31.31 in noble amd64
linux-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-headers-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-headers-virtual-oem-24.04 6.8.0-31.31 in noble amd64
linux-image-extra-virtual-oem-24.04 6.8.0-31.31 in noble amd64
linux-image-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-image-uc-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-image-virtual-oem-24.04 6.8.0-31.31 in noble amd64
linux-modules-ipu6-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-modules-ivsc-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-modules-iwlwifi-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-tools-generic-oem-24.04 6.8.0-31.31 in noble amd64
linux-tools-virtual-oem-24.04 6.8.0-31.31 in noble amd64
linux-virtual-oem-24.04 6.8.0-31.31 in noble amd64
Comment: Bad variant
15 packages successfully removed.
+ remove-package -y -m Bad variant --binary --architecture arm64 
linux-generic-64k-oem-24.04 linux-generic-oem-24.04 
linux-headers-generic-64k-oem-24.04 linux-headers-generic-oem-24.04 
linux-headers-virtual-oem-24.04 linux-image-extra-virtual-oem-24.04 
linux-image-generic-64k-oem-24.04 linux-image-generic-oem-24.04 
linux-image-uc-generic-oem-24.04 linux-image-virtual-oem-24.04 
linux-tools-generic-64k-oem-24.04 linux-tools-generic-oem-24.04 
linux-tools-virtual-oem-24.04 linux-virtual-oem-24.04
Removing packages from noble:
linux-generic-64k-oem-24.04 6.8.0-31.31 in noble arm64
linux-generic-oem-24.04 6.8.0-31.31 in noble arm64
linux-headers-generic-64k-oem-24.04 6.8.0-31.31 in noble arm64
linux-headers-generic-oem-24.04 6.8.0-31.31 in noble arm64
linux-headers-virtual-oem-24.04 6.8.0-31.31 in noble arm64
linux-image-extra-virtual-oem-24.04 6.8.0-31.31 in noble arm64
linux-image-generic-64k-oem-24.04 6.8.0-31.31 in noble arm64
linux-image-generic-oem-24.04 6.8.0-31.31 in noble arm64
linux-image-uc-generic-oem-24.04 6.8.0-31.31 in noble arm64
linux-image-virtual-oem-24.04 6.8.0-31.31 in noble arm64
linux-tools-generic-64k-oem-24.04 6.8.0-31.31 in noble arm64
linux-tools-generic-oem-24.04 6.8.0-31.31 in noble arm64
linux-tools-virtual-oem-24.04 6.8.0-31.31 in noble arm64
linux-virtual-oem-24.04 6.8.0-31.31 in noble arm64
Comment: Bad variant
14 packages successfully removed.
+ remove-package -y -m Bad variant --binary --architecture armhf 
linux-generic-oem-24.04 linux-headers-generic-oem-24.04 
linux-headers-virtual-oem-24.04 linux-image-generic-oem-24.04 
linux-image-virtual-oem-24.04 linux-tools-generic-oem-24.04 
linux-tools-virtual-oem-24.04 linux-virtual-oem-24.04
Removing packages from noble:
linux-generic-oem-24.04 6.8.0-31.31 in noble armhf
linux-headers-generic-oem-24.04 6.8.0-31.31 in noble armhf
linux-headers-virtual-oem-24.04 6.8.0-31.31 in noble armhf
linux-image-generic-oem-24.04 6.8.0-31.31 in noble armhf
linux-image-virtual-oem-24.04 6.8.0-31.31 in noble armhf
linux-tools-generic-oem-24.04 6.8.0-31.31 in noble armhf
linux-tools-virtual-oem-24.04 6.8.0-31.31 in noble armhf
linux-virtual-oem-24.04 6.8.0-31.31 in noble armhf
Comment: Bad variant
8 packages successfully removed.
+ remove-package -y -m Bad variant --binary --architecture ppc64el 
linux-generic-oem-24.04 linux-headers-generic-oem-24.04 
linux-headers-virtual-oem-24.04 linux-image-extra-virtual-oem-24.04 
linux-image-generic-oem-24.04 linux-image-virtual-oem-24.04 
linux-tools-generic-oem-24.04 linux-tools-virtual-oem-24.04 
linux-virtual-oem-24.04
Removing packages from noble:
linux-generic-oem-24.04 6.8.0-31.31 in noble ppc64el
linux-headers-generic-oem-24.04 6.8.0-31.31 in noble ppc64el
linux-headers-virtual-oem-24.04 6.8.0-31.31 in noble ppc64el
linux-image-extra-virtual-oem-24.04 6.8.0-31.31 in noble ppc64el
linux-image-generic-oem-24.04 6.8.0-31.31 in noble ppc64el
linux-image-virtual-oem-24.04 6.8.0-31.31 in noble ppc64el
linux-tools-generic-oem-24.04 6.8.0-31.31 in noble ppc64el
linux-tools-virtual-oem-24.04 6.8.0-31.31 in noble ppc64el

[Kernel-packages] [Bug 2056387] Re: [T14 Gen 3 AMD] Fail to suspend/resume for the second time

[Launchpad Bug Tracker]

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

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

Title:
  [T14 Gen 3 AMD] Fail to suspend/resume for the second time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had a similar issue before:
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
  However, I haven't seen the issue with later kernels until getting 
6.8.0-11.11+1 recently.

  * 6.8.0-11 - fails to suspend/resume for the second time although the first 
suspend/resume works
  * 6.6.0-14 - no issue in terms of suspend/resume

  One thing worth noting is that connecting an external monitor or not
  might be a key to trigger this issue. I cannot reproduce it when an
  external monitor (through USB-C to HDMI) is not connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-11-generic 6.8.0-11.11
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  7 11:17:31 2024
  InstallationDate: Installed on 2024-01-08 (59 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  MachineType: LENOVO 21CFCTO1WW
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2023
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET73W (1.49 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET73W(1.49):bd11/30/2023:br1.49:efr1.32:svnLENOVO:pn21CFCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21CFCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CFCTO1WW
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

** Bug watch added: github.com/sddm/sddm/issues #1917
   https://github.com/sddm/sddm/issues/1917

** Also affects: sddm via
   https://github.com/sddm/sddm/issues/1917
   Importance: Unknown
   Status: Unknown

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

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  Unknown
Status in SDDM:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

AMD kernel developer wants to classify this is as both SDDM bug and
plymouth bug https://gitlab.freedesktop.org/drm/amd/-/issues/3341.
amdgpu kernel driver is not ready by the time that sddm and plymouth are
started in some cases (race condition). Marking this as a sddm and
plymouth bug (in addition to linux) because of this.

To me it seems that at least a systemd service should be handling
blocking starting GUI userspace services until the kernel drivers are
actually loaded but that is just my thought. I guess the AMD developer
sees this the same way you do Daniel.

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

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

** No longer affects: plymouth (Ubuntu)

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

** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #253
   https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/253

** Also affects: plymouth via
   https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/253
   Importance: Unknown
   Status: Unknown

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

Title:
  Frequent boot to black display

Status in Linux:
  New
Status in Plymouth:
  Unknown
Status in SDDM:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in plymouth package in Ubuntu:
  New
Status in sddm package in Ubuntu:
  New

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  

[Kernel-packages] [Bug 2063228] Re: screen sometimes blinking

[dom21121]

Sorry but after applying the setting the screen flashing continues...

** Attachment added: "VID_20240424_212658.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+attachment/5770114/+files/VID_20240424_212658.mp4

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

Title:
  screen sometimes blinking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Pavilion Laptop 14-ce2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2022
  dmi.bios.release: 15.27
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84BB
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 14-ce2xxx
  dmi.product.sku: 8KZ34EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel

[Joseph Salisbury]

** Changed in: linux (Ubuntu Focal)
   Status: Triaged => Won't Fix

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

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

Title:
  Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4
  Ubuntu 20.04 kernel

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

Bug description:
  We in the Canonical Public Cloud team have received report from our
  colleagues in Google regarding a potential performance regression with
  the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were
  performed using the linux-gkeop and linux-gkeop-5.15 kernels.

  I have verified with the generic Ubuntu 20.04 5.4 linux-generic and
  the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels.

  The tests were run using `fio`

  fio commands:

  * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`
  * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`

  
  My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the 
results are below:

  Using 5.4 kernel

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.4.0-164-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] 
  fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov  2 09:15:22 2023
write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets
  slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61
  clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38
   lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80
  clat percentiles (usec):
   |  1.00th=[  775],  5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024],
   | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261],
   | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932],
   | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676],
   | 99.99th=[32113]
 bw (  MiB/s): min=  524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, 
samples=4232
 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, 
samples=4232
lat (nsec)   : 500=0.01%, 750=0.01%, 1000=0.01%
lat (usec)   : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01%
lat (usec)   : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93%
lat (msec)   : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07%
lat (msec)   : 100=0.01%
cpu  : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103
IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
   submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.0%
   complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.1%
   issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0
   latency   : target=0, window=0, percentile=100.00%, depth=128

  Run status group 0 (all jobs):
WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), 
io=320GiB (344GB), run=264837-264837msec

  Disk stats (read/write):
sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, 
util=100.00%
  ```

  
  After upgrading to linux-generic-hwe-20.04 kernel and rebooting

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.15.0-88-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 1 (f=1): [_(7),W(1)][100.0%][w=410MiB/s][w=105k IOPS][eta 00m:00s]
  fiojob1: (groupid=0, jobs=8): err= 0: pid=1438: Thu Nov  2 09:46:49 2023
write: IOPS=155k, BW=605MiB/s (634MB/s)(320GiB/541949msec); 0 zone resets
  slat (nsec): min=660, max=325426k, avg=10351.04, stdev=232438.50
  clat (nsec): min=1100, max=782743k, avg=6595008.67, stdev=6290570.04
   lat (usec): min=86, max=782748, avg=6606.08, stdev=6294.03
  clat percentiles (usec):
   |  1.00th=[   914],  5.00th=[  2180], 10.00th=[  2802], 20.00th=[  3556],
   | 30.00th=[  4178], 

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Jens Glathe]

Hi @xypron,

my /etc/initramfs-tools/modules is this:

---
pwm_bl
phy_qcom_qmp_pcie
pcie_qcom
phy_qcom
qmp_pcie
phy_qcom_qmp_combo
qrtr
drm-dp-aux-bus
phy_qcom_edp
gpio_sbu_mux
i2c_hid_of
i2c_qcom_geni
pmic_glink_altmode
leds_qcom_lpg
qcom_q6v5_pas
panel-edp
gpucc_sc8280xp
dispcc_sc8280xp
msm
nvme
usb_storage
uas
--

I had severe issues booting from type-c due to late-loading of
qcadsp8280.mbn, therefore I experimented a little until found. I am not
familiar with the installer at all, so I'm afraid I'm no help there. But
the loading of the firmwares goes hand in hand with my /etc/initramfs-
tools/hooks/x13s-firmware script:

-
#!/bin/sh

set -e

PREREQ=""

prereqs()
{
echo "$PREREQ"
}

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

. /usr/share/initramfs-tools/hook-functions

mv
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn.disabled
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn

# Define a list of firmware files to be included
FIRMWARE_FILES="\
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qccdsp8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcdxkmsuc8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcvss8280.mbn \
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcslpi8280.mbn \
/lib/firmware/qcom/a660_sqe.fw.zst \
/lib/firmware/qcom/a660_gmu.bin.zst"

# Copy each firmware file to initramfs
for file in $FIRMWARE_FILES; do
dir=$(dirname "$file")
mkdir -p "${DESTDIR}/${dir}"
cp "${file}" "${DESTDIR}/${dir}/"
done

mv /lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn
/lib/firmware/updates/qcom/sc8280xp/LENOVO/21BX/qcadsp8280.mbn.disabled

---

This ensures the crucial files (and some not so crucial) are in the
initramfs and accessible before rootfs can be mounted. My boot tests
found that you actually run into trouble occasionally when you:

- have a slow boot device, like the stick plugged in swapped condition (then 
it's USB-2 only)
- have qcadsp8280.mbn in the rootfs as well. "Late" attempts to load this blob 
(after mounting rootfs from type-c) will lead to the [VBUS 
issue](https://gitlab.com/postmarketOS/pmaports/-/blob/master/device/testing/firmware-lenovo-yoga-5g/APKBUILD?ref_type=heads#L44-46)
 which I experienced for a few ... weeks ... and pulled my hair out. 
For reference: https://github.com/jglathe/linux_ms_dev_kit/discussions/14 There 
is also an X13s image that boots reliably from type-c: 
https://drive.google.com/file/d/1e8LA6o-EKKet3_sCQqXR4lOVE_TgOVNI/view?usp=sharing
 But, danger. It is deliberately rooted, root pw is FsecuritY! and can be 
reached via ssh. It is for debug purposes.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: 

[Kernel-packages] [Bug 2063365] [NEW] brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52

[Paul Larson]

Public bug reported:

On the noble server release candidate image testing, I noticed that the
automated wifi tests we run for certification were passing, but they
logged some errors from dmesg related to brcmfmac. The log is filled
with lots of these errors:

kern  :err   : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set 
chanspec 0x100c fail, reason -52
kern  :err   : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set 
chanspec 0x100d fail, reason -52
kern  :err   : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set 
chanspec 0x100e fail, reason -52
...

To be clear, it was able to get a wifi connection, but something seems off with 
this. 
I've noticed this on rpi4 and rpi5 so far, not sure about others yet

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


** Tags: iso-testing

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

Title:
  brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  On the noble server release candidate image testing, I noticed that
  the automated wifi tests we run for certification were passing, but
  they logged some errors from dmesg related to brcmfmac. The log is
  filled with lots of these errors:

  kern  :err   : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set 
chanspec 0x100c fail, reason -52
  kern  :err   : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set 
chanspec 0x100d fail, reason -52
  kern  :err   : [Wed Apr 24 11:19:12 2024] brcmfmac: brcmf_set_channel: set 
chanspec 0x100e fail, reason -52
  ...

  To be clear, it was able to get a wifi connection, but something seems off 
with this. 
  I've noticed this on rpi4 and rpi5 so far, not sure about others yet

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


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

[Kernel-packages] [Bug 1987052] Re: Running MySQL8 in Docker on ZFS only works if you have ZFS 2.1.5. Ubuntu 22.04 only has 2.1.4 right now.

[Heitor Alves de Siqueira]

** Changed in: zfs-linux (Ubuntu)
   Status: New => Fix Released

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

Title:
  Running MySQL8 in Docker on ZFS only works if you have ZFS 2.1.5.
  Ubuntu 22.04 only has 2.1.4 right now.

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Running MySQL 8 using Docker on a ZFS system currently is not possible due to 
a bug in ZFS.
  It has been fixed in ZFS 2.1.5, but jammy-updates is still on 2.1.4

  Can someone please update from 2.1.4 to 2.1.5?

  MySQL 8 is a popular database and running using Docker (and ZFS) is
  more and more common.

  More details on this and confirmed by the MySQL Docker team:
  https://github.com/docker-library/mysql/issues/868

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


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

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Aaron Honeycutt]

I've seen a report of the 6.9-rc5 kernel booting on the hardware. I have
also had issues with Fedora Rawhide and NixOS booting on the hardware so
I think it is an upstream issue with the kernel.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Heinrich Schuchardt]

@glathe

We used to have packate linux-image-laptop-23.10 which provided file
/usr/share/initramfs-tools/modules.d/laptop. This contained
qcom_q6v5_pas.  It have recreated this file manually but this does not
resolve my problems.

Which follow up package provided with the X13s installer image defines
the modules to be included in the initrd?

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1980848] Re: arc_summary doesn't work with HWE kernel 5.15

[Heitor Alves de Siqueira]

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

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

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

** Changed in: zfs-linux (Ubuntu Focal)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

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

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

Title:
  arc_summary doesn't work with HWE kernel 5.15

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  In Progress

Bug description:
  # Issue description

  `arc_summary` no longer works with kernel 5.15. It used to work with
  previous kernel like 5.13.

  # Steps to reproduce

  1) setup 20.04 with HWE kernel 5.15
  2) install `zfsutils-linux`
  3) run `arc_summary`
  $ arc_summary 
  Traceback (most recent call last):
File "/usr/sbin/arc_summary", line 875, in 
  main()
File "/usr/sbin/arc_summary", line 826, in main
  kstats = get_kstats()
File "/usr/sbin/arc_summary", line 259, in get_kstats
  with open(PROC_PATH+section, 'r') as proc_location:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/proc/spl/kstat/zfs/xuio_stats'


  Indeed, the xuio_stats file isn't there anymore:
  $ ll /proc/spl/kstat/zfs/
  total 0
  dr-xr-xr-x 21 root root 0 Jul  6 10:49 ./
  dr-xr-xr-x  4 root root 0 Jul  6 10:49 ../
  -rw-r--r--  1 root root 0 Jul  6 10:49 abdstats
  -rw-r--r--  1 root root 0 Jul  6 10:49 arcstats
  dr-xr-xr-x 20 root root 0 Jul  6 10:49 data/
  -rw---  1 root root 0 Jul  6 10:49 dbgmsg
  -rw---  1 root root 0 Jul  6 10:49 dbufs
  -rw-r--r--  1 root root 0 Jul  6 10:49 dbufstats
  dr-xr-xr-x 70 root root 0 Jul  6 10:49 default/
  -rw-r--r--  1 root root 0 Jul  6 10:49 dmu_tx
  -rw-r--r--  1 root root 0 Jul  6 10:49 dnodestats
  -rw-r--r--  1 root root 0 Jul  6 10:49 fletcher_4_bench
  -rw-r--r--  1 root root 0 Jul  6 10:49 fm
  -rw-r--r--  1 root root 0 Jul  6 10:49 import_progress
  -rw-r--r--  1 root root 0 Jul  6 10:49 metaslab_stats
  -rw-r--r--  1 root root 0 Jul  6 10:49 vdev_cache_stats
  -rw-r--r--  1 root root 0 Jul  6 10:49 vdev_mirror_stats
  -rw-r--r--  1 root root 0 Jul  6 10:49 vdev_raidz_bench
  -rw-r--r--  1 root root 0 Jul  6 10:49 zfetchstats
  -rw-r--r--  1 root root 0 Jul  6 10:49 zil
  -rw-r--r--  1 root root 0 Jul  6 10:49 zstd

  
  # Workaround

  This (naive) patch sidesteps the problem:

  $ diff -Naur /usr/sbin/arc_summary.old /usr/sbin/arc_summary
  --- /usr/sbin/arc_summary.old 2022-07-06 10:59:50.752833101 -0400
  +++ /usr/sbin/arc_summary 2022-07-06 10:59:22.449113169 -0400
  @@ -255,6 +255,8 @@
   secs = SECTION_PATHS.values()
   
   for section in secs:
  +if not os.path.exists(PROC_PATH+section):
  +continue
   
   with open(PROC_PATH+section, 'r') as proc_location:
   lines = [line for line in proc_location]

  
  # Additional information
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -r
  5.15.0-41-generic
  $ apt-cache policy zfsutils-linux linux-image-generic-hwe-20.04
  zfsutils-linux:
Installed: 0.8.3-1ubuntu12.14
Candidate: 0.8.3-1ubuntu12.14
Version table:
   *** 0.8.3-1ubuntu12.14 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12.9 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   0.8.3-1ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  linux-image-generic-hwe-20.04:
Installed: 5.15.0.41.44~20.04.13
Candidate: 5.15.0.41.44~20.04.13
Version table:
   *** 5.15.0.41.44~20.04.13 400
  400 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.13.0.52.59~20.04.31 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   5.4.0.26.32 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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


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

[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Timo Aaltonen]

6.6.x has this in addition

commit 3a3bbc6911f57e1c3b4eabf1d098cde7bf7baeb0
Author: Rafael J. Wysocki 
Date:   Tue Sep 19 20:59:53 2023 +0200

thermal: trip: Drop redundant trips check from for_each_thermal_trip()

[ Upstream commit a15ffa783ea4210877886c59566a0d20f6b2bc09 ]

It is invalid to call for_each_thermal_trip() on an unregistered thermal
zone anyway, and as per thermal_zone_device_register_with_trips(), the
trips[] table must be present if num_trips is greater than zero for the
given thermal zone.

Hence, the trips check in for_each_thermal_trip() is redundant and so it
can be dropped.

Signed-off-by: Rafael J. Wysocki 
Acked-by: Daniel Lezcano 
Stable-dep-of: e95fa7404716 ("thermal: gov_power_allocator: avoid inability 
to reset a cdev")
Signed-off-by: Sasha Levin 


FYI, 6.1 didn't backport any of these, even though e95fa7404716 says "5.13+"

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

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are no journal logs existed when it boot with the 6.5.0-33
  kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => 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/2063143

Title:
  Frequent boot to black display

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

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Jens Glathe]

Hmm I see two issues here.

qcom_q6v5_pas should be in /etc/initramfs-tools/modules (it is in mine), or 
loading of adsp and cdsp firmware will be deferred until rootfs is mounted, 
with the odd VBUS interruption on type-c connectors at a moment where this will 
result in an inaccessible rootfs afterwards.
The endless loop is something I'm not seeing with my builds, looked like 
something IOMMU and DWC3 that were clashing.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3341
   https://gitlab.freedesktop.org/drm/amd/-/issues/3341

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/3341
   Importance: Unknown
   Status: Unknown

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

Title:
  Frequent boot to black display

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

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2063355] Re: snapd/2.61.3+22.04 ADT test failure with linux/5.15.0-106.116

[Stefan Bader]

I re-triggered the test for the previous kernel which was ok before:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/snapd/20240411_081655_0c5b9@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/snapd/20240424_154314_79f82@/log.gz

The test downloads itself dynamically from various sites on the
internet. So I believe this is neither related to the new kernel nor the
snapd package itself but on those dynamic portions.

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

Title:
  snapd/2.61.3+22.04 ADT test failure with linux/5.15.0-106.116

Status in linux package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  New

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

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/snapd/20240424_154314_79f82@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/snapd/20240423_025812_a85b2@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/s/snapd/20240422_150145_a64fe@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/s/snapd/20240422_155419_7896b@/log.gz

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


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

[Kernel-packages] [Bug 2063355] [NEW] snapd/2.61.3+22.04 ADT test failure with linux/5.15.0-106.116

[Stefan Bader]

Public bug reported:

This is a scripted bug report about ADT failures while running snapd
tests for linux/5.15.0-106.116 on jammy. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.

Testing failed on:
amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/snapd/20240424_154314_79f82@/log.gz
arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/snapd/20240423_025812_a85b2@/log.gz
ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/s/snapd/20240422_150145_a64fe@/log.gz
s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/s/snapd/20240422_155419_7896b@/log.gz

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

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

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

Title:
  snapd/2.61.3+22.04 ADT test failure with linux/5.15.0-106.116

Status in linux package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  New

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

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/snapd/20240424_154314_79f82@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/snapd/20240423_025812_a85b2@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/s/snapd/20240422_150145_a64fe@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/s/snapd/20240422_155419_7896b@/log.gz

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


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

[Kernel-packages] [Bug 2063228] Re: screen sometimes blinking

[dom21121]

thank you for your reply. I applied the settings in grub. I will let you
know if I notice the flashing again.

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

Title:
  screen sometimes blinking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Pavilion Laptop 14-ce2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2022
  dmi.bios.release: 15.27
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84BB
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 14-ce2xxx
  dmi.product.sku: 8KZ34EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~kernel-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-restricted-modules-lowlatency/5.15.0-106.116)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-lowlatency 
(5.15.0-106.116) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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-restricted-modules-lowlatency

[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 packaging 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 2060039] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From hbath...@in.ibm.com 2024-04-24 12:23 EDT---
Posted the patches to reduce memory consumption for KFENCE upstream:

https://lore.kernel.org/all/20240424110926.184077-1-hbath...@linux.ibm.com/
("[PATCH 1/2] radix/kfence: map __kfence_pool at page granularity")

https://lore.kernel.org/all/20240424110926.184077-1-hbath...@linux.ibm.com/
("[PATCH 2/2] radix/kfence: support late __kfence_pool allocation")

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

Title:
  [Ubuntu-24.04] FADump with recommended crash size is making the L1
  hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problem description :
  ==

  Triggered FADump with the recommended crash. L1 host got hung.

  As per the public document
  https://wiki.ubuntu.com/ppc64el/Recommendations recommended crash
  kernel size is 1024M for the system. But with 1024M and 2048M, the L1
  is getting hanged. with 4096, crash is generated and collected.

  
  root@ubuntu2404:~# uname -ar
  Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 
ppc64le ppc64le ppc64le GNU/Linux

  
  root@ubuntu2404:~# free -h
 totalusedfree  shared  buff/cache   
available
  Mem:48Gi   1.7Gi46Gi13Mi   687Mi
46Gi
  Swap:  8.0Gi  0B   8.0Gi

  
  root@ubuntu2404:~# cat /proc/cmdline 
  BOOT_IMAGE=/vmlinux-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 
ro fadump=on crashkernel=1024M

  
  root@ubuntu2404:~# dmesg | grep -i reser
  [0.00] fadump: Reserved 1024MB of memory at 0x004000 (System 
RAM: 51200MB)
  [0.00] fadump: Initialized 0x4000 bytes cma area at 1024MB from 
0x4007 bytes of memory reserved for firmware-assisted dump
  [0.00] Memory: 49316672K/52428800K available (23616K kernel code, 
4096K rwdata, 25536K rodata, 8832K init, 2487K bss, 2063552K reserved, 1048576K 
cma-reserved)
  [0.396408] ibmvscsi 3066: Client reserve enabled

  
  root@ubuntu2404:~# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
 /var/lib/kdump/vmlinuz
  kdump initrd: 
 /var/lib/kdump/initrd.img
  current state:ready to fadump

  IBM is looking to update the crash kernel reservations section of the
  wiki for Power.

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


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

[Kernel-packages] [Bug 2062985] Re: ALSA Fails to detect any devices with kernel 6.8.0

[Kyrylo Bohdanenko]

Sorry, false alarm. Still not fixed with 6.8.0-31-generic (must have
been some fluke). I'll continue my observations.

I did one experiment: sudo alsactl store on kernel 6.5. And here is what
I get running the restore:

$ sudo alsactl -d restore
alsa-lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -2
alsactl: init_ucm:48: ucm open '-hw:0': -2
alsactl: set_controls:1499: device='hw:0', doit=0
alsactl: set_controls:1511: card-info-id: 'avsprobemb'
alsactl: set_controls:1546: list count: 0
alsactl: set_controls:1574: maxnumid=-1 maxnumid2=-1
alsactl: set_controls:1587: result code: 0
alsactl: set_controls:1499: device='hw:0', doit=1
alsactl: set_controls:1511: card-info-id: 'avsprobemb'
alsactl: set_controls:1587: result code: 0

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

Title:
  ALSA Fails to detect any devices with kernel 6.8.0

Status in linux package in Ubuntu:
  New

Bug description:
  Submitting this bug report from kernel 6.5.0 where it seems to work.

  When running aplay -l on kernel 6.8 the output is empty. And
  pulseaudio also shows an error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-28-generic 6.8.0-28.28
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh 1363 F wireplumber
   /dev/snd/seq:kyrboh 1358 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Apr 20 21:15:03 2024
  InstallationDate: Installed on 2023-11-04 (169 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=db41af68-2c72-4fc6-a654-5b0f2be10d62 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-28-generic N/A
   linux-backports-modules-6.5.0-28-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-04-20 (0 days ago)
  dmi.bios.date: 11/10/2022
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2063337] Re: RM: noble linux-meta/linux-restricted-modules incorrectly expressing -oem-24.04 variants

[Andy Whitcroft]

There are no external reverse-depends:

+ reverse-depends linux-cloud-tools-generic-oem-24.04   
No reverse dependencies found
+ reverse-depends linux-cloud-tools-virtual-oem-24.04   
No reverse dependencies found
+ reverse-depends linux-generic-64k-oem-24.04
No reverse dependencies found
+ reverse-depends linux-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-headers-generic-64k-oem-24.04   
Reverse-Depends
===
* linux-generic-64k-oem-24.04   

Packages without architectures listed are reverse-dependencies in: arm64
+ reverse-depends linux-headers-generic-oem-24.04   
Reverse-Depends
===
* linux-generic-oem-24.04   
* linux-headers-virtual-oem-24.04


Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, ppc64el, s390x
+ reverse-depends linux-headers-virtual-oem-24.04
Reverse-Depends
===  
* linux-virtual-oem-24.04


Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, ppc64el, s390x
+ reverse-depends linux-image-extra-virtual-oem-24.04
No reverse dependencies found
+ reverse-depends linux-image-generic-64k-oem-24.04
Reverse-Depends
===
* linux-generic-64k-oem-24.04  


Packages without architectures listed are reverse-dependencies in: arm64
+ reverse-depends linux-image-generic-oem-24.04
Reverse-Depends 
===  
* linux-generic-oem-24.04   
* linux-image-extra-virtual-oem-24.04 [amd64 arm64 ppc64el s390x]


Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, ppc64el, s390x
+ reverse-depends linux-image-uc-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-image-virtual-oem-24.04
Reverse-Depends  
===  
* linux-virtual-oem-24.04


Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, ppc64el, s390x
+ reverse-depends linux-modules-ipu6-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-ivsc-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-iwlwifi-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-470-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-470-server-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-generic-64k-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-open-generic-64k-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-open-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-server-generic-64k-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-server-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-server-open-generic-64k-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-525-server-open-generic-oem-24.04
No reverse dependencies found
+ reverse-depends linux-modules-nvidia-535-generic-64k-oem-24.04
Reverse-Depends
===
* linux-modules-nvidia-525-generic-64k-oem-24.04

Packages without architectures listed are reverse-dependencies in: arm64
+ reverse-depends linux-modules-nvidia-535-generic-oem-24.04
Reverse-Depends
===
* linux-modules-nvidia-525-generic-oem-24.04

Packages without architectures listed are reverse-dependencies in: amd64, arm64
+ reverse-depends linux-modules-nvidia-535-open-generic-64k-oem-24.04
Reverse-Depends
===
* linux-modules-nvidia-525-open-generic-64k-oem-24.04

Packages without architectures listed are reverse-dependencies in: arm64
+ reverse-depends linux-modules-nvidia-535-open-generic-oem-24.04
Reverse-Depends
===
* linux-modules-nvidia-525-open-generic-oem-24.04

Packages without architectures listed are reverse-dependencies in: amd64, arm64
+ reverse-depends linux-modules-nvidia-535-server-generic-64k-oem-24.04
Reverse-Depends
===
* 

[Kernel-packages] [Bug 2063337] Re: RM: noble linux-meta/linux-restricted-modules incorrectly expressing -oem-24.04 variants

[Andy Whitcroft]

Full list of packages:

# https://api.launchpad.net/devel/ubuntu/+archive/primary/+sourcepub/15986501 
linux-meta 6.8.0-31.31
  linux-cloud-tools-generic-oem-24.04 amd64
  linux-cloud-tools-virtual-oem-24.04 amd64
  linux-generic-64k-oem-24.04 arm64
  linux-generic-oem-24.04 amd64
  linux-generic-oem-24.04 arm64
  linux-generic-oem-24.04 armhf
  linux-generic-oem-24.04 ppc64el
  linux-generic-oem-24.04 s390x
  linux-headers-generic-64k-oem-24.04 arm64
  linux-headers-generic-oem-24.04 amd64
  linux-headers-generic-oem-24.04 arm64
  linux-headers-generic-oem-24.04 armhf
  linux-headers-generic-oem-24.04 ppc64el
  linux-headers-generic-oem-24.04 s390x
  linux-headers-virtual-oem-24.04 amd64
  linux-headers-virtual-oem-24.04 arm64
  linux-headers-virtual-oem-24.04 armhf
  linux-headers-virtual-oem-24.04 ppc64el
  linux-headers-virtual-oem-24.04 s390x
  linux-image-extra-virtual-oem-24.04 amd64
  linux-image-extra-virtual-oem-24.04 arm64
  linux-image-extra-virtual-oem-24.04 ppc64el
  linux-image-extra-virtual-oem-24.04 s390x
  linux-image-generic-64k-oem-24.04 arm64
  linux-image-generic-oem-24.04 amd64
  linux-image-generic-oem-24.04 arm64
  linux-image-generic-oem-24.04 armhf
  linux-image-generic-oem-24.04 ppc64el
  linux-image-generic-oem-24.04 s390x
  linux-image-uc-generic-oem-24.04 amd64
  linux-image-uc-generic-oem-24.04 arm64
  linux-image-virtual-oem-24.04 amd64
  linux-image-virtual-oem-24.04 arm64
  linux-image-virtual-oem-24.04 armhf
  linux-image-virtual-oem-24.04 ppc64el
  linux-image-virtual-oem-24.04 s390x
  linux-modules-ipu6-generic-oem-24.04 amd64
  linux-modules-ivsc-generic-oem-24.04 amd64
  linux-modules-iwlwifi-generic-oem-24.04 amd64
  linux-tools-generic-64k-oem-24.04 arm64
  linux-tools-generic-oem-24.04 amd64
  linux-tools-generic-oem-24.04 arm64
  linux-tools-generic-oem-24.04 armhf
  linux-tools-generic-oem-24.04 ppc64el
  linux-tools-generic-oem-24.04 s390x
  linux-tools-virtual-oem-24.04 amd64
  linux-tools-virtual-oem-24.04 arm64
  linux-tools-virtual-oem-24.04 armhf
  linux-tools-virtual-oem-24.04 ppc64el
  linux-tools-virtual-oem-24.04 s390x
  linux-virtual-oem-24.04 amd64
  linux-virtual-oem-24.04 arm64
  linux-virtual-oem-24.04 armhf
  linux-virtual-oem-24.04 ppc64el
  linux-virtual-oem-24.04 s390x
# https://api.launchpad.net/devel/ubuntu/+archive/primary/+sourcepub/15986504 
linux-restricted-modules 6.8.0-31.31
  linux-modules-nvidia-470-generic-oem-24.04 amd64
  linux-modules-nvidia-470-server-generic-oem-24.04 amd64
  linux-modules-nvidia-525-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-525-generic-oem-24.04 amd64
  linux-modules-nvidia-525-generic-oem-24.04 arm64
  linux-modules-nvidia-525-open-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-525-open-generic-oem-24.04 amd64
  linux-modules-nvidia-525-open-generic-oem-24.04 arm64
  linux-modules-nvidia-525-server-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-525-server-generic-oem-24.04 amd64
  linux-modules-nvidia-525-server-generic-oem-24.04 arm64
  linux-modules-nvidia-525-server-open-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-525-server-open-generic-oem-24.04 amd64
  linux-modules-nvidia-525-server-open-generic-oem-24.04 arm64
  linux-modules-nvidia-535-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-535-generic-oem-24.04 amd64
  linux-modules-nvidia-535-generic-oem-24.04 arm64
  linux-modules-nvidia-535-open-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-535-open-generic-oem-24.04 amd64
  linux-modules-nvidia-535-open-generic-oem-24.04 arm64
  linux-modules-nvidia-535-server-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-535-server-generic-oem-24.04 amd64
  linux-modules-nvidia-535-server-generic-oem-24.04 arm64
  linux-modules-nvidia-535-server-open-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-535-server-open-generic-oem-24.04 amd64
  linux-modules-nvidia-535-server-open-generic-oem-24.04 arm64
  linux-modules-nvidia-545-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-545-generic-oem-24.04 amd64
  linux-modules-nvidia-545-generic-oem-24.04 arm64
  linux-modules-nvidia-545-open-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-545-open-generic-oem-24.04 amd64
  linux-modules-nvidia-545-open-generic-oem-24.04 arm64
  linux-modules-nvidia-550-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-550-generic-oem-24.04 amd64
  linux-modules-nvidia-550-generic-oem-24.04 arm64
  linux-modules-nvidia-550-open-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-550-open-generic-oem-24.04 amd64
  linux-modules-nvidia-550-open-generic-oem-24.04 arm64
  linux-modules-nvidia-550-server-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-550-server-generic-oem-24.04 amd64
  linux-modules-nvidia-550-server-generic-oem-24.04 arm64
  linux-modules-nvidia-550-server-open-generic-64k-oem-24.04 arm64
  linux-modules-nvidia-550-server-open-generic-oem-24.04 amd64
  linux-modules-nvidia-550-server-open-generic-oem-24.04 arm64

-- 
You received this bug notification because you are a member of 

[Kernel-packages] [Bug 2060071] Re: Add initial r36.3 out-of-tree module meta packages

[Jacob Martin]

** Also affects: linux-meta-nvidia-tegra-igx (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu)
   Status: New => Fix Committed

** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu)
 Assignee: (unassigned) => Jacob Martin (jacobmartin)

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

Title:
  Add initial r36.3 out-of-tree module meta packages

Status in linux-meta-nvidia-tegra-igx package in Ubuntu:
  Fix Committed
Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu:
  Fix Committed

Bug description:
  We want to enable tracks for different versions of the out-of-tree
  modules. For now we only have R36.3, so create the meta packages for
  that version.

  These meta packages include:
  * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM
  * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2060071/+subscriptions


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

[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7

[Jacek Kowalski]

I have tested wifi7 with latest linux-generic-hwe-22.04 with
6.5.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4
14:39:20 UTC 2 x86_64 x86_64 x86_64 GNU/Linux.

The problem with iwlwifi(and wifi7) no longer exists - no disconnects,
no crash, no unusual errors messages in dmesg. Thanks.

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

Title:
  iwlwifi disconnect and crash - intel wifi7

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.

  [ cut here ]
  Invalid rxb from HW 0
  WARNING: CPU: 14 PID: 896 at 
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds 
joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
   xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
  CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
  Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
  RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
  RSP: 0018:b91d803e0e18 EFLAGS: 00010246
  RAX:  RBX: 956747353c30 RCX: 
  RDX:  RSI:  RDI: 
  RBP: b91d803e0e78 R08:  R09: 
  R10:  R11:  R12: 1007
  R13: 0015 R14:  R15: 956746a30028
  FS:  () GS:95768f38() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
  PKRU: 5554
  Call Trace:
   
   ? show_regs+0x6d/0x80
   ? __warn+0x89/0x160
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? report_bug+0x17e/0x1b0
   ? handle_bug+0x46/0x90
   ? exc_invalid_op+0x18/0x80
   ? asm_exc_invalid_op+0x1b/0x20
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? free_unref_page+0x30/0x180
   iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
   ? skb_free_head+0xa8/0xd0
   __napi_poll+0x30/0x1f0
   net_rx_action+0x181/0x2e0
   ? __irq_wake_thread+0x42/0x50
   __do_softirq+0xd9/0x349
   ? __pfx_irq_thread_fn+0x10/0x10
   do_softirq.part.0+0x41/0x80
   
   
   __local_bh_enable_ip+0x72/0x80
   iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
   irq_thread_fn+0x21/0x70
   irq_thread+0xf8/0x1c0
   ? __pfx_irq_thread_dtor+0x10/0x10
   ? __pfx_irq_thread+0x10/0x10
   kthread+0xef/0x120
   ? __pfx_kthread+0x10/0x10
   ret_from_fork+0x44/0x70
   ? __pfx_kthread+0x10/0x10
   ret_from_fork_asm+0x1b/0x30
   
  ---[ end trace  ]---
  iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
  iwlwifi :05:00.0: Start IWL Error Log Dump:
  iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
  iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
  iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
  iwlwifi :05:00.0: 0x0003 | trm_hw_status0
  iwlwifi :05:00.0: 0x | trm_hw_status1
  iwlwifi :05:00.0: 0x002C280A | branchlink2
  iwlwifi :05:00.0: 0x9328 | interruptlink1
  iwlwifi :05:00.0: 0x9328 | interruptlink2
  iwlwifi :05:00.0: 0xF46C | data1
  iwlwifi :05:00.0: 0x0100 | data2
  iwlwifi :05:00.0: 0x | data3
  iwlwifi :05:00.0: 0xA0005E44 | beacon time
  iwlwifi :05:00.0: 0x2806818F | tsf low
  iwlwifi :05:00.0: 0x | tsf hi
  iwlwifi :05:00.0: 0x | time gp1
  iwlwifi :05:00.0: 0x0BB840A7 | time gp2
  iwlwifi :05:00.0: 0x0001 | uCode revision type
  iwlwifi :05:00.0: 

[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

[Heinrich Schuchardt]

On my LicheeRV Dock it dos not work for me with HDMI plugged in at
start. I just get

[   67.521944] sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY
[   67.613930] sun4i-drm display-engine: Couldn't bind all pipelines components

and no output. On the Nezha D1 I did not have this issue.

When Alexandre wrote the tests it was explicitly foreseen to plug in
HDMI after login. So this must have worked previously.

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2037335] Re: kernel leaking TCP_MEM

[Jonathan Heathcote]

Hello there,

I think this may be the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
aws-6.2/+bug/2045560

I believe this might be related to the following kernel bug which
impacts Linux 6.0.0+:

https://lore.kernel.org/netdev/vi1pr01mb42407d7947b2ea448f1e04efd1...@vi1pr01mb4240.eurprd01.prod.exchangelabs.com/

A patch has been produced which fixes this issue (but has not yet made
it into a Linux release):

https://lore.kernel.org/all/20240421175248.1692552-1-eduma...@google.com/

Hope this helps!

Jonathan

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

Title:
  kernel leaking TCP_MEM

Status in linux-meta-aws-6.2 package in Ubuntu:
  New

Bug description:
  We are running our Kafka brokers on Jammy on ARM64. Previous they were
  on kernel version 5.15.0-1028-aws, but a few weeks ago we built a new
  AMI and it picked up 6.2.0-1009-aws, and we have also upgraded to
  6.2.0-1012-aws and found the same problem.

  What we expected to happen:
  TCP memory (TCP_MEM) to fluctuate but stay relatively low (on a busy 
production broker running 5.15.0-1028-aws, we average 1900 pages over a 24 hour 
period)

  What happened instead:
  TCP memory (TCP_MEM) continues to rise until hitting the limit (1.5 million 
pages as configured currently). At this point, the broker is no longer able to 
properly create new connections and we start seeing "kernel: TCP: out of memory 
-- consider tuning tcp_mem" in dmesg output. If allowed to continue, the broker 
will eventually isolate itself from the rest of the cluster since it can't talk 
to the other brokers.

  Attached is a graph of the average TCP memory usage per kernel version
  for our production environment over the past 24 hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-aws 6.2.0.1012.12~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-1012.12~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1012-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-east-1
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Sep 25 20:56:02 2023
  Ec2AMI: ami-0b9c5aafc5b2a4725
  Ec2AMIManifest: (unknown)
  Ec2Architecture: arm64
  Ec2AvailabilityZone: us-east-1b
  Ec2Imageid: ami-0b9c5aafc5b2a4725
  Ec2InstanceType: im4gn.4xlarge
  Ec2Instancetype: im4gn.4xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-east-1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-aws-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws-6.2/+bug/2037335/+subscriptions


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

this issue has appeared before on other AMD hardware but was closed due
to lack of activity and driver changes. my issue shows that it has re-
appeared on new hardware and drivers
https://gitlab.freedesktop.org/drm/amd/-/issues/1256

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1256
   https://gitlab.freedesktop.org/drm/amd/-/issues/1256

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

Title:
  Frequent boot to black display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2063143] Re: Frequent boot to black display

[theofficialgman]

Going to change this back to linux as the plymouth failing to display
indicates an issues with KMS (plymouth uses KMS to display graphics on
earlyboot which is what is happening here). The bootlogo from plymouth
always shows (even for a very brief time) when SDDM starts and when it
boots to a black screen the bootlog NEVER shows from plymouth. Using
your reasoning of the race condition I should see the bootlogo at least
sometimes in the boot to black screen but this has never happened (I
have booted dozens of times to black screen and have always never seen
the bootlogo).

I do not think this has anything to do with sddm. If KMS is not working
then of course everything else that relies on it later in the bootstack
will also fail.

The Ubuntu default drivers are in use.

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

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

Title:
  Frequent boot to black display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: AMD Framework 13
  OS: Ubuntu Noble 24.04
  DE: Plasma Wayland
  BIOS: version 3.03 and 3.05 (latest new release)
  Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  This issue started about 2-3 weeks ago I believe around the time that
  Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
  This issue may not be a kernel regression but instead a wayland
  regression but I am not certain and looking for help.

  The issue is that on boot the (internal laptop and external displays
  if connected) are black but backlight is lit. I am able to boot into
  recovery mode without issue since the graphics drivers are not loaded
  in that case (only amd framebuffer driver and userspace mesa
  llvmpipe). Cold boot from OFF seems to be the most common case for
  this issue and it happens about 50-75% of the time from there. I have
  to force power the device off and try again in this case. I don't know
  how to get proper bootlogs from the previous boot when this is the
  case since /var/log only seems to contain logs from the current boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 22 13:35:21 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) 
(prog-if 00 [VGA controller])
 Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
  InstallationDate: Installed on 2023-11-16 (159 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP05
  dmi.board.vendor: Framework
  dmi.board.version: A5
  dmi.chassis.asset.tag: FRANDGCPA5342400SJ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP05
  dmi.product.version: A5
  dmi.sys.vendor: Framework
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: 

[Kernel-packages] [Bug 2063143] [NEW] Frequent boot to black display

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hardware: AMD Framework 13
OS: Ubuntu Noble 24.04
DE: Plasma Wayland
BIOS: version 3.03 and 3.05 (latest new release)
Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 
2024 x86_64 x86_64 x86_64 GNU/Linux

This issue started about 2-3 weeks ago I believe around the time that
Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages.
This issue may not be a kernel regression but instead a wayland
regression but I am not certain and looking for help.

The issue is that on boot the (internal laptop and external displays if
connected) are black but backlight is lit. I am able to boot into
recovery mode without issue since the graphics drivers are not loaded in
that case (only amd framebuffer driver and userspace mesa llvmpipe).
Cold boot from OFF seems to be the most common case for this issue and
it happens about 50-75% of the time from there. I have to force power
the device off and try again in this case. I don't know how to get
proper bootlogs from the previous boot when this is the case since
/var/log only seems to contain logs from the current boot.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Apr 22 13:35:21 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 
00 [VGA controller])
   Subsystem: Framework Computer Inc. Phoenix1 [f111:0006]
InstallationDate: Installed on 2023-11-16 (159 days ago)
InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: Framework Laptop 13 (AMD Ryzen 7040Series)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 
quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP05
dmi.board.vendor: Framework
dmi.board.version: A5
dmi.chassis.asset.tag: FRANDGCPA5342400SJ
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A5
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP05
dmi.product.version: A5
dmi.sys.vendor: Framework
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 amdgpu apport-bug freeze kubuntu noble ubuntu wayland-session
-- 
Frequent boot to black display
https://bugs.launchpad.net/bugs/2063143
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE

[Joseph Salisbury]

A kernel bisect is underway.  We should have further details regarding
the commit that introduced this regression soon.

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

Title:
  Suspend & Resume functionality broken/timesout in GCE

Status in Release Notes for Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Noble:
  In Progress

Bug description:
  [Impact]
   
  Suspend/Resume capability is broken in all noble images with kernel version 
6.8.0-1007-gcp.

  GCE offers the capability to "Suspend" a VM to conserve power/lower
  costs when the instance is not in use [0]. It uses ACPI S3 signals to
  tell the guest to power down. This capability no longer works in the
  latest kernel with the following error:

  ```
  Operation type [suspend] failed with message "Instance suspend failed due to 
guest timeout."
  ```

  which points to the following [1].

  

  Refs:

  [0]: https://cloud.google.com/compute/docs/instances/suspend-resume-
  instance

  [1]:
  https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-
  suspend-resume#there_was_a_guest_timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions


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

[Kernel-packages] [Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE

[Joseph Salisbury]

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

** Changed in: linux-gcp (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: linux-gcp (Ubuntu Noble)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Suspend & Resume functionality broken/timesout in GCE

Status in Release Notes for Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Noble:
  In Progress

Bug description:
  [Impact]
   
  Suspend/Resume capability is broken in all noble images with kernel version 
6.8.0-1007-gcp.

  GCE offers the capability to "Suspend" a VM to conserve power/lower
  costs when the instance is not in use [0]. It uses ACPI S3 signals to
  tell the guest to power down. This capability no longer works in the
  latest kernel with the following error:

  ```
  Operation type [suspend] failed with message "Instance suspend failed due to 
guest timeout."
  ```

  which points to the following [1].

  

  Refs:

  [0]: https://cloud.google.com/compute/docs/instances/suspend-resume-
  instance

  [1]:
  https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-
  suspend-resume#there_was_a_guest_timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions


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

[Kernel-packages] [Bug 1980805] Re: Backport packages for 20.04.5 HWE stack

[Timo Aaltonen]

** Changed in: mesa-amber (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

** Changed in: llvm-toolchain-13 (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

** Changed in: libdrm (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

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

Title:
  Backport packages for 20.04.5 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-13 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Won't Fix
Status in llvm-toolchain-13 source package in Focal:
  Won't Fix
Status in mesa source package in Focal:
  Won't Fix
Status in mesa-amber source package in Focal:
  Won't Fix

Bug description:
  [Impact]

  These are needed for 20.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: pci-id updates, some minor api updates

  mesa: a new major release, but we'll pull the final stable release of
  22.0.x series, so there shouldn't be any regressions left at that
  point

  mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI
  drivers that were removed from main mesa

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


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

[Kernel-packages] [Bug 2061986] Re: Mount CIFS fails with Permission denied

[Heitor Alves de Siqueira]

Marking Ubuntu as "Fix Released" according to parent description, as fix
was introduced upstream in v5.16.

** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => In Progress

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


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

[Kernel-packages] [Bug 2061986] Re: Mount CIFS fails with Permission denied

[Launchpad Bug Tracker]

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

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


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

[Kernel-packages] [Bug 2061986] Re: Mount CIFS fails with Permission denied

[Launchpad Bug Tracker]

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

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


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

[Kernel-packages] [Bug 2061986] Re: Mount CIFS fails with Permission denied

[Heitor Alves de Siqueira]

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

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

Title:
  Mount CIFS fails with Permission denied

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

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


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

[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

[Emil Renner Berthing]

For all previous kernels and the 6.8.0-31-generic in Noble detection
have been an issue. As long as the cable is attached at boot it does
work.

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2063337] Re: RM: noble linux-meta/linux-restricted-modules incorrectly expressing -oem-24.04 variants

[Andy Whitcroft]

** Summary changed:

- nobel linux-meta/linux-restricted-modules incorrectly expressing -oem-24.04 
variants
+ RM: noble linux-meta/linux-restricted-modules incorrectly expressing 
-oem-24.04 variants

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  RM: noble linux-meta/linux-restricted-modules incorrectly expressing
  -oem-24.04 variants

Status in linux package in Ubuntu:
  In Progress

Bug description:
  We are generating a number of additional meta-package suffixed by
  -oem-24.04.  These we added early in development to try and pick up
  oem-22.04 users.  They failed in this task because they were firstly
  using the wrong flavour (ultimately -generic-oem-24.04) and because
  they have since been incorrectly corrected to be -24.04.

  As these should not have any reverse-depends (by their nature) we
  should be safe to do binary removals on these in the release pocket
  before it is frozen and remove them from the next upload.

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


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

[Kernel-packages] [Bug 2063337] [NEW] nobel linux-meta/linux-restricted-modules incorrectly expressing -oem-24.04 variants

[Andy Whitcroft]

Public bug reported:

We are generating a number of additional meta-package suffixed by
-oem-24.04.  These we added early in development to try and pick up
oem-22.04 users.  They failed in this task because they were firstly
using the wrong flavour (ultimately -generic-oem-24.04) and because they
have since been incorrectly corrected to be -24.04.

As these should not have any reverse-depends (by their nature) we should
be safe to do binary removals on these in the release pocket before it
is frozen and remove them from the next upload.

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

Title:
  nobel linux-meta/linux-restricted-modules incorrectly expressing
  -oem-24.04 variants

Status in linux package in Ubuntu:
  New

Bug description:
  We are generating a number of additional meta-package suffixed by
  -oem-24.04.  These we added early in development to try and pick up
  oem-22.04 users.  They failed in this task because they were firstly
  using the wrong flavour (ultimately -generic-oem-24.04) and because
  they have since been incorrectly corrected to be -24.04.

  As these should not have any reverse-depends (by their nature) we
  should be safe to do binary removals on these in the release pocket
  before it is frozen and remove them from the next upload.

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


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

[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network (arm64)

[Jonathan Heathcote]

The bug report can be found here:

https://lore.kernel.org/netdev/vi1pr01mb42407d7947b2ea448f1e04efd1...@vi1pr01mb4240.eurprd01.prod.exchangelabs.com/

The subsequently produced patch (not by me!) to fix this can be found
here:

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=3584718cf2ec

I've also verified that the above patch does fix the problem at least in
my case!

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

Title:
  TCP memory  leak, slow network (arm64)

Status in linux-signed-aws-6.2 package in Ubuntu:
  Confirmed

Bug description:
  Hello! 

  We have Ubuntu OS-based servers running in both AWS and Azure clouds.
  These servers are handling thousands of connections, and we've been
  experiencing issues with TCP memory usage since upgrading to Ubuntu
  22.04.3 from 22.04.2.

  $ cat /proc/net/sockstat
  sockets: used 6642
  TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989
  UDP: inuse 5 mem 0
  UDPLITE: inuse 0
  RAW: inuse 0
  FRAG: inuse 0 memory 0

  As shown in the output below, even after stopping all possible
  services and closing all open connections, the TCP memory usage
  remains high and only decreases very slowly.

  $ cat /proc/net/sockstat
  sockets: used 138
  TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320
  UDP: inuse 3 mem 0
  UDPLITE: inuse 0
  RAW: inuse 0
  FRAG: inuse 0 memory 0

  I have attached a screenshot of linear TCP memory usage growth, which
  we believe may indicate a TCP memory leak

  When net.ipv4.tcp_mem limit is reached, it causes network slowdown

  We've never had these issues before, and the only solution we've found
  so far is to reboot the node. Do you have any suggestions on how to
  troubleshoot further?

  Thank you for any help or guidance you can provide!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1015-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-west-2
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Dec  4 13:13:08 2023
  Ec2AMI: ami-095a68e28e781dfe1
  Ec2AMIManifest: (unknown)
  Ec2Architecture: arm64
  Ec2AvailabilityZone: us-west-2b
  Ec2Imageid: ami-095a68e28e781dfe1
  Ec2InstanceType: m7g.large
  Ec2Instancetype: m7g.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-west-2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-aws-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions


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

[Kernel-packages] [Bug 787738]

[icebear.loves.cookies]

(In reply to icebear.loves.cookies from comment #40)
> Just created an account to say exactly the same thing that's been said over
> and over and hopefully this can get sorted out.
> 
> Thinkpad x395 yoga on Arch linux-lts 6.6.28-1-lts I tried all kernels for
> arch and nothing.
> I'm forced to reload psmouse every time the trackpoint stops working. It
> seems to be spotty at best. Sometimes it's not detected after boot sometimes
> it is. It's an Elantech trackpoint. Here's the logs:
> [ 6035.568923] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync
> at byte 1
> [ 6035.570351] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync
> at byte 1
> [ 6035.570363] psmouse serio1: issuing reconnect request
> [ 6036.332627] psmouse serio1: synaptics: queried max coordinates: x
> [..5678], y [..4760]
> [ 6036.366980] psmouse serio1: synaptics: queried min coordinates: x
> [1266..], y [1092..]
> [ 6275.304399] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync
> at byte 1
> [ 6275.305556] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync
> at byte 1
> [ 6275.305569] psmouse serio1: issuing reconnect request
> [ 6276.061561] psmouse serio1: synaptics: queried max coordinates: x
> [..5678], y [..4760]
> [ 6276.096558] psmouse serio1: synaptics: queried min coordinates: x
> [1266..], y [1092..
> This is what gets reported every time it fails. Listed as: I: Bus=0011
> Vendor=0002 Product=000a Version=
> N: Name="TPPS/2 Elan TrackPoint"
> P: Phys=synaptics-pt/serio0/input0
> S: Sysfs=/devices/platform/i8042/serio1/serio2/input/input19
> U: Uniq=
> H: Handlers=event8 mouse3 
> B: PROP=21
> B: EV=7
> B: KEY=7 0 0 0 0
> B: REL=3
> under /proc/bus/input/devices
> 
> Works fine under windows I even upgraded the trackpoint's firmware to see if
> it helped (it did not)

To add to this sometimes when I reload the psmouse module my kernel
crashes (you get that blinking caps lock light)

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

Title:
  [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd
  behaviour

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Natty:
  Invalid
Status in linux source package in Oneiric:
  Invalid
Status in Fedora:
  New

Bug description:
  Using the touchpad does not result in expected behavior. The touchpad
  has three "mouse" buttons on top, and none of these buttons currently
  function. Using xev does not show any output from these buttons. The
  touchpad itself works fine. There are two bottom buttons integrated
  with the touchpad, which do not work consistantly. The left button
  will sometimes act like a left-click and sometime like a right click,
  making it hard to move applications on the screen. The right button
  acts like a left click and only sometimes bring up menus. Trying to
  change from a left hand to a right hand mouse in mouse options does
  not change the behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1235 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:14f1506e,17aa21da,0010 
HDA:80862805,80860101,0010'
     Controls  : 20
     Simple ctrls  : 8
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
     Mixer name : 'ThinkPad EC (unknown)'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Tue May 24 14:44:59 2011
  HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: LENOVO 428623U
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.52
  SourcePackage: linux
  UpgradeStatus: No 

[Kernel-packages] [Bug 787738]

[icebear.loves.cookies]

Just created an account to say exactly the same thing that's been said
over and over and hopefully this can get sorted out.

Thinkpad x395 yoga on Arch linux-lts 6.6.28-1-lts I tried all kernels for arch 
and nothing.
I'm forced to reload psmouse every time the trackpoint stops working. It seems 
to be spotty at best. Sometimes it's not detected after boot sometimes it is. 
It's an Elantech trackpoint. Here's the logs:
[ 6035.568923] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
[ 6035.570351] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
[ 6035.570363] psmouse serio1: issuing reconnect request
[ 6036.332627] psmouse serio1: synaptics: queried max coordinates: x [..5678], 
y [..4760]
[ 6036.366980] psmouse serio1: synaptics: queried min coordinates: x [1266..], 
y [1092..]
[ 6275.304399] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
[ 6275.305556] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at 
byte 1
[ 6275.305569] psmouse serio1: issuing reconnect request
[ 6276.061561] psmouse serio1: synaptics: queried max coordinates: x [..5678], 
y [..4760]
[ 6276.096558] psmouse serio1: synaptics: queried min coordinates: x [1266..], 
y [1092..
This is what gets reported every time it fails. Listed as: I: Bus=0011 
Vendor=0002 Product=000a Version=
N: Name="TPPS/2 Elan TrackPoint"
P: Phys=synaptics-pt/serio0/input0
S: Sysfs=/devices/platform/i8042/serio1/serio2/input/input19
U: Uniq=
H: Handlers=event8 mouse3 
B: PROP=21
B: EV=7
B: KEY=7 0 0 0 0
B: REL=3
under /proc/bus/input/devices

Works fine under windows I even upgraded the trackpoint's firmware to
see if it helped (it did not)

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

Title:
  [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd
  behaviour

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Natty:
  Invalid
Status in linux source package in Oneiric:
  Invalid
Status in Fedora:
  New

Bug description:
  Using the touchpad does not result in expected behavior. The touchpad
  has three "mouse" buttons on top, and none of these buttons currently
  function. Using xev does not show any output from these buttons. The
  touchpad itself works fine. There are two bottom buttons integrated
  with the touchpad, which do not work consistantly. The left button
  will sometimes act like a left-click and sometime like a right click,
  making it hard to move applications on the screen. The right button
  acts like a left click and only sometimes bring up menus. Trying to
  change from a left hand to a right hand mouse in mouse options does
  not change the behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1235 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:14f1506e,17aa21da,0010 
HDA:80862805,80860101,0010'
     Controls  : 20
     Simple ctrls  : 8
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
     Mixer name : 'ThinkPad EC (unknown)'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Tue May 24 14:44:59 2011
  HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: LENOVO 428623U
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.52
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET28WW (1.00 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 428623U
  dmi.board.vendor: LENOVO
  

[Kernel-packages] [Bug 2057960] Re: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

[Anderson Soares Ferreira]

Hello Kleber,

I've installed the last kernel update (5.15.0-106.116) and it's solved the 
problem.
Now FCoE interfaces are correctly detected and the system got storage disks 
access back.

Regards,

Anderson

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

Title:
  Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

Status in linux package in Ubuntu:
  New

Bug description:
  Since I've upgraded my server's to Ubuntu 22.04.4  I'm facing problems to 
make my fcoe setup to work correctly.
  Firstly, some context. We have a HPE Synergy appliance with a bunch of 
Synergy 480 Gen10 servers still running Ubuntu 20.04. 
  Each 480 server has 4 QLogic BCM57840 NetXtreme II Ethernet Multi Function 
network adapters with two of them dedicated to storage communication through 
FCoE.

  Recently, I've upgraded one of them to Ubuntu 22.04 and realized that after 
the upgrade, all the Fibre Channel LUNs have disappeared. During the diagnostic 
process I noticed that both network (bnx2x) and fcoe (fcoe, bnx2fc) kernel 
drivers have been loaded properly, FCoE vlans were correctly detected by 
fcoe-utils, but there was no connection between the server and the storage and 
the server could not detect any LUN.
  I also noticed that fcoeadm was reporting the following status:

  # fcoeadm -i
  Description:  BCM57840 NetXtreme II Ethernet Multi Function
  Revision: 11
  Manufacturer: Broadcom Inc. and subsidiaries
  Serial Number:9440C953B7F0

  Driver:   bnx2x Unknown
  Number of Ports:  1

  Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f2.4093-fco
  OS Device Name:host2
  Node Name: 0x1a3d2725
  Port Name: 0x1a3d2724
  Fabric Name:   0x0
  Speed: 20 Gbit
  Supported Speed:   1 Gbit, 10 Gbit
  MaxFrameSize:  2048 bytes
  FC-ID (Port ID):   0x
  State: Offline
  Description:  BCM57840 NetXtreme II Ethernet Multi Function
  Revision: 11
  Manufacturer: Broadcom Inc. and subsidiaries
  Serial Number:9440C953B7F0

  Driver:   bnx2x Unknown
  Number of Ports:  1

  Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f3.4094-fco
  OS Device Name:host3
  Node Name: 0x1a3d2727
  Port Name: 0x1a3d2726
  Fabric Name:   0x0
  Speed: 20 Gbit
  Supported Speed:   1 Gbit, 10 Gbit
  MaxFrameSize:  2048 bytes
  FC-ID (Port ID):   0x
  State: Offline

  Although most of information displayed was correct, the port state was
  always offline (what explains no storage connectivity) and the FC-ID
  reported was 0x for both interfaces.

  Supposing that something went wrong during the upgrade process, I decided to 
make a fresh install of the server and, for my surprise, the fcoe ports went 
online and all luns were detected correctly.
  Unfortunately, the ports went offline again after a dist-upgrade.
  Trying to understand what was happening I performed another fresh install of 
the Ubuntu 22.04, but this time collecting some information about kernel and 
packages versions from before and after dist-upgrade.
  What I discovered was that all packages related (fcoe-utils, lldpad) had the 
same versions before and after, the only exception was the kernel itself. 
Before the dist-upgrade the kernel in use was 5.15.0-25-generic and after 
dist-upgrade the kernel was 5.15.0-100-generic.
  Suspecting a kernel problem I installed and booted different kernel versions 
from 5.15.0-25 and 5.15.0-100 and discovered that the problem probably was 
introduced with kernel 5.15.0-94, since it is the first version showing the 
describe behavior.
  Looking at the changelog of linux-modules package, I noticed some changes on 
fcoe and other scsi modules, right after the 5.15.0-91 version. 
  Could those changes be the cause of the behavior observed on my server or 
just a coincidence? Is there any fix to it?

  Thanks in advance.

  Anderson

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-94-generic 5.15.0-94.104
  ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136
  Uname: Linux 5.15.0-94-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 14 11:03 seq
   crw-rw 1 root audio 116, 33 Mar 14 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  

[Kernel-packages] [Bug 2061840] Re: Ubuntu 24.04 freezes after plug in power cable

[Kleber Sacilotto de Souza]

Hello,

Could you please try again with the latest 24.04 image? It has a more
recent kernel version (6.8.0-31.31) and before we start investigating we
need to know if it is still reproducible with the latest kernel
available.

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

Title:
  Ubuntu 24.04 freezes after plug in power cable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Ubuntu 24.04 installed on my laptop, when I plug in my power
  cable to my laptop, the whole Ubuntu freezes and nothing is responds,
  so I have to force shutdown my laptop and restart it. I want to make
  notice that all other version Ubuntu 23.10, 22.04... with all
  different flavors work perfect without any issue

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-22-generic 6.8.0-22.22
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zakaria1758 F pipewire
   /dev/snd/controlC0:  zakaria1765 F wireplumber
   /dev/snd/controlC1:  zakaria1765 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 14:40:45 2024
  InstallationDate: Installed on 2024-04-14 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  MachineType: Dell Inc. Latitude E7450
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=63a3cbd0-c29b-4ef3-8be8-7c43b782a9b9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-22-generic N/A
   linux-backports-modules-6.8.0-22-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2020
  dmi.bios.release: 65.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A24
  dmi.board.name: 0D8H72
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA24:bd04/11/2020:br65.24:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:sku062E:
  dmi.product.name: Latitude E7450
  dmi.product.sku: 062E
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2060437] Re: The module ib_ipoib does not load automatically on ubuntu server 24.04

[Kleber Sacilotto de Souza]

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

Title:
  The module ib_ipoib does not load automatically on ubuntu server 24.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Fresh install Ubuntu server 24.04 on a server with mellanox card and 
infiniband mode
  2. As the module "ib_ipoib" does not load automatically, it fail to display 
the port via the command "ip a". The port can display after load manually.

  Please help to fix it, thanks.

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


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

[Kernel-packages] [Bug 2063322] [NEW] ite-cir driver failed to load due to a regression in linux kernel 6.5+ serial driver change

[James Joseph]

Public bug reported:

[Impact]

From Kernel 6.5 and above, the serial driver now claims multiple UART
ports by default, when the previous behaviour was it would only claim 1.
Due to this the ite-cir driver can no longer load because the port it
would assign itself is now being used in memory by the 16550/8250
driver.  We have found a workaround by disabling the serial driver from
consuming more than 1 port.  Below is the steps we went to troubleshoot,
investigate and the solution we’ve found.  This is a regression from 6.4
behaviour.

When installing 24.04 I noticed that the /dev/lirc0 device was not
loaded on the system which is what is created when the driver is loaded.
After reviewing the driver we use on 20.04 I then searched the kernel
logs and found that the ite-cir driver failed to load due to error -16.

```
2024-04-19T13:44:51.873060+00:00 host kernel: rc rc0: ITE8708 CIR transceiver 
as /devices/pnp0/00:03/rc/rc0
2024-04-19T13:44:51.873062+00:00 host kernel: rc rc0: lirc_dev: driver ite-cir 
registered at minor = 0, raw IR receiver, raw IR transmitter
2024-04-19T13:44:51.873070+00:00 host kernel: input: ITE8708 CIR transceiver as 
/devices/pnp0/00:03/rc/rc0/input6
2024-04-19T13:44:51.873072+00:00 host kernel: i2c i2c-2: 2/2 memory slots 
populated (from DMI)
2024-04-19T13:44:51.873076+00:00 host kernel: i2c i2c-2: Successfully 
instantiated SPD at 0x50
2024-04-19T13:44:51.873078+00:00 host kernel: ite-cir: probe of 00:03 failed 
with error -16
```

I reviewed kernel error message and this error is due to the
device/resource is busy or in use.  My colleague and I reviewed the ite-
cir driver source code and noticed the driver initialisation succeeds up
until L1404
https://github.com/torvalds/linux/blob/master/drivers/media/rc/ite-
cir.c#L1404 where it attempts to request_region, if it fails to do this
it will unregister the device.

The request region allocates a place in memory for the device to use, we
believe it’s using the ioport.h’s request region function
https://github.com/torvalds/linux/blob/master/include/linux/ioport.h#L278

When we added some debug lines to ite-cir we noticed that the memory
reference it is trying to allocate is 02f8-02ff. We checked the ioports
on 24.04 and noticed that the serial driver was taking up this reference
in memory when in 20.04 (The OS we currently use) and 23.04 it would
not.

Ubuntu 24.04 ioports

```
user@host:~$ sudo cat /proc/ioports
-0cf7 : PCI Bus :00
  02f8-02ff : serial
  03f8-03ff : serial
```

Ubuntu 20.04 ioports memory allocation

```
user@host:~$ sudo cat /proc/ioports
-0cf7 : PCI Bus :00
  02f8-02ff : ite-cir
  03f8-03ff : serial
```

When we investigated any changes that might cause this, we came with two
potential commits that were released in 6.5 that might have caused this
issue:

* 
https://github.com/torvalds/linux/commit/9d86719f8769244dc99b8cb6091c41eae3fd684f
* 
https://github.com/torvalds/linux/commit/84a9582fd203063cd4d301204971ff2cd8327f1a

The serial changes allow 16550/8250 driver to consume as many serial
ports as they require initializing the driver, originally they only used
1.  Due to this we noticed that when we checked the serial ports in use
by the device that 8250 was consuming the place in memory that ite-cir
should.

Ubuntu 24.04

```
user@host:~$ sudo setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 8250, Port: 0x02f8, IRQ: 3
```

Ubuntu 20.04

```
user@host:~$ sudo setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
```
[Regression]
We believe that the regression started from 6.5 kernel onwards based on the 
commit changes that were done to the serial driver that shipped to those 
kernels.  23.04 that uses 6.2 works as expected and shows no issues with using 
the serial port for IR while 23.10 that uses 6.5 and 24.04 that uses 6.8 does 
not load the ite-cir driver.

[Reproducible steps]

* Use Ubuntu 23.10 + or use Kernel 6.5+
* Use IR hardware that requires the ite-cir driver to be loaded
* Attempt to load ite-cir driver on boot of OS
* Check /var/log/kern.log for ite-cir driver failure

[Fix]

The requested solution would be to either:

* Set the serial driver to no longer consume more than 1 serial port
* Have the serial driver check what memory reference ite-cir driver needs to 
load, ignore that reference and then consume another point in memory instead.

We have found a workaround where we set the /etc/default/grub config to
make the 8250 use only 1 UART port, this allows ite-cir to consume the
port in memory like it use to, enabling us to use the driver again

/etc/default/grub

```
GRUB_CMDLINE_LINUX_DEFAULT="8250.nr_uarts=1"
```
The alternative fix is to have a startup script that will remove 8250 from 
using /dev/ttyS1 and then remove and re-add the ite-cir driver

```
#!/bin/bash

setserial /dev/ttyS1 uart none
modprobe -r ite-cir

```

[Diagnostic information]

version

```
Linux 

[Kernel-packages] [Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE

[Brian Murray]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  Suspend & Resume functionality broken/timesout in GCE

Status in Release Notes for Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Noble:
  New

Bug description:
  [Impact]
   
  Suspend/Resume capability is broken in all noble images with kernel version 
6.8.0-1007-gcp.

  GCE offers the capability to "Suspend" a VM to conserve power/lower
  costs when the instance is not in use [0]. It uses ACPI S3 signals to
  tell the guest to power down. This capability no longer works in the
  latest kernel with the following error:

  ```
  Operation type [suspend] failed with message "Instance suspend failed due to 
guest timeout."
  ```

  which points to the following [1].

  

  Refs:

  [0]: https://cloud.google.com/compute/docs/instances/suspend-resume-
  instance

  [1]:
  https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-
  suspend-resume#there_was_a_guest_timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions


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

[Kernel-packages] [Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE

[Philip Roche]

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

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

Title:
  Suspend & Resume functionality broken/timesout in GCE

Status in Release Notes for Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Noble:
  New

Bug description:
  [Impact]
   
  Suspend/Resume capability is broken in all noble images with kernel version 
6.8.0-1007-gcp.

  GCE offers the capability to "Suspend" a VM to conserve power/lower
  costs when the instance is not in use [0]. It uses ACPI S3 signals to
  tell the guest to power down. This capability no longer works in the
  latest kernel with the following error:

  ```
  Operation type [suspend] failed with message "Instance suspend failed due to 
guest timeout."
  ```

  which points to the following [1].

  

  Refs:

  [0]: https://cloud.google.com/compute/docs/instances/suspend-resume-
  instance

  [1]:
  https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-
  suspend-resume#there_was_a_guest_timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions


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

[Kernel-packages] [Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE

[Chloé Smith]

** Description changed:

- Suspend/Resume capability is broken in all noble images with kernel
- version
+ [Impact]
+  
+ Suspend/Resume capability is broken in all noble images with kernel version 
6.8.0-1007-gcp.
+ 
+ GCE offers the capability to "Suspend" a VM to conserve power/lower
+ costs when the instance is not in use [0]. It uses ACPI S3 signals to
+ tell the guest to power down. This capability no longer works in the
+ latest kernel with the following error:
+ 
+ ```
+ Operation type [suspend] failed with message "Instance suspend failed due to 
guest timeout."
+ ```
+ 
+ which points to the following [1].
+ 
+ 
+ 
+ Refs:
+ 
+ [0]: https://cloud.google.com/compute/docs/instances/suspend-resume-
+ instance
+ 
+ [1]:
+ https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-
+ suspend-resume#there_was_a_guest_timeout

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

Title:
  Suspend & Resume functionality broken/timesout in GCE

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  [Impact]
   
  Suspend/Resume capability is broken in all noble images with kernel version 
6.8.0-1007-gcp.

  GCE offers the capability to "Suspend" a VM to conserve power/lower
  costs when the instance is not in use [0]. It uses ACPI S3 signals to
  tell the guest to power down. This capability no longer works in the
  latest kernel with the following error:

  ```
  Operation type [suspend] failed with message "Instance suspend failed due to 
guest timeout."
  ```

  which points to the following [1].

  

  Refs:

  [0]: https://cloud.google.com/compute/docs/instances/suspend-resume-
  instance

  [1]:
  https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-
  suspend-resume#there_was_a_guest_timeout

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


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

[Kernel-packages] [Bug 2063315] [NEW] Suspend & Resume functionality broken/timesout in GCE

[Chloé Smith]

Public bug reported:

Suspend/Resume capability is broken in all noble images with kernel
version

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

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

Title:
  Suspend & Resume functionality broken/timesout in GCE

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  Suspend/Resume capability is broken in all noble images with kernel
  version

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


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

[Kernel-packages] [Bug 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)

[Launchpad Bug Tracker]

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

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

Title:
  Keyboard does not work after waking up from suspend with 5.15.0-105
  (but works with 5.15.0-101)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear Ubuntu maintainers, I think I found a regression in linux
  5.15.0-105.

  In the past few days, my keyboard stopped working after waking up from
  suspend (sleep), so I couldn't unlock my laptop. Various workarounds
  found on the internet helped, but I wanted to investigate if it was a
  gdm issue, grub, or a hardware failure. I managed to narrow it down to
  the kernel, which is why I'm filing this bug report.

  AFAICT the only keys that work are the keyboard lights and the
  brightness knobs (in the Fn functions). I can confirm that 5.15.0-105
  has the issue, and I can consistently reproduce it with the following
  steps:

  1. boot fresh with 5.15.0-105
  2. login to my account
  3. choose suspend from the power menu
  4. wake up

  
  Following the same steps above with the last kernel available does not cause 
the issue (package version 5.15.0-101.111). I'll keep using that one for the 
time being.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-105-generic 5.15.0-105.115
  ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148
  Uname: Linux 5.15.0-105-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philsf 5465 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 02:58:26 2024
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc
  InstallationDate: Installed on 2018-06-07 (2145 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic 
root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-105-generic N/A
   linux-backports-modules-5.15.0-105-generic  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.29
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2023
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 0TXW78
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Agoston Horvath]

Following the above guides results in:

$ cheese -d "Intel MIPI Camera"
[0:00:46.050565361] [4778] ERROR IPAModule ipa_module.cpp:172 Symbol 
ipaModuleInfo not found
[0:00:46.050587032] [4778] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: 
IPA module has no valid info
[0:00:46.050602739] [4778]  INFO Camera camera_manager.cpp:284 libcamera v0.2.0

(cheese:4778): cheese-WARNING **: 10:01:53.240: stream error: can't
negotiate buffers on port: ../src/gst/gstpipewiresrc.c(692):
on_state_changed ():
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Released
Status in ivsc-driver source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble 

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Agoston Horvath]

The Intel IPU6 in my Dell Precision 5680 fails in any which way I'm
trying to get it to work with ubuntu 24.04 (kernel 6.8.0-31-generic).
The clickyclicky 'Additional drivers' doesn't work, the oem-solutions-
group/intel-ipu6 PPA doesn't work. The failures are various, from not
even having a /dev/video* showing up to just having a buffer ioctl-
related error in v4l2-dependant software, to not finding the .zst
compressed firmware under /lib/firmware.

To add to the already confusing heap of issues, there's also a
libcamera0.2, that may or may not work - it didn't in my case, but I've
got to spend a few hours trying to explore that route.

I have to say this was a humiliating experience; there is virtually no
documentation, now HOWTO, only some vague guides that all end up with a
non-existant or non-working camera.

Is there some movement to get this fixed before the ubuntu 24.04
release?

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Released
Status in ivsc-driver source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's 

[Kernel-packages] [Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta

[lijian]

The 4/22 ISO still has this issue

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

Title:
  [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST
  screen disappears in Ubuntu24.04 Beta

Status in linux package in Ubuntu:
  New

Bug description:
  1.The Version of product
 # lsb_release -rd
No LSB modules are available.
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
  2.The version of package
 root@t:/tmp# apt-cache policy linux-image-6.8.0-22-generic
linux-image-6.8.0-22-generic:
Installed: 6.8.0-22.22
Candidate: 6.8.0-22.22
Version table:
*** 6.8.0-22.22 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 
Packages
100 /var/lib/dpkg/status
  3.Expected to happen
  Print kernel output information after the server's POST screen disappears
  4.Actual happend
  Print kernel output information before the server's POST screen disappears
  Please refer to the attached screenshot for details

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-22-generic 6.8.0-22.22
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 15 07:46 seq
   crw-rw 1 root audio 116, 33 Apr 15 07:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Apr 15 08:26:52 2024
  InstallationDate: Installed on 2024-04-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 
(20240410.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Lenovo ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=77cf1cbe-6d2e-4dec-9439-c7aa2a69b5d9 ro
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-22-generic N/A
   linux-backports-modules-6.8.0-22-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2023
  dmi.bios.release: 3.10
  dmi.bios.vendor: Lenovo
  dmi.bios.version: ESE121R-3.10
  dmi.board.asset.tag: None
  dmi.board.name: STA7B05327
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: None
  dmi.ec.firmware.release: 3.90
  dmi.modalias: 
dmi:bvnLenovo:bvrESE121R-3.10:bd11/15/2023:br3.10:efr3.90:svnLenovo:pnThinkSystemSR650V3MB,EGS,DDR5,SH,2U:pvr05:rvnLenovo:rnSTA7B05327:rvr05:cvnLenovo:ct23:cvrNone:sku7D75CTO0WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U
  dmi.product.sku: 7D75CTO0WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

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


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

[Kernel-packages] [Bug 2060437] Re: The module ib_ipoib does not load automatically on ubuntu server 24.04

[Kleber Sacilotto de Souza]

Could you please also provide a list of the loaded modules after a fresh
boot? We need to understand if only the ib_ipoib module is not loading
or if any additional dependency is also 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/2060437

Title:
  The module ib_ipoib does not load automatically on ubuntu server 24.04

Status in linux package in Ubuntu:
  New

Bug description:
  1. Fresh install Ubuntu server 24.04 on a server with mellanox card and 
infiniband mode
  2. As the module "ib_ipoib" does not load automatically, it fail to display 
the port via the command "ip a". The port can display after load manually.

  Please help to fix it, thanks.

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


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

[Kernel-packages] [Bug 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"

[Kleber Sacilotto de Souza]

This issue is definitely not a regression in 24.04 as it also affects
22.04 as reported.

For now this doesn't seem to be a kernel issue. The module
"iscsi_ibft.ko" is shipped by the linux-modules- package, therefore
if it's not loaded and configured during installation it seems to be a
user-space issue.

I'll keep it as "Triaged" though on the kernel side until we have more
information from the investigation.

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

Title:
  [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
  show " detected conn error (1020)"

Status in subiquity:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Description:
  When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can 
not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk 
and boot up to OS, the OS can not detect the remote iscsi disk either. 

  Reproduce Steps:
1. Install Ubunut 24.04 
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
   
  Configuration:
  System: Lenovo SR655V3
  OS:noble-live-server-amd64-0401.iso
  BMC Version ：2.30 (Build ID: KAX321V)
  UEFI Version:3.10 (Build ID: KAE115K)
  CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
  NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet 
Adapte 
  storage：Lenovo D7000 or Lenovo V7000

   Expected results:
   OS can recognize the remote iscsi disk

   Actual results:
   OS cannot recognize the remote iscsi disk.

  Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.

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


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

[Kernel-packages] [Bug 2063309] Re: RISC-V: nouveau 0000:05:00.0: timer: stalled at ffffffffffffffff

[Heinrich Schuchardt]

When connected before boot the HDMI output works fine.

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

Title:
  RISC-V: nouveau :05:00.0: timer: stalled at 

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  After connecting a monitor to an SiFive HiFive Unmatched board running
  kernel 6.8.0-28-generic I saw:

  nouveau :05:00.0: timer: stalled at 
  nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-28-generic 6.8.0-28.28.1
  ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1
  Uname: Linux 6.8.0-28-generic riscv64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20210714
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Wed Apr 24 09:43:12 2024
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2063309] [NEW] RISC-V: nouveau 0000:05:00.0: timer: stalled at ffffffffffffffff

[Heinrich Schuchardt]

Public bug reported:

After connecting a monitor to an SiFive HiFive Unmatched board running
kernel 6.8.0-28-generic I saw:

nouveau :05:00.0: timer: stalled at 
nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-28-generic 6.8.0-28.28.1
ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1
Uname: Linux 6.8.0-28-generic riscv64
ApportVersion: 2.28.1-0ubuntu2
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20210714
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Wed Apr 24 09:43:12 2024
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug cloud-image noble riscv64

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

Title:
  RISC-V: nouveau :05:00.0: timer: stalled at 

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  After connecting a monitor to an SiFive HiFive Unmatched board running
  kernel 6.8.0-28-generic I saw:

  nouveau :05:00.0: timer: stalled at 
  nouveau :05:00.0: Xorg[3338]: nv50cal_space: -16

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-28-generic 6.8.0-28.28.1
  ProcVersionSignature: Ubuntu 6.8.0-28.28.1-generic 6.8.1
  Uname: Linux 6.8.0-28-generic riscv64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20210714
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Wed Apr 24 09:43:12 2024
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"

[Kleber Sacilotto de Souza]

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

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

Title:
  [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
  show " detected conn error (1020)"

Status in subiquity:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Description:
  When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can 
not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk 
and boot up to OS, the OS can not detect the remote iscsi disk either. 

  Reproduce Steps:
1. Install Ubunut 24.04 
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
   
  Configuration:
  System: Lenovo SR655V3
  OS:noble-live-server-amd64-0401.iso
  BMC Version ：2.30 (Build ID: KAX321V)
  UEFI Version:3.10 (Build ID: KAE115K)
  CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
  NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet 
Adapte 
  storage：Lenovo D7000 or Lenovo V7000

   Expected results:
   OS can recognize the remote iscsi disk

   Actual results:
   OS cannot recognize the remote iscsi disk.

  Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.

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


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

[Kernel-packages] [Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[Daniel van Vugt]

Not having a monitors.xml is fine. I was only concerned about the
possibility of monitors.xml containing bad data.

What if you choose 'Ubuntu on Xorg' on the login screen (menu in the
bottom right corner). Does that prevent the bug from occurring?

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

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2024
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1UET46W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21B4S4QB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76465 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.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
  dmi.product.family: ThinkPad L13 Gen 3
  dmi.product.name: 21B4S4QB00
  dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
  dmi.product.version: ThinkPad L13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[J K]

I don't know if I have the fix for bug 2034664

I can't delete that monitors.xml since it doesn't exist in my computer
in that directory

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

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2024
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1UET46W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21B4S4QB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76465 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.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
  dmi.product.family: ThinkPad L13 Gen 3
  dmi.product.name: 21B4S4QB00
  dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
  dmi.product.version: ThinkPad L13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2063308] [NEW] lenovo p1g5 suspend issues with docking stations

[AaronMa]

Public bug reported:

Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery

Hello,
We are having trouble with our lenovo p1 laptops docking stations. When waking 
from suspend on Ubuntu with a docking station is an issue for some users even 
with Intel AMT disabled in BIOS.
The exact steps to reproduce are as follows:
1) Suspend/sleep the laptop
2) Plug the docking station into the laptop
3) Wake the laptop

The sleep settings in BIOS are set to Linux S3. Docking station issues,
such as Ethernet not working after waking, do not occur with
Windows/Linux sleep settings, but the laptop doesn't properly suspend
processes in Windows/Linux sleep mode and will overheat the laptop when
in an enclosed space such as a bag. Linux S3 is the only way we've found
laptops to not overheat after suspending, but we that makes the dock
inoperable after waking from suspend.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: AaronMa (mapengyu)
 Status: Triaged

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  lenovo p1g5 suspend issues with docking stations

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery

  Hello,
  We are having trouble with our lenovo p1 laptops docking stations. When 
waking from suspend on Ubuntu with a docking station is an issue for some users 
even with Intel AMT disabled in BIOS.
  The exact steps to reproduce are as follows:
  1) Suspend/sleep the laptop
  2) Plug the docking station into the laptop
  3) Wake the laptop

  The sleep settings in BIOS are set to Linux S3. Docking station
  issues, such as Ethernet not working after waking, do not occur with
  Windows/Linux sleep settings, but the laptop doesn't properly suspend
  processes in Windows/Linux sleep mode and will overheat the laptop
  when in an enclosed space such as a bag. Linux S3 is the only way
  we've found laptops to not overheat after suspending, but we that
  makes the dock inoperable after waking from suspend.

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


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

[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

[Heinrich Schuchardt]

With 6.8.0-31-generic I am not able to get any HDMI output on the Nezha D1 
either.
Unplugging and reconnecting did not help.

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2063300] Re: On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2063300

** Tags added: iso-testing

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

Title:
  On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not
  detected

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
  after reconnecting the USB Hub. It should have been detected while
  booting.

  $ lsusb -t
  /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  |__ Port 001: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M
  |__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M
  |__ Port 004: Dev 010, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
  /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  /:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M

  $ dmesg | grep -i usb
  [0.200341] usbcore: registered new interface driver usbfs
  [0.200487] usbcore: registered new interface driver hub
  [0.200635] usbcore: registered new device driver usb
  [   54.280232] ehci-platform 420.usb: EHCI Host Controller
  [   54.280305] ehci-platform 420.usb: new USB bus registered, assigned 
bus number 1
  [   54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420
  [   54.280897] ehci-platform 4101000.usb: EHCI Host Controller
  [   54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned 
bus number 2
  [   54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000
  [   54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
  [   54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.302466] usb usb1: Product: EHCI Host Controller
  [   54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.302495] usb usb1: SerialNumber: 420.usb
  [   54.312820] hub 1-0:1.0: USB hub found
  [   54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
  [   54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.329444] usb usb2: Product: EHCI Host Controller
  [   54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.329474] usb usb2: SerialNumber: 4101000.usb
  [   54.340294] hub 2-0:1.0: USB hub found
  [   54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform
  [   54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, 
bcdDevice= 1.00
  [   54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [   54.767133] usb 1-1: Product: USB2.0 HUB
  [   54.769892] hub 1-1:1.0: USB hub found
  [   55.201407] usb 1-1.2: new full-speed USB device number 3 using 
ehci-platform
  [   55.429317] usb 1-1.2: device descriptor read/all, error -32
  [   55.641464] usb 1-1.2: new full-speed USB device number 4 using 
ehci-platform
  [   55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller
  [   55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned 
bus number 3
  [   55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400
  [   55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller
  [   55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned 
bus number 4
  [   55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400
  [   55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.794158] usb usb3: Product: Generic Platform OHCI controller
  [   55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.794189] usb usb3: SerialNumber: 4101400.usb
  [   55.802158] hub 3-0:1.0: USB hub found
  [   55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.841574] usb usb4: Product: Generic Platform OHCI controller
  [   55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.841605] usb usb4: SerialNumber: 4200400.usb
  [   55.849788] hub 4-0:1.0: USB hub found
  [   57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not 
allowed for exclusive requests
  [   57.572184] musb-hdrc 

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

[bugproxy]

--- Comment From david_pa...@uk.ibm.com 2024-04-24 02:47 EDT---
Hi,
We have had a reply from the AIX support team (see below) explaining the RENEW 
requests. Do you have any further questions for the AIX support team or can we 
supply any further diagnostic information to progress this issue ?

Regarding the comment/question about RENEW reqs from Linux:

RENEW is done when half the lease period has elapsed without any state
operation going on.

Here, the Linux server's lease is 90 seconds. From an NFS perspective,
there is nothing strange or remarkable about the pattern of RENEW reqs
sent in the good & bad cases. If there is a specific question about
renews in the latest captures let us know.

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

Title:
  AIX 7.3 NFS client frequently returns an EIO error to an application
  when reading or writing to a file that has been locked with fcntl() on
  a Ubuntu 20.04 NFSV4 server

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl(). NFS server is 
Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not 
appear to affect other combinations of NFS client (including AIX 7.2) with this 
NFS server.

  The AIX team have indicated that the cause of the EIO is triggered by the NFS 
server returning a BAD_SEQID error which leads to the AIX NFS client 
incorrectly zeroing the stateid, which then leads to the NFS server returning a 
BAD_STATEID error and the NFS client then returns the EIO error. The AIX team 
would like to understand why the BAD_SEQID has been returned.
   
  ---uname output---
  Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
   
  Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 
2.30GHz  

  ---Steps to Reproduce---
   We cannot offer a simple way to recreate the problem as it involves IBM MQ 
running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 
storage.

  However, we can provide any requested trace or dumps from any or all
  of the involved machines.

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


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

[Kernel-packages] [Bug 2063300] Re: On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected

[Heinrich Schuchardt]

The problem did not occur on every boot.

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

Title:
  On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not
  detected

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
  after reconnecting the USB Hub. It should have been detected while
  booting.

  $ lsusb -t
  /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  |__ Port 001: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M
  |__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M
  |__ Port 004: Dev 010, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
  /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  /:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M

  $ dmesg | grep -i usb
  [0.200341] usbcore: registered new interface driver usbfs
  [0.200487] usbcore: registered new interface driver hub
  [0.200635] usbcore: registered new device driver usb
  [   54.280232] ehci-platform 420.usb: EHCI Host Controller
  [   54.280305] ehci-platform 420.usb: new USB bus registered, assigned 
bus number 1
  [   54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420
  [   54.280897] ehci-platform 4101000.usb: EHCI Host Controller
  [   54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned 
bus number 2
  [   54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000
  [   54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
  [   54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.302466] usb usb1: Product: EHCI Host Controller
  [   54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.302495] usb usb1: SerialNumber: 420.usb
  [   54.312820] hub 1-0:1.0: USB hub found
  [   54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
  [   54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.329444] usb usb2: Product: EHCI Host Controller
  [   54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.329474] usb usb2: SerialNumber: 4101000.usb
  [   54.340294] hub 2-0:1.0: USB hub found
  [   54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform
  [   54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, 
bcdDevice= 1.00
  [   54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [   54.767133] usb 1-1: Product: USB2.0 HUB
  [   54.769892] hub 1-1:1.0: USB hub found
  [   55.201407] usb 1-1.2: new full-speed USB device number 3 using 
ehci-platform
  [   55.429317] usb 1-1.2: device descriptor read/all, error -32
  [   55.641464] usb 1-1.2: new full-speed USB device number 4 using 
ehci-platform
  [   55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller
  [   55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned 
bus number 3
  [   55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400
  [   55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller
  [   55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned 
bus number 4
  [   55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400
  [   55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.794158] usb usb3: Product: Generic Platform OHCI controller
  [   55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.794189] usb usb3: SerialNumber: 4101400.usb
  [   55.802158] hub 3-0:1.0: USB hub found
  [   55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.841574] usb usb4: Product: Generic Platform OHCI controller
  [   55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.841605] usb usb4: SerialNumber: 4200400.usb
  [   55.849788] hub 4-0:1.0: USB hub found
  [   57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not 
allowed for exclusive requests
  [   57.572184] musb-hdrc musb-hdrc.2.auto: MUSB HDRC host driver
  [   57.572253] musb-hdrc musb-hdrc.2.auto: new USB bus registered, assigned 
bus number 5
  [   57.650728] usb usb5: New USB device 

[Kernel-packages] [Bug 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  In Progress

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2059822] Re: package linux-intel-iotg-tools-common 5.15.0-1050.56 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-b

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-intel-iotg-tools-common 5.15.0-1050.56 [modified:
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz
  usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf-
  buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz
  usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-
  daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-
  diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz
  usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf-
  kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz
  usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz
  usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz
  usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz
  usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz
  usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-
  script-python.1.gz usr/share/man/man1/perf-script.1.gz
  usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz
  usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf-
  top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf-
  version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-tools-common 5.15.0-101.111

Status in linux-intel-iotg package in Ubuntu:
  New

Bug description:
  Calculating upgrade... Done
  The following packages have been kept back:
apt apt-transport-https apt-utils libapt-pkg6.0 libsmbclient libwbclient0 
samba-libs
  The following packages will be upgraded:
linux-intel-iotg-tools-common
  1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
  Need to get 0 B/284 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  (Reading database ... 344068 files and directories currently installed.)
  Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1051.57_all.deb 
...
  Unpacking linux-intel-iotg-tools-common (5.15.0-1051.57) over 
(5.15.0-1050.56) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1051.57_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.15.0-101.111
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1051.57_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Mar 30 11:46:30 2024
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.15.0-101.111
  InstallationDate: Installed on 2024-01-11 (79 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.11
  SourcePackage: linux-intel-iotg
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2060373] Re: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade: 의존성 문제 - 설정하지 않고 남겨둠

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
  의존성 문제 - 설정하지 않고 남겨둠

Status in linux package in Ubuntu:
  New

Bug description:
  This occured while system updater installing packages with no user
  operation.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-generic-hwe-22.04 6.5.0.26.26
  ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jungwonyong   2613 F wireplumber
   /dev/snd/controlC0:  jungwonyong   2613 F wireplumber
   /dev/snd/seq:jungwonyong   2607 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Apr  7 12:08:46 2024
  ErrorMessage: 의존성 문제 - 설정하지 않고 남겨둠
  InstallationDate: Installed on 2024-01-25 (73 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ricifp@/vmlinuz-6.5.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_ricifp ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade: 
의존성 문제 - 설정하지 않고 남겨둠
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 16.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1620
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H470-PLUS
  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.:bvr1620:bd07/08/2021:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH470-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 2062433] Re: package firmware-b43-installer 1:019-8 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit s

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package firmware-b43-installer 1:019-8 failed to install/upgrade:
  installed firmware-b43-installer package post-installation script
  subprocess returned error exit status 1

Status in b43-fwcutter package in Ubuntu:
  New

Bug description:
  I have dual boot. Win 11 & Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: firmware-b43-installer 1:019-8
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Apr  7 12:58:17 2024
  ErrorMessage: installed firmware-b43-installer package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-08 (42 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1.1
   apt  2.7.3ubuntu0.1
  SourcePackage: b43-fwcutter
  Title: package firmware-b43-installer 1:019-8 failed to install/upgrade: 
installed firmware-b43-installer package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to mantic on 2024-04-07 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/2062433/+subscriptions


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

[Kernel-packages] [Bug 2063179] Re: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic package post-

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-modules-nvidia-470-6.5.0-27-generic
  6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-
  modules-nvidia-470-6.5.0-27-generic package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules-hwe-6.5 package in Ubuntu:
  New

Bug description:
  the problem occurred during installation while trying to remove
  previous package

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Apr 23 09:40:31 2024
  ErrorMessage: installed linux-modules-nvidia-470-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-01-25 (88 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.12
  SourcePackage: linux-restricted-modules-hwe-6.5
  Title: package linux-modules-nvidia-470-6.5.0-27-generic 
6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed 
linux-modules-nvidia-470-6.5.0-27-generic package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2063300] [NEW] On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected

[Heinrich Schuchardt]

Public bug reported:

A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
after reconnecting the USB Hub. It should have been detected while
booting.

$ lsusb -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
|__ Port 001: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M
|__ Port 004: Dev 010, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M

$ dmesg | grep -i usb
[0.200341] usbcore: registered new interface driver usbfs
[0.200487] usbcore: registered new interface driver hub
[0.200635] usbcore: registered new device driver usb
[   54.280232] ehci-platform 420.usb: EHCI Host Controller
[   54.280305] ehci-platform 420.usb: new USB bus registered, assigned bus 
number 1
[   54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420
[   54.280897] ehci-platform 4101000.usb: EHCI Host Controller
[   54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned bus 
number 2
[   54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000
[   54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
[   54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
[   54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   54.302466] usb usb1: Product: EHCI Host Controller
[   54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
[   54.302495] usb usb1: SerialNumber: 420.usb
[   54.312820] hub 1-0:1.0: USB hub found
[   54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
[   54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
[   54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   54.329444] usb usb2: Product: EHCI Host Controller
[   54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
[   54.329474] usb usb2: SerialNumber: 4101000.usb
[   54.340294] hub 2-0:1.0: USB hub found
[   54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform
[   54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, 
bcdDevice= 1.00
[   54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   54.767133] usb 1-1: Product: USB2.0 HUB
[   54.769892] hub 1-1:1.0: USB hub found
[   55.201407] usb 1-1.2: new full-speed USB device number 3 using ehci-platform
[   55.429317] usb 1-1.2: device descriptor read/all, error -32
[   55.641464] usb 1-1.2: new full-speed USB device number 4 using ehci-platform
[   55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller
[   55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned bus 
number 3
[   55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400
[   55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller
[   55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned bus 
number 4
[   55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400
[   55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
[   55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   55.794158] usb usb3: Product: Generic Platform OHCI controller
[   55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
[   55.794189] usb usb3: SerialNumber: 4101400.usb
[   55.802158] hub 3-0:1.0: USB hub found
[   55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
[   55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   55.841574] usb usb4: Product: Generic Platform OHCI controller
[   55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
[   55.841605] usb usb4: SerialNumber: 4200400.usb
[   55.849788] hub 4-0:1.0: USB hub found
[   57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not 
allowed for exclusive requests
[   57.572184] musb-hdrc musb-hdrc.2.auto: MUSB HDRC host driver
[   57.572253] musb-hdrc musb-hdrc.2.auto: new USB bus registered, assigned bus 
number 5
[   57.650728] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
[   57.650766] usb usb5: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   57.650784] usb usb5: Product: MUSB HDRC host driver
[   57.650799] usb usb5: Manufacturer: Linux 6.8.0-31-generic musb-hcd
[   57.650814] usb usb5: SerialNumber: musb-hdrc.2.auto
[   57.711752] hub 5-0:1.0: USB hub found
[   61.089405] usb 1-1.2: device descriptor read/64, error -71
[   66.477463] usb 1-1.2: device descriptor read/64, error 

[Kernel-packages] [Bug 2038933] Re: sun8i-dw-hdmi 5500000.hdmi: Couldn't get the HDMI PHY

[Heinrich Schuchardt]

With 6.8.0-31-generic I am not able to get any HDMI output on the LicheeRV Dock.
Unplugging and reconnecting did not help.

[0.133313] platform 546.tcon-top: Fixed dependency cycle(s) with 
/soc/hdmi@550
[0.141438] platform 546.tcon-top: Fixed dependency cycle(s) with 
/soc/hdmi@550
[0.141784] platform 550.hdmi: Fixed dependency cycle(s) with 
/soc/tcon-top@546
[0.151475] platform 550.hdmi: Fixed dependency cycle(s) with /connector
[0.151769] platform connector: Fixed dependency cycle(s) with 
/soc/hdmi@550
[   63.119552] sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY
[   63.287954] sun8i-dw-hdmi 550.hdmi: Detected HDMI TX controller v2.12a 
with HDCP (sun8i_dw_hdmi_phy)
[   63.298653] sun8i-dw-hdmi 550.hdmi: registered DesignWare HDMI I2C bus 
driver
[   63.299605] sun4i-drm display-engine: bound 550.hdmi (ops 
sun8i_dw_hdmi_ops [sun8i_drm_hdmi])
[   72.732580] rc rc0: dw_hdmi as /devices/platform/soc/550.hdmi/rc/rc0
[   72.733035] input: dw_hdmi as 
/devices/platform/soc/550.hdmi/rc/rc0/input1

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

Title:
  sun8i-dw-hdmi 550.hdmi: Couldn't get the HDMI PHY

Status in linux-riscv package in Ubuntu:
  Confirmed

Bug description:
  I am testing the Mantic preinstalled image on the LicheeRV Dock. HDMI
  output is not working.

  There is a kernel message "sun8i-dw-hdmi 550.hdmi: Couldn't get
  the HDMI PHY".

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 14:42:06 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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