date:20240221

Next time the problem happens please:

1. Reboot.

2. Run:

   journalctl -b-1 > prevboot.txt

3. Attach the resulting text file here.


** Summary changed:

- Xorg freeze
+ Xorg freeze: i915 flips and commits are timing out

** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)

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

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

Title:
  Xorg freeze: i915 flips and commits are timing out

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

Bug description:
  Random freezes occur since the installation of 6.5.x kernel. 
  Freeze occur several times a day, probably after touching the mouse or 
keyboard, but I'm not sure.
  App continue to work sound is OK, there is just no dispay updated.

  Booting to old 6.2 kernel solves the problem. I have tried all 6.5
  updates since the first released, but each time, I had a freeze after
  a few hours.

  Example of last mesg in dmesg when freeze occur :

  Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
  Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out

  or :
  Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), 
lowering kernel.perf_event_max_sample_rate to 79750
  Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
  Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
  Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
  Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
  Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
  Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait

[Kernel-packages] [Bug 2054560] [NEW] Xorg freeze: i915 flips and commits are timing out

2024-02-21 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Random freezes occur since the installation of 6.5.x kernel. 
Freeze occur several times a day, probably after touching the mouse or 
keyboard, but I'm not sure.
App continue to work sound is OK, there is just no dispay updated.

Booting to old 6.2 kernel solves the problem. I have tried all 6.5
updates since the first released, but each time, I had a freeze after a
few hours.

Example of last mesg in dmesg when freeze occur :

Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:274:DP-5] commit wait timed out
Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out

or :
Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), 
lowering kernel.perf_event_max_sample_rate to 79750
Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CONNECTOR:282:DP-5] commit wait timed out
Feb 13 11:36:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out

or

Feb 01 09:37:11 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] flip_done timed out
Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done 
timed out
Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* 
[CRTC:131:pipe B] commit wait timed out
Feb 01 09:37:45 pf46avw7 kernel: rfkill: input handler enabled
Feb 01 09:37:55 pf46avw7 kernel: i915

[Kernel-packages] [Bug 1930745] Re: AT Translated Set 2 keyboard locks up seemingly randomly, infinitely repeating last pressed key

2024-02-21 Thread John Jameson

A temporary fix is to fold down the screen of the laptop and then reopen
it. This may provide a clue as to the underlying problem.

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

Title:
  AT Translated Set 2 keyboard locks up seemingly randomly, infinitely
  repeating last pressed key

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

Bug description:
  I am running Ubuntu 20.04.2 LTS on my ThinkPad L15 laptop.

  From time to time the keyboard gets stuck / locked up. Sometimes it
  takes days to happen, sometimes it happens within a few minutes. It
  also does not seem to depend on the programs I am running, it seems to
  be entirely random. Basically, I am working/playing on the laptop and
  then suddenly the key I pressed last "gets stuck" and the keyboard
  does not respond any more. Other than that everything is running fine
  and I can still use the mouse and so on, but logging out does not
  resolve the issue and only a restart seems to work. I have also tried
  connecting a USB keyboard while the problem is occurring. The external
  keyboard is then detected and works fine, the built-in keyboard stops
  sending the signal and remains unresponsive.

  I have already mentioned the problem here, but it could not be resolved: 
  https://ubuntuforums.org/showthread.php?t=2460675
  I have also contacted Lenovo Hardware Support, and ran their tests, but those 
did not return anything, so they said it was not a hardware issue. 

  My best guess is that it is a bug in the driver for the AT Translated
  Set 2 keyboard (I have the German keyboard layout), which is listed as
  supported hardware. Current and latest driver version is 1.0.1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  3 13:45:29 2021
  InstallationDate: Installed on 2020-12-29 (156 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  Description of problem:

  Observed device_dax related probe errors in dmesg when HBM CPU is set
  to flat mode.  Duplicate device_dax ids were created and hence probing
  is failing.

  How reproducible:
  Frequently

  Version-Release
  Release:22.04.2, 22.10

  [Test Case]

  Steps to Reproduce:
  1. Set HBM cpu to flat mode in memory settings in BIOS.
  2. Boot to the OS.
  3. Perform OS warm boot cycle test.
  4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.

  Actual results:
  Observed device_dax related errors in dmesg, device Dax is creating 
dummy/duplicate devices and probe failing.

  Expected results:
  Dummy/duplicate devices should not create.

  [Fix]
  Upstream Fix
  
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/

  
  [Where problems could occur]

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2

  Additional info:
  SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should 
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is 
"mode":"devdax" which are actuall devadax to system-ram convertible devices. 
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of 
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0, 
5.0 etc..].

  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"devdax"---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"devdax" ---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    }
  ]
  root@ubuntu:/home/ubuntu# dmesg | grep -i error
  [   12.748884] device_dax: probe of dax2.0 failed with error -16
  [   12.748902] device_dax: probe of dax3.0 failed with error -16

  After reconfig-device devdax to system-ram below are the results:
  ---
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
  {
    "chardev":"dax0.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":2,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
  {
    "chardev":"dax1.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":3,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax4.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax1.0",

[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  linux tools packages for derived kernels refuse to install
  simultaneously due to libcpupower name collision

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple kernel flavours are conflicting with each on .deb / file
  level via their tools packages

   * Resolve the conflicting private libcpupower.so by statically
  linking it into the only C binary that uses said library in the linux-
  tools

  [ Test Plan ]

   * co-install tools packages from multiple kernel flavours of the same
  major version and abi, it should be successful

  [ Where problems could occur ]

   * If one tries really hard to find the private location of
  libcpupower.so and dlopen it by ever changing abi name, that will not
  be possible, until the separate bug report is fixed to introduce the
  public stable libcpupower.so.1 which so far ubuntu has never yet
  provided.

  [ Other Info ]
   
   * original bug report

  Taking linux-kvm and linux-gcp for example:

  $ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103384 2023-07-25 20:00 
./usr/lib/libcpupower.so.6.2.0-1011
  $ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103392 2023-08-16 15:08 
./usr/lib/libcpupower.so.6.2.0-1011

  linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
  a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
  utilities, and yet files of the same full path cannot be installed
  from two distinct debian packages, which follows we won't be able to
  install two linux-tools packages of two different derived kernels on
  the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
  Uname: Linux 6.5.0-9004-generic x86_64
  NonfreeKernelModules: zfs wl
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicamo 6331 F wireplumber
   /dev/snd/controlC0:  vicamo 6331 F wireplumber
   /dev/snd/seq:vicamo 6315 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Sep 14 23:31:16 2023
  InstallationDate: Installed on 2022-04-10 (522 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic 
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-generic N/A
   linux-backports-modules-6.5.0-9004-generic  N/A
   linux-firmware  20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.60.3.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#

[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Change in trace file leads to test timeout in ftrace tests on 5.15
  ARM64

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc,
  event-pid.tc in linux/tools/testing/selftests/ftrace will take too
  much time to run and consequently leads to test timeout.

  The culprit is the `cat` command on the changing trace file.

  [Fix]
  * 25b9513872 selftests/ftrace: Stop tracing while reading the trace
    file by default

  This patch can be cherry-picked into Jammy. I didn't see this issue in
  our 5.4 kernels. And it's already landed in newer kernels.

  [Test]
  On an ARM64 testing node, apply this patch to the kernel tree and run
  event-pid.tc test in linux/tools/testing/selftests/ftrace with:

    sudo ./ftracetest -vvv test.d/event/event-pid.tc

  The test should finish within a few minutes.

  [Regression Potential]
  Change limited to testing tools, it should not have any actual impact
  to kernel functions.

  == Original Bug Report ==
  First time seen this since ftrace refactor out from ubuntu_kernel_selftests 
to ubuntu-kselftests-ftrace

  Issue found on ARM64 nodes with both generic / generic-64k kernel.

  Partial test log:
   Running './ftracetest -vvv test.d/event/subsystem-enable.tc'
   === Ftrace unit tests ===
   
   [1] event tracing - enable/disable with event level files
   + [ 2 -eq 1 ]
   + [ -f set_event_pid ]
   + echo
   + [ -f set_ftrace_pid ]
   + echo
   + [ -f set_ftrace_notrace ]
   + echo
   + [ -f set_graph_function ]
   + echo
   + tee set_graph_function set_graph_notrace
   + [ -f stack_trace_filter ]
   + echo
   + [ -f kprobe_events ]
   + echo
   + [ -f uprobe_events ]
   + echo
   + [ -f synthetic_events ]
   + echo
   + [ -f snapshot ]
   + echo 0
   + clear_trace
   + echo
   + enable_tracing
   + echo 1
   + . 
/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc
   + echo sched:sched_switch
   + yield
   + ping 127.0.0.1 -c 1
   PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
   64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms

   --- 127.0.0.1 ping statistics ---
   1 packets transmitted, 1 received, 0% packet loss, time 0ms
   rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms
   + cat trace
   + grep sched_switch
   + wc -l
   Timer expired (600 sec.), nuking pid 20982

  From the code (tools/testing/selftests/ftrace/test.d/event/event-
  enable.tc) this test is trying to run:

  count=`cat trace | grep sched_switch | wc -l`

  This command caused the timeout as `cat trace` seems to be never
  ending.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+subscriptions


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

[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System can't enter suspend on AHCI mode,
  the CPU FAN and System FAN is running, PSU LED is on.
  When fail to enter suspend, remove ODD, the system can successfully enter 
suspend again.

  [Fix]
  Enable LPM on Alder Lake-P AHCI.

  [Test Cases]
  1. enabled AHCI on target machine.
  2. boot with kernel applied fix.
  3. suspend then check slp_s0_residency_usec_cstate_show
  ~~~
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  4951200
  Package C2 : 63571033
  Package C3 : 6212
  Package C6 : 5633477
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 5255561
  u@ubuntu:~$ sudo rtcwake -m mem -s 10
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  12965280
  Package C2 : 75052691
  Package C3 : 46989
  Package C6 : 8108332
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 13628111
  ~~~

  [where the issue could happen]
  Medium, Intel promise there's no issue of ADL AHCI and
  they will take responsibility after regression.
  Intel also take LPM as POR so they will fix any issues.

  [Misc]
  Because the board_ahci_mobile is still not modified to board_ahci_low_power 
on Jammy,
  provide a single patch for Jammy.

  For generic J/M, passed the all arch compilations on cbd,
  Jammy,
  ~~~
  $ git push j_cbd
  Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ
  remote: * 0/1 workers busy, 0 builds queued
  remote: 2023-11-17 19:50:25  kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK
  remote: 2023-11-17 20:18:29  kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK
  remote: 2023-11-17 20:01:41  kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK
  remote: 2023-11-17 20:31:51  kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK
  remote: 2023-11-17 20:37:25  kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK
  remote: 

  To cbd.kernel:jammy.git
   * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next
  ~~~

  Lunar,
  $ git push l_cbd
  Enumerating objects: 9, done.
  Counting objects: 100% (9/9), done.
  Delta compression using up to 8 threads
  Compressing objects: 100% (5/5), done.
  Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done.
  Total 5 (delta 4), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-915de03d6ecf-V1nm
  remote: * 9/9 workers busy, 0 builds queued
  remote: 2023-11-20

[Kernel-packages] [Bug 2041842] Re: Kernel doesn't compile with CONFIG_IMA

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Kernel doesn't compile with CONFIG_IMA

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

Bug description:
  Because of typo error in function declaration kernel doesn't compile
  with specific configuration

  Steps to reproduce:

  make defconfig
  ./scripts/config --file .config \
   -d SECURITY_SELINUX \
   -e IMA
  make olddefconfig
  grep -E "CONFIG_IMA=|CONFIG_IMA_LSM_RULES" .config
  make bzImage

  Grep should return "CONFIG_IMA=y" but not "CONFIG_IMA_LSM_RULES=y"

  Error:

  In file included from security/integrity/ima/ima_fs.c:25:
  security/integrity/ima/ima.h:440:41: error: unknown type name 'strcut'; did 
you mean 'struct'?
440 | static inline int ima_filter_rule_match(strcut lsmblob *blob, u32 
field, u32 op,
| ^~
| struct
  make[3]: *** [scripts/Makefile.build:297: security/integrity/ima/ima_fs.o] 
Error 1
  make[2]: *** [scripts/Makefile.build:560: security/integrity/ima] Error 2
  make[1]: *** [scripts/Makefile.build:560: security/integrity] Error 2

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


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

[Kernel-packages] [Bug 2042888] Re: It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic.

2024-02-21 Thread Kokoro Natsume

I have suffered the same issue. I have found that I lost one CPU thread
after upgrading amd64-microcode from `3.20191218.1ubuntu1` to
`3.20191218.1ubuntu1.2`. Backporting the latest microcode resolves the
issue.

OS: Ubuntu 20.04.6 LTS
Release: 20.04
Kernel: 5.4.0-144-generic
CPU: 2x EPYC 9654
DIMM: 24x Micron DDR5 64G

lscpu log show Off-line CPU(s) info as below. Please note that my SMT is
enabled but "Thread(s) per core" shows "1":

Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   52 bits physical, 57 bits virtual
CPU(s):  384
On-line CPU(s) list: 0-191,193-383
Off-line CPU(s) list:192
Thread(s) per core:  1
Core(s) per socket:  96
Socket(s):   2
NUMA node(s):2
Vendor ID:   AuthenticAMD
CPU family:  25
Model:   17
Model name:  AMD EPYC 9654 96-Core Processor
Stepping:1
Frequency boost: enabled

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

Title:
  It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system
  dmesg log with kernel version 6.2.0-060200-generic.

Status in linux-hwe package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 22.04.3 LTS
  Release: 22.04
  Kernel: 6.2.0-060200-generic
  CPU: 1x EPYC 9654
  DIMM: 2x Samsung DDR5 16G

  1.Install Ubuntu 22.04.3 and upgrade its kernel to 6.2.0-060200-generic (also 
tried on kernel 6.5.7-060507)
  2.Reboot system and enable SMT-Control from BIOS.
  3.Boot to system to read lscpu.txt and dmesg.txt,
  lscpu log show Off-line CPU(s) info as below:

  CPU(s):  192
  On-line CPU(s) list: 0-95,97-191
  Off-line CPU(s) list:96
  Vendor ID:   AuthenticAMD
  Model name:  AMD EPYC 9654 96-Core Processor
  CPU family:  25
  Model:   17
  Thread(s) per core:  2
  Core(s) per socket:  96
  Socket(s):   1
  Stepping:1
  Frequency boost: enabled

  dmesg log show CPU fail info as below,

  [0.360560] smp: Bringing up secondary CPUs ...
  [0.360708] x86: Booting SMP configuration:
  [0.360711]  node  #0, CPUs:  #1   #2   #3   #4   #5   #6   #7 
  #8   #9  #10  #11  #12  #13  #14  #15  #16  #17  #18  #19  #20  #21  #22  #23 
 #24  #25  #26  #27  #28  #29  #30  #31  #32  #33  #34  #35  #36  #37  #38  #39 
 #40  #41  #42  #43  #44  #45  #46  #47  #48  #49  #50  #51  #52  #53  #54  #55 
 #56  #57  #58  #59  #60  #61  #62  #63  #64  #65  #66  #67  #68  #69  #70  #71 
 #72  #73  #74  #75  #76  #77  #78  #79  #80  #81  #82  #83  #84  #85  #86  #87 
 #88  #89  #90  #91  #92  #93  #94  #95  #96
  [   10.631524] smpboot: do_boot_cpu failed(-1) to wakeup CPU#96
  [   10.631842]   #97

  BTW, we also find the same bug on AMD EPYC 9534 64-Core CPU with
  Ubuntu 22.04.3-kernel 6.2.0 and 6.5.7.

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


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

[Kernel-packages] [Bug 2044192] Re: Patches needed for AmpereOne (arm64)

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Patches needed for AmpereOne (arm64)

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

Bug description:
  [Impact]

  * Google requested patches for AmpereOne machine type

  [Fix]

  * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 
5.15 GCP and Focal 5.4 GCP for now
  * Also submitting to Jammy 5.15 generic
  * Cherry-picks from upstream

  db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround 
synchronisation around")
  c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq 
counters")
  ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on 
CVAL programming")
  41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the 
TVAL programming interface")
  012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL 
implementations")
  30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to 
the core code")
  8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer 
programming over to CVAL")
  72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs 
callback ordering issue")
  ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from 
erratum function names")
  a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer 
programming over to CVAL")
  1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer 
register accessors to u64")
  d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read 
accessors")
  4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for 
unhandled register accesses")

  [Test Case]

  * Compile tested
  * Boot tested on GCP AmpereOne instance

  [Where things could go wrong]

  * Low chance of regression. Changes isolated to ARM timers.

  [Other Info]

  * SF #00372821

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


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

[Kernel-packages] [Bug 2045385] Re: Add ODM driver rtc-pcf85263

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Add ODM driver rtc-pcf85263

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

Bug description:
  From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:43:41 +0100
  Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385

  
  [ Impact ]
  rtc-pcf85263 driver needed for ODM partner

  [ Test Plan ]

  Load the driver setting the timestamp level to 0 (default to 1) :
  modprobe rtc-pcf85263 tsl=0

  export the rtc device:
  echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device

  RTC device should act as a standard RTC,
  hwclock -r -f /dev/rtc1 #for reading
  hwclock -w -f /dev/rtc1 #for writing

  This driver has anti-tampering function.
  Get the current tamper timestamp:
  cat /sys/class/rtc/rtc1/device/timestamp1

  unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the 
anti-tampering goes in open state.
  The timestamp should be updated to the current time.

  [ Where problems could occur ]

  Events could occur on the I2C bus communication.

  [ Other Info ]

  X-HWE-Bug: Bug #2046985

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


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

[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  AppArmor patch for mq-posix interface is missing in jammy

Status in linux package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in livecd-rootfs source package in Jammy:
  New

Bug description:
  [ Impact ]

  mq-posix snapd interface does not work on Ubuntu Core 22. It results
  in permission denied even all interfaces are connected.

  Our brandstore customer is using posix message queue for IPC between
  snaps. They added mq-posix interface and connected them properly but
  getting permission denied error.

  The AppArmor patch for posix message queue created for other customer
  did not land in the standard jammy kernel.

  Userspace support for AppArmor message queue handling is already
  present in Ubuntu Core 22, it is just missing from the kernel.

  [ Test Plan ]

   * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or 
Classic 22.04 with the standard kernel.
   * Example snaps for testing: 
https://code.launchpad.net/~itrue/+git/mqtest-provider and 
https://code.launchpad.net/~itrue/+git/mqtest-client

  [ Where problems could occur ]

   * The patches already exist for 5.15 and have been used on other
  private customer kernels and all kernels released after 22.04, so
  there is already a good track record for this patchset and it
  shouldn't create any issues.

  [ Other Info ]
   
   * This is a time-sensitive issue for a paying customer

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


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

[Kernel-packages] [Bug 2045386] Re: Add ODM driver gpio-m058ssan

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Add ODM driver gpio-m058ssan

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

Bug description:
  From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:45:07 +0100
  Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386

  [ Impact ]
  gpio-m058ssan driver needed for ODM partner

  [ Test Plan ]

  Connect the loopback GPIO connector to the ReliaCOR-40-13 system and
  connect the power supply of the GPIO connector.

  insert the "m058ssan" module:
  modprobe m058ssan

  create GPIOchip:
  echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device

  get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs ,
  the latter 8 are GPIs.

  Set and reset all of the GPOs one at a time and check that the
  corresponding GPI is set and reset accordingly.

  [ Where problems could occur ]

  Make sure that the power supply of the GPIO connector is correctly connected, 
otherwise the GPI will always report 0.
  Events could occur on the i2c bus communication that may cause miss-behavior 
of the driver.

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  [Debian] autoreconstruct - Do not generate chmod -x for deleted  files

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Debian source format 1.0 cannot remove files, create symlinks and change
  permission in the .diff.gz tarball. Therefore any changes in these 3
  categories cannot be represented without any tricks. To solve this,
  the `reconstruct` script is used every time we build the source package.
  The script is generated by `gen-auto-reconstruct` script during `cranky
  close`. It checks if there has been any changes in the 3 categories
  mentioned above between the upstream version (i.e v6.5) and the current one.
  The problem with the script is that in case a file A was removed since the
  upstream version was released, the `reconstruct` script will contains
  these commands in this exact order:
  rm -f A
  chmod -x A
  The second command will fail because file A does not exist anymore.
  This is solved by generating the `chmod +/-x` commands before `rm`.
  Which results in:
  chmod -x A
  rm -f A
  But because the reconstruct script is used during `clean` rule which is
  triggered pretty much during every cranky step which is run in the
  source repo, the first command will always file because file A is not
  present anymore in the tree. To solved this, any `chmod` change is added
  only if the file has not been deleted. Therefore if file A has been
  deleted, the `reconstruct` script will contain only this:
  rm -f A

  [Fix]
  Generate chmod commands first.
  And when generating chmod -x command, first check if the file has been 
deleted. If yes, no need for a chmod command.

  [Test Plan]
  It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and 
it reconstruct script looked correct.

  [Other Info]
  An example of this is #lp2038611 where `script/is_rust_module.sh` was 
removed, but we keep seeing
  "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory"
  because `rm -f` and `chmod -x` command were generated.

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


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

[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Add ODM driver f81604 usb-can

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

Bug description:
  From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:46:08 +0100
  Subject: [PATCH 3/3] Add f81604 usb-can kernel driver

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387

  [ Impact ]
  f81604  driver needed for ODM partner

  [ Test Plan ]

  Install can-utils

  apt install can-utils

  insert the driver:
  modprobe f81604

  two socket can interfaces will be created, can0 and can1

  connect the DB9 cable and termination provided.
  Set up the two interfaces:
  ip link set can1 up type can bitrate 50
  ip link set can1 up type can bitrate 50
  candump can0

  In another shell run:
  cansend can1 123#DEADBEEF

  The first shell should report the received frame. Switch the
  interfaces in the last commands to test the frame flow in the other
  way around.

  [ Where problems could occur ]
  USB bus miss-behavior could cause issues to the driver.

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2046217] Re: Some machines can't pass the pm-graph test

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Some machines can't pass the pm-graph test

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-6.5 source package in Jammy:
  Fix Released
Status in linux-signed-hwe-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Fix Released
Status in linux-hwe-6.5 source package in Mantic:
  New
Status in linux-signed-hwe-6.5 source package in Mantic:
  New
Status in linux source package in Noble:
  Confirmed
Status in linux-hwe-6.5 source package in Noble:
  New
Status in linux-signed-hwe-6.5 source package in Noble:
  In Progress

Bug description:
  == SRU Justification ==
  [Impact]
  When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system
  resume, NULL pointer dereference occurs and the system stops working.

  [Fix]
  Rescan the bus in order to reprobe the device to avoid mac80211 layer
  gets messed up.

  [Test]
  With the fix in place, system keeps working after firmware issue occurs.
  Verified with thousand times of suspend.

  [Where problems could occur]
  If the firmware/hardware is really dead and beyond recoverable, the same
  process can be triggered again and again.

  == Original bug report ==
  During the jammy-hwe migration test, I found some machines failed to run the 
pm-graph. 
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)

  One of machine when I rerun it locally, it passed, but others are
  still failed.

  Following are the machines failed to run pm-graph.
  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201702-25401/
  https://certification.canonical.com/hardware/202002-27718/
  https://certification.canonical.com/hardware/201711-25989/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Tue Dec 12 02:48:24 2023
  InstallationDate: Installed on 2023-02-22 (293 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2046105] Re: Sound: Add rtl quirk of M90-Gen5

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Sound: Add rtl quirk of M90-Gen5

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

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


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

[Kernel-packages] [Bug 2047382] Re: Hotplugging SCSI disk in QEMU VM fails

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Hotplugging SCSI disk in QEMU VM fails

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
  Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest 
kernels >= 6.5 might be broken.
  The inconsistency suggests a potential race condition.

  [Fix]
  Reverting the two specified commits appears to restore reliability.
  ==
  cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only 
for non-root bus
  40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  Upstream has resolved the issue by reverting both commits through a commit 
placed below.
  ==
  5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  [Test Plan]
  1. Create a VM
  virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk 
path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio
  -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0
  2. Prepare two XMLs for adding two disk devices
  # cat disk_X.xml
  
    
    
    
  
  3. Hotplug disks and check for success
  virsh attach-device scsi_test disk_X.xml

  [Where problems could occur]
  The patch reverts two commits that previously addressed long-standing issues 
related to hotplugging devices with large BARs.
  While this reversion may reintroduce legacy issues, it does not introduce new 
problems.
  The associated risks are deemed low, making it worthwhile to address timing 
issues during the hotplugging of SCSI disks in QEMU VM.

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


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

[Kernel-packages] [Bug 2047630] Re: Add quirk to disable i915 fastboot on B PC

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  Add quirk to disable i915 fastboot on B PC

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

Bug description:
  [Impact]
  Some displays connect to the B PC device got the garbled display

  [Fix]
  The issue will disappear after commit 
5ac860cc52540df8bca27e0bb25b6744df67e8f0,
  but these patches cannot be backported from 5.19 to 5.15. So add quirk
  to force disable the i915 fastboot on the device to fix the abnormal display

  [Test Case]
  1. Connect the display and power on the B PC device
  2. Check the display for boot up

  [Where problems could occur]
  Quirk only on the B PCs. Risk of regression is low.

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


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

[Kernel-packages] [Bug 2049689] Re: partproke is broken on empty loopback device

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  partproke is broken on empty loopback device

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

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


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

[Kernel-packages] [Bug 2052479] Re: apply nvidia-tegra patches 2024 Jan 16-Feb 5

This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
'verification-failed-jammy-linux-nvidia-tegra'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 
verification-needed-jammy-linux-nvidia-tegra

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

Title:
  apply nvidia-tegra patches 2024 Jan 16-Feb 5

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

Bug description:
  Apply patches to linux-nvidia-tegra and linux-nvida-tegra-igx.

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


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

[Kernel-packages] [Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data

2024-02-21 Thread Matthew Ruffell

Submitted the patch as SRU to mantic. Noble will pick it up when the
kernel team pulls in 6.8-rc5.

Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149042.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149043.html

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

Title:
  smb: wsize blocks of bytes followed with binary zeros on copy,
  destroying data

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

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

  [Impact]

  Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
  set will see data destruction when copying files from their systems
  onto a cifs smb mount.

  wsize defaults to 65535 bytes, but when set to smaller values, like
  16850, users will see blocks of 16850 bytes copied over, followed by
  3900 binary zeros, followed by the next block of data followed by more
  binary zeros. This destroys what you are copying, and the data
  corruption is completely silent.

  A workaround is to set wsize to a multiple of PAGE_SIZE.

  [Fix]

  This was fixed upstream in 6.8-rc5 by the following:

  commit 4860abb91f3d7fbaf8147d54782149bb1fc45892
  Author: Steve French 
  Date: Tue Feb 6 16:34:22 2024 -0600
  Subject: smb: Fix regression in writes when non-standard maximum write size 
negotiated
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4860abb91f3d7fbaf8147d54782149bb1fc45892

  This patch has been selected for upstream stable.

  The patch looks at wsize negotiation from the server, and also what is set on 
the mount command line, and if not a multiple of PAGE_SIZE, rounds it down, 
taking care to not be 0.
  The real corruption bug still exists in netfs/folios subsystems and we are 
looking for it still, but this solves the immediate data corruption issues on 
smb.

  [Testcase]

  Start two VMs, one for the server, and the other, the client.

  Server
  --

  $ sudo apt update
  $ sudo apt upgrade
  $ sudo apt install samba
  $ sudo vim /etc/samba/smb.conf 
  server min protocol = NT1
  [sambashare]
  comment = Samba on Ubuntu
  path = /home/ubuntu/sambashare
  read only = no
  browsable = yes
  $ mkdir ~/sambashare
  $ sudo smbpasswd -a ubuntu

  Client
  --

  $ sudo apt update
  $ sudo apt install cifs-utils
  $ mkdir ~/share
  $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 
//192.168.122.172/sambashare ~/share
  $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc 
-aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing 
--format '40/1 "%02x"' --format '"\n"' >"testdata.txt" )
  $ sha256sum testdata.txt 
  9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2  testdata.txt

  Now copy the file to the share.

  Client
  --
  $ cp testdata.txt share/

  Server
  --
  $ sha256sum sambashare/testdata.txt 
  9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866  
sambashare/testdata.txt

  The SHA256 hash is different. If you view the file with less, you will
  find a block of wsize=16850 bytes, then 3900 bytes of binary zeros,
  followed by another wsize=16850 bytes, then 3900 bytes of binary
  zeros, etc.

  An example of a broken file is:
  https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt

  [Where problems could occur]

  We are changing the wsize that the SMB server negotiates or the user
  explicitly sets on the mount command line to a safe value, if the
  asked for value was not a multiple of PAGE_SIZE.

  It is unlikely that any users will notice any difference. If the wsize
  happens to be rounded down to a significantly smaller number, there
  may be a small performance impact, e.g. you set wsize=8094 for some
  reason, it would round down to wsize=4096, and lead to double the
  writes. At least you have data integrity though.

  Most users default to wsize=65535, and will have no impact at all.
  Only those with very old smb 1.0 servers that negotiate down to 16850
  will see any difference.

  If a regression were to occur, it could result in user's wsize being
  incorrectly set, leading to the underlying netfs/folios data
  corruption being triggered and causing data corruption.

  [Other info]

  The issue was introduced in 6.3-rc1 by:

  commit d08089f649a0cfb2099c8551ac47eef0cc23fdf2
  Author: David Howells 
  Date: Mon Jan 24 21:13:24 2022 +
  Subject: cifs: Change the I/O paths to use an iterator rather than a page list
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d08089f649a0cfb2099c8551ac47eef0cc23fdf2

  Upstream mailing list discussion:

  https://lore.kernel.org/linux-

[Kernel-packages] [Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data

2024-02-21 Thread Matthew Ruffell

** Description changed:

+ BugLink: https://bugs.launchpad.net/bugs/2049634
+
[Impact]

Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
set will see data destruction when copying files from their systems onto
- a cifs smb 1.0 mount.
+ a cifs smb mount.

wsize defaults to 65535 bytes, but when set to smaller values, like
16850, users will see blocks of 16850 bytes copied over, followed by
3900 binary zeros, followed by the next block of data followed by more
- binary zeros.
+ binary zeros. This destroys what you are copying, and the data
+ corruption is completely silent.

- A workaround is to increase wsize, but this only works for small files,
- as any files larger than wsize will see the bug.
+ A workaround is to set wsize to a multiple of PAGE_SIZE.

- Most users will want to use the 6.2 HWE kernel until this is fixed.
+ [Fix]
+
+ This was fixed upstream in 6.8-rc5 by the following:
+
+ commit 4860abb91f3d7fbaf8147d54782149bb1fc45892
+ Author: Steve French
+ Date: Tue Feb 6 16:34:22 2024 -0600
+ Subject: smb: Fix regression in writes when non-standard maximum write size
negotiated
+ Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4860abb91f3d7fbaf8147d54782149bb1fc45892
+
+ This patch has been selected for upstream stable.
+
+ The patch looks at wsize negotiation from the server, and also what is set on
the mount command line, and if not a multiple of PAGE_SIZE, rounds it down,
taking care to not be 0.
+ The real corruption bug still exists in netfs/folios subsystems and we are
looking for it still, but this solves the immediate data corruption issues on
smb.

[Testcase]

Start two VMs, one for the server, and the other, the client.

Server
--

$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
server min protocol = NT1
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
read only = no
browsable = yes
$ mkdir ~/sambashare
$ sudo smbpasswd -a ubuntu

Client
--

$ sudo apt update
$ sudo apt install cifs-utils
$ mkdir ~/share
$ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850
//192.168.122.172/sambashare ~/share
$ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc
-aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing
--format '40/1 "%02x"' --format '"\n"' >"testdata.txt" )
$ sha256sum testdata.txt
9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt

Now copy the file to the share.

Client
--
$ cp testdata.txt share/

Server
--
$ sha256sum sambashare/testdata.txt
9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866
sambashare/testdata.txt

The SHA256 hash is different. If you view the file with less, you will
find a block of wsize=16850 bytes, then 3900 bytes of binary zeros,
followed by another wsize=16850 bytes, then 3900 bytes of binary zeros,
etc.

An example of a broken file is:
https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt

[Where problems could occur]

+ We are changing the wsize that the SMB server negotiates or the user
+ explicitly sets on the mount command line to a safe value, if the asked
+ for value was not a multiple of PAGE_SIZE.
+
+ It is unlikely that any users will notice any difference. If the wsize
+ happens to be rounded down to a significantly smaller number, there may
+ be a small performance impact, e.g. you set wsize=8094 for some reason,
+ it would round down to wsize=4096, and lead to double the writes. At
+ least you have data integrity though.
+
+ Most users default to wsize=65535, and will have no impact at all. Only
+ those with very old smb 1.0 servers that negotiate down to 16850 will
+ see any difference.
+
+ If a regression were to occur, it could result in user's wsize being
+ incorrectly set, leading to the underlying netfs/folios data corruption
+ being triggered and causing data corruption.
+
[Other info]

- Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline
- 6.8-rc3.
+ The issue was introduced in 6.3-rc1 by:
+
+ commit d08089f649a0cfb2099c8551ac47eef0cc23fdf2
+ Author: David Howells
+ Date: Mon Jan 24 21:13:24 2022 +
+ Subject: cifs: Change the I/O paths to use an iterator rather than a page list
+ Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d08089f649a0cfb2099c8551ac47eef0cc23fdf2
+
+ Upstream mailing list discussion:
+
+ https://lore.kernel.org/linux-
+
cifs/6a65b2d1-7596-438a-8ade-2f7526b15...@rd10.de/T/#m22cd9b7289f87cd945978bd7995bcaf1beebfe67

** Tags added: mantic noble

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

Title:
smb: wsize blocks of bytes

[Kernel-packages] [Bug 2054614] Re: please include dummy_hcd module in kernel package

2024-02-21 Thread roland aus köln

https://lists.ubuntu.com/archives/kernel-team/2009-February/004192.html

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

Title:
  please include dummy_hcd module in kernel package

Status in linux package in Ubuntu:
  New

Bug description:
  please add CONFIG_USB_DUMMY_HCD=m ( as CONFIG_USB_DUMMY_HCD is not set
  )

  adding this module should do no harm. it's useful for simulating usb
  devices

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


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

[Kernel-packages] [Bug 2054614] [NEW] please include dummy_hcd module in kernel package

2024-02-21 Thread roland aus köln

Public bug reported:

please add CONFIG_USB_DUMMY_HCD=m ( as CONFIG_USB_DUMMY_HCD is not set )

adding this module should do no harm. it's useful for simulating usb
devices

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

Title:
  please include dummy_hcd module in kernel package

Status in linux package in Ubuntu:
  New

Bug description:
  please add CONFIG_USB_DUMMY_HCD=m ( as CONFIG_USB_DUMMY_HCD is not set
  )

  adding this module should do no harm. it's useful for simulating usb
  devices

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


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

[Kernel-packages] [Bug 1073089] Re: ubuntu kernel does not support gadgetfs

2024-02-21 Thread roland aus köln

is there a reason why ubuntu still has no dummy_hcd module, i.e. is
building kernel without CONFIG_USB_DUMMY_HCD=m ?

this sucks , and other distributions inherit this

https://bugzilla.proxmox.com/show_bug.cgi?id=4879

** Bug watch added: bugzilla.proxmox.com/ #4879
   https://bugzilla.proxmox.com/show_bug.cgi?id=4879

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

Title:
  ubuntu kernel does not support gadgetfs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu kernel does not appear to support gadgetfs:

  $ sudo modprobe g_mass_storage file=/tmp/fake_usb_disk
  FATAL: Error inserting g_mass_storage 
(/lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko): No 
such device
  $ ll /lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko
  -rw-r--r-- 1 root root 56436 oct  9 21:06 
/lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko
  $

  This seems to have been resolved in Igloo (see bug 923674) so is presumably a 
case of a cherry-pick?
  --- 
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  3464 F pulseaudio
   /dev/snd/controlC0:  james  3464 F pulseaudio
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312
  InstallationDate: Installed on 2010-10-21 (740 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: LENOVO 2516CTO
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: linux-image-generic-pae 3.5.0.17.19
  PackageArchitecture: i386
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-17-generic i686
  UpgradeStatus: Upgraded to quantal on 2012-09-30 (29 days ago)
  UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare 
sbuild vboxusers
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes

All of these patches are in the latest master-next noble kernel.

git describe --tags
Ubuntu-6.8.0-11.11-1-g04cdb2da2df3

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

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

Title:
  [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and
  include critical  fixes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  This request is to add support for SAS5116 controller and few critical 
bug-fixes in Ubuntu 24.04 LTS.
  Below is the list of upstream commits that adds support for SAS5116:

  b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50
  1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor
  cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32
  c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116
  6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs

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


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

[Kernel-packages] [Bug 2043733] Re: HP Zbook 17 G6 internal microphone causes hard crashes

2024-02-21 Thread Jordan Garcia

Hello!

Just checking in on this bug to see if there is any new info.

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

Title:
  HP Zbook 17 G6 internal microphone causes hard crashes

Status in linux package in Ubuntu:
  New

Bug description:
  Anything that changes the state of the internal microphone on the HP
  Zbook 17 G6 can result in a hard crash of the entire system. This
  includes things like noise reduction being applied by Google Meets,
  but it can be reliably replicated by just changing the volume of the
  microphone until the system crashes. When the crashes occur, the logs
  cut off just as they would if the system's power were completely cut.

  This behavior only occurs with the internal microphone. External
  microphones (both 3.5 mm TRRS and USB microphones) do not exhibit this
  same behavior.

  This behavior has been tested on 20.04, 22.04, 23.04, and 23.10 and
  reliably occurs on kernels 5.4, 5.15, 6.2, and 6.5.

  This is the system device that should be responsible for handling the
  internal microphone.

  description: Multimedia audio controller
   product: Cannon Lake PCH cAVS
   vendor: Intel Corporation
   physical id: 1f.3
   bus info: pci@:00:1f.3
   logical name: card0
   logical name: /dev/snd/controlC0
   logical name: /dev/snd/hwC0D0
   logical name: /dev/snd/hwC0D2
   logical name: /dev/snd/pcmC0D0c
   logical name: /dev/snd/pcmC0D0p
   logical name: /dev/snd/pcmC0D31p
   logical name: /dev/snd/pcmC0D3p
   logical name: /dev/snd/pcmC0D4p
   logical name: /dev/snd/pcmC0D5p
   logical name: /dev/snd/pcmC0D6c
   logical name: /dev/snd/pcmC0D7c
   version: 10
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list
   configuration: driver=sof-audio-pci-intel-cnl latency=64
   resources: iomemory:400-3ff iomemory:400-3ff irq:191 
memory:404a108000-404a10bfff memory:404a00-404a0f

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


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

[Kernel-packages] [Bug 2048864] Re: Remove armhf support

2024-02-21 Thread Dave Jones

Indeed -- the Pi isn't compatible with our generic arm64 kernel, so
we'll be sticking with the flavour limit for the time being, and this
does actually reduce our delta with Debian. I've got a couple of other
patches to incorporate into f-k this week, so I'm going to sponsor this
as part of a larger upload but that should be fine for the devel series.

** Changed in: flash-kernel (Ubuntu Noble)
   Status: Won't Fix => New

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

Title:
  Remove armhf support

Status in flash-kernel package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in flash-kernel source package in Noble:
  New
Status in linux-raspi source package in Noble:
  New

Bug description:
  Noble and newer don't support armhf for Pi anymore. We can drop the
  armhf specific kernel flavor raspi-nolpae from flash-kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2048864/+subscriptions


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

[Kernel-packages] [Bug 2046875] Re: [22.04.04]: mpt3sas: Critical Bug Fixes

This is a public version of the following bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224

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

Title:
  [22.04.04]: mpt3sas: Critical Bug Fixes

Status in linux package in Ubuntu:
  New

Bug description:
  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  3c978492c333  : scsi: mpt3sas: Fix loop logic
  0854065092a7  : scsi: mpt3sas: Remove volatile qualifier
  4ca10f3e3174 :  scsi: mpt3sas: Perform additional retries if doorbell read 
returns 0

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


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

[Kernel-packages] [Bug 2046722] Re: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

This is a public version of the following bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2054598] [NEW] AWS kernels lacking sound support (even snd-aloop missing)

2024-02-21 Thread Daniel Gibson

Public bug reported:

I need the snd-aloop module (and its dependencies: snd, snd-timer, snd-
pcm) on an AWS server.

The linux-modules-extra-aws package (or the one this drags in) used to provide 
that module (as a fix for 
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586) but then 
stopped providing it (probably when upgrading from Kernel 5.15 to 6.2?).
That means that this bug is a regression (I didn't find a way to reopen the 
aforementioned bugreport, so I'm creating a new one).

Please bring back snd-aloop (and possibly other modules that make sense
on a server that doesn't actually have a soundcard).

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

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

Title:
  AWS kernels lacking sound support (even snd-aloop missing)

Status in linux-aws package in Ubuntu:
  New

Bug description:
  I need the snd-aloop module (and its dependencies: snd, snd-timer,
  snd-pcm) on an AWS server.

  The linux-modules-extra-aws package (or the one this drags in) used to 
provide that module (as a fix for 
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586) but then 
stopped providing it (probably when upgrading from Kernel 5.15 to 6.2?).
  That means that this bug is a regression (I didn't find a way to reopen the 
aforementioned bugreport, so I'm creating a new one).

  Please bring back snd-aloop (and possibly other modules that make
  sense on a server that doesn't actually have a soundcard).

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

I have created tests kernels for both Jammy and Mantic.  Please test and
provide feedback.


Jammy
https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/jammy/

Mantic
https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/mantic/

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

These patches are already in 6.8

** Summary changed:

- [22.04.04]: megaraid_sas: Critical Bug Fixes
+ [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

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

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
 Assignee: Michael Reed (mreed8855)
   Status: New

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Michael Reed (mreed8855)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

Hi Chandrakanth,

Can you also fill in these fields for the SRU process in addition to
testing the test kernels

[Test Plan]

[ Where problems could occur ]

[ Other Info ]

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

** Description changed:

+ [Impact]
+ 
  This update has been initiated to include a few critical bug fixes from
  upstream into the upcoming 22.04.04 point kernel. Below are the upstream
  commit IDs:
  
+ 
+ [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()
  
+ The change log for the above commit IDs is small and doesn't require
+ rigorous validation. So please include these patches.
  
- The change log for the above commit IDs is small and doesn't require rigorous 
validation. So please include these patches.
+ [Test Plan]
+ 
+ [ Where problems could occur ]
+ 
+ [ Other Info ]
+ 
+ Jammy
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update
+ 
+ 
+ Mantic
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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

Title:
  [22.04.04]: megaraid_sas: Critical Bug Fixes

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2054489] Re: Crash on blank screen

2024-02-21 Thread Brett Holman

** Summary changed:

- Crash on lock screen
+ Crash on blank screen

** Description changed:

- When my computer locks due to inactivity the screen goes white and
- requires a reboot to recover.
+ When my computer screen goes blank and then locks due to inactivity, the
+ screen goes white and requires a reboot to recover.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 20 17:29:43 2024
  InstallationDate: Installed on 2024-02-02 (19 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  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=
+  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.6.0-14-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-6.6.0-14-generic N/A
-  linux-backports-modules-6.6.0-14-generic  N/A
-  linux-firmware20240202.git36777504-0ubuntu1
+  linux-restricted-modules-6.6.0-14-generic N/A
+  linux-backports-modules-6.6.0-14-generic  N/A
+  linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  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: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

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

Title:
  Crash on blank screen

Status in linux package in Ubuntu:
  New

Bug description:
  When my computer screen goes blank and then locks due to inactivity,
  the screen goes white and requires a reboot to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 20 17:29:43 2024
  InstallationDate: Installed on 2024-02-02 (19 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  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=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic 
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.6.0-14-generic N/A
   linux-backports-modules-6.6.0-14-generic  N/A
   linux-firmware20240202.git36777504-0ubuntu1
  SourcePackage: linux
  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: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA735010072
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

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


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

[Kernel-packages] [Bug 2039720] Re: Intel IDPF support

2024-02-21 Thread Joseph Salisbury

Request on mailing list for jammy:linux-gke:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149030.html

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

Title:
  Intel IDPF support

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  In Progress
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-gke source package in Jammy:
  In Progress
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  * Request from Google to include new Intel IDPF driver support

  [Fix]

  * Mantic - 24 clean cherry-picks, 1 backport from upstream
  * Jammy - 11 clean cherry-picks, 7 backports from upstream

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested internally and by Google using neper 
(https://github.com/google/neper)
  * Networking is functional and throughput is as expected

  [Where things could go wrong]

  * Low chance of regression, changes have been upstream since 6.6 kernel
  * Bulk of changes in IDPF driver
  * Other changes to network drivers largely adding #include directives

  [Other Info]

  * SF #00368902

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


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

[Kernel-packages] [Bug 2046726] Re: [24.04 LTS]: megaraid_sas driver update

2024-02-21 Thread Jeff Lane 

Marking Fix Committed as these are all in our  6.8 tree and will land in
24.04, there's nothing more to do here but track it for release.

linux-image-generic | 6.8.0-11.11 | noble-proposed | amd64, arm64,
ppc64el, s390x


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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Michael Reed (mreed8855)

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
 Assignee: Michael Reed (mreed8855)
   Status: Fix Committed

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

Title:
  [24.04 LTS]: megaraid_sas driver update

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  This update has been initiated to incorporate the megaraid_sas driver
  from upstream into the upcoming Ubuntu 24.04 LTS release.

  Assuming the 24.04 already included the patches up to driver version
  07.725.01.00-rc1. So, below are the commit IDs after it.

  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code
  a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code
  d67790ddf021 overflow: Add struct_size_t() helper
  aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()
  264e222b004c scsi: megaraid: Declare SCSI host template const

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


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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-02-21 Thread Catherine Redfield

I tested the flock-based solution with some of the CPC pipelines in
jammy and saw consistently clean builds (30 successful images built
yesterday).  Thank you very much for everyone's hard work debugging and
fixing this race condition!

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in livecd-rootfs source package in Jammy:
  Fix Released
Status in util-linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in livecd-rootfs source package in Mantic:
  New
Status in util-linux source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in livecd-rootfs source package in Noble:
  Fix Released
Status in util-linux source package in Noble:
  New

Bug description:
  [impact]
  In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, 
with the expectation that this would give us a reliable, race-free way of 
loop-mounting partitions from a disk image during image build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

    https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

    https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

  The losetup usage has been backported to Jammy, and sees frequent
  failures there.

  [test case]
  The autopkgtests will provide enough confidence that the changes are not 
completely broken. Whether the change helps with the races on riscv can be 
"tested in prod" just as well as any other way.

  [regression potential]
  If the backport has been done incorrectly, image builds can fail (and the 
autopkgtests will fail if it has been completely bungled). This can be quickly 
handled. There is no foreseeable way for this to result in successful builds 
but broken images, which would be a much more difficult failure mode to unpick.

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


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

[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.

2024-02-21 Thread Mike Ferreira

In the next few days, when I get some "spare" time... I will spin up a
few test Jammy VM's to capture what depends it has to pull in from other
repo's, so that the depends can be ID'ed and maybe those packages can be
added to that Jammy package in this new PPA.

Otherwise, as I just found out with a User, it put him into broken
packages depends hell.

Doing that while possibly bringing in those depends would simplify
that... as just add the PPA and go with it.

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

Title:
  Grub2 2.06 has upstream bug that results in Non-booting with ZFS after
  snapshot of bpool.

Status in grub2 package in Ubuntu:
  Confirmed
Status in grub2-unsigned package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  There is an upstream Bug with Grub where if you create snapshots of bpool, it 
results in a non-booting System. The problem was found to be an upstream Bug 
with Grub2:
  https://savannah.gnu.org/bugs/index.php?64297

  Multiple Ubuntu 22.04.3 Users Affected:
  https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug
  https://ubuntuforums.org/showthread.php?t=2494957

  Brought up as an issue at OpenZFS:
  https://github.com/openzfs/zfs/issues/13873

  If you look at this comment 
(https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was 
found the Savanaugh at GNU released a fix for it in Grub2 2.12, here:
  https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c

  Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch
  to Grub2 2.06 so that Users are not caught of in this bug for or
  currently supported LTS Release.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-amd64 2.06-2ubuntu14.4
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu Feb  1 16:40:28 2024
  InstallationDate: Installed on 2021-09-23 (861 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: grub2-unsigned
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago)

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


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

[Kernel-packages] [Bug 2054447] Re: Title: System Freeze Post Suspend with Browser and Sensor App Open

2024-02-21 Thread Daniel Morales Salazar

Recently observed that my computer becomes unusually warm during the
Suspend state, more so than under normal operation. Given the
intermittent nature of the Suspend issue previously reported, I've opted
to disable Suspend functionality as a precaution. I thought it important
to update this report with these observations. It would be greatly
appreciated if these concerns could be addressed in future updates,
enhancing the system's reliability and user experience. Thank you for
your ongoing efforts in improving Ubuntu (and Linux).

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

Title:
Title: System Freeze Post Suspend with Browser and Sensor App Open

Status in linux package in Ubuntu:
New

Bug description:
I've encountered a recurring system freeze issue on my Ubuntu machine.
The system was left unattended with two instances of Firefox open, one
on ChatGPT and another on Coursera, as well as the hardware sensor
notification program running. Upon returning and resuming from
suspend, I was able to log in, but the system was entirely
unresponsive. Ctrl-Alt-Delete resulted in a system reboot. This issue
had ceased occurring for about a week but has now reappeared.

Previously, similar freezes would occur, but Ctrl-Alt-Delete led to a
black screen requesting login details, necessitating a forced
shutdown. There is a possibility that the open applications may be
contributing to the freezing issue, although the problem had paused
for several days before returning, which is puzzling. This
intermittent nature of the problem adds complexity to pinpointing the
exact cause.

Steps to Reproduce:
1. Leave the system idle with Firefox open on ChatGPT and Coursera.
2. Run the hardware sensor notification program.
3. Enter system suspend state.
4. Resume from suspend after an extended period.
5. Attempt to interact with the system post-login.

Expected Result:
The system should resume from suspend and allow normal operation without
freezing.

Actual Result:
The system becomes unresponsive after resuming from suspend, requiring a
reboot via Ctrl-Alt-Delete or, in previous instances, necessitating a forced
shutdown after a black screen appears.

Additional Information:
- Occurrences have been intermittent, with a period of one week where the
issue did not manifest.
- The problem may be related to the system suspend/resume process,
potentially exacerbated by the running applications at the time of suspend.

This summary should provide a concise and clear description of the
issue for a bug report, outlining the problem, the steps to reproduce
it, and the unexpected behavior experienced.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: qd91 2735 F wireplumber
/dev/snd/seq:qd91 2715 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 16:32:25 2024
InstallationDate: Installed on 2024-02-08 (12 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb 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-17-generic N/A
linux-backports-modules-6.5.0-17-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2024-02-10 (11 days ago)
dmi.bios.date: 11/10/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0772C9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd11/10/2023:br1.33:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:
dmi.product.family: Latitude
dmi.product.name: Latitude 5420
dmi.product.sku: 0A20
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 2054570] [NEW] Monitor plugged in to Intel NUC10i7FNK via USB-C cable goes blank

2024-02-21 Thread coderef3

Public bug reported:

One of my monitors, which is plugged in via a USBC-USBC cable, tends to
reset a couple of times per hour. The screens go blank, then come back
after a second or two. After the display comes back, everything looks
the same as before (the desktop isn't being reset or restarted).

The same errors which show up in /var/log/syslog every time this
happens:

kernel: [186446.744863] xhci_hcd :39:00.0: xHC error in resume, USBSTS 
0x401, Reinit
kernel: [186446.744867] usb usb3: root hub lost power or was reset
kernel: [186446.744868] usb usb4: root hub lost power or was reset

I dual boot to Windows 11 on the same machine and the issue never occurs
on Windows 11.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  arnav 92545 F wireplumber
 /dev/snd/seq:arnav 92540 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 21 07:14:08 2024
InstallationDate: Installed on 2023-12-17 (66 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=3146f964-532e-4160-9126-ee6a75b2c6a8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-17-generic N/A
 linux-backports-modules-6.5.0-17-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-12-31 (52 days ago)
dmi.bios.date: 10/24/2023
dmi.bios.release: 5.16
dmi.bios.vendor: Intel Corp.
dmi.bios.version: FNCML357.0063.2023.1024.1117
dmi.board.asset.tag: Default string
dmi.board.name: NUC10i7FNB
dmi.board.vendor: Intel Corporation
dmi.board.version: K61360-302
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.12
dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0063.2023.1024.1117:bd10/24/2023:br5.16:efr3.12:svnIntel(R)ClientSystems:pnNUC10i7FNK:pvrK61156-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i7FNK:
dmi.product.family: FN
dmi.product.name: NUC10i7FNK
dmi.product.sku: BXNUC10i7FNK
dmi.product.version: K61156-302
dmi.sys.vendor: Intel(R) Client Systems

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


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

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

Title:
  Monitor plugged in to Intel NUC10i7FNK via USB-C cable goes blank

Status in linux package in Ubuntu:
  New

Bug description:
  One of my monitors, which is plugged in via a USBC-USBC cable, tends
  to reset a couple of times per hour. The screens go blank, then come
  back after a second or two. After the display comes back, everything
  looks the same as before (the desktop isn't being reset or restarted).

  The same errors which show up in /var/log/syslog every time this
  happens:

  kernel: [186446.744863] xhci_hcd :39:00.0: xHC error in resume, USBSTS 
0x401, Reinit
  kernel: [186446.744867] usb usb3: root hub lost power or was reset
  kernel: [186446.744868] usb usb4: root hub lost power or was reset

  I dual boot to Windows 11 on the same machine and the issue never
  occurs on Windows 11.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arnav 92545 F wireplumber
   /dev/snd/seq:arnav 92540 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 21 07:14:08 2024
  InstallationDate: Installed on 2023-12-17 (66 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=3146f964-532e-4160-9126-ee6a75b2c6a8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-17-generic N/A
   linux-backports-modules-6.5.0-17-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms

2024-02-21 Thread Timo Aaltonen

did this get the pre-verification already?

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

Title:
  There is sound from the speakers and headphones at the same time on
  Oasis 14 and 16 platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  While playing audio with headset plugged, the sound play from both headset 
and internal speaker.

  [Fix]
  The commit from v6.5-rc5 fixes the issue
  fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform

  [Test Case]
  1. play an audio file.
  2. plug 3.5mm headset.
  3. select "headset".
  4. sound will play only from headset

  [Where problems could occur]
  It simply added 2 IDs to the table, should have no impact to the existing 
machines.

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


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

[Kernel-packages] [Bug 2054567] [NEW] ubuntu_bpf selftests fail to build

2024-02-21 Thread Roxana Nicolescu

Public bug reported:

Sru justification

[Impact]
Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail call 
counting with bpf2bpf and data on stack" that affects one of the bpf kselftests.
because LIBBPF_OPTS macro does not exists, it does not compile. Error below.

[Fix]
Cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS"

[Test]
This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
I tested it by using our regression testing tooling, but same results can be 
achieved by running:
$ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
from the linux tree directory

Without the fix, it fails to compile:
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
| ^~~
| LIBBPF_API
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
| ^
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
|^
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
823 | .data_in = _v4,
| ^
  make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
  make: *** [Makefile:172: all] Error 2

With the fix, it compiles.

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

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


** Tags: sru-20240205

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

** Tags added: sru-20240205

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

Title:
  ubuntu_bpf selftests fail to build

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

Bug description:
  Sru justification

  [Impact]
  Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests.
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.

  [Fix]
  Cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS"

  [Test]
  This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
  I tested it by using our regression testing tooling, but same results can be 
achieved by running:
  $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory

  Without the fix, it fails to compile:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^~~
  | LIBBPF_API

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts,

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

** Description changed:

  [ Impact ]
  
  Kernel (and systemd) log messages appear during boot for many machines,
  when the user should be seeing only the BIOS logo and/or Plymouth splash
  screens.
  
+ [ Workaround ]
+ 
+ On most machines you can hide the problem by using these kernel parameters 
together:
+   quiet splash loglevel=2 fastboot
+ 
  [ Test Plan ]
  
- 1. Boot Ubuntu on a number of laptops that have the problem and verify
- no console text messages appear during boot.
- 
- 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them
- still.
- 
- 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages
- should appear.
+ 1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
+ 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
+ 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.
  
  [ Where problems could occur ]
  
  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to VT
  switch.
  
  [ Original Description ]
  
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as
  clean as it used to be.
  
  Basically, the flow used to be in 20.04:
  
  GRUB > Splash screen > Login prompt
  
  Currently in 22.04:
  
  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt
  
  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.
  
  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".
  
  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".
  
  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.
  
  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain hidden
  like they were in Focal.
  
  Obviously a minor issue, but important to the whole look and feel of the
  OS for desktop.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background

** Tags added: noble

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

Title:
  Display flickers (monitor loses signal briefly) during "flickerfree"
  boot, while showing the BIOS logo on a black background

Status in Plymouth:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  I am trying flickerfree boot in 19.10 [1], but find it actually
  flickers part way through:

1. BIOS logo on a black background.
2. Display mode resets, no image on a black background briefly.
3. BIOS logo on a black background.

  The flicker occurs seemingly during kernel startup since my
  peripherals are lit up before the problem occurs.

  Suspecting this might be related to FB handover:

    [2.751028] fb0: switching to inteldrmfb from EFI VGA

  I tried disabling that with a big hammer:

    i915.modeset=0

  so it stays in efifb, and that works -- no more flickering, providing
  I don't let i915 take over the framebuffer.

  [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jul 17 16:34:36 2019
  InstallationDate: Installed on 2019-05-02 (76 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  MachineType: LENOVO 10M7CTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 
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-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen