date:20240223

This bug is awaiting verification that the linux-
bluefield/5.15.0-1037.39 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-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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-bluefield-v2 
verification-needed-jammy-linux-bluefield

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

Title:
  mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  This is a cherry-pick fix from upstream to drop Tx network packet when Tx 
TmFIFO is full.

  [Fix]
  Starting from Linux 5.16 kernel, Tx timeout mechanism was added
  in the virtio_net driver which prints the "Tx timeout" warning
  message when a packet stays in Tx queue for too long. Below is an
  example of the reported message:

  "[494105.316739] virtio_net virtio1 tmfifo_net0: TX timeout on
  queue: 0, sq: output.0, vq: 0×1, name: output.0, usecs since
  last trans: 3079892256".

  This issue could happen when external host driver which drains the
  FIFO is restared, stopped or upgraded. To avoid such confusing
  "Tx timeout" messages, this commit adds logic to drop the outstanding
  Tx packet if it's not able to transmit in two seconds due to Tx FIFO
  full, which can be considered as congestion or out-of-resource drop.

  This commit also handles the special case that the packet is half-
  transmitted into the Tx FIFO. In such case, the packet is discarded
  with remaining length stored in vring->rem_padding. So paddings with
  zeros can be sent out when Tx space is available to maintain the
  integrity of the packet format. The padded packet will be dropped on
  the receiving side.

  
  [Test Case]
  Same functionality and testing as on BlueField-1/2/3. No functionality change.

  [Regression Potential]
  Same behavior from user perspective.

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


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

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

2024-02-23 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1120.117) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.23 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

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

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1016.17
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-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.


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-oem-6.5-v2 
verification-needed-jammy-linux-oem-6.5

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/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 2049689] Re: partproke is broken on empty loopback device

This bug is awaiting verification that the linux-aws/5.15.0-1055.60
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-aws' to 'verification-done-jammy-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.


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-aws-v2 
verification-needed-jammy-linux-aws

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released

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 2054860] [NEW] AMD-Vi Failed to allocate IRTE

2024-02-23 Thread Zhanglei Mao

Public bug reported:

A partner report below error which seems a fixed issue from upstream and
it affect NVME performance, hope to backport it.

Oct 27 06:05:17 quanta kernel: [ 1238.707245] AMD-Vi: Failed to allocate
IRTE


The related patch and discussion is below:
https://lkml.org/lkml/2020/10/14/1153  

Certain device drivers allocate IO queues on a per-cpu basis.
On AMD EPYC platform, which can support up-to 256 cpu threads,
this can exceed the current MAX_IRQ_PER_TABLE limit of 256,
and result in the error message:

AMD-Vi: Failed to allocate IRTE

This has been observed with certain NVME devices.

AMD IOMMU hardware can actually support upto 512 interrupt
remapping table entries. Therefore, update the driver to
match the hardware limit.

Please note that this also increases the size of interrupt remapping
table to 8KB per device when using the 128-bit IRTE format.

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

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

Title:
   AMD-Vi Failed to allocate IRTE

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

Bug description:
  A partner report below error which seems a fixed issue from upstream
  and it affect NVME performance, hope to backport it.

  Oct 27 06:05:17 quanta kernel: [ 1238.707245] AMD-Vi: Failed to
  allocate IRTE

  
  The related patch and discussion is below:
  https://lkml.org/lkml/2020/10/14/1153  

  Certain device drivers allocate IO queues on a per-cpu basis.
  On AMD EPYC platform, which can support up-to 256 cpu threads,
  this can exceed the current MAX_IRQ_PER_TABLE limit of 256,
  and result in the error message:

  AMD-Vi: Failed to allocate IRTE

  This has been observed with certain NVME devices.

  AMD IOMMU hardware can actually support upto 512 interrupt
  remapping table entries. Therefore, update the driver to
  match the hardware limit.

  Please note that this also increases the size of interrupt remapping
  table to 8KB per device when using the 128-bit IRTE format.

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


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

[Kernel-packages] [Bug 1908090] Re: kdump-gaps: Default 192MB crashkernel reservation is never enough (kdump fails on 20.04)

This bug was fixed in the package kdump-tools - 1:1.10.2ubuntu1

---
kdump-tools (1:1.10.2ubuntu1) noble; urgency=medium

  * Merge from Debian unstable. Remaining changes:
- Update default s390x crashkernel.
  - Install the updated zipl.conf with ucf, so users will be able to
decide whether to pick any crashkernel changes.
- Bump grub default (x86 amd64) crashkernel params to those used on
  arm64, ppc64le, s390x.
- Add riscv64 build

kdump-tools (1:1.10.2) unstable; urgency=medium

  * debian/tests/crash: Support makedumpfile's flattened format,
which file(1) reports as "Flattened kdump compressed dump" instead
of the "Kdump compressed dump" string we were looking for.

kdump-tools (1:1.10.1) unstable; urgency=medium

  * Delete the temporary sysctl files on kernel removal. Thanks to
Guilherme G. Piccoli.

 -- dann frazier   Thu, 22 Feb 2024 15:39:13 -0700

** Changed in: kdump-tools (Ubuntu Noble)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kdump-tools in Ubuntu.
Matching subscriptions: Maintainer
https://bugs.launchpad.net/bugs/1908090

Title:
  kdump-gaps: Default 192MB crashkernel reservation is never enough
  (kdump fails on 20.04)

Status in kdump-tools package in Ubuntu:
  Fix Released
Status in kdump-tools source package in Focal:
  New
Status in kdump-tools source package in Jammy:
  New
Status in kdump-tools source package in Mantic:
  New
Status in kdump-tools source package in Noble:
  Fix Released

Bug description:
  When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS,
  everything appears to be in good working order, according to
  "systemctl status kdump-tools" and "kdump-config status". However,
  upon an actual crash, the system hangs, and no crash files are
  produced. I've investigated and have learned that the capture kernel
  does indeed start, but it is unable to unpack the rootfs/initrd, and
  thus fails and hangs.

  [1.070469] Trying to unpack rootfs image as initramfs...
  [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), 
order=0, oom_score_adj=0
  [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic 
#30-Ubuntu 
  [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [1.336396] Call Trace:
  [1.336396]  dump_stack+0x6d/0x9a
  [1.336396]  dump_header+0x4f/0x1eb
  [1.336396]  out_of_memory.part.0.cold+0x39/0x83
  [1.336396]  out_of_memory+0x6d/0xd0
  ...
  [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on 
memory ]---

  
  On this system with 8G of memory, the crash memory as specified on the kernel 
command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now 
kdump works.

  Not sure how the 192M value is chosen, but it does not work. I think
  this used value used to work for 16.04 and maybe 18.04 (I didn't try),
  but is no longer useful for 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1908090/+subscriptions


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

[Kernel-packages] [Bug 2054855] [NEW] Azure: Network doesn't get configured after triggering kdump

2024-02-23 Thread Tim Gardner

Public bug reported:

SRU Justification

[Impact]

The network doesn't get configured after a kdump on some generations of
hardware.

[Fix]

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a8a8afba0c305

[Test Plan]

Microsoft tested.

[[Where things could go wrong]

You're already in deep doo doo if you have to run kdump. However. not
having a network afterwards is a sure sign that this patch doesn't work
for your hardware.

[Other Info]

SF: #00378199

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

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

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

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

** Changed in: linux-azure (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Azure: Network doesn't get configured after triggering kdump

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

Bug description:
  SRU Justification

  [Impact]

  The network doesn't get configured after a kdump on some generations
  of hardware.

  [Fix]

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a8a8afba0c305

  [Test Plan]

  Microsoft tested.

  [[Where things could go wrong]

  You're already in deep doo doo if you have to run kdump. However. not
  having a network afterwards is a sure sign that this patch doesn't
  work for your hardware.

  [Other Info]

  SF: #00378199

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


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

[Kernel-packages] [Bug 2017846] Re: System kept waking up after pressing power button

2024-02-23 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  System kept waking up after pressing power button

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F wireplumber
   /dev/snd/seq:yamiyuki  42972 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  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.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  Package: systemd 252.5-2ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

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

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

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later

2024-02-23 Thread Nick Rosbrook

*** This bug is a duplicate of bug 2037667 ***
https://bugs.launchpad.net/bugs/2037667

This sounds like a duplicate of 2037667, which is planned to be fixed
sometime soon-ish.

** This bug has been marked a duplicate of bug 2037667
   Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

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

Title:
  non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or
  later

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  jammy kernel 5.15.0-81.90 includes the following backport:

  
https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43
  https://bugs.launchpad.net/bugs/2029401

  This causes creation of ip6tnl tunnel interface to fail through
  systemd-networkd. The following systemd commit also has to be applied
  to jammy:

  
https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb

  (Other commits might be required along with above)

  Since the systemd commit is missing on jammy, Kind=ip6tnl netdev
  configuration fails as follows:

  > eno1: Could not create stacked netdev: Invalid argument

  I believe this is a regression; We encountered this linux-
  image-5.15.0-91-generic installed via unattended-upgrade -- Also
  EINVAL during creating tunnel interfaces let AcceptIPv6RA function not
  to start, so we lose connection to our server due to missing IP
  address.

  ```
  # eno1.network
  [Match]
  Name=eno1

  [Network]
  Tunnel=test_tun
  ```

  ```
  # test_tun.netdev
  [NetDev]
  Name=test_tun
  Kind=ip6tnl

  [Tunnel]
  Local=2001:db8::a
  Remote=2001:db8::b
  Mode=any
  ```

  ```
  # test_tun.network
  [Match]
  Name=test_tun

  [Network]
  Address=10.0.0.1/24
  ```

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


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

[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly

2024-02-23 Thread Alex Desh

Kernel 6.5.0-21 - the problem is not solved, the HDD heads park loudly
in an emergency. Why is it that after 2 releases of the kernel the
problem is still not fixed and you continue to break users’ hard drives?

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

Title:
  Issue when shutting down computer: internal hard drive is not shut
  down properly

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

Bug description:
  After the last kernel upgrade, I noticed that, in the S.M.A.R.T.
  monitor, parameter ID 192 "Power Off Retract Count" increased every
  time I turned off the system. I also noticed the "click" of the head
  parking when shutting down the computer. By restarting the computer
  with previous kernel version (6.5.0-15.15~22.04.1) the issue didn't
  happen, so I assume it's a kernel bug, that causes it to shut down the
  computer before hard drive is deactivated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Feb 13 16:35:55 2024
  InstallationDate: Installed on 2020-10-02 (1228 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-08-11 (550 days ago)

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


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

[Kernel-packages] [Bug 2039167] Re: I get this message "array-index-out-of-bounds" every time I turn on my laptop since I upgraded from 23.04. to 23.10. (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwm

2024-02-23 Thread Alex Desh

6.5.0-* "array-index-out-of-bounds" every boot

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

Title:
  I get this message "array-index-out-of-bounds"  every time I turn on
  my laptop since I upgraded from 23.04. to 23.10.
  (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
  index 1 is out of range for type 'UCHAR [1]'

  My firmware version is X515DAP.311.
  OS type 64-bit.
  GNOME version 45.0.
  Kernel version Linux 6.5.0-9-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zoran  2329 F wireplumber
   /dev/snd/controlC0:  zoran  2329 F wireplumber
   /dev/snd/seq:zoran  2316 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 13:42:16 2023
  InstallationDate: Installed on 2023-09-21 (21 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 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X515DAP.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515DAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515DAP_M515DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1983223] Re: [24.04 FEAT] [VS2029] KVM: Provide virtual CPU topology to guests - qemu part

2024-02-23 Thread Frank Heimes

*** This bug is a duplicate of bug 2049703 ***
https://bugs.launchpad.net/bugs/2049703

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

** Changed in: ubuntu-z-systems
   Status: Confirmed => Fix Released

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

Title:
  [24.04 FEAT] [VS2029] KVM: Provide virtual CPU topology to guests -
  qemu part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Currently, KVM guests will see an evenly distributed CPU topology,
  where every CPU resides on a separate drawer. This may not be optimal
  for scheduling decisions. The goal of this feature is to allow to
  specify a virtual CPU topology which can help to configure the guest
  for better performance. The full range of topology nodes should be
  configurable (drawer -> book -> chip -> core -> thread).

  This feature has a kernel, qemu and libvirt part.

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


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

[Kernel-packages] [Bug 2054845] Re: mlxbf-gige: support fixed phy for Bobcat

2024-02-23 Thread Asmaa Mnebhi

** Summary changed:

- mlxbf-gige: support bobcat
+ mlxbf-gige: support fixed phy for Bobcat

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

Title:
  mlxbf-gige: support fixed phy for Bobcat

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  Bobcat is a new board which doesn't have an external PHY connected to
  the OOB. There are no MDIO busses involved and no PHY involved. The
  OOB is directly connected to the switch (MAC to MAC). SO we need to
  use the linux fixed phy to be able to emulate the mdio behavior and
  load the ethernet driver.

  [Fix]

  * Register the fixed-phy register in the case of the bobcat.

  [Test Case]

  * Important: For testing on the bobcat board, make sure the corresponding 
UEFI image is also loaded, otherwise, the oob driver will fail to load.  For 
other board, it is backward compatible.
  * Check if the mlxbf-gige is loaded on bobcat
  * Check that it is using the fixed-phy via dmesg | grep PHY
  * check that the oob interface is pingable
  * check that files can be copied over via oob interface
  * rmmod/modprobe
  * ifconfig up/down
  * reboot test

  [Regression Potential]

  * Redo all the OOB testing on other boards (moonraker) and make sure
  the bobcat changes dont trigger any regressions.

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


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

[Kernel-packages] [Bug 2054845] [NEW] mlxbf-gige: support bobcat

2024-02-23 Thread Asmaa Mnebhi

Public bug reported:

SRU Justification:

[Impact]

Bobcat is a new board which doesn't have an external PHY connected to
the OOB. There are no MDIO busses involved and no PHY involved. The OOB
is directly connected to the switch (MAC to MAC). SO we need to use the
linux fixed phy to be able to emulate the mdio behavior and load the
ethernet driver.

[Fix]

* Register the fixed-phy register in the case of the bobcat.

[Test Case]

* Important: For testing on the bobcat board, make sure the corresponding UEFI 
image is also loaded, otherwise, the oob driver will fail to load.  For other 
board, it is backward compatible.
* Check if the mlxbf-gige is loaded on bobcat
* Check that it is using the fixed-phy via dmesg | grep PHY
* check that the oob interface is pingable
* check that files can be copied over via oob interface
* rmmod/modprobe
* ifconfig up/down
* reboot test

[Regression Potential]

* Redo all the OOB testing on other boards (moonraker) and make sure the
bobcat changes dont trigger any regressions.

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

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

Title:
  mlxbf-gige: support bobcat

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  Bobcat is a new board which doesn't have an external PHY connected to
  the OOB. There are no MDIO busses involved and no PHY involved. The
  OOB is directly connected to the switch (MAC to MAC). SO we need to
  use the linux fixed phy to be able to emulate the mdio behavior and
  load the ethernet driver.

  [Fix]

  * Register the fixed-phy register in the case of the bobcat.

  [Test Case]

  * Important: For testing on the bobcat board, make sure the corresponding 
UEFI image is also loaded, otherwise, the oob driver will fail to load.  For 
other board, it is backward compatible.
  * Check if the mlxbf-gige is loaded on bobcat
  * Check that it is using the fixed-phy via dmesg | grep PHY
  * check that the oob interface is pingable
  * check that files can be copied over via oob interface
  * rmmod/modprobe
  * ifconfig up/down
  * reboot test

  [Regression Potential]

  * Redo all the OOB testing on other boards (moonraker) and make sure
  the bobcat changes dont trigger any regressions.

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


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

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

2024-02-23 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-raspi (6.5.0.1012.13) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

acpi-call/unknown (arm64)
adv-17v35x/unknown (arm64)
backport-iwlwifi-dkms/unknown (arm64)
bbswitch/unknown (arm64)
dahdi-linux/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
digimend-dkms/unknown (arm64)
dm-writeboost/unknown (arm64)
dpdk-kmods/unknown (arm64)
evdi/unknown (arm64)
falcosecurity-libs/unknown (arm64)
fwts/unknown (arm64)
glibc/unknown (arm64)
gost-crypto/unknown (arm64)
iptables-netflow/unknown (arm64)
jool/unknown (arm64)
langford/unknown (arm64)
librem-ec-acpi/unknown (arm64)
libvpoll-eventfd/unknown (arm64)
lime-forensics/unknown (arm64)
linux-apfs-rw/unknown (arm64)
lttng-modules/unknown (arm64)
lxc/unknown (arm64)
nat-rtsp/unknown (arm64)
openafs/unknown (arm64)
openrazer/unknown (arm64)
openvpn-dco-dkms/unknown (arm64)
r8125/unknown (arm64)
r8168/unknown (arm64)
rapiddisk/unknown (arm64)
rtl8812au/unknown (arm64)
rtpengine/unknown (arm64)
snapd/unknown (arm64)
systemd/unknown (arm64)
v4l2loopback/unknown (arm64)
west-chamber/unknown (arm64)
xilinx-runtime/unknown (arm64)
xtables-addons/unknown (arm64)
xtrx-dkms/unknown (arm64)
zfs-linux/unknown (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

2024-02-23 Thread Philip Cox

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

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

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

Title:
  performance: Scheduler: ratelimit updating of load_avg

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

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2040026

  [Description]
    Improve cache bouncing on tg->load_avg

  [Hardware Information]
    Architecture:
  Intel / AMD (x86_64)
    Platform(s):
  Sapphire Rapids
    Date HW is expected at Canonical:

    Component(s):
  Perf-Scalability
  Scheduler

  [Software Information]
    Target Version:
  24.04
    Target Kernel:
  TBD
    Commit IDs:
  1528c661c24b sched/fair: Ratelimit update to tg->load_avg
    External Links:

  [Business Justification]

  [Testing guidance]

  [External ID]
    LFE-7154

  Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0

  
https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0

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


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

[Kernel-packages] [Bug 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform

2024-02-23 Thread Philip Cox

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

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

Title:
  x86: performance: tsc: Extend watchdog check exemption to 4-Sockets
  platform

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

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2044822

  
  SRU Justification:

  [Impact]
Fix tsc clocksource on 4 sockets x86 servers was wrongly judged as 
'unstable' by 'jiffies' and other watchdogs, and disabled

  
  [Fix]
  cherry-pick 
  233756a640be x86/tsc: Extend watchdog check exemption to 4-Sockets 
platform
  from upstream fixes this 

  [Test Plan]
  This has been tested by intel, and has been upstreamed for a while. 

  
  [Where problems could occur]
  This is a fairly narrow change, and extends a behaviour correction to cover 
up to 4-socket machines, rather than just 2 socket machines

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


-- 
Mailing list: https://launchpad.net/~kernel-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] Re: please include dummy_hcd module in kernel package

2024-02-23 Thread roland aus köln

people missing it !

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073089/comments/23
https://forums.linuxmint.com/viewtopic.php?t=356963
https://www.duboucher.eu/gadgetfs-ubuntu.html
https://askubuntu.com/questions/226136/how-to-simulate-a-usb-plug
https://xakcop.com/post/vmw-kernel-debugging/
https://blog.gimx.fr/dummy_hcd/

-- 
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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040

2024-02-23 Thread Ciaby

This finally fixed it for me.

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

Title:
  Update firmware for MT7921 in order to fix Framework 13 AMD 7040

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2049220

  [Impact]

  MT7921 - IPv6 no longer working (Not receiving Multicast).

  [Fix]

  Update WiFi/Bluetooth firmware to upstream commits:
  * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi 
device")
  * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for 
mediatek bluetooth chip (MT7921)")

  [Test Case]

  1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
  adapter and connect it to a Dual-stack network leveraging Router
  Advertisements for IPv6.

  2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the 
following:
 - IPv6 stateless autoconfiguration works and a public/global address is 
assigned.
 - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.

  3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the 
following:
 - IPv6 only configures link-local address (fe80::) and no public/global 
address.
 - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.

  [Where problems could occur]

  Opaque binary. No known dependency to kernel version.

  [Other Info]

  Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
  Mantic. All the commits are in upstream repository, so Noble should
  have them after rebased.

  == original bug report ==

  The current firmware for MT7921 WiFi is giving me problems like dropping 
multicast packets (mDNS).
  I manually updated the firmware files and that fixed the issue.
  To be more specific, please include this commit:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
  And possibly also this:
  
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
  Thanks!

  We also need:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04.3 LTS

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  linux-firmware 20220329.git681281e4-0ubuntu3.24 all  Firmware for 
Linux kernel drivers

  3) What you expected to happen
  WiFi working

  4) What happened instead
  Multicast packets dropped, mDNS not working

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


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

[Kernel-packages] [Bug 2054820] [NEW] Virt-manager windows VM slowed down

2024-02-23 Thread Kai Tchong

Public bug reported:

My virt-manager build VM Windows 10 guest had some problems when I
started using it in November 2023. I solved it along the lines of trying
to get the intel GPU working as a vGPU for this virtual machine. I
noticed some upgrades to the use of Nvidia were on the way. (It runs on
a laptop with Nvidia dedicated GPU).

Two kernel updates arrived in a row the past two weeks. I saw many gpu
features were involved though i'm not deep enough into Linux kernels to
know exactly what is going on.

The first one was the update to linux-image-5.15.0-92-lowlatency (and
it's accompanying modules and headers). The second one was linux-
headers-5.15.0-94-lowlatency. That one causes my VM to be slow as it was
at the start.

I use the intel gpu through a virtio driver since I cannot passthrough
the Nvidia card. I need that for several other applications. But with
the nvme Windows is installed on it works quite flawlessly for a while
now. Until this kernel update. I had to roll it back.

Thought it would be best to leave a note here.

** Affects: linux-signed-lowlatency-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New

** Tags: libvirt

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

Title:
Virt-manager windows VM slowed down

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

Bug description:
My virt-manager build VM Windows 10 guest had some problems when I
started using it in November 2023. I solved it along the lines of
trying to get the intel GPU working as a vGPU for this virtual
machine. I noticed some upgrades to the use of Nvidia were on the way.
(It runs on a laptop with Nvidia dedicated GPU).

Two kernel updates arrived in a row the past two weeks. I saw many gpu
features were involved though i'm not deep enough into Linux kernels
to know exactly what is going on.

Thought it would be best to leave a note here.

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

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

[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly

2024-02-23 Thread angros47

Is there any relation with this one?

https://bugs.archlinux.org/task/80064

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

Title:
  Issue when shutting down computer: internal hard drive is not shut
  down properly

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

Bug description:
  After the last kernel upgrade, I noticed that, in the S.M.A.R.T.
  monitor, parameter ID 192 "Power Off Retract Count" increased every
  time I turned off the system. I also noticed the "click" of the head
  parking when shutting down the computer. By restarting the computer
  with previous kernel version (6.5.0-15.15~22.04.1) the issue didn't
  happen, so I assume it's a kernel bug, that causes it to shut down the
  computer before hard drive is deactivated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Feb 13 16:35:55 2024
  InstallationDate: Installed on 2020-10-02 (1228 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-08-11 (550 days ago)

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


-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Fix bpf selftests build failure after v5.15.139 update

I missed that the test itself was removed in v5.15.149. We should do the same.
Considering the last one applied to our tree is 140 (I think), I'll push this 
sooner.

** Description changed:

  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"
+ Initially, I thought cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS 
into LIBBPF_OPTS" would be the best, but upstream stable just reverted the 
commit
+ that broke it.
+ Commit  62900d358c48 "Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack"" will be cherry picked.
  
  [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.
  
  [Regression potential]
  The only place this is being used is selftests, so the risk is very low.

-- 
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:
  Fix bpf selftests build failure after v5.15.139 update

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

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]
  Initially, I thought cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS 
into LIBBPF_OPTS" would be the best, but upstream stable just reverted the 
commit
  that broke it.
  Commit  62900d358c48 "Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack"" will be cherry picked.

  [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

[Kernel-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

2024-02-23 Thread drouineau

I also enclose the apt log describing the dist-upgrade that causes the
issue

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+attachment/5748703/+files/apt.log

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

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


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

[Kernel-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

2024-02-23 Thread drouineau

Dear all, after the upgrade of mesa packages on monday 
(23.2.1-1ubuntu3.1~22.04.2 from repo jammy-updates), I suffer similar symptoms 
at startup (causing a blank screen with no GDM running and message "something 
went wrong). I am using 22.04.3 LTS "Jammy Jellyfish" with kernel 
6.1.0-1034-oem but the issue remains with kernel 6.2.0-26-generic). I have a 
Dell precision 5480. The issue occurs if I use the nouveau driver or the 
proprietary nvidia driver (535) with profile "on-demand". The problem is solved 
with proprietary driver and profile "nvidia" (but costs a lot to the battery 
lifetime).  
I enclose the syslog around the crash which mentions an issue with mesa drivers.

Is this the same issue or should I open a new issue?


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+attachment/5748702/+files/syslog

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

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


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

[Kernel-packages] [Bug 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

2024-02-23 Thread Heinrich Schuchardt

** Package changed: linux-riscv (Ubuntu) => lxd-agent-loader (Ubuntu)

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

Title:
  lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

Status in lxd-agent-loader package in Ubuntu:
  New

Bug description:
  Starting the lxd-agent.service service fails with kernel
  6.5.0-9-generic.

  # /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
  available for device config

  [ 1239.456813] 9pnet_virtio: no channels available for device config
  Couldn't mount virtiofs or 9p, failing.

  
  The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

  Removing the 9pnet_virtio module does not resolve the issue.

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Feb 23 12:28:11 2024
  InstallationDate: Installed on 2023-12-04 (81 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 
(20231204)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+subscriptions


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

[Kernel-packages] [Bug 2051922] Re: Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected at all

2024-02-23 Thread Ferenc Jozsef Stefan

maybe some extr, if any worth, why does it list the bluetooth as usb?

"intel dual band" so ubuntu sees something but perhaps not recognized
correctly since bluetooth works

lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 003 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 003 Device 004: ID 1a2c:6004 China Resource Semico Co., Ltd USB Keyboard
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04e8:6863 Samsung Electronics Co., Ltd Galaxy series, 
misc. (tethering mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected
  at all

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

Bug description:
  Dear Members!

  No wifi adapter detected on ubuntu, on win11 it works fine

  lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  But wifi failed to manifest on previous versions and on the upcoming 24.04 as 
well
  ---

  
  tethering works
  bluetooth works fine
  no soft block / no hard block

  "Additional drivers" empty
  "ethernet interface" never tried but it is detected
  "lspci" doesnt show wifi
  "lshw -C network" doesnt show wifi

  did a woodoo with iwlwifi-7265-ucode-25.30.14.0 file, copied files to 
firmware folder, it must have failed since still no wifi. 
  I have done a couple other things in vain, glad to repeat for the sake of 
practice and result.
  
-
  inxi -Abd
  System:
Kernel: 6.5.0-14-generic x86_64 bits: 64
  Desktop: GNOME 42.9 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
  Machine:
Type: Mini-pc Mobo: N/A model: N/A v: V00 serial: 
  UEFI: American Megatrends v: 1.11_P4C4M43_EC_0_0_59_AMI date: 11/05/2022
  Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  driver: r8169
Device-2: Intel Bluetooth wireless interface type: USB driver: btusb

  
  Is there a way to give life to that piece of wifi technology?

  
  Thank you all in advance!

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


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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Committed
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-
  
cifs/6a65b2d1-7596-438a-8ade-2f7526b15...@rd10.de/T/#m22cd9b7289f87cd945978bd7995bcaf1beebfe67

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

[Kernel-packages] [Bug 2054814] Re: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

2024-02-23 Thread Heinrich Schuchardt

The installed snap version is 5.20-f3dd836.

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

Title:
  lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Starting the lxd-agent.service service fails with kernel
  6.5.0-9-generic.

  # /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
  available for device config

  [ 1239.456813] 9pnet_virtio: no channels available for device config
  Couldn't mount virtiofs or 9p, failing.

  
  The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

  Removing the 9pnet_virtio module does not resolve the issue.

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Feb 23 12:28:11 2024
  InstallationDate: Installed on 2023-12-04 (81 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 
(20231204)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2054411] Re: Jammy update: v5.15.147 upstream stable release

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

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

Title:
  Jammy update: v5.15.147 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  block: Don't invalidate pagecache for invalid falloc modes
  ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP ProBook 440 G6
  Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()"
  wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ
  drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer
  nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local
  octeontx2-af: Fix marking couple of structure as __packed
  drm/i915/dp: Fix passing the correct DPCD_REV for drm_dp_set_phy_test_pattern
  i40e: Fix filter input checks to prevent config with invalid values
  igc: Report VLAN EtherType matching back to user
  igc: Check VLAN TCI mask
  igc: Check VLAN EtherType mask
  ASoC: fsl_rpmsg: Fix error handler with pm_runtime_enable
  mlxbf_gige: fix receive packet race condition
  net: sched: em_text: fix possible memory leak in em_text_destroy()
  r8169: Fix PCI error on system resume
  net: Implement missing getsockopt(SO_TIMESTAMPING_NEW)
  can: raw: add support for SO_TXTIME/SCM_TXTIME
  can: raw: add support for SO_MARK
  net-timestamp: extend SOF_TIMESTAMPING_OPT_ID to HW timestamps
  ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init
  sfc: fix a double-free bug in efx_probe_filters
  net: bcmgenet: Fix FCS generation for fragmented skbuffs
  netfilter: nft_immediate: drop chain reference counter on error
  net: Save and restore msg_namelen in sock_sendmsg
  i40e: fix use-after-free in i40e_aqc_add_filters()
  ASoC: meson: g12a-toacodec: Validate written enum values
  ASoC: meson: g12a-tohdmitx: Validate written enum values
  ASoC: meson: g12a-toacodec: Fix event generation
  ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux
  i40e: Restore VF MSI-X state during PCI reset
  igc: Fix hicredit calculation
  net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues
  octeontx2-af: Don't enable Pause frames by default
  octeontx2-af: Set NIX link credits based on max LMAC
  octeontx2-af: Always configure NIX TX link credits based on max frame size
  octeontx2-af: Re-enable MAC TX in otx2_stop processing
  asix: Add check for usbnet_get_endpoints
  bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters()
  net: Implement missing SO_TIMESTAMPING_NEW cmsg support
  selftests: secretmem: floor the memory size to the multiple of page_size
  mm/memory-failure: check the mapcount of the precise page
  firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and 
ASM108x/VT630x PCIe cards
  x86/kprobes: fix incorrect return address calculation in 
kprobe_emulate_call_indirect
  i2c: core: Fix atomic xfer check for non-preempt config
  mm: fix unmap_mapping_range high bits shift bug
  mmc: meson-mx-sdhc: Fix initialization frozen issue
  mmc: rpmb: fixes pause retune on all RPMB partitions.
  mmc: core: Cancel delayed work before releasing host
  mmc: sdhci-sprd: Fix eMMC init failure after hw reset
  ipv6: remove max_size check inline with ipv4
  perf inject: Fix GEN_ELF_TEXT_OFFSET for jit
  kallsyms: Make module_kallsyms_on_each_symbol generally available
  tracing/kprobes: Fix symbol counting logic by looking at modules as well
  net: usb: ax88179_178a: remove redundant init code
  net: usb: ax88179_178a: move priv to driver_priv
  Linux 5.15.147
  UBUNTU: Upstream stable to v5.15.147

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


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

[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

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

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

Title:
  performance: Scheduler: ratelimit updating of load_avg

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

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2040026

  [Description]
    Improve cache bouncing on tg->load_avg

  [Hardware Information]
    Architecture:
  Intel / AMD (x86_64)
    Platform(s):
  Sapphire Rapids
    Date HW is expected at Canonical:

    Component(s):
  Perf-Scalability
  Scheduler

  [Software Information]
    Target Version:
  24.04
    Target Kernel:
  TBD
    Commit IDs:
  1528c661c24b sched/fair: Ratelimit update to tg->load_avg
    External Links:

  [Business Justification]

  [Testing guidance]

  [External ID]
    LFE-7154

  Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0

  
https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0

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


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

[Kernel-packages] [Bug 2054814] [NEW] lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

2024-02-23 Thread Heinrich Schuchardt

Public bug reported:

Starting the lxd-agent.service service fails with kernel
6.5.0-9-generic.

# /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
available for device config

[ 1239.456813] 9pnet_virtio: no channels available for device config
Couldn't mount virtiofs or 9p, failing.


The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

Removing the 9pnet_virtio module does not resolve the issue.

Best regards

Heinrich

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
Uname: Linux 6.5.0-9-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
 {
   "result": "skip"
 }
Date: Fri Feb 23 12:28:11 2024
InstallationDate: Installed on 2023-12-04 (81 days ago)
InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 (20231204)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug noble riscv64

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

Title:
  lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Starting the lxd-agent.service service fails with kernel
  6.5.0-9-generic.

  # /lib/systemd/lxd-agent-setup[ 1238.980879] 9pnet_virtio: no channels
  available for device config

  [ 1239.456813] 9pnet_virtio: no channels available for device config
  Couldn't mount virtiofs or 9p, failing.

  
  The "9pnet_virtio: no channels available for device config" messages occur 
frequently in the kernel log and did not exist in kernels prior to 6.5.

  Removing the 9pnet_virtio module does not resolve the issue.

  Best regards

  Heinrich

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Feb 23 12:28:11 2024
  InstallationDate: Installed on 2023-12-04 (81 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily riscv64 
(20231204)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2054406] Re: Focal update: v5.4.267 upstream stable release

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

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

Title:
  Focal update: v5.4.267 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local
  i40e: Fix filter input checks to prevent config with invalid values
  net: sched: em_text: fix possible memory leak in em_text_destroy()
  can: raw: add support for SO_TXTIME/SCM_TXTIME
  can: raw: add support for SO_MARK
  net-timestamp: extend SOF_TIMESTAMPING_OPT_ID to HW timestamps
  ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init
  net: bcmgenet: Fix FCS generation for fragmented skbuffs
  net: Save and restore msg_namelen in sock_sendmsg
  i40e: fix use-after-free in i40e_aqc_add_filters()
  ASoC: meson: g12a: extract codec-to-codec utils
  UBUNTU: [Config] Update annotations for CONFIG_SND_MESON_CODEC_GLUE
  ASoC: meson: g12a-tohdmitx: Validate written enum values
  ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux
  i40e: Restore VF MSI-X state during PCI reset
  net/qla3xxx: switch from 'pci_' to 'dma_' API
  net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues
  asix: Add check for usbnet_get_endpoints
  bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters()
  net: Implement missing SO_TIMESTAMPING_NEW cmsg support
  mm/memory-failure: check the mapcount of the precise page
  firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and 
ASM108x/VT630x PCIe cards
  i2c: core: Fix atomic xfer check for non-preempt config
  mm: fix unmap_mapping_range high bits shift bug
  mmc: rpmb: fixes pause retune on all RPMB partitions.
  mmc: core: Cancel delayed work before releasing host
  mmc: sdhci-sprd: Fix eMMC init failure after hw reset
  ath10k: Wait until copy complete is actually done before completing
  ath10k: Add interrupt summary based CE processing
  ath10k: Keep track of which interrupts fired, don't poll them
  ath10k: Get rid of "per_ce_irq" hw param
  PCI: Extract ATS disabling to a helper function
  PCI: Disable ATS for specific Intel IPU E2000 devices
  net/dst: use a smaller percpu_counter batch for dst entries accounting
  ipv6: make ip6_rt_gc_expire an atomic_t
  ipv6: remove max_size check inline with ipv4
  ASoC: meson: codec-glue: fix pcm format cast warning
  Linux 5.4.267
  UBUNTU: Upstream stable to v5.4.267

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


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

[Kernel-packages] [Bug 2054541] Re: Jammy update: v6.1.78 upstream stable release

2024-02-23 Thread Timo Aaltonen

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

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

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

Title:
  Jammy update: v6.1.78 upstream stable release

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

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

 v6.1.78 upstream stable release
 from git://git.kernel.org/

  
  Linux 6.1.78
  netfilter: nft_set_rbtree: skip end interval element from gc
  net: stmmac: xgmac: fix a typo of register name in DPP safety handling
  ALSA: usb-audio: Sort quirk table entries
  net: stmmac: xgmac: use #define for string constants
  clocksource: Skip watchdog check for large watchdog intervals
  block: treat poll queue enter similarly to timeouts
  f2fs: add helper to check compression level
  RDMA/irdma: Fix support for 64k pages
  vhost: use kzalloc() instead of kmalloc() followed by memset()
  Revert "ASoC: amd: Add new dmi entries for acp5x platform"
  io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers
  Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
  Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU
  hrtimer: Report offline hrtimer enqueue
  usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK
  usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK
  USB: serial: cp210x: add ID for IMST iM871A-USB
  USB: serial: option: add Fibocom FM101-GL variant
  USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e
  ALSA: usb-audio: add quirk for RODE NT-USB+
  ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter
  ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision
  mtd: parsers: ofpart: add workaround for #size-cells 0
  fs: dlm: don't put dlm_local_addrs on heap
  blk-iocost: Fix an UBSAN shift-out-of-bounds warning
  scsi: core: Move scsi_host_busy() out of host lock if it is for per-command
  fs/ntfs3: Fix an NULL dereference bug
  netfilter: nft_set_pipapo: remove scratch_aligned pointer
  netfilter: nft_set_pipapo: add helper to release pcpu scratch area
  netfilter: nft_set_pipapo: store index in scratch maps
  netfilter: nft_ct: reject direction for ct id
  drm/amd/display: Implement bounds check for stream encoder creation in DCN301
  netfilter: nft_compat: restrict match/target protocol to u16
  netfilter: nft_compat: reject unused compat flag
  netfilter: nft_compat: narrow down revision to unsigned 8-bits
  selftests: cmsg_ipv6: repeat the exact packet
  ppp_async: limit MRU to 64K
  af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC.
  tipc: Check the bearer type before calling tipc_udp_nl_bearer_add()
  rxrpc: Fix response to PING RESPONSE ACKs to a dead call
  drm/i915/gvt: Fix uninitialized variable in handle_mmio()
  inet: read sk->sk_family once in inet_recv_error()
  hwmon: (coretemp) Fix bogus core_id to attr name mapping
  hwmon: (coretemp) Fix out-of-bounds memory access
  hwmon: (aspeed-pwm-tacho) mutex for tach reading
  octeontx2-pf: Fix a memleak otx2_sq_init
  atm: idt77252: fix a memleak in open_card_ubr0
  tunnels: fix out of bounds access when building IPv6 PMTU error
  selftests: net: avoid just another constant wait
  selftests: net: cut more slack for gro fwd tests.
  net: atlantic: Fix DMA mapping for PTP hwts ring
  netdevsim: avoid potential loop in nsim_dev_trap_report_work()
  wifi: mac80211: fix waiting for beacons logic
  net: stmmac: xgmac: fix handling of DPP safety error for DMA channels
  drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup
  drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case
  drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case
  cifs: failure to add channel on iface should bump up weight
  phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP
  dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV
  phy: renesas: rcar-gen3-usb2: Fix returning wrong error code
  dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA
  dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA
  dmaengine: ti: k3-udma: Report short packet errors
  dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools
  ext4: regenerate buddy after block freeing failed if under

[Kernel-packages] [Bug 2054810] Re: Adding bpf to CONFIG_LSM in linux kernel

2024-02-23 Thread roblabla

(This is reposting 1964941 which appears to have expired)

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

Title:
   Adding bpf to CONFIG_LSM in linux kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Linux kernel since 5.7 allows to write eBPF programs which can be
  attached to LSM hooks. More details here:

  https://www.kernel.org/doc/html/v5.9/bpf/bpf_lsm.html

  There are already projects trying to leverage that

  systemd with the restrict-fs feature
  
https://github.com/systemd/systemd/blob/main/src/core/bpf/restrict_fs/restrict-fs.bpf.c

  https://github.com/linux-lock/bpflock

  https://github.com/lockc-project/lockc

  However, BPF LSM has to be enabled by adding bpf to CONFIG_LSM.
  That was already done in:

  Arch Linux

  https://github.com/archlinux/svntogit-
  packages/blob/4615bb2493649ad6fa133f864f94cb95c824f361/trunk/config#L9963

  Fedora

  
https://fedorapeople.org/cgit/thl/public_git/kernel.git/tree/kernel-x86_64-fedora.config?h=kernel-5.17.0-0.rc5.20220225git53ab78cd6d5a.106.vanilla.1.fc34=e661d91eb909e777a9d28425ef50fcc5ef7fa5ed#n3291

  openSUSE

  https://github.com/openSUSE/kernel-
  source/commit/c2c25b18721866d6211054f542987036ed6e0a50

  Could we please enable BPF LSM in Ubuntu kernels as well? Without that
  change, users trying to play with the mentioned projects have to edit
  their /etc/default/grub to add bpf LSM.

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


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

[Kernel-packages] [Bug 2054810] [NEW] Adding bpf to CONFIG_LSM in linux kernel

2024-02-23 Thread roblabla

Public bug reported:

Linux kernel since 5.7 allows to write eBPF programs which can be
attached to LSM hooks. More details here:

https://www.kernel.org/doc/html/v5.9/bpf/bpf_lsm.html

There are already projects trying to leverage that

systemd with the restrict-fs feature
https://github.com/systemd/systemd/blob/main/src/core/bpf/restrict_fs/restrict-fs.bpf.c

https://github.com/linux-lock/bpflock

https://github.com/lockc-project/lockc

However, BPF LSM has to be enabled by adding bpf to CONFIG_LSM.
That was already done in:

Arch Linux

https://github.com/archlinux/svntogit-
packages/blob/4615bb2493649ad6fa133f864f94cb95c824f361/trunk/config#L9963

Fedora

https://fedorapeople.org/cgit/thl/public_git/kernel.git/tree/kernel-x86_64-fedora.config?h=kernel-5.17.0-0.rc5.20220225git53ab78cd6d5a.106.vanilla.1.fc34=e661d91eb909e777a9d28425ef50fcc5ef7fa5ed#n3291

openSUSE

https://github.com/openSUSE/kernel-
source/commit/c2c25b18721866d6211054f542987036ed6e0a50

Could we please enable BPF LSM in Ubuntu kernels as well? Without that
change, users trying to play with the mentioned projects have to edit
their /etc/default/grub to add bpf LSM.

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

Title:
   Adding bpf to CONFIG_LSM in linux kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Linux kernel since 5.7 allows to write eBPF programs which can be
  attached to LSM hooks. More details here:

  https://www.kernel.org/doc/html/v5.9/bpf/bpf_lsm.html

  There are already projects trying to leverage that

  systemd with the restrict-fs feature
  
https://github.com/systemd/systemd/blob/main/src/core/bpf/restrict_fs/restrict-fs.bpf.c

  https://github.com/linux-lock/bpflock

  https://github.com/lockc-project/lockc

  However, BPF LSM has to be enabled by adding bpf to CONFIG_LSM.
  That was already done in:

  Arch Linux

  https://github.com/archlinux/svntogit-
  packages/blob/4615bb2493649ad6fa133f864f94cb95c824f361/trunk/config#L9963

  Fedora

  
https://fedorapeople.org/cgit/thl/public_git/kernel.git/tree/kernel-x86_64-fedora.config?h=kernel-5.17.0-0.rc5.20220225git53ab78cd6d5a.106.vanilla.1.fc34=e661d91eb909e777a9d28425ef50fcc5ef7fa5ed#n3291

  openSUSE

  https://github.com/openSUSE/kernel-
  source/commit/c2c25b18721866d6211054f542987036ed6e0a50

  Could we please enable BPF LSM in Ubuntu kernels as well? Without that
  change, users trying to play with the mentioned projects have to edit
  their /etc/default/grub to add bpf LSM.

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


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

[Kernel-packages] [Bug 2054809] [NEW] linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

2024-02-23 Thread Daan De Meyer

Public bug reported:

SRU Justification

[Impact]

The erofs.ko module (CONFIG_EROFS) is currently shipped in linux-
modules-extra. This makes it hard to pull in via the linux-virtual
package, it can only come from the linux-generic one that also pulls in
the firmware and everything else needed for baremetal, and that serves
no purpose in a qemu VM. This stops VMs using these kernels from using
the erofs filesystem. Erofs is a modern alternative to squashfs that
supports more features such as ACLs. The following LPC presentation has
more details on erofs and its advantages over squashfs:
https://youtu.be/jt-hp_LtSBc.

A user launching a VM using the linux-virtual kernel image is not able
to mount erofs filesystems due to the lack of this kconfig. We make
extensive use of erofs in systemd's upstream CI, which is running on
Github Actions, which uses Jammy, so it would be great to have this
backported.

[Fix]

Please consider moving this module to linux-modules.

These are already enabled in the 'main' kernel config, and in other
distros. In Debian/Archlinux/Fedora it is a (core) module that is built
by default.

To verify this works, it is sufficient to create an erofs filesystem
with mkfs.erofs and verify that it can be mounted:

$ mkdir sources
$ echo abcde > sources/file
$ mkfs.erofs erofs sources
$ mount erofs mnt --mkdir
$ ls mnt
file

Without this module installed and loaded, the mount will fail. Once
enabled, it will succeed.

[Test]

1. pull built linux-modules packages for architectures with do_extras_package
   set to true;
2. extract the deb and check if erofs kernel module file exists:

   $ dpkg-deb -R linux-modules-*.deb .
   $ find . -name erofs.ko\*

[Regression Potential]

Moving a module from a less-common to a more-common package should not
have any negative side effects. The main effect will be a little more
disk space used by the more common package, whether the module is in use
or not. There will also be more functionality available in the default
installation, which means a slightly increased surface and possibility
of new bugs in case it gets used.

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

Title:
  linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from
  linux-modules-extra to linux-modules

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  [Impact]

  The erofs.ko module (CONFIG_EROFS) is currently shipped in linux-
  modules-extra. This makes it hard to pull in via the linux-virtual
  package, it can only come from the linux-generic one that also pulls
  in the firmware and everything else needed for baremetal, and that
  serves no purpose in a qemu VM. This stops VMs using these kernels
  from using the erofs filesystem. Erofs is a modern alternative to
  squashfs that supports more features such as ACLs. The following LPC
  presentation has more details on erofs and its advantages over
  squashfs: https://youtu.be/jt-hp_LtSBc.

  A user launching a VM using the linux-virtual kernel image is not able
  to mount erofs filesystems due to the lack of this kconfig. We make
  extensive use of erofs in systemd's upstream CI, which is running on
  Github Actions, which uses Jammy, so it would be great to have this
  backported.

  [Fix]

  Please consider moving this module to linux-modules.

  These are already enabled in the 'main' kernel config, and in other
  distros. In Debian/Archlinux/Fedora it is a (core) module that is
  built by default.

  To verify this works, it is sufficient to create an erofs filesystem
  with mkfs.erofs and verify that it can be mounted:

  $ mkdir sources
  $ echo abcde > sources/file
  $ mkfs.erofs erofs sources
  $ mount erofs mnt --mkdir
  $ ls mnt
  file

  Without this module installed and loaded, the mount will fail. Once
  enabled, it will succeed.

  [Test]

  1. pull built linux-modules packages for architectures with do_extras_package
 set to true;
  2. extract the deb and check if erofs kernel module file exists:

 $ dpkg-deb -R linux-modules-*.deb .
 $ find . -name erofs.ko\*

  [Regression Potential]

  Moving a module from a less-common to a more-common package should not
  have any negative side effects. The main effect will be a little more
  disk space used by the more common package, whether the module is in
  use or not. There will also be more functionality available in the
  default installation, which means a slightly increased surface and
  possibility of new bugs in case it gets used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+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 2051468] Re: Fix snapcraftyaml.yaml for jammy:linux-raspi

This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
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-raspi' to 'verification-done-jammy-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.


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-raspi-v2 
verification-needed-jammy-linux-raspi

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

Title:
  Fix snapcraftyaml.yaml for jammy:linux-raspi

Status in linux package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  New
Status in linux-raspi source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  The in-tree snapcraft.yaml is stale. It does not produce any functional kernel
  snap for jammy:linux-raspi.

  [Fix]

  Replace the stale snapcraft.yaml with a newly implemented one.

  [Testcase]

  Build a pi-kernel with the following command:

  [for arm64]

  $ snapcraft --use-lxd --build-for=arm64

  for armhf]

  $ snapcraft --use-lxd --build-for=armhf

  Then, install it to Ubuntu Core 22 running on a raspi board.

  $ snap install --dangerous 

  Please note you need "grade: dangerous" for replacing
  the kernel using the local snap.

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


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

[Kernel-packages] [Bug 2051199] Please test proposed package

2024-02-23 Thread Łukasz Zemczak

Hello ethan.hsieh, or anyone else affected,

Accepted alsa-ucm-conf into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu1.11 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Mantic:
  Fix Committed
Status in alsa-ucm-conf source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs.

  mt8370-evk (G510):
  https://github.com/alsa-project/alsa-ucm-conf/pull/380
  
https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97
  mt8390-evk (G700):
  https://github.com/alsa-project/alsa-ucm-conf/pull/321
  
https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b
  mt8395-evk (G1200):
  https://github.com/alsa-project/alsa-ucm-conf/pull/322
  
https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0
  Fix a file type issue:
  https://github.com/alsa-project/alsa-ucm-conf/pull/386
  
https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf
  mt8395-evk (G1200) HDMI RX:
  https://github.com/alsa-project/alsa-ucm-conf/pull/389
  
https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1

  [Where problems could occur]
  1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu 
archive was rejected by upstream. Replace them with new patches accepted by 
upstream.
  2. Add initial support for mt8370-evk
  3. Add mt8395-evk HDMI RX support

  [Test Case]
  Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and 
mt8395-evk).
  1. Headset Jack Playback
  2. Audio (Speaker) Jack Playback
  3. mt8395-evk: HDMI RX

  Play audio by following commands.
  $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav

  [Regression Potential]
  1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk.
  2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream 
and new configs have been verified by MediaTek. It should be low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+subscriptions


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

[Kernel-packages] [Bug 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs

2024-02-23 Thread Łukasz Zemczak

Hello ethan.hsieh, or anyone else affected,

Accepted alsa-ucm-conf into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.9-1ubuntu3.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: alsa-ucm-conf (Ubuntu Mantic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-mantic

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Mantic:
  Fix Committed
Status in alsa-ucm-conf source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs.

  mt8370-evk (G510):
  https://github.com/alsa-project/alsa-ucm-conf/pull/380
  
https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97
  mt8390-evk (G700):
  https://github.com/alsa-project/alsa-ucm-conf/pull/321
  
https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b
  mt8395-evk (G1200):
  https://github.com/alsa-project/alsa-ucm-conf/pull/322
  
https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0
  Fix a file type issue:
  https://github.com/alsa-project/alsa-ucm-conf/pull/386
  
https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf
  mt8395-evk (G1200) HDMI RX:
  https://github.com/alsa-project/alsa-ucm-conf/pull/389
  
https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1

  [Where problems could occur]
  1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu 
archive was rejected by upstream. Replace them with new patches accepted by 
upstream.
  2. Add initial support for mt8370-evk
  3. Add mt8395-evk HDMI RX support

  [Test Case]
  Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and 
mt8395-evk).
  1. Headset Jack Playback
  2. Audio (Speaker) Jack Playback
  3. mt8395-evk: HDMI RX

  Play audio by following commands.
  $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav

  [Regression Potential]
  1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk.
  2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream 
and new configs have been verified by MediaTek. It should be low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+subscriptions


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

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

2024-02-23 Thread Xavier

Hi Daniel, Thank you for your quick reply. 
I will try that and post here the results.

All the best 
Xavier

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

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

2024-02-23 Thread Bin Li

commit 3c9a7d086da4a403d72ab8df8d924f7247882653
Author: Dimitri John Ledkov 
Date:   Fri Oct 27 18:53:00 2023 +0200

Revert "UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting"

BugLink: https://bugs.launchpad.net/bugs/2041613

This reverts commit a53dba9297be9597eac7b17738723bd44bac97ea.

Signed-off-by: Dimitri John Ledkov 
Acked-by: Andrea Righi 
Acked-by: Roxana Nicolescu 
Signed-off-by: Stefan Bader 

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

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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


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

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

2024-02-23 Thread Bin Li

On 22.04.4 with 6.5.0-oem kernel, we also met this issue during
shutdown.

Feb 23 15:20:36 P3-Tiny-Ref3-1 kernel: evict_inodes inode 20f5b07f, 
i_count = 1, was skipped!
Feb 23 15:20:36 P3-Tiny-Ref3-1 kernel: evict_inodes inode 3d74f469, 
i_count = 1, was skipped!

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

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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


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

[Kernel-packages] [Bug 2054782] Re: A typo in 2100-zfs-load-module.patch might cause unit to fail

2024-02-23 Thread Ubuntu Foundations Team Bug Bot

The attachment "Fix to the typo" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  A typo in 2100-zfs-load-module.patch might cause unit to fail

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The patch 2100-zfs-load-module.patch contains a typo that the second
  "Requires=zfs-load-module.service" in the diff of zfs-import-
  scan.service should be "After=".

  This might cause zfs-import-scan.service to start in parallel with
  zfs-load-module.service, causing it to fail.

  I have already corrected it on the debian side.

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


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

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

This bug was fixed in the package firmware-sof - 2.0-1ubuntu4.5

---
firmware-sof (2.0-1ubuntu4.5) jammy; urgency=medium

  * Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090
- Add Intel SOF2.7.2 topology files.
  * Update soundwire topology files for Intel RPL platforms. LP: #2044330
- Update v2.2.8 topology files for Intel RPL platforms

 -- You-Sheng Yang   Wed, 15 Nov 2023
23:32:40 +0800

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

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

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

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

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


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

[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms