date:20240201

You have an unsupported DKMS module (virtualbox) installed that breaks
the kernel headers installation. Please remove it:

$ dkms remove virtualbox


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

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

Title:
  package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to
  install/upgrade: le sous-processus paquet linux-
  headers-6.6.0-14-generic script post-installation installé a renvoyé
  un état de sortie d'erreur 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  i try to restore my grub

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  allan2 2792 F wireplumber
   /dev/snd/controlC0:  allan2 2792 F wireplumber
   /dev/snd/seq:allan2 2788 F pipewire
  CasperMD5CheckResult: unknown
  Date: Thu Feb  1 17:03:59 2024
  ErrorMessage: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
  InstallationDate: Installed on 2023-08-04 (181 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic 
root=UUID=57f5a567-b182-49a7-95fc-5618da43a67e ro i8042.nopnp=1 pci=nocrs quiet
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 
3.11.4-5ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12~rc1-12ubuntu4
  SourcePackage: linux
  Title: package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to 
install/upgrade: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2018
  dmi.bios.release: 2.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET97WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN0079MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET97WW(2.51):bd09/27/2018:br2.51:efr1.12:svnLENOVO:pn20AN0079MZ:pvrThinkPadT440p:rvnLENOVO:rn20AN0079MZ:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AN_BU_Think_FM_ThinkPadT440p:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN0079MZ
  dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2051953] Re: package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to install/upgrade: le sous-processus paquet linux-headers-6.6.0-14-generic script post-installation insta

Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.6.0-14-generic -C /lib/modules/6.6.0-14-generic/build 
M=/var/lib/dkms/virtualbox/6.1.38/build(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.6.0-14-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.38/build/make.log for more information.
dkms autoinstall on 6.6.0-14-generic/x86_64 succeeded for nvidia
dkms autoinstall on 6.6.0-14-generic/x86_64 failed for virtualbox(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
 * dkms: autoinstall for kernel 6.6.0-14-generic
   ...fail!

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

Title:
  package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to
  install/upgrade: le sous-processus paquet linux-
  headers-6.6.0-14-generic script post-installation installé a renvoyé
  un état de sortie d'erreur 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  i try to restore my grub

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  allan2 2792 F wireplumber
   /dev/snd/controlC0:  allan2 2792 F wireplumber
   /dev/snd/seq:allan2 2788 F pipewire
  CasperMD5CheckResult: unknown
  Date: Thu Feb  1 17:03:59 2024
  ErrorMessage: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
  InstallationDate: Installed on 2023-08-04 (181 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic 
root=UUID=57f5a567-b182-49a7-95fc-5618da43a67e ro i8042.nopnp=1 pci=nocrs quiet
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 
3.11.4-5ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12~rc1-12ubuntu4
  SourcePackage: linux
  Title: package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to 
install/upgrade: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2018
  dmi.bios.release: 2.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET97WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN0079MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET97WW(2.51):bd09/27/2018:br2.51:efr1.12:svnLENOVO:pn20AN0079MZ:pvrThinkPadT440p:rvnLENOVO:rn20AN0079MZ:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AN_BU_Think_FM_ThinkPadT440p:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN0079MZ
  dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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


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

2024-02-01 Thread Allison Karlitskaya

> It is expected to be released in 2 weeks

Thanks!  Is there anywhere we can get access to a proposed/pre-release
package with the fix inside to verify that it fixes the issue in our CI?

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

Title:
  partproke is broken on empty loopback device

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

Bug description:
  SRU Justification:

  [Impact]

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

  [Fix]

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

  [Test Plan]

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

  [Where problems could occur]

  * We may see issues on disk partitions operations.

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

  Do this:

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

  Notice this very odd error message:

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update

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

Title:
  [SRU][22.04.04]: mpi3mr driver update

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Opinion
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [Impact]

  This update has been initiated to incorporate the mpi3mr driver from
  upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point
  releases).

  This has been requested by both Broadcom as the upstream and by one of
  the larger OEM partners who are going to be selling systems with these
  storage controllers to customers.  This series of patches includes bug
  fixes and support for current Broadcom controllers.

  [Fixes]
  Below are the commit IDs for the latest upstream version (v6.8).

  The 22.04 LTS point kernel already includes the latest mpi3mr driver
  version 8.0.0.69.0. Therefore, the listed commit IDs below correspond
  to the subsequent patches.

  The commit IDs listed below are in sequential order from bottom to
  top, indicating the order for applying the patches.

  linux-next
  d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0
  9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers 
part-3
  fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers 
part-2
  c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers 
part-1
  07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply 
descriptor
  f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and 
Unrecoverable State
  c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset
  e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset
  b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50
  1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor
  cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32
  c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116
  6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs

  Mainline at 6.6/6.7
  82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset
  9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0
  d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after 
controller reset
  e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation
  d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O
  6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28
  9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out

  [Testing]
  verify the mpi3mr driver is loaded
  verify the version string shows 8.5.1.0.0

  [Regression Risk]
  Low. These patches are contained to the mpi3mr driver code itself and are all 
already accepted upstream.  They cleanly pick into our 6.5 kernel tree.

  Broadcom has tested these and the only concern is the kernel warning
  below in Comment #7

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


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

[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel

MAntic is fixed with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051584

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

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

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

Title:
  i915 regression introduced with 5.5 kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.15 source package in Focal:
  Triaged
Status in linux source package in Jammy:
  Fix Committed
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-hwe-5.15 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-5.15 source package in Noble:
  Invalid

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Original bug description:

  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

To manage notifications

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

** 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-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  
  SRU Justification:

  [Impact]

  Multiple users have reported frozen displays when external HDMI device
  is connected on systems with intel graphics chipsets.

  [Fix]

  * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
  from 6.6.9

  [Test Plan]

  * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
  It seems it affects mostly Alder Lake though, but at least it does not
  cause any issues on other models.
  * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  [Where problems could occur]
  * We could see issues on systems with Intel Graphics when HDMI devices
  are connected during power state changes.

  
  Old description:
  It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec

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

** 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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051050

Title:
  Audio balancing setting doesn't work with the cirrus codec

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

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

  Currently this patch is in the linux-next, and will be in the
  mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble
  kernel, Noble kernel will have this patch automatically.

  [Impact]
  In the gnome audio setting, if we adjust balancing setting, it doesn't
  work at all on a Dell machine with cirrus codec, that is because with
  the current driver, the exported amixer controls can't be handled by
  pulseaudio.

  [Fix]
  Cherry-pick a mainline kernel patch, this could fix this issue.

  [Test]
  Booted with the patched kernel, move the bar to the left or right to
  adjust the balance, we could hear the sound from left channel or right
  channel accordingly.

  [Where problems could occur]
  This change will not create "Master Volume" amixer controls, probably
  will make the audio control malfunction, that is we couldn't control
  playback or capture volume correctly, but this regression possibility
  is very low, we already tested the patch on the machines with cirrus
  codec, they all worked well as before.

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


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

It is expected to be released in 2 weeks

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

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

Title:
  partproke is broken on empty loopback device

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

Bug description:
  SRU Justification:

  [Impact]

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

  [Fix]

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

  [Test Plan]

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

  [Where problems could occur]

  * We may see issues on disk partitions operations.

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

  Do this:

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

  Notice this very odd error message:

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2051733] Re: Specifying nohz_full breaks CPU frequency reporting

2024-02-01 Thread Doug Smythies

The way it is currently done, I don't think valid CPU frequency listing
via "scaling_cur_freq", or /proc/cpuinfo, is expected to work. Why not?
Because the required code is never executed, on purpose. Here is an
excerpt from a commit (see the bit about NOHZ full)


commit f3eca381bd49d708073ba1a9af4fa6ea5d5810a6
Author: Thomas Gleixner 
Date:   Fri Apr 15 21:20:04 2022 +0200

x86/aperfmperf: Replace arch_freq_get_on_cpu()

Reading the current CPU frequency from /sys//scaling_cur_freq involves
in the worst case two IPIs due to the ad hoc sampling.

The frequency invariance infrastructure provides the APERF/MPERF samples
already. Utilize them and consolidate this with the /proc/cpuinfo readout.

The sample is considered valid for 20ms. So for idle or isolated NOHZ full
CPUs the function returns 0, which is matching the previous behaviour.

There was couple of later commits and now it prints out the minimum CPU
frequency when it thinks the number are stale. With NOHz full it always
thinks the numbers are stale.

The intel_cpufreq driver seems to display CPU frequencies okay, but only
the pstate that was requested, not the actual frequency granted.

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

Title:
  Specifying nohz_full breaks CPU frequency reporting

Status in linux-signed-lowlatency-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  With the lowlatency kernel, if I specify "nohz_full=1-15" boot
  parameter then CPU frequency reporting doesn't work for the logical
  cores 1-15. That is, only logical core 0 shows varying CPU frequency
  in its /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all
  other cores constantly show 80 in their scaling_cur_freq files
  (which is the lowest supported frequency) regardless of the CPU load.

  Steps to reproduce:

  1. Add "nohz_full=1-15" (specify the core numbers to include all logical 
cores except 0) to kernel boot options in /etc/default/grub.
  2. Run `sudo update-grub` and reboot.
  3. Upon booting, run a multithreaded workload. For example, run `openssl 
speed -multi $(nproc --all)`.
  4. In another console, monitor CPU frequencies by running `watch cat 
/sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`.

  Actual results:

  All cores specified in "nohz_full" parameter always report their
  lowest frequency.

  Despite that, the actual performance seems to be as if frequency
  scaling actually works (i.e. according to benchmarks, the performance
  seems to be similar with and without the "nohz_full" parameter).

  Expected results:

  All cores must report their actual frequency depending on the load.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3
  Uname: Linux 6.5.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Jan 30 23:39:51 2024
  InstallationDate: Installed on 2015-05-01 (3196 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: linux-signed-lowlatency-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago)

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


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

[Kernel-packages] [Bug 2051733] Re: Specifying nohz_full breaks CPU frequency reporting

2024-02-01 Thread Doug Smythies

CPU frequency scaling driver: intel_pstate
CPU frequency scaling governor: powersave
HWP: disabled.

Purpose to verify that the driver is working correctly, regardless of CPU
frequencies reported.
A single threaded load was applied to CPU 5 at 347 hertz sleep/work frequency.
The load was increased then deceased. The intel_pstate_tracer.py utility was
run during the test capturing the attached.
All pstates were used and appropriate per the load.

** Attachment added: "all_cpu_frequencies.png"

https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.5/+bug/2051733/+attachment/5744261/+files/all_cpu_frequencies.png

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

Title:
Specifying nohz_full breaks CPU frequency reporting

Status in linux-signed-lowlatency-hwe-6.5 package in Ubuntu:
Confirmed

Bug description:
With the lowlatency kernel, if I specify "nohz_full=1-15" boot
parameter then CPU frequency reporting doesn't work for the logical
cores 1-15. That is, only logical core 0 shows varying CPU frequency
in its /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all
other cores constantly show 80 in their scaling_cur_freq files
(which is the lowest supported frequency) regardless of the CPU load.

Steps to reproduce:

1. Add "nohz_full=1-15" (specify the core numbers to include all logical
cores except 0) to kernel boot options in /etc/default/grub.
2. Run `sudo update-grub` and reboot.
3. Upon booting, run a multithreaded workload. For example, run `openssl
speed -multi $(nproc --all)`.
4. In another console, monitor CPU frequencies by running `watch cat
/sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`.

Actual results:

All cores specified in "nohz_full" parameter always report their
lowest frequency.

Despite that, the actual performance seems to be as if frequency
scaling actually works (i.e. according to benchmarks, the performance
seems to be similar with and without the "nohz_full" parameter).

Expected results:

All cores must report their actual frequency depending on the load.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3
Uname: Linux 6.5.0-15-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Jan 30 23:39:51 2024
InstallationDate: Installed on 2015-05-01 (3196 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: linux-signed-lowlatency-hwe-6.5
UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago)

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

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

** Tags added: originate-from-2000353

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

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 1970069] Re: Annoying boot messages interfering with splash screen

The blanking from GRUB_TIMEOUT>0 will be made much worse by
CONFIG_FB_EFI=n because usually in Ubuntu it's the efifb that restores
the logo after Grub has wiped it. I think not having CONFIG_FB_EFI at
the same time as using GRUB_TIMEOUT>0 explains your previous "really
long time of a black screen".

I can tell you've restored GRUB_TIMEOUT=0 in the video and the one
remaining screen blank at Plymouth's startup might be bug 1836858. But
either way it's not this bug. Related bugs can be found at
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=flickerfreeboot

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

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

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2051994] Re: /tmp drive fills up

2024-02-01 Thread Russell Harper

Okay, I'll try to see what the tools say, but so far it happens only
when the computer is left at the login for a while. This is the page
where various users can login, so technically only background processes
are running.

I've tried multiple times to catch it in the act, but never successful.
/tmp is either at 0.1% or 100%. When at 100%, it's very difficult to
diagnose anything because the computer is going haywire.

If I just reboot and don't login, it still happens on its own after a
day or so. The only substantive change was a recent update to 23.10:

  Distributor ID: Ubuntu
  Description:Ubuntu 23.10
  Release:23.10
  Codename:   mantic

The /tmp drive issues started happening just after the update to 23.10.

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

Title:
  /tmp drive fills up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If left at the login screen, after a day or so, /tmp seems to fill up
  on its own. It will show an X window message upon login regarding
  /tmp, then any applications, like LibreOffice, won't run. The files
  don't shows up using du, likely because it's a tmpfs type.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-15-generic 6.5.0-15.15
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  russell1197 F wireplumber
   /dev/snd/controlC1:  russell1197 F wireplumber
   /dev/snd/controlC0:  russell1197 F wireplumber
   /dev/snd/seq:russell1191 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Feb  1 17:24:21 2024
  InstallationDate: Installed on 2023-06-23 (223 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ff2b9230-f3ac-4af5-ae27-88eae14765d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-15-generic N/A
   linux-backports-modules-6.5.0-15-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2024-01-26 (6 days ago)
  dmi.bios.date: 05/09/2017
  dmi.bios.release: 2.71
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.71
  dmi.board.asset.tag: 2UA4101ZMS
  dmi.board.name: 18E7
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA4101ZMS
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.71:bd05/09/2017:br2.71:svnHewlett-Packard:pnHPProDesk600G1SFF:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct4:cvr:skuE3S71UT#ABA:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP ProDesk 600 G1 SFF
  dmi.product.sku: E3S71UT#ABA
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 2052005] [NEW] Validate connection interval to pass Bluetooth Test Suite

2024-02-01 Thread Kai-Heng Feng

Public bug reported:

[Impact]
Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified.

[Fix]
Validate max connection interval to pass test case
"GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid
Parameters Central Responder'" 

[Test]
Run the test suite. With the patch applied the case is passed.

[Where problems could occur]
If any device requires setting a wrong interval to function properly,
this might affect those devices in theory.

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

** Affects: linux (Ubuntu Jammy)
 Importance: Low
 Status: Confirmed

** Affects: linux (Ubuntu Mantic)
 Importance: Low
 Status: Confirmed

** Affects: linux (Ubuntu Noble)
 Importance: Low
 Status: Confirmed

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Noble)
   Importance: Undecided => 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/2052005

Title:
  Validate connection interval to pass Bluetooth Test Suite

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

Bug description:
  [Impact]
  Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified.

  [Fix]
  Validate max connection interval to pass test case
  "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid
  Parameters Central Responder'" 

  [Test]
  Run the test suite. With the patch applied the case is passed.

  [Where problems could occur]
  If any device requires setting a wrong interval to function properly,
  this might affect those devices in theory.

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


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

[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad

2024-02-01 Thread Kai-Heng Feng

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

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

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

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

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

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

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

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

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

Title:
  Fix spurious wakeup caused by Cirque touchpad

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Spurious wakeup event caused by Cirque touchpad, prevent the system from
  sleep properly.

  [Fix]
  Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad.

  [Test]
  Suspend the system 100 times and make sure non of the wakeup event is
  caused by the touchpad and its IRQ line.

  [Where problems could occur]
  Logically the power consumption can increase slightly, but in reality
  there isn't any noticeable change. Since the quirk only applies to one
  device, there isn't much regression risk.

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


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

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

2024-02-01 Thread Mario Limonciello

With your change Fedora and Ubuntu are now behaving relatively similarly.
* Both have a deficiency where the handoff from BGRT logo to Plymouth is doing 
a modeset for some reason.  
* Due to something in Fedora's GRUB it's a little clearer when GRUB starts.

Here's various artifacts if you want to be able to compare anything since I 
have both on the same hardware.
I ran the same kernel binary that has your patches on both (but on Fedora it 
behavedthe same with a stock one).

Ubuntu booting (video): https://youtu.be/1J0_Vg1pScQ
Kernel config: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-kernel-config-both
Ubuntu /etc/default/grub: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-etc-default-grub
Ubuntu journal: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-journal
Fedora booting (video): https://youtu.be/IzesNHpM-nw
Fedora journal: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-fedora-journal

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

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

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

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

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

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

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

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

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

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

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


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

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

2024-02-01 Thread Mario Limonciello

Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black
screen.

Moving that to zero certainly helps.  It's a lot better; but still not perfect.
Let me get things back to as close as possible to stock and capture logs and a 
videos to compare with Ubuntu and Fedora with this exact same kernel and I'll 
get back.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

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

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

2024-02-01 Thread Hui Wang

Installed the proposed kernel (1014) to some lenovo/dell/hp machines,
the audio worked as well as before. verification done.


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

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

Title:
  Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  To support HP stella's latest machine, we need to backport some new PCIIDs 
and corresponding drivers to our OEM kernel, the requirement is here:
  
https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508

  This pull-request is to unitfy and add some audio controller's ID, but
  to do so, need to apply some depending patches otherwise it will have
  conflict to introduce the new ID and new driver to OEM kernel.

  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL

  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

  [Fix]
  This add the audio driver for machines with Intel Arrowlake.

  [Test case]
  Boot the patched kernel on a Arrowlake machine, the audio function could 
work. Boot the patches kernel on non-Arrowlake machines, the audio function 
could work as well as before.

  [Where problems could occur]
  Could lose some pciids and make the auido driver not work on those machines, 
and could not play sound or record sound. But this possibility is very low, I 
checked each patch carefully and I verify the patcheset on some lenovo an dell 
machines.

  From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based 
on it, added new PCIID and audio support for arrowlake-s, need to backport them 
to oem-6.5, this is a preparation for supporting HP latest laptops:
  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL

  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

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


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

[Kernel-packages] [Bug 2051450] Re: Nouveau kernel errors prevent reaching the login screen on NVIDIA GA106

The slow login is unrelated to this bug. Please open a new bug for that.

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

Title:
  Nouveau kernel errors prevent reaching the login screen on NVIDIA
  GA106

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

Bug description:
  n/a

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-session-bin 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:29:28 2024
  ExecutablePath: /usr/libexec/gnome-session-binary
  InstallationDate: Installed on 2023-12-27 (31 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apport: [deleted]

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


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

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

GRUB_TIMEOUT > 0 also causes the vendor logo to be replaced by a black
screen, but that seems to be Grub's fault. Default Ubuntu won't have
that problem since it ships GRUB_TIMEOUT=0. And if you want a nonzero
timeout without the blackness then GRUB_TERMINAL=console is a
workaround.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

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

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 241000] Re: Pairing: passcode dialogue disappears in <1 second

This bug has been closed for over 14 years so if you have any current
issues then please open new bugs for each of them.

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

Title:
  Pairing: passcode dialogue disappears in <1 second

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez-utils package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: bluez-utils

  The pairing dialogues to allow entering a pin and initiate pairing
  disappear too fast.

  If I do the following:

sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth
  00:19:DB:0A:xx:yy

  a notifier window will pop up for ~1 second and then disappear.

  If I click on the notifier window fastest, the main passcode/pincode
  entry dialogue will disappear.  This also disappears within 1second.

  The key seems to be that it is necessary to 'auth', click and
  'pincode' within 1 second of a connection being made.  This should
  actually wait until the user is able to and none of the dialogue boxes
  should cut-off early and disappear without warning.

  Forum post discussing the same thing, with screenshots:

http://ph.ubuntuforums.com/showthread.php?p=5044322

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


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

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

I think that's a different bug. I believe it's when plymouthd is
starting and is the handover (mode set?) from efifb to DRM. It doesn't
happen at all if you add "nomodeset" (please try that).

"Really long time" might be subjective though? How long?

VT switches (or more accurately virtual console switches if fbcon isn't
active yet) shouldn't ever be affected by the patch. It only defers the
introduction of text to the screen.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

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

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2006557] Re: Enable rdma-sniffer for libpcap

** Changed in: libpcap (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: libpcap (Ubuntu)
   Status: Triaged => 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/2006557

Title:
  Enable rdma-sniffer for libpcap

Status in libpcap package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Invalid
Status in libpcap package in Debian:
  Won't Fix

Bug description:
  Hi,

  The request is to build and configure stock package libpcap with rdma-sniffer 
enabled.
  We'd like users of rdma devices to be able to sniff on them using stock 
tcpdump.
  Currently when using default tcpdump It does not list rdma devices.

  $ tcpdump -D |grep -i rdma
  $ 

  when using locally build tcpdump (with rdma enabled)
  $ cd 
  $ ./tcpdump -D |grep -i rdma
  24.rocep4s0 (RDMA sniffer)
  25.rocep7s0f0 (RDMA sniffer)
  26.rocep7s0f1 (RDMA sniffer)
  27.rocep10s0f0 (RDMA sniffer)
  28.rocep10s0f1 (RDMA sniffer)
  29.rocep33s0f0 (RDMA sniffer)
  30.rocep33s0f1 (RDMA sniffer)
  31.rocep36s0f0 (RDMA sniffer)
  32.ibp36s0f1 (RDMA sniffer)

  Locally build steps:
  clone sources:
  $ mkdir tcpdumpbuild
  $ cd tcpdumpbuild/
  $ git clone https://github.com/the-tcpdump-group/tcpdump.git
  $ git clone https://github.com/the-tcpdump-group/libpcap.git

  install required packages (including rdma packages so libpcap is built with 
rdma enabled):
  $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils
  configure and build
  $ cd libpcap
  $ ./autogen.sh 
  $ ./configure --enable-rdma=yes
  $ make 
  cd ../tcpdump/
  ./autogen.sh 
  ./configure 
  $ make

  now ./tcpdump -D can show rdma devices.

  Thanks !

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


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

[Kernel-packages] [Bug 2051994] Re: /tmp drive fills up

2024-02-01 Thread Seth Arnold

Hello, I suspect this is more likely a program on your computer acting
poorly.

I suggest trying a few different tools from the bpfcc-tools package:

- opensnoop-bpfcc
- filelife-bpfcc
- dirtop-bpfcc
- filetop-bpfcc

Thanks

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

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

Title:
  /tmp drive fills up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If left at the login screen, after a day or so, /tmp seems to fill up
  on its own. It will show an X window message upon login regarding
  /tmp, then any applications, like LibreOffice, won't run. The files
  don't shows up using du, likely because it's a tmpfs type.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-15-generic 6.5.0-15.15
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  russell1197 F wireplumber
   /dev/snd/controlC1:  russell1197 F wireplumber
   /dev/snd/controlC0:  russell1197 F wireplumber
   /dev/snd/seq:russell1191 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Feb  1 17:24:21 2024
  InstallationDate: Installed on 2023-06-23 (223 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ff2b9230-f3ac-4af5-ae27-88eae14765d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-15-generic N/A
   linux-backports-modules-6.5.0-15-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2024-01-26 (6 days ago)
  dmi.bios.date: 05/09/2017
  dmi.bios.release: 2.71
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.71
  dmi.board.asset.tag: 2UA4101ZMS
  dmi.board.name: 18E7
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA4101ZMS
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.71:bd05/09/2017:br2.71:svnHewlett-Packard:pnHPProDesk600G1SFF:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct4:cvr:skuE3S71UT#ABA:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP ProDesk 600 G1 SFF
  dmi.product.sku: E3S71UT#ABA
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 2049768] Re: my computer doesnt start

2024-02-01 Thread Seth Arnold

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

Title:
  my computer doesnt start

Status in linux package in Ubuntu:
  New

Bug description:
  This shows up on the black screen:

  UBSAN:
   array-index-out-of-bounds in 
/build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 
: 28 index 15 is out of range for type 'u8 [1]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonathan   1116 F pulseaudio
   /dev/snd/controlC1:  jonathan   1116 F pulseaudio
   /dev/snd/pcmC0D0p:   jonathan   1116 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-09 (709 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset 
dis_ucode_ldr
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/30/2018
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: INTEL H55
  dmi.board.vendor: INTEL
  dmi.board.version: INTEL
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

2024-02-01 Thread Sunit

Thanks Daniel Letzesien that worked

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Invalid
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Invalid
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Invalid
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Invalid
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Invalid
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

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


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

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

2024-02-01 Thread Mario Limonciello

I tested it on Noble with a hand built kernel and it at least does what
you planned (don't see any console messages), but also I'm not seeing
the OEM vendor logo stick all the way through.  There's a really long
time of a black screen.  Not sure if this is because it was an upstream
kernel and it's missing a VT switch patch or something.

Does that match what you're seeing?

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

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

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2051994] [NEW] /tmp drive fills up

2024-02-01 Thread Russell Harper

Public bug reported:

If left at the login screen, after a day or so, /tmp seems to fill up on
its own. It will show an X window message upon login regarding /tmp,
then any applications, like LibreOffice, won't run. The files don't
shows up using du, likely because it's a tmpfs type.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-15-generic 6.5.0-15.15
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  russell1197 F wireplumber
 /dev/snd/controlC1:  russell1197 F wireplumber
 /dev/snd/controlC0:  russell1197 F wireplumber
 /dev/snd/seq:russell1191 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Thu Feb  1 17:24:21 2024
InstallationDate: Installed on 2023-06-23 (223 days ago)
InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ff2b9230-f3ac-4af5-ae27-88eae14765d1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-15-generic N/A
 linux-backports-modules-6.5.0-15-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2024-01-26 (6 days ago)
dmi.bios.date: 05/09/2017
dmi.bios.release: 2.71
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.71
dmi.board.asset.tag: 2UA4101ZMS
dmi.board.name: 18E7
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA4101ZMS
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.71:bd05/09/2017:br2.71:svnHewlett-Packard:pnHPProDesk600G1SFF:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct4:cvr:skuE3S71UT#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP ProDesk 600 G1 SFF
dmi.product.sku: E3S71UT#ABA
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug mantic

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

Title:
  /tmp drive fills up

Status in linux package in Ubuntu:
  New

Bug description:
  If left at the login screen, after a day or so, /tmp seems to fill up
  on its own. It will show an X window message upon login regarding
  /tmp, then any applications, like LibreOffice, won't run. The files
  don't shows up using du, likely because it's a tmpfs type.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-15-generic 6.5.0-15.15
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  russell1197 F wireplumber
   /dev/snd/controlC1:  russell1197 F wireplumber
   /dev/snd/controlC0:  russell1197 F wireplumber
   /dev/snd/seq:russell1191 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Feb  1 17:24:21 2024
  InstallationDate: Installed on 2023-06-23 (223 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ff2b9230-f3ac-4af5-ae27-88eae14765d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-15-generic N/A
   linux-backports-modules-6.5.0-15-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2024-01-26 (6 days ago)
  dmi.bios.date: 05/09/2017
  dmi.bios.release: 2.71
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.71
  dmi.board.asset.tag: 2UA4101ZMS
  dmi.board.name: 18E7
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA4101ZMS
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.71:bd05/09/2017:br2.71:svnHewlett-Packard:pnHPProDesk600G1SFF:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct4:cvr:skuE3S71UT#ABA:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP ProDesk 600 G1 SFF
  dmi.product.sku: E3S71UT#ABA
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

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

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

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

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  Confirmed
Status in gcc-defaults package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

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

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

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

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  Confirmed
Status in gcc-defaults package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

2024-02-01 Thread Heinrich Schuchardt

Flash-kernel contains a database matching device-tree machine values
with devicetree names.

There is no necessity to remove entries for architectures that are not
supported in Ubuntu. We should try to minimize the differences to
Debian. So setting this to won't fix for flash-kernel.

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

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

Title:
  Remove armhf support

Status in flash-kernel package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in flash-kernel source package in Noble:
  Won't Fix
Status in linux-raspi source package in Noble:
  New

Bug description:
  Noble and newer don't support armhf for Pi anymore.

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


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

[Kernel-packages] [Bug 2051763] Re: RTL8821CE did not work

2024-02-01 Thread Florian Kreutzer

We ran into a similar issue since Ubuntu 22.04.3 moved from linux-6.2.y to 
6.5.y for linux-generic-hwe-22.04.
The corresponding dkms package rtl8821ce-dkms-5.5.2.1-0ubuntu11~0.22.04.1 
unsurprisingly no longer compiles due to quite a number of kernel API changes.

Btw, we're currently considering to test
https://github.com/tomaspinho/rtl8821ce (Arch upstream for their dkms)
as it seems to support recent versions of linux and it compiles mostly
clean using linux-generic-hwe-22.04-6.5.0.14.14~22.04.7.

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

Title:
  RTL8821CE did not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless
  Network Adapter did not work on 6.5 kernels

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2024-02-01 Thread Charles Hedrick

For what it's worth, we've been running a file server for several weeks
with the 2.1.14 .ko files in 22.04 with no problem. I didn't try to
cherry pick the one fix as I'd prefer to have the whole 2.1.14.

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  In Progress
Status in zfs-linux source package in Jammy:
  In Progress
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

   * The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
 only makes it stronger and not weaker, thus if it were incorrect, likely
 only performance would be impacted (and it is unlikely to be incorrect
 given upstream reviews and attention to data corruption issues; also,
 there are no additional changes to that function upstream)

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

Reviewed zfs-linux on mantic/jammy/focal-unapproved for acceptance.

They all look good to me (notes below, in addition to usual checks),
but I'll ask for another reviewer to provide input too, as it's ZFS.
(But I did want to provide some assistance in this long-running SRU.)

Thanks,
Mauricio

...

mantic:

The code change looks good and hasn't changed further upstream.
(There are suggested /alternatives/ in Draft state [1], but the draft 
reassures that the original, merged PR is correct.)

The [Test Plan] section provides both a specific reproducer and
general testing (in many forms), which is reassuring for -proposed
verification.

P.S.: not very polished changelog/patch files, but combined they do 
provide the information to find the LP bug and upstream/commit, usually found 
via DEP-3 headers as Origin/Bug-Ubuntu.
(Style isn't the most important thing in this case or at the moment.)

$ git log --oneline zfs-2.2.2 -- module/zfs/dnode.c | grep -m1 
'dnode_is_dirty: check dnode and its data for dirtiness'
9b9b09f452a4 dnode_is_dirty: check dnode and its data for dirtiness

jammy:

Likewise.

Regarding the point release, 22.04.4 (scheduled for Feb 22 [2]),
we are still before 'Release minus 14 (or 7) days' [3]
(when '6. Coordinate with the SRU team' and '7. ... -updates pocket 
freeze' happen).

$ git log --oneline zfs-2.1.14 -- module/zfs/dnode.c | grep -m1 
'dnode_is_dirty: check dnode and its data for dirtiness'
77b0c6f0403b dnode_is_dirty: check dnode and its data for dirtiness

focal:

The code change is a backport not from upstream (0.8 no longer 
maintained, apparently),
but comes from the original author of the patch (and noted with DEP-3 
Origin:, great!),
and looks equivalent (same code change, just in a different function 
and context).
[4]

links:
[1] https://github.com/openzfs/zfs/pull/15615
[2] https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906
[3] https://wiki.ubuntu.com/PointReleaseProcess
[4] https://github.com/robn/zfs/commit/f2f7f43a9bf4628328292f25b1663b873f271b1a

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  In Progress
Status in zfs-linux source package in Jammy:
  In Progress
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation,

[Kernel-packages] [Bug 2051450] Re: Nouveau kernel errors prevent reaching the login screen on NVIDIA GA106

2024-02-01 Thread Joel Vázquez Ortiz

I went into the recovery with "nomodeset" option. I installed the up-to-
date driver "nvidia-driver-545". I rebooted, the bootup process was
quick and it went straight to the login screen without a problem. The
only thing I noticed is that after I entered my credentials and hit the
enter key it took about 2 minutes to completely load up to the desktop
screen. I clocked it as I was watching the time on my cell phone. This
has been a problem with the nvidia drivers for a while. I don't remember
the bug tracker number at this moment.

As I am checking the logs of the current boot I noticed that the nvidia driver
has tainted the kernel. The nvidia module is "out-of-tree" which means it's
outside of the Linux Kernel source tree. This happens when a module uses
proprietary code and is not approved by (Linux Kernel Developers), my guess, or
has buggy code.
Apparently I can safely ignore this warning message.

I ran this command:

$ cat /proc/sys/kernel/tainted

Which gives me this error code: 4097

I go to this website: https://docs.kernel.org/admin-guide/tainted-kernels.html
To find the "Table for decoding tainted state". I get "G/PO".

I ran the command "journalctl -b-0" for the current boot log. I left the
log in the attachment. Thank you.

** Attachment added: "crntboot.log"

https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051450/+attachment/5744214/+files/crntboot.log

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

Title:
Nouveau kernel errors prevent reaching the login screen on NVIDIA
GA106

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

Bug description:
n/a

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-session-bin 42.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 28 09:29:28 2024
ExecutablePath: /usr/libexec/gnome-session-binary
InstallationDate: Installed on 2023-12-27 (31 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apport: [deleted]

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

[Kernel-packages] [Bug 2051974] Re: Mounting Redmi 7A not sucessfull

2024-02-01 Thread Maksymilian Nowak

** Description changed:

  Phone name is displayed properly. After click turning circle icons appears.
  info appears: cannot open device MTP "001,026"
  
  Mounting via Nautilus works on Debian and it doesn't work on Ubuntu
+ Mounting Samsung-Android works as intended.
  Please hint me what info should I provide.
  Ubuntu 22.04.3 LTS
  
- sudo mtp-detect 
+ sudo mtp-detect
  libmtp version: 1.1.19
  Listing raw device(s)
  Device 0 (VID=2717 and PID=ff48) is a Xiaomi Mi-2s (MTP).
-Found 1 device(s):
-Xiaomi: Mi-2s (MTP) (2717:ff48) @ bus 1, dev 26
+    Found 1 device(s):
+    Xiaomi: Mi-2s (MTP) (2717:ff48) @ bus 1, dev 26
  Attempting to connect device(s)
  PTP_ERROR_IO: failed to open session, trying again after resetting USB 
interface
  LIBMTP libusb: Attempt to reset device
  LIBMTP PANIC: failed to open session on second attempt
  Unable to open raw device 0
  OK.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 19:20:43 2024
  HotplugNewDevices:
-  
+ 
  HotplugNewMounts:
-  
+ 
  InstallationDate: Installed on 2023-06-19 (227 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no username)
-  XDG_RUNTIME_DIR=
-  LANG=pl_PL.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no username)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  Symptom: storage
  UdisksMonitorLog:
-  Monitoring the udisks daemon. Press Ctrl+C to exit.
-  19:21:20.233: The udisks-daemon is running (name-owner :1.12).
+  Monitoring the udisks daemon. Press Ctrl+C to exit.
+  19:21:20.233: The udisks-daemon is running (name-owner :1.12).
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Mounting Redmi 7A not sucessfull

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

Bug description:
  Phone name is displayed properly. After click turning circle icons appears.
  info appears: cannot open device MTP "001,026"

  Mounting via Nautilus works on Debian and it doesn't work on Ubuntu
  Mounting Samsung-Android works as intended.
  Please hint me what info should I provide.
  Ubuntu 22.04.3 LTS

  sudo mtp-detect
  libmtp version: 1.1.19
  Listing raw device(s)
  Device 0 (VID=2717 and PID=ff48) is a Xiaomi Mi-2s (MTP).
     Found 1 device(s):
     Xiaomi: Mi-2s (MTP) (2717:ff48) @ bus 1, dev 26
  Attempting to connect device(s)
  PTP_ERROR_IO: failed to open session, trying again after resetting USB 
interface
  LIBMTP libusb: Attempt to reset device
  LIBMTP PANIC: failed to open session on second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 19:20:43 2024
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2023-06-19 (227 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   19:21:20.233: The udisks-daemon is running (name-owner :1.12).
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2051720] Re: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

2024-02-01 Thread Rio

I can confirm this issue exists on both Ubuntu 22.04.3 and 24.04.beta
(2024-01-25) with Linux 6.5x.

Both the Logitech (Bluetooth) M535 mouse and Microsoft Surface (Pro 7)
Type Cover were problematic with Linux 6.5x to the point where they were
unusable (timeouts or non-responsive for the mouse and boot-up or non-
responsive Type Cover).

The only solution I found was to re-image with Ubuntu 22.04 (offline),
place a hold on the installed Linux 6.2x, then connect to internet to
complete the installation and updating process. The Linux hold prevents
the updating to the 6.5x kernel.

If Linux 6.5x got installed (usually as a choice to have internet
connected during the OS installation which followed with an
update/upgrade), it had to be removed and replaced by Linux 6.2x to
resolve the Bluetooth issues with the mouse and Type Cover.

Bluetooth failed to perform properly on Ubuntu 24.04 or 22.04 with Linux
6.5.0-14-generic.

Bluetooth performs properly under the following conditions:
Ubuntu 22.04.3, Linux 6.2.0-26-generic (hold), gnome-bluetooth 3.34.5-8, bluez 
5.64

lsusb - Bus 003 includes three devices:
Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover
Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth (Logitech M535 mouse)
Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I don't have any additional specifics for the Linux 6.5x builds of
Ubuntu 22.04 and 24.04 other than I was unable to get the Bluetooth
mouse and Type Cover to work properly. I went through several builds of
both Ubuntu versions and the only one that worked properly was the one I
detailed above.

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

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

Bug description:
  ```
  kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  ```

  This issue started with kernel 6.5. Bluetooth has been broken ever
  since. The issue was not present in earlier versions of the kernel.

  ```
  $ uname -a

  Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth

  Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  ```

  ```
  $ journalctl -b | egrep -i bluetooth

  Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
  Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
  Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
  ```

  ```
  linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
  ```

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


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

[Kernel-packages] [Bug 2051975] Re: Graphics Crashes Frequently Making Machine Unusable

2024-02-01 Thread Brett Holman

** Description changed:

  The issue is very reproducible. It happened within a minute or two of
  using my machine after updating from Lunar to Mantic. I tried upgrading
  to Noble to see if a newer kernel might have the fix - it didn't. My
  machine is unusable and I'm happy to repro if anyone has the fix
  
  Sometimes (such as in the case of the logs grabbed from this report),
  the GPU is able to reset and I just have to restart my Gnome session and
  log back in. Far more frequently, however, reset fails and I have to
  hard reboot. In all cases I can ssh into my system to debug.
  
  The crash symptoms start with a sudden freeze of the desktop environment
  for a few seconds, followed by the screen becoming pixelated and multi-
  colored (typical gpu crash in my experience).
+ 
+ Crashes typically happen when under load (firefox open, switching
+ applications) and are less likely to happen when I'm only using gnome-
+ terminal.
  
  My system has a Vega 56 GPU using the amdgpu driver and has 3 actively
  used monitors.
  
  [Thu Feb  1 11:22:17 2024] [drm:do_aquire_global_lock.isra.0 [amdgpu]] 
*ERROR* [CRTC:75:crtc-2] hw_done or flip_done timed out
  [Thu Feb  1 11:22:17 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
gfx_high timeout, signaled seq=175374, emitted seq=175375
  [Thu Feb  1 11:22:17 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process gnome-shell pid 8117 thread gnome-shel:cs0 pid 8149
  [Thu Feb  1 11:22:17 2024] amdgpu :1f:00.0: amdgpu: GPU reset begin!
  [Thu Feb  1 11:22:18 2024] [drm] psp gfx command UNLOAD_TA(0x2) failed and 
response status is (0x117)
  [Thu Feb  1 11:22:18 2024] amdgpu :1f:00.0: amdgpu: BACO reset
  [Thu Feb  1 11:22:18 2024] amdgpu :1f:00.0: amdgpu: GPU reset succeeded, 
trying to resume
  [Thu Feb  1 11:22:18 2024] [drm] PCIE GART of 512M enabled.
  [Thu Feb  1 11:22:18 2024] [drm] PTB located at 0x00F4
  [Thu Feb  1 11:22:18 2024] [drm] VRAM is lost due to GPU reset!
  [Thu Feb  1 11:22:18 2024] [drm] PSP is resuming...
  [Thu Feb  1 11:22:19 2024] [drm] reserve 0x40 from 0xf5fec0 for PSP 
TMR
  [Thu Feb  1 11:22:19 2024] [drm] kiq ring mec 2 pipe 1 q 0
  [Thu Feb  1 11:22:19 2024] [drm] UVD and UVD ENC initialized successfully.
  [Thu Feb  1 11:22:19 2024] [drm] VCE initialized successfully.
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring gfx uses VM inv 
eng 0 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring gfx_low uses VM 
inv eng 1 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring gfx_high uses VM 
inv eng 4 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.0.0 uses 
VM inv eng 5 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.1.0 uses 
VM inv eng 6 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.2.0 uses 
VM inv eng 7 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.3.0 uses 
VM inv eng 8 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.0.1 uses 
VM inv eng 9 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.1.1 uses 
VM inv eng 10 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.2.1 uses 
VM inv eng 11 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.3.1 uses 
VM inv eng 12 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring kiq_0.2.1.0 uses 
VM inv eng 13 on hub 0
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring sdma0 uses VM 
inv eng 0 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring page0 uses VM 
inv eng 1 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring sdma1 uses VM 
inv eng 4 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring page1 uses VM 
inv eng 5 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring uvd_0 uses VM 
inv eng 6 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring uvd_enc_0.0 uses 
VM inv eng 7 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring uvd_enc_0.1 uses 
VM inv eng 8 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring vce0 uses VM inv 
eng 9 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring vce1 uses VM inv 
eng 10 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring vce2 uses VM inv 
eng 11 on hub 8
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: recover vram bo from 
shadow start
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: recover vram bo from 
shadow done
  [Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: GPU reset(2) 
succeeded!
  [Thu Feb  1 11:22:19 2024] [drm] Skip scheduling IBs!
- 
  
  Also worth noting is that the system has lots of UBSAN array-index-out-
  of-bounds warnings, though I believe that

[Kernel-packages] [Bug 2051975] [NEW] Graphics Crashes Frequently Making Machine Unusable

2024-02-01 Thread Brett Holman

Public bug reported:

The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone has the fix

Sometimes (such as in the case of the logs grabbed from this report),
the GPU is able to reset and I just have to restart my Gnome session and
log back in. Far more frequently, however, reset fails and I have to
hard reboot. In all cases I can ssh into my system to debug.

The crash symptoms start with a sudden freeze of the desktop environment
for a few seconds, followed by the screen becoming pixelated and multi-
colored (typical gpu crash in my experience).

My system has a Vega 56 GPU using the amdgpu driver and has 3 actively
used monitors.

[Thu Feb  1 11:22:17 2024] [drm:do_aquire_global_lock.isra.0 [amdgpu]] *ERROR* 
[CRTC:75:crtc-2] hw_done or flip_done timed out
[Thu Feb  1 11:22:17 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
gfx_high timeout, signaled seq=175374, emitted seq=175375
[Thu Feb  1 11:22:17 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process gnome-shell pid 8117 thread gnome-shel:cs0 pid 8149
[Thu Feb  1 11:22:17 2024] amdgpu :1f:00.0: amdgpu: GPU reset begin!
[Thu Feb  1 11:22:18 2024] [drm] psp gfx command UNLOAD_TA(0x2) failed and 
response status is (0x117)
[Thu Feb  1 11:22:18 2024] amdgpu :1f:00.0: amdgpu: BACO reset
[Thu Feb  1 11:22:18 2024] amdgpu :1f:00.0: amdgpu: GPU reset succeeded, 
trying to resume
[Thu Feb  1 11:22:18 2024] [drm] PCIE GART of 512M enabled.
[Thu Feb  1 11:22:18 2024] [drm] PTB located at 0x00F4
[Thu Feb  1 11:22:18 2024] [drm] VRAM is lost due to GPU reset!
[Thu Feb  1 11:22:18 2024] [drm] PSP is resuming...
[Thu Feb  1 11:22:19 2024] [drm] reserve 0x40 from 0xf5fec0 for PSP TMR
[Thu Feb  1 11:22:19 2024] [drm] kiq ring mec 2 pipe 1 q 0
[Thu Feb  1 11:22:19 2024] [drm] UVD and UVD ENC initialized successfully.
[Thu Feb  1 11:22:19 2024] [drm] VCE initialized successfully.
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring gfx uses VM inv 
eng 0 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring gfx_low uses VM 
inv eng 1 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring gfx_high uses VM 
inv eng 4 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.0.0 uses VM 
inv eng 5 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.1.0 uses VM 
inv eng 6 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.2.0 uses VM 
inv eng 7 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.3.0 uses VM 
inv eng 8 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.0.1 uses VM 
inv eng 9 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.1.1 uses VM 
inv eng 10 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.2.1 uses VM 
inv eng 11 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring comp_1.3.1 uses VM 
inv eng 12 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring kiq_0.2.1.0 uses 
VM inv eng 13 on hub 0
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring sdma0 uses VM inv 
eng 0 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring page0 uses VM inv 
eng 1 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring sdma1 uses VM inv 
eng 4 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring page1 uses VM inv 
eng 5 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring uvd_0 uses VM inv 
eng 6 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring uvd_enc_0.0 uses 
VM inv eng 7 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring uvd_enc_0.1 uses 
VM inv eng 8 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring vce0 uses VM inv 
eng 9 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring vce1 uses VM inv 
eng 10 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: ring vce2 uses VM inv 
eng 11 on hub 8
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: recover vram bo from 
shadow start
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: recover vram bo from 
shadow done
[Thu Feb  1 11:22:19 2024] amdgpu :1f:00.0: amdgpu: GPU reset(2) succeeded!
[Thu Feb  1 11:22:19 2024] [drm] Skip scheduling IBs!


Also worth noting is that the system has lots of UBSAN array-index-out-
of-bounds warnings, though I believe that these are probably harmless:

[Wed Jan 31 09:47:40 2024] 
===
=
[Wed Jan 31 09:47:40 2024] UBSAN: array-index-out-of-bounds in 
/build/linux-xR9R4C/linux-6.6.0/drivers/gpu

[Kernel-packages] [Bug 2006557] Re: Enable rdma-sniffer for libpcap

2024-02-01 Thread Athos Ribeiro

** Changed in: libpcap (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Enable rdma-sniffer for libpcap

Status in libpcap package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Invalid
Status in libpcap package in Debian:
  Won't Fix

Bug description:
  Hi,

  The request is to build and configure stock package libpcap with rdma-sniffer 
enabled.
  We'd like users of rdma devices to be able to sniff on them using stock 
tcpdump.
  Currently when using default tcpdump It does not list rdma devices.

  $ tcpdump -D |grep -i rdma
  $ 

  when using locally build tcpdump (with rdma enabled)
  $ cd 
  $ ./tcpdump -D |grep -i rdma
  24.rocep4s0 (RDMA sniffer)
  25.rocep7s0f0 (RDMA sniffer)
  26.rocep7s0f1 (RDMA sniffer)
  27.rocep10s0f0 (RDMA sniffer)
  28.rocep10s0f1 (RDMA sniffer)
  29.rocep33s0f0 (RDMA sniffer)
  30.rocep33s0f1 (RDMA sniffer)
  31.rocep36s0f0 (RDMA sniffer)
  32.ibp36s0f1 (RDMA sniffer)

  Locally build steps:
  clone sources:
  $ mkdir tcpdumpbuild
  $ cd tcpdumpbuild/
  $ git clone https://github.com/the-tcpdump-group/tcpdump.git
  $ git clone https://github.com/the-tcpdump-group/libpcap.git

  install required packages (including rdma packages so libpcap is built with 
rdma enabled):
  $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils
  configure and build
  $ cd libpcap
  $ ./autogen.sh 
  $ ./configure --enable-rdma=yes
  $ make 
  cd ../tcpdump/
  ./autogen.sh 
  ./configure 
  $ make

  now ./tcpdump -D can show rdma devices.

  Thanks !

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


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

[Kernel-packages] [Bug 2051974] [NEW] Mounting Redmi 7A not sucessfull

2024-02-01 Thread Maksymilian Nowak

Public bug reported:

Phone name is displayed properly. After click turning circle icons appears.
info appears: cannot open device MTP "001,026"

Mounting via Nautilus works on Debian and it doesn't work on Ubuntu
Please hint me what info should I provide.
Ubuntu 22.04.3 LTS

sudo mtp-detect 
libmtp version: 1.1.19
Listing raw device(s)
Device 0 (VID=2717 and PID=ff48) is a Xiaomi Mi-2s (MTP).
   Found 1 device(s):
   Xiaomi: Mi-2s (MTP) (2717:ff48) @ bus 1, dev 26
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  1 19:20:43 2024
HotplugNewDevices:
 
HotplugNewMounts:
 
InstallationDate: Installed on 2023-06-19 (227 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.5
Symptom: storage
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 19:21:20.233: The udisks-daemon is running (name-owner :1.12).
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Mounting Redmi 7A not sucessfull

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

Bug description:
  Phone name is displayed properly. After click turning circle icons appears.
  info appears: cannot open device MTP "001,026"

  Mounting via Nautilus works on Debian and it doesn't work on Ubuntu
  Please hint me what info should I provide.
  Ubuntu 22.04.3 LTS

  sudo mtp-detect 
  libmtp version: 1.1.19
  Listing raw device(s)
  Device 0 (VID=2717 and PID=ff48) is a Xiaomi Mi-2s (MTP).
 Found 1 device(s):
 Xiaomi: Mi-2s (MTP) (2717:ff48) @ bus 1, dev 26
  Attempting to connect device(s)
  PTP_ERROR_IO: failed to open session, trying again after resetting USB 
interface
  LIBMTP libusb: Attempt to reset device
  LIBMTP PANIC: failed to open session on second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-15-generic 6.5.0-15.15~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 19:20:43 2024
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2023-06-19 (227 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   19:21:20.233: The udisks-daemon is running (name-owner :1.12).
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

** Description changed:

  [ Impact ]
  
   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables to
  possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.
  
   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).
  
-  * In the absence of the upgrade a cherry-pick will address this
+  * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues w.r.t.
  Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as this
  popular issue.
  
  [ Test Plan ]
  
   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and
  confirm if that issue is resolved or not. Do not run on production ZFS
  pools / systems.
  
   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )
  
   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
  
   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)
  
   * zsys integration test pass (upgrade of zsys installed systems for all
  releases)
  
   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)
  
   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)
  
  [ Where problems could occur ]
  
   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)
  
   * Uncertain of the perfomance impact of the extra checks in dnat patch
  fix itself. Possibly affecting speed of operation, at the benefit of
  correctness.
  
+  * The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
+only makes it stronger and not weaker, thus if it were incorrect, likely
+only performance would be impacted (and it is unlikely to be incorrect
+given upstream reviews and attention to data corruption issues; also,
+there are no additional changes to that function upstream)
+ 
  [ Other Info ]
  
   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  In Progress
Status in zfs-linux source package in Jammy:
  In Progress
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

Hey Chris,

> ... the primary way that users get zfs in Ubuntu is via the module built with 
> the *kernel* image. 
> ... fixing that requires a zfs-linux upload and then a further kernel upload 
> to pull in the new zfs.

Yes, fixing the zfs modules shipped with the kernel packages require
uploads for zfs-linux and kernel packages.

Additionally, users can build zfs modules locally with the zfs-dkms
package (from zfs-linux; similarly to the kernel package build).

This may be useful after the new zfs-linux is available but before a new
kernel package (based on it) is avaiable.

Hope this helps!

For reference,

$ lxc launch ubuntu:mantic --vm -c limits.cpu=2 -c limits.memory=2GiB -c 
security.secureboot=false mantic-vm-zfs
$ lxc shell mantic-vm-zfs

# modinfo zfs | head -n2
filename:   /lib/modules/6.5.0-15-generic/kernel/zfs/zfs.ko.zst
version:2.2.0-0ubuntu1~23.10

# dpkg -l | grep zfs
#

# apt-cache show zfs-dkms | grep -m1 Source:
Source: zfs-linux

# apt update && apt install --yes zfs-dkms
...
Setting up zfs-dkms (2.2.0-0ubuntu1~23.10.1) ...
Loading new zfs-2.2.0 DKMS files...
Building for 6.5.0-15-generic
Building initial module for 6.5.0-15-generic
Done.
...

# modinfo zfs | head -n2
filename:   /lib/modules/6.5.0-15-generic/updates/dkms/zfs.ko.zst
version:2.2.0-0ubuntu1~23.10.1

# modprobe zfs

# cat /sys/module/zfs/version
2.2.0-0ubuntu1~23.10.1

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  In Progress
Status in zfs-linux source package in Jammy:
  In Progress
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

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


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

[Kernel-packages] [Bug 2051942] Re: autopkgtest fails: EE Missing modules

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

** No longer affects: linux-nvidia-tegra (Ubuntu)

** No longer affects: linux-nvidia-tegra (Ubuntu Jammy)

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

Title:
  autopkgtest fails: EE Missing modules

Status in linux-nvidia-tegra-igx package in Ubuntu:
  New
Status in linux-nvidia-tegra-igx source package in Jammy:
  New

Bug description:
  From
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  jammy/jammy/arm64/l/linux-nvidia-tegra-
  igx/20240121_072109_094a7@/log.gz :

  6243s dpkg-deb: building package 'linux-nvidia-tegra-igx-tools-5.15.0-1007' 
in '../linux-nvidia-tegra-igx-tools-5.15.0-1007_5.15.0-1007.7_arm64.deb'.
  6253s Debug: module-check-nvidia-tegra-igx
  6253s debian/scripts/module-check "nvidia-tegra-igx" \
  6253s 
"/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/abi/arm64" 
"/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/__abi.current/arm64"
 
  6254s II: Checking modules for nvidia-tegra-igx...
  6254s read 11 modules.
  6254sreading new modules...read 7343 modules.
  6254sreading old modules...
  6254s   MISS: ar1335_common
  6254s   MISS: arm64-ras
  6254s   MISS: bluedroid_pm
  6254s   MISS: bmi088
  6254s   MISS: cam_cdi_tsc
  [...]
  6254s   MISS: tegracam_log
  6254s   MISS: ti_fpdlink_dp_serializer
  6254s   MISS: tsecriscv
  6254s   MISS: ufs-tegra
  6254s   MISS: ufs-tegra-provision
  6254s   MISS: userspace_ivc_mempool
  6254s   MISS: virtual_i2c_mux
  6254s   MISS: watchdog-tegra-t18x
  6254s   MISS: wch
  6254s   NEW: pps-ktimer
  6254s   read 7498 modules : new(1)  missing(154)
  6254s EE: Missing modules
  6254s make: *** [debian/rules.d/4-checks.mk:10: 
module-check-nvidia-tegra-igx] Error 1
  6254s dpkg-buildpackage: error: fakeroot debian/rules binary subprocess 
returned exit status 2
  6254s autopkgtest [07:05:29]: test rebuild: ---]
  6259s autopkgtest [07:05:34]: test rebuild:  - - - - - - - - - - results - - 
- - - - - - - -
  6259s rebuild  FAIL non-zero exit status 2

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


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

[Kernel-packages] [Bug 2051960] [NEW] Provide a raspi-realtime kernel

Public bug reported:

Provide raspi-realtime kernel package/flavor (arm64 only) for Pi 4 and
5.

** Affects: flash-kernel (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: flash-kernel (Ubuntu Noble)
 Importance: Undecided
 Status: New

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


** Tags: kern-9083

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

** Tags added: kern-9083

** Also affects: flash-kernel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Provide a raspi-realtime kernel

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

Bug description:
  Provide raspi-realtime kernel package/flavor (arm64 only) for Pi 4 and
  5.

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


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

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

** Description changed:

- Noble and newer doesn't support armhf for Pi anymore.
+ Noble and newer doesn't support armhf for Pi anymore. As a result of
+ that, the raspi-nolpae package/flavor will disappear since that is armhf
+ only.

** Tags added: kern-9084

** Description changed:

- Noble and newer doesn't support armhf for Pi anymore. As a result of
- that, the raspi-nolpae package/flavor will disappear since that is armhf
- only.
+ Noble and newer don't support armhf for Pi anymore.

** Also affects: flash-kernel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove armhf support

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

Bug description:
  Noble and newer don't support armhf for Pi anymore.

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


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

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

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

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  In Progress
Status in zfs-linux source package in Jammy:
  In Progress
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

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


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

[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

2024-02-01 Thread Andrew Reis

Any update on this?

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6

[Kernel-packages] [Bug 2006557] Re: Enable rdma-sniffer for libpcap

2024-02-01 Thread Athos Ribeiro

** Tags removed: server-triage-discuss

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

Title:
  Enable rdma-sniffer for libpcap

Status in libpcap package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Invalid
Status in libpcap package in Debian:
  Won't Fix

Bug description:
  Hi,

  The request is to build and configure stock package libpcap with rdma-sniffer 
enabled.
  We'd like users of rdma devices to be able to sniff on them using stock 
tcpdump.
  Currently when using default tcpdump It does not list rdma devices.

  $ tcpdump -D |grep -i rdma
  $ 

  when using locally build tcpdump (with rdma enabled)
  $ cd 
  $ ./tcpdump -D |grep -i rdma
  24.rocep4s0 (RDMA sniffer)
  25.rocep7s0f0 (RDMA sniffer)
  26.rocep7s0f1 (RDMA sniffer)
  27.rocep10s0f0 (RDMA sniffer)
  28.rocep10s0f1 (RDMA sniffer)
  29.rocep33s0f0 (RDMA sniffer)
  30.rocep33s0f1 (RDMA sniffer)
  31.rocep36s0f0 (RDMA sniffer)
  32.ibp36s0f1 (RDMA sniffer)

  Locally build steps:
  clone sources:
  $ mkdir tcpdumpbuild
  $ cd tcpdumpbuild/
  $ git clone https://github.com/the-tcpdump-group/tcpdump.git
  $ git clone https://github.com/the-tcpdump-group/libpcap.git

  install required packages (including rdma packages so libpcap is built with 
rdma enabled):
  $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils
  configure and build
  $ cd libpcap
  $ ./autogen.sh 
  $ ./configure --enable-rdma=yes
  $ make 
  cd ../tcpdump/
  ./autogen.sh 
  ./configure 
  $ make

  now ./tcpdump -D can show rdma devices.

  Thanks !

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


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

[Kernel-packages] [Bug 2042363] Re: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 ser

2024-02-01 Thread Frank Heimes

I did a screening of the traces, but couldn't really find suspicious entries.
I'm now looking for a someone else's view and opinion...

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

Title:
  AIX 7.3 NFS client frequently returns an EIO error to an application
  when reading or writing to a file that has been locked with fcntl() on
  a Ubuntu 20.04 NFSV4 server

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl(). NFS server is 
Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not 
appear to affect other combinations of NFS client (including AIX 7.2) with this 
NFS server.

  The AIX team have indicated that the cause of the EIO is triggered by the NFS 
server returning a BAD_SEQID error which leads to the AIX NFS client 
incorrectly zeroing the stateid, which then leads to the NFS server returning a 
BAD_STATEID error and the NFS client then returns the EIO error. The AIX team 
would like to understand why the BAD_SEQID has been returned.
   
  ---uname output---
  Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
   
  Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 
2.30GHz  

  ---Steps to Reproduce---
   We cannot offer a simple way to recreate the problem as it involves IBM MQ 
running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 
storage.

  However, we can provide any requested trace or dumps from any or all
  of the involved machines.

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


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

[Kernel-packages] [Bug 2051953] [NEW] package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to install/upgrade: le sous-processus paquet linux-headers-6.6.0-14-generic script post-installation ins

2024-02-01 Thread RENAUD

Public bug reported:

i try to restore my grub

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  allan2 2792 F wireplumber
 /dev/snd/controlC0:  allan2 2792 F wireplumber
 /dev/snd/seq:allan2 2788 F pipewire
CasperMD5CheckResult: unknown
Date: Thu Feb  1 17:03:59 2024
ErrorMessage: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
InstallationDate: Installed on 2023-08-04 (181 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic 
root=UUID=57f5a567-b182-49a7-95fc-5618da43a67e ro i8042.nopnp=1 pci=nocrs quiet
Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 
3.11.4-5ubuntu1
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.12~rc1-12ubuntu4
SourcePackage: linux
Title: package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to 
install/upgrade: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2018
dmi.bios.release: 2.51
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET97WW (2.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AN0079MZ
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.12
dmi.modalias: 
dmi:bvnLENOVO:bvrGLET97WW(2.51):bd09/27/2018:br2.51:efr1.12:svnLENOVO:pn20AN0079MZ:pvrThinkPadT440p:rvnLENOVO:rn20AN0079MZ:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AN_BU_Think_FM_ThinkPadT440p:
dmi.product.family: ThinkPad T440p
dmi.product.name: 20AN0079MZ
dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package noble

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

Title:
  package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to
  install/upgrade: le sous-processus paquet linux-
  headers-6.6.0-14-generic script post-installation installé a renvoyé
  un état de sortie d'erreur 1

Status in linux package in Ubuntu:
  New

Bug description:
  i try to restore my grub

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  allan2 2792 F wireplumber
   /dev/snd/controlC0:  allan2 2792 F wireplumber
   /dev/snd/seq:allan2 2788 F pipewire
  CasperMD5CheckResult: unknown
  Date: Thu Feb  1 17:03:59 2024
  ErrorMessage: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
  InstallationDate: Installed on 2023-08-04 (181 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic 
root=UUID=57f5a567-b182-49a7-95fc-5618da43a67e ro i8042.nopnp=1 pci=nocrs quiet
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 
3.11.4-5ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12~rc1-12ubuntu4
  SourcePackage: linux
  Title: package linux-headers-6.6.0-14-generic 6.6.0-14.14 failed to 
install/upgrade: le sous-processus paquet linux-headers-6.6.0-14-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2018
  dmi.bios.release: 2.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET97WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN0079MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.12
  dmi.modalias:

[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel

2024-02-01 Thread Andrea Righi

@andysem yes that is also another possibility. The idea is to do a lot
of tests and if we find that there's a remote possibility to introduce
significant performance regressions in certain cases we can still keep
HZ=250, but definitely go with the other options.

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

Title:
  Enable lowlatency settings in the generic kernel

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

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, more performant and more power
  efficient (therefore more "generic"), simply by tuning run-time and
  boot-time options.

  Moreover, once these changes are applied we will be able to deprecate
  the lowlatency kernel, saving engineering time and also reducing power
  consumption (required to build the kernel and do all the testing).

  Optionally, we can also provide optimal "lowlatency"

[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel

2024-02-01 Thread Lastique

@arighi: Did you consider applying lowlatency settings to generic kernel
but keeping CONFIG_HZ=250?

I suspect, the majority of desktop usage issues (i.e. responsiveness)
would be solved by `preempt=full rcu_nocbs=all` being the default (or
whatever the equivalent boot options are). While keeping CONFIG_HZ=250
would mitigate the potential throughput loss.

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

Title:
  Enable lowlatency settings in the generic kernel

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

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, more performant and more power
  efficient (therefore more "generic"), simply by tuning run-time and
  boot-time options.

  Moreover, once these changes are applied we will be able to deprecate
  the lowlatency kernel, saving engineering time and also reducing power
  consumption (required to build the

[Kernel-packages] [Bug 2033416] Re: [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y

2024-02-01 Thread Jeff Lane 

** Summary changed:

- change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
+ [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: Confirmed

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

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

** Description changed:

- Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro
- kernels.
+ [Impact]
+ Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels.
  
  However, unlike plug and play devices, there is no way to load uncore module 
when user tries to use uncore event.
  Also, a primary motivation to add module support in uncore driver was to ease 
development (https://git.kernel.org/torvalds/c/05485745ad482).
  
- So, ask ubuntu to switch to CONFIG_PERF_EVENTS_AMD_UNCORE=y.
+ Its not immediately apparent from perf tool output that the "amd-uncore"
+ module is not loaded when opening "amd_df" or "amd_l3" events fail or
+ when they do not show up in "perf list" despite using a compatible
+ kernel. Since the primary motivation of the commit [1] that made it
+ possible for this to be loaded as a module was to make development
+ easier, CONFIG_PERF_EVENTS_AMD_UNCORE defaults to 'y' [2].
+ 
+ [1] https://git.kernel.org/torvalds/c/05485745ad482
+ [2] https://github.com/torvalds/linux/blob/master/arch/x86/events/Kconfig#L40
+ 
+ [Fix]
+ 
+ Change kernel config to CONFIG_PERF_EVENTS_AMD_UNCORE=y
+ 
+ [Test case]
+ 
+ (How can this change be tested/verified?)
+ 
+ [Where problems may occur]
+ 
+ (What side effects or regressions could this change create?)

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

Title:
  [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y

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

Bug description:
  [Impact]
  Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels.

  However, unlike plug and play devices, there is no way to load uncore module 
when user tries to use uncore event.
  Also, a primary motivation to add module support in uncore driver was to ease 
development (https://git.kernel.org/torvalds/c/05485745ad482).

  Its not immediately apparent from perf tool output that the "amd-
  uncore" module is not loaded when opening "amd_df" or "amd_l3" events
  fail or when they do not show up in "perf list" despite using a
  compatible kernel. Since the primary motivation of the commit [1] that
  made it possible for this to be loaded as a module was to make
  development easier, CONFIG_PERF_EVENTS_AMD_UNCORE defaults to 'y' [2].

  [1] https://git.kernel.org/torvalds/c/05485745ad482
  [2] https://github.com/torvalds/linux/blob/master/arch/x86/events/Kconfig#L40

  [Fix]

  Change kernel config to CONFIG_PERF_EVENTS_AMD_UNCORE=y

  [Test case]

  (How can this change be tested/verified?)

  [Where problems may occur]

  (What side effects or regressions could this change create?)

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


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

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

** Description changed:

  [Impact]
  When plugin the headset jack, only speaker is identified.
  
  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  
  [Test]
  Vendor tested on hardware, headset mic works fine.
  
  [Where problems could occur]
  It may break audio.
- 
- X-HWE-Bug: Bug #2051947

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

Title:
  Sound: Add rtl quirk of M90-Gen5

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

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

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

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

  [Where problems could occur]
  It may break audio.

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


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

[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5

** Tags removed: originate-from-2046105
** Tags added: originate-from-2049464

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

Title:
  Sound: Add rtl quirk of M70-Gen5

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid

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

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

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

  [Where problems could occur]
  It may break audio.

  This commit is merged by stable updates in noble kernel,
  5.15 doesn't support this platform,
  SRU for mantic and oem-6.5.

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


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

[Kernel-packages] [Bug 2046184] Re: [arm64] Increase max CPU count to 512

2024-02-01 Thread John Cabaj

** Changed in: linux-oracle (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  [arm64] Increase max CPU count to 512

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

Bug description:
  [Impact]

  * Request to accommodate new shape with 320 CPUs, greater than current
  max value of 256.

  [Fix]

  * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch.

  [Test Case]

  * Compile tested
  * Boot tested

  [Where things could go wrong]

  * Low chance of regression. Simple config change.

  [Other Info]

  * Change proposed in Debian unstable 
(https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1),
 but was denied due to additional kernel size. This shouldn't affect Ubuntu 
kernel so much as it's compressed.
  * SF #00375112

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


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

[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5

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

** Description changed:

  [Impact]
  When plugin the headset jack, only speaker is identified.
  
  [Fix]
  Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work.
  
  [Test]
  Vendor tested on hardware, headset mic works fine.
  
  [Where problems could occur]
  It may break audio.
+ 
+ This commit is merged by stable updates in noble kernel,
+ 5.15 doesn't support this platform,
+ SRU for mantic and 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/2051947

Title:
  Sound: Add rtl quirk of M70-Gen5

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid

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

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

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

  [Where problems could occur]
  It may break audio.

  This commit is merged by stable updates in noble kernel,
  5.15 doesn't support this platform,
  SRU for mantic and oem-6.5.

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


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

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

** Description changed:

  [Impact]
  When plugin the headset jack, only speaker is identified.
  
  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  
  [Test]
  Vendor tested on hardware, headset mic works fine.
  
  [Where problems could occur]
  It may break audio.
+ 
+ X-HWE-Bug: Bug #2051947

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

Title:
  Sound: Add rtl quirk of M90-Gen5

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

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

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

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

  [Where problems could occur]
  It may break audio.

  X-HWE-Bug: Bug #2051947

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


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

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

2024-02-01 Thread Andreas Hasenack

Thanks @vicamo, but what we want to ensure is much simpler than that
whole release process.

We just want to be sure that the firmware-sof from proposed, and the
updated kernel from proposed (and updates, i.e., currently available
outside proposed) were tested together according to the test plan.

In other words:

> Please confirm that you have completed SRU verification using the Test Plan 
> and using packages only
> from the main archive (including packages from -proposed as appropriate) and 
> from no other sources.
> Please detail the specific combinations of kernel and firmware-sof tested.

No PPAs must be involved at this stage, since everything is in proposed.

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

-- 
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 Committed
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 Committed
Status in linux source package in Mantic:
  Fix Committed
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 2051947] [NEW] Sound: Add rtl quirk of M70-Gen5

Public bug reported:

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

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

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

[Where problems could occur]
It may break audio.

** Affects: hwe-next
 Importance: High
 Assignee: AaronMa (mapengyu)
 Status: New

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

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

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

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

** Affects: linux (Ubuntu Mantic)
 Importance: High
 Status: New

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


** Tags: hwe-next oem-priority originate-from-2046105

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

** Tags added: hwe-next oem-priority originate-from-2046105

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

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

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

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

** Changed in: hwe-next
   Importance: Undecided => High

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

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

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

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

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

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

** Changed in: hwe-next
 Assignee: (unassigned) => AaronMa (mapengyu)

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

Title:
  Sound: Add rtl quirk of M70-Gen5

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid

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

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

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

  [Where problems could occur]
  It may break audio.

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


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

[Kernel-packages] [Bug 2051672] Re: Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable (main)

2024-02-01 Thread Jeremy Bícha

** Summary changed:

- Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable 
(main)
+ Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable 
(main)

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

Title:
  Merge iproute2 with the latest Debian version: 6.7.0-2 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  New

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable; urgency=medium

    * Drop obsolete conflicts/replaces
    * Update upstream source from tag 'upstream/6.3.0'

   -- Luca Boccassi <>  Tue, 13 Jun 2023 23:49:37 +0100

  iproute2 (6.1.0-3) unstable; urgency=medium

    * Ensure 'ip mo' resolves to 'ip monitor' (Closes: #1036534)

   -- Luca Boccassi <>  Mon, 22 May 2023 14:19:52 +0100

  iproute2 (6.1.0-2) unstable; urgency=medium

    * Add Romanian language translation for debconf (Closes: #1031917)
    * Bump Standards-Version to 4.6.2, no changes
    * Bump d/copyright year range

   -- Luca Boccassi <>  Sat, 25 Feb 2023

[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot

** Description changed:

- Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
- /etc/kernel/postinst.d/dkms:
-  * dkms: running auto installation service for kernel 5.15.0-1040-nvidia
-...done.
- /etc/kernel/postinst.d/initramfs-tools:
- update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia
- cryptsetup: WARNING: Couldn't determine root device
- W: Couldn't identify type of root file system for fsck hook
- cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory
- /etc/kernel/postinst.d/kdump-tools:
- kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia
- mkinitramfs: failed to determine device for /
- mkinitramfs: workaround is MODULES=most, check:
- grep -r MODULES /var/lib/kdump/initramfs-tools
+ [Impact]
+ When installing in a chroot environment, the kdump-tools kernel hook will 
fail. This breaks certain OS image creation tools, such as BCM (which I assume 
is NVIDIA Base Command Manager from context). While BCM's image generation tool 
requires some additional tweaks to consume this, the proposed fix is necessary, 
and should be sufficient for other tools that use chroots.
  
- Error please report bug on initramfs-tools
- Include the output of 'mount' and 'cat /proc/mounts'
- update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia 
with 1.
- run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
- dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure):
-  installed linux-image-5.15.0-1040-nvidia package post-installation script 
subprocess returned error exit status 1
- Errors were encountered while processing:
-  linux-image-5.15.0-1040-nvidia
- E: Sub-process /usr/bin/dpkg returned an error code (1)
+ [Test Plan]
+ 1) debootstrap a chroot environment for the target Ubuntu release
+ 2) Install kdump-tools within that environment
+ 3) Install a kernel package and make sure it succeeds.
+ 4) do the same steps in a virtual machine, but with `ischroot` symlinked to 
/dev/true at install time. This should simulate a system that was just 
installed with an image prepared as above.
+ 5) Then restore ischroot, and reboot.
+ 6) Confirm the systemd service does generate an initramfs at boot, and
+ 7) that a crash dump can be triggered afterwords.
+ 
+ [Where Problems Could Occur]
+ The solution we implemented in noble was simply to detect a chroot 
environment with ischroot, and disable initramfs generation. The systemd 
service will detect that an initrd is missing, and generate one on first boot. 
A source of potential problems is if that does not happen for some reason, 
resulting in a kdump-tools service failure on first boot.

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

Title:
  Installation errors out when installing in a chroot

Status in kdump-tools package in Ubuntu:
  Fix Released
Status in linux-nvidia package in Ubuntu:
  Invalid
Status in kdump-tools source package in Jammy:
  In Progress
Status in linux-nvidia source package in Jammy:
  Invalid
Status in kdump-tools source package in Mantic:
  In Progress
Status in linux-nvidia source package in Mantic:
  Invalid
Status in kdump-tools source package in Noble:
  Fix Released
Status in linux-nvidia source package in Noble:
  Invalid

Bug description:
  [Impact]
  When installing in a chroot environment, the kdump-tools kernel hook will 
fail. This breaks certain OS image creation tools, such as BCM (which I assume 
is NVIDIA Base Command Manager from context). While BCM's image generation tool 
requires some additional tweaks to consume this, the proposed fix is necessary, 
and should be sufficient for other tools that use chroots.

  [Test Plan]
  1) debootstrap a chroot environment for the target Ubuntu release
  2) Install kdump-tools within that environment
  3) Install a kernel package and make sure it succeeds.
  4) do the same steps in a virtual machine, but with `ischroot` symlinked to 
/dev/true at install time. This should simulate a system that was just 
installed with an image prepared as above.
  5) Then restore ischroot, and reboot.
  6) Confirm the systemd service does generate an initramfs at boot, and
  7) that a crash dump can be triggered afterwords.

  [Where Problems Could Occur]
  The solution we implemented in noble was simply to detect a chroot 
environment with ischroot, and disable initramfs generation. The systemd 
service will detect that an initrd is missing, and generate one on first boot. 
A source of potential problems is if that does not happen for some reason, 
resulting in a kdump-tools service failure on first boot.

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


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

[Kernel-packages] [Bug 2039755] Re: kernel crashes in CIFS code

2024-02-01 Thread Alex Ball

Since upgrading to the 6.5.0 Ubuntu HWE kernel a few weeks ago, I have
not experienced this issue; so it looks like it is specific to the 6.2.0
Ubuntu kernel.

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

Title:
  kernel crashes in CIFS code

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

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:

[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot

** Also affects: linux-nvidia (Ubuntu Noble)
   Importance: Undecided
   Status: Invalid

** Also affects: kdump-tools (Ubuntu Noble)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: Fix Released

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

** Also affects: kdump-tools (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Also affects: kdump-tools (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: kdump-tools (Ubuntu Mantic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: kdump-tools (Ubuntu Jammy)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: kdump-tools (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: kdump-tools (Ubuntu Jammy)
   Status: New => In Progress

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

Title:
  Installation errors out when installing in a chroot

Status in kdump-tools package in Ubuntu:
  Fix Released
Status in linux-nvidia package in Ubuntu:
  Invalid
Status in kdump-tools source package in Jammy:
  In Progress
Status in linux-nvidia source package in Jammy:
  Invalid
Status in kdump-tools source package in Mantic:
  In Progress
Status in linux-nvidia source package in Mantic:
  Invalid
Status in kdump-tools source package in Noble:
  Fix Released
Status in linux-nvidia source package in Noble:
  Invalid

Bug description:
  Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 5.15.0-1040-nvidia
 ...done.
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia
  cryptsetup: WARNING: Couldn't determine root device
  W: Couldn't identify type of root file system for fsck hook
  cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory
  /etc/kernel/postinst.d/kdump-tools:
  kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /var/lib/kdump/initramfs-tools

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia 
with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure):
   installed linux-image-5.15.0-1040-nvidia package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.15.0-1040-nvidia
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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


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

[Kernel-packages] [Bug 2051941] [NEW] autopkgtest fails: EE: Missing modules

Public bug reported:

From
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
jammy/jammy/arm64/l/linux-nvidia-6.5/20240131_012859_fd7ca@/log.gz:

7141s dpkg-deb: building package 'linux-nvidia-6.5-tools-6.5.0-1011' in 
'../linux-nvidia-6.5-tools-6.5.0-1011_6.5.0-1011.11_arm64.deb'.
7150s Debug: module-check-nvidia
7150s debian/scripts/checks/module-check "nvidia" \
7150s   "/tmp/autopkgtest.99vLuG/build.vn7/src/debian.nvidia-6.5/abi/arm64" 
"/tmp/autopkgtest.99vLuG/build.vn7/src/debian.nvidia-6.5/__abi.current/arm64" 
7150s II: Checking modules for nvidia...
7150s Reading modules to ignore...read 11 modules.
7150s Reading new modules...read 8037 modules.
7150s Reading old modules...read 8040 modules.
7150s II: Checking for modules changes...
7150s MISS : mstflint_access
7150s MISS : spl (ignored)
7150s MISS : zfs (ignored)
7150s EE: Missing modules
7150s make: *** [debian/rules.d/4-checks.mk:10: module-check-nvidia] Error 1
7150s dpkg-buildpackage: error: fakeroot debian/rules binary subprocess 
returned exit status 2
7150s autopkgtest [01:14:33]: test rebuild: ---]
7152s rebuild  FAIL non-zero exit status 2

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

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

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

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

Title:
  autopkgtest fails: EE: Missing modules

Status in linux-nvidia-6.5 package in Ubuntu:
  New
Status in linux-nvidia-6.5 source package in Jammy:
  New

Bug description:
  From
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  jammy/jammy/arm64/l/linux-nvidia-6.5/20240131_012859_fd7ca@/log.gz:

  7141s dpkg-deb: building package 'linux-nvidia-6.5-tools-6.5.0-1011' in 
'../linux-nvidia-6.5-tools-6.5.0-1011_6.5.0-1011.11_arm64.deb'.
  7150s Debug: module-check-nvidia
  7150s debian/scripts/checks/module-check "nvidia" \
  7150s 
"/tmp/autopkgtest.99vLuG/build.vn7/src/debian.nvidia-6.5/abi/arm64" 
"/tmp/autopkgtest.99vLuG/build.vn7/src/debian.nvidia-6.5/__abi.current/arm64" 
  7150s II: Checking modules for nvidia...
  7150s Reading modules to ignore...read 11 modules.
  7150s Reading new modules...read 8037 modules.
  7150s Reading old modules...read 8040 modules.
  7150s II: Checking for modules changes...
  7150s MISS : mstflint_access
  7150s MISS : spl (ignored)
  7150s MISS : zfs (ignored)
  7150s EE: Missing modules
  7150s make: *** [debian/rules.d/4-checks.mk:10: module-check-nvidia] Error 1
  7150s dpkg-buildpackage: error: fakeroot debian/rules binary subprocess 
returned exit status 2
  7150s autopkgtest [01:14:33]: test rebuild: ---]
  7152s rebuild  FAIL non-zero exit status 2

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


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

[Kernel-packages] [Bug 2051942] [NEW] autopkgtest fails: EE Missing modules

Public bug reported:

From
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
jammy/jammy/arm64/l/linux-nvidia-tegra-igx/20240121_072109_094a7@/log.gz
:

6243s dpkg-deb: building package 'linux-nvidia-tegra-igx-tools-5.15.0-1007' in 
'../linux-nvidia-tegra-igx-tools-5.15.0-1007_5.15.0-1007.7_arm64.deb'.
6253s Debug: module-check-nvidia-tegra-igx
6253s debian/scripts/module-check "nvidia-tegra-igx" \
6253s   
"/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/abi/arm64" 
"/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/__abi.current/arm64"
 
6254s II: Checking modules for nvidia-tegra-igx...
6254s read 11 modules.
6254sreading new modules...read 7343 modules.
6254sreading old modules...
6254s   MISS: ar1335_common
6254s   MISS: arm64-ras
6254s   MISS: bluedroid_pm
6254s   MISS: bmi088
6254s   MISS: cam_cdi_tsc
[...]
6254s   MISS: tegracam_log
6254s   MISS: ti_fpdlink_dp_serializer
6254s   MISS: tsecriscv
6254s   MISS: ufs-tegra
6254s   MISS: ufs-tegra-provision
6254s   MISS: userspace_ivc_mempool
6254s   MISS: virtual_i2c_mux
6254s   MISS: watchdog-tegra-t18x
6254s   MISS: wch
6254s   NEW: pps-ktimer
6254s   read 7498 modules : new(1)  missing(154)
6254s EE: Missing modules
6254s make: *** [debian/rules.d/4-checks.mk:10: module-check-nvidia-tegra-igx] 
Error 1
6254s dpkg-buildpackage: error: fakeroot debian/rules binary subprocess 
returned exit status 2
6254s autopkgtest [07:05:29]: test rebuild: ---]
6259s autopkgtest [07:05:34]: test rebuild:  - - - - - - - - - - results - - - 
- - - - - - -
6259s rebuild  FAIL non-zero exit status 2

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

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

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

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

Title:
  autopkgtest fails: EE Missing modules

Status in linux-nvidia-tegra package in Ubuntu:
  New
Status in linux-nvidia-tegra source package in Jammy:
  New

Bug description:
  From
  
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
  jammy/jammy/arm64/l/linux-nvidia-tegra-
  igx/20240121_072109_094a7@/log.gz :

  6243s dpkg-deb: building package 'linux-nvidia-tegra-igx-tools-5.15.0-1007' 
in '../linux-nvidia-tegra-igx-tools-5.15.0-1007_5.15.0-1007.7_arm64.deb'.
  6253s Debug: module-check-nvidia-tegra-igx
  6253s debian/scripts/module-check "nvidia-tegra-igx" \
  6253s 
"/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/abi/arm64" 
"/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/__abi.current/arm64"
 
  6254s II: Checking modules for nvidia-tegra-igx...
  6254s read 11 modules.
  6254sreading new modules...read 7343 modules.
  6254sreading old modules...
  6254s   MISS: ar1335_common
  6254s   MISS: arm64-ras
  6254s   MISS: bluedroid_pm
  6254s   MISS: bmi088
  6254s   MISS: cam_cdi_tsc
  [...]
  6254s   MISS: tegracam_log
  6254s   MISS: ti_fpdlink_dp_serializer
  6254s   MISS: tsecriscv
  6254s   MISS: ufs-tegra
  6254s   MISS: ufs-tegra-provision
  6254s   MISS: userspace_ivc_mempool
  6254s   MISS: virtual_i2c_mux
  6254s   MISS: watchdog-tegra-t18x
  6254s   MISS: wch
  6254s   NEW: pps-ktimer
  6254s   read 7498 modules : new(1)  missing(154)
  6254s EE: Missing modules
  6254s make: *** [debian/rules.d/4-checks.mk:10: 
module-check-nvidia-tegra-igx] Error 1
  6254s dpkg-buildpackage: error: fakeroot debian/rules binary subprocess 
returned exit status 2
  6254s autopkgtest [07:05:29]: test rebuild: ---]
  6259s autopkgtest [07:05:34]: test rebuild:  - - - - - - - - - - results - - 
- - - - - - - -
  6259s rebuild  FAIL non-zero exit status 2

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


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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

2024-02-01 Thread Mike Ferreira

Ubfan1 and I have talking about this out on the Forum: Were we have to help 
other Users with this.
RE: https://ubuntuforums.org/showthread.php?t=2494834

I think his idea on something is genius: That if the compiler version is
brought in by the kernel on kernel updates as a dependency, so that the
compiler is of the same version as the Kernel was compiled with...
Noting that it doesn't not have to replace the old compiler, can be
additional, along side it, then this solves this problem.

He just tested this on some fresh 22.04.3 installs and it works.

Sorry, It's hard to grasp that the answer is 
"Not going to fix", 
...when there is a drastic problem that is being caused by the current update 
path, that is causing Users to have non-working installations.

We are just here to report it and to help in any way to resolve it.

If this is not the accepted solution, then lets work together to find
one that is.

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

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  New

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

2024-02-01 Thread Mike Ferreira

** Also 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/2051457

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  New

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049327] Update Released

2024-02-01 Thread Andreas Hasenack

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

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

Title:
  `alsactl init` unable to initialze audio device on G700

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

Bug description:
  [Impact]
  This bug cause "alsactl init" command unable to initialize mt8390-evk 
correctly and print these error message:

  ```
  ceqa@ubuntu:/home/ceqa$ alsactl init
  alsa-lib main.c:761:(execute_sequence) unable to execute cset 
'name='DP_OUT_MUX' Disconnect'
  alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence
  Found hardware: "mt8390-evk" "" "" "" ""
  Hardware is initialized using a generic method
  ```

  Thus, the audio devices on MediaTek G700 do not work.

  This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'.

  [ Test Plan ]
  Reproduce:
  1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device
  2. Run `alsactl init` on MediaTek G700 device
  3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' 
Disconnect'" and audio devices do not work.

  Verify:
  By applying this patch, alsactl does not print this error message and audio 
devices work.

  
  [Where problems could occur]
  This patch fix the typo in ucm files, and it affects the device init process 
on Mediatek Genio boards.

  
  [ Other Info ]
  There is a typo in 
'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'.

  The name of the flag that controls the audio output of the DP port is
  not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'.

  MediaTek fix this issue in the PR in upstream:
  
https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079

  
  mt8390-evk (G700) Pull Request: (Still under review)
  https://github.com/alsa-project/alsa-ucm-conf/pull/321

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


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

[Kernel-packages] [Bug 2049327] Re: `alsactl init` unable to initialze audio device on G700

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.10

---
alsa-ucm-conf (1.2.6.3-1ubuntu1.10) jammy; urgency=medium

  * d/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch
- fix typo to make the patch work on mt8390-evk (lp: #2049327)

 -- Zhaoxuan Zhai   Fri, 12 Jan 2024
16:24:24 +0800

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

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

Title:
  `alsactl init` unable to initialze audio device on G700

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

Bug description:
  [Impact]
  This bug cause "alsactl init" command unable to initialize mt8390-evk 
correctly and print these error message:

  ```
  ceqa@ubuntu:/home/ceqa$ alsactl init
  alsa-lib main.c:761:(execute_sequence) unable to execute cset 
'name='DP_OUT_MUX' Disconnect'
  alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence
  Found hardware: "mt8390-evk" "" "" "" ""
  Hardware is initialized using a generic method
  ```

  Thus, the audio devices on MediaTek G700 do not work.

  This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'.

  [ Test Plan ]
  Reproduce:
  1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device
  2. Run `alsactl init` on MediaTek G700 device
  3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' 
Disconnect'" and audio devices do not work.

  Verify:
  By applying this patch, alsactl does not print this error message and audio 
devices work.

  
  [Where problems could occur]
  This patch fix the typo in ucm files, and it affects the device init process 
on Mediatek Genio boards.

  
  [ Other Info ]
  There is a typo in 
'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'.

  The name of the flag that controls the audio output of the DP port is
  not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'.

  MediaTek fix this issue in the PR in upstream:
  
https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079

  
  mt8390-evk (G700) Pull Request: (Still under review)
  https://github.com/alsa-project/alsa-ucm-conf/pull/321

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


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

[Kernel-packages] [Bug 2049327] Re: `alsactl init` unable to initialze audio device on G700

This bug was fixed in the package alsa-ucm-conf - 1.2.9-1ubuntu3.2

---
alsa-ucm-conf (1.2.9-1ubuntu3.2) mantic; urgency=medium

  * d/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch
- fix typo to make the patch work on mtk8390-evk  (lp: #2049327)

 -- Zhaoxuan Zhai   Fri, 12 Jan 2024
16:26:31 +0800

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

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

Title:
  `alsactl init` unable to initialze audio device on G700

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

Bug description:
  [Impact]
  This bug cause "alsactl init" command unable to initialize mt8390-evk 
correctly and print these error message:

  ```
  ceqa@ubuntu:/home/ceqa$ alsactl init
  alsa-lib main.c:761:(execute_sequence) unable to execute cset 
'name='DP_OUT_MUX' Disconnect'
  alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence
  Found hardware: "mt8390-evk" "" "" "" ""
  Hardware is initialized using a generic method
  ```

  Thus, the audio devices on MediaTek G700 do not work.

  This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'.

  [ Test Plan ]
  Reproduce:
  1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device
  2. Run `alsactl init` on MediaTek G700 device
  3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' 
Disconnect'" and audio devices do not work.

  Verify:
  By applying this patch, alsactl does not print this error message and audio 
devices work.

  
  [Where problems could occur]
  This patch fix the typo in ucm files, and it affects the device init process 
on Mediatek Genio boards.

  
  [ Other Info ]
  There is a typo in 
'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'.

  The name of the flag that controls the audio output of the DP port is
  not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'.

  MediaTek fix this issue in the PR in upstream:
  
https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079

  
  mt8390-evk (G700) Pull Request: (Still under review)
  https://github.com/alsa-project/alsa-ucm-conf/pull/321

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


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

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

Here's a no-compromises patch set. No bugs, no delays, it just does the
right thing.

If I haven't changed my mind again on Friday then it will be sent
upstream.


** Patch added: "lp1970069-patchset-20240201a.patch"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5744101/+files/lp1970069-patchset-20240201a.patch

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

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

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2024-02-01 Thread Heitor Alves de Siqueira

Yes, HWE kernels based on the Jammy/Mantic/Noble kernels should get this
fix automatically when the GA versions get 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/2036239

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

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

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia:

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2024-02-01 Thread Dimitri John Ledkov

** Changed in: zfs-linux (Ubuntu Mantic)
   Status: Incomplete => In Progress

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

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

** Changed in: zfs-linux (Ubuntu Lunar)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

** Changed in: zfs-linux (Ubuntu Focal)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  In Progress
Status in zfs-linux source package in Jammy:
  In Progress
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

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


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

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

2024-02-01 Thread Christian Rohmann

Thx a log Heitor! With no mention of some new package fixing this I did not 
correlate that to any patch to the kernel.
Will the be fixed in the HWE kernel as well then?

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

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

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22

[Kernel-packages] [Bug 241000] Re: Pairing: passcode dialogue disappears in <1 second

2024-02-01 Thread PaulSchulz

Resetting the bluez package did NOT fix the problem.
  Removing the bluez package(s), removing /var/lib/bluetooth and re-installing.

  sudo apt remove --purge bluez
  rm -rf /var/lib/bluetooth
  sudo apt install bluez gnome-bluetooth gnome-bluetooth-sendto
 
The bluetooth system need to be started, and this empties the list of 
discovered bluetoothe devices, 
but the popup for the keyboard auth number disappears again.

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

Title:
  Pairing: passcode dialogue disappears in <1 second

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez-utils package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: bluez-utils

  The pairing dialogues to allow entering a pin and initiate pairing
  disappear too fast.

  If I do the following:

sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth
  00:19:DB:0A:xx:yy

  a notifier window will pop up for ~1 second and then disappear.

  If I click on the notifier window fastest, the main passcode/pincode
  entry dialogue will disappear.  This also disappears within 1second.

  The key seems to be that it is necessary to 'auth', click and
  'pincode' within 1 second of a connection being made.  This should
  actually wait until the user is able to and none of the dialogue boxes
  should cut-off early and disappear without warning.

  Forum post discussing the same thing, with screenshots:

http://ph.ubuntuforums.com/showthread.php?p=5044322

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


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

[Kernel-packages] [Bug 241000] Re: Pairing: passcode dialogue disappears in <1 second

2024-02-01 Thread PaulSchulz

- This occurs on my daily use laptopm which has been upgraded from 23.04
-> 23.10

- I have just tried to pair on another laptop with freshly installed 23.10
  - The dialog displaying the pairing code persists
and I can pair correctly with same keyboard (it can pair with 3 separate 
devices)
  - bluez 5.68-0ubuntu1.1

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

Title:
  Pairing: passcode dialogue disappears in <1 second

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez-utils package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: bluez-utils

  The pairing dialogues to allow entering a pin and initiate pairing
  disappear too fast.

  If I do the following:

sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth
  00:19:DB:0A:xx:yy

  a notifier window will pop up for ~1 second and then disappear.

  If I click on the notifier window fastest, the main passcode/pincode
  entry dialogue will disappear.  This also disappears within 1second.

  The key seems to be that it is necessary to 'auth', click and
  'pincode' within 1 second of a connection being made.  This should
  actually wait until the user is able to and none of the dialogue boxes
  should cut-off early and disappear without warning.

  Forum post discussing the same thing, with screenshots:

http://ph.ubuntuforums.com/showthread.php?p=5044322

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


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

[Kernel-packages] [Bug 241000] Re: Pairing: passcode dialogue disappears in <1 second

2024-02-01 Thread PaulSchulz

I am seeing this bug in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1

Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html

I have managed to have it working in the past, but the 6-digit code pop-
up disappears very quickly (as described, <1sec).

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

Title:
  Pairing: passcode dialogue disappears in <1 second

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez-utils package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: bluez-utils

  The pairing dialogues to allow entering a pin and initiate pairing
  disappear too fast.

  If I do the following:

sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth
  00:19:DB:0A:xx:yy

  a notifier window will pop up for ~1 second and then disappear.

  If I click on the notifier window fastest, the main passcode/pincode
  entry dialogue will disappear.  This also disappears within 1second.

  The key seems to be that it is necessary to 'auth', click and
  'pincode' within 1 second of a connection being made.  This should
  actually wait until the user is able to and none of the dialogue boxes
  should cut-off early and disappear without warning.

  Forum post discussing the same thing, with screenshots:

http://ph.ubuntuforums.com/showthread.php?p=5044322

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


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

[Kernel-packages] [Bug 2049248] Re: Kernel 6.5 breaks display brightness controls and sets it to 100% all the time

2024-02-01 Thread Paddy Landau

** Description changed:

  Since kernel 6.5, monitor brightness is set to 100%, and cannot be
  changed: The brightness controls have disappeared from Settings, and
  brightness doesn't respond to the keypad controls.
  
  See the attached screenshot, showing the difference between the settings
  in kernels 6.2 and 6.5.
  
  This applies to Ubuntu 22.04 and 23.10, whether using Wayland or X.Org.
  
  It's possible (when using X.Org) to adjust the brightness with…
  
  $ xrandr --output [monitor] --brightness [brightness]
  
  e.g. on my machine…
  
  $ xrandr --output eDP-1 --brightness 0.5
  
  … but, unfortunately, it doesn't last long — anywhere between a less
  than a second later and about a minute later, the screen reverts to 100%
  brightness.
  
  As a workaround, I am running the following command in the background…
  
  $ while true; do xrandr --output eDP-1 --brightness 0.5; sleep 1s; done
  
  … which results in the screen at the correct brightness, but frequently
  flashing!
  
- Update: See comment #7 — This is somehow linked to the Night Light.
+ ———
+ UPDATES
+ ———
  
- Tested on:
+ • See comment #7 — This is somehow linked to the Night Light.
+ • Even when Night Light is permanently turned off, the screen still 
(sometimes; it's intermittent) goes bright when…
+ — Playing a video full screen (e.g. VLC, YouTube).
+ — Chrome gives a pop-up dialogue (e.g. downloading) or a notification (e.g. 
Calendar notification).
+ 
+ —
+ TESTED ON
+ —
  
  • Ubuntu 22.04
  — Kernel 6.2.0-39 and prior works correctly
- — Kernel 6.5.0-14 has the problem
+ — Kernels 6.5.0-14 & 6.5.0.15 have the problem
  
  • Ubuntu 23.10
  — Kernel 6.5.0-9 has the problem
  
  $ sudo lshw -numeric -C display
    *-display
     description: VGA compatible controller
     product: CometLake-S GT2 [UHD Graphics 630] [8086:9BC5]
     vendor: Intel Corporation [8086]
     physical id: 2
     bus info: pci@:00:02.0
     logical name: /dev/fb0
     version: 05
     width: 64 bits
     clock: 33MHz
     capabilities: pciexpress msi pm vga_controller bus_master cap_list rom 
fb
     configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
     resources: irq:145 memory:c100-c1ff memory:d000-dfff 
ioport:3000(size=64) memory:c-d
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 13 07:19:58 2024
  InstallationDate: Installed on 2022-08-28 (502 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Kernel 6.5 breaks display brightness controls and sets it to 100% all
  the time

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

Bug description:
  Since kernel 6.5, monitor brightness is set to 100%, and cannot be
  changed: The brightness controls have disappeared from Settings, and
  brightness doesn't respond to the keypad controls.

  See the attached screenshot, showing the difference between the
  settings in kernels 6.2 and 6.5.

  This applies to Ubuntu 22.04 and 23.10, whether using Wayland or
  X.Org.

  It's possible (when using X.Org) to adjust the brightness with…

  $ xrandr --output [monitor] --brightness [brightness]

  e.g. on my machine…

  $ xrandr --output eDP-1 --brightness 0.5

  … but, unfortunately, it doesn't last long — anywhere between a less
  than a second later and about a minute later, the screen reverts to
  100% brightness.

  As a workaround, I am running the following command in the background…

  $ while true; do xrandr --output eDP-1 --brightness 0.5; sleep 1s;
  done

  … which results in the screen at the correct brightness, but
  frequently flashing!

  ———
  UPDATES
  ———

  • See comment #7 — This is somehow linked to the Night Light.
  • Even when Night Light is permanently turned off, the screen still 
(sometimes; it's intermittent) goes bright when…
  — Playing a video full screen (e.g. VLC, YouTube).
  — Chrome gives a pop-up dialogue (e.g. downloading) or a notification (e.g. 
Calendar notification).

  —
  TESTED ON
  —

  • Ubuntu 22.04
  — Kernel 6.2.0-39 and prior works correctly
  — Kernels 6.5.0-14 & 6.5.0.15 have the problem

  • Ubuntu 23.10
  — Kernel 6.5.0-9 has the problem

  $ sudo lshw -numeric -C display
    *-display
     description: VGA compatible controller
     product: CometLake-S GT2 [UHD

[Kernel-packages] [Bug 2051924] Re: Mantic update: upstream stable patchset 2024-02-01

2024-02-01 Thread Manuel Diewald

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Manuel Diewald (diewald)

** Description changed:

  
  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:
  
 upstream stable patchset 2024-02-01
+ 
+ Ported from the following upstream stable relases:
+ v6.1.69, v6.6.8
+ 
 from git://git.kernel.org/
+ 
+ r8152: add vendor/device ID pair for D-Link DUB-E250
+ r8152: add vendor/device ID pair for ASUS USB-C2500
+ ext4: fix warning in ext4_dio_write_end_io()
+ ksmbd: fix memory leak in smb2_lock()
+ afs: Fix refcount underflow from error handling race
+ HID: lenovo: Restrict detection of patched firmware only to USB cptkbd
+ net/mlx5e: Fix possible deadlock on mlx5e_tx_timeout_work
+ net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX
+ qca_debug: Prevent crash on TX ring changes
+ qca_debug: Fix ethtool -G iface tx behavior
+ qca_spi: Fix reset behavior
+ bnxt_en: Fix wrong return value check in bnxt_close_nic()
+ bnxt_en: Fix HWTSTAMP_FILTER_ALL packet timestamp logic
+ atm: solos-pci: Fix potential deadlock on _queue_lock
+ atm: solos-pci: Fix potential deadlock on _queue_lock
+ net: fec: correct queue selection
+ octeontx2-af: fix a use-after-free in rvu_nix_register_reporters
+ octeontx2-pf: Fix promisc mcam entry action
+ octeontx2-af: Update RSS algorithm index
+ atm: Fix Use-After-Free in do_vcc_ioctl
+ iavf: Introduce new state machines for flow director
+ iavf: Handle ntuple on/off based on new state machines for flow director
+ qed: Fix a potential use-after-free in qed_cxt_tables_alloc
+ net: Remove acked SYN flag from packet in the transmit queue correctly
+ net: ena: Destroy correct number of xdp queues upon failure
+ net: ena: Fix xdp drops handling due to multibuf packets
+ net: ena: Fix XDP redirection error
+ stmmac: dwmac-loongson: Make sure MDIO is initialized before use
+ sign-file: Fix incorrect return values check
+ vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space()
+ dpaa2-switch: fix size of the dma_unmap
+ dpaa2-switch: do not ask for MDB, VLAN and FDB replay
+ net: stmmac: Handle disabled MDIO busses from devicetree
+ appletalk: Fix Use-After-Free in atalk_ioctl
+ net: atlantic: fix double free in ring reinit logic
+ cred: switch to using atomic_long_t
+ fuse: dax: set fc->dax to NULL in fuse_dax_conn_free()
+ ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB
+ ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants
+ ALSA: hda/realtek: Apply mute LED quirk for HP15-db
+ PCI: loongson: Limit MRRS to 256
+ ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE
+ drm/mediatek: Add spinlock for setting vblank event in atomic_begin
+ x86/hyperv: Fix the detection of E820_TYPE_PRAM in a Gen2 VM
+ usb: aqc111: check packet for fixup for true limit
+ stmmac: dwmac-loongson: Add architecture dependency
+ UBUNTU: [Config] updateconfigs for DWMAC_LOONGSON
+ blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!"
+ blk-cgroup: bypass blkcg_deactivate_policy after destroying
+ bcache: avoid oversize memory allocation by small stripe_size
+ bcache: remove redundant assignment to variable cur_idx
+ bcache: add code comments for bch_btree_node_get() and 
__bch_btree_node_alloc()
+ bcache: avoid NULL checking to c->root in run_cache_set()
+ nbd: fold nbd config initialization into nbd_alloc_config()
+ nvme-auth: set explanation code for failure2 msgs
+ nvme: catch errors from nvme_configure_metadata()
+ selftests/bpf: fix bpf_loop_bench for new callback verification scheme
+ LoongArch: Add dependency between vmlinuz.efi and vmlinux.efi
+ LoongArch: Implement constant timer shutdown interface
+ platform/x86: intel_telemetry: Fix kernel doc descriptions
+ HID: glorious: fix Glorious Model I HID report
+ HID: add ALWAYS_POLL quirk for Apple kb
+ nbd: pass nbd_sock to nbd_read_reply() instead of index
+ HID: hid-asus: reset the backlight brightness level on resume
+ HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad
+ asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation
+ net: usb: qmi_wwan: claim interface 4 for ZTE MF290
+ arm64: add dependency between vmlinuz.efi and Image
+ HID: hid-asus: add const to read-only outgoing usb buffer
+ btrfs: do not allow non subvolume root targets for snapshot
+

[Kernel-packages] [Bug 2051924] [NEW] Mantic update: upstream stable patchset 2024-02-01

2024-02-01 Thread Manuel Diewald

Public bug reported:


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:

   upstream stable patchset 2024-02-01
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Mantic)
   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/2051924

Title:
  Mantic update: upstream stable patchset 2024-02-01

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

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:

 upstream stable patchset 2024-02-01
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2050885] Re: hd will not mount

2024-02-01 Thread Randolph Gamo

Hello! Please what error message do you get, when trying to mount the
disks?

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

Title:
  hd will not mount

Status in linux package in Ubuntu:
  New

Bug description:
  I now have two hd that will not work on linux but work on window 11 .

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tlr2004 F wireplumber
   /dev/snd/seq:tlr1987 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 06:03:16 2024
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2023-11-13 (71 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=88481562-dc81-4d92-bc63-a1c80eeb6605 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.5
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   06:03:39.779: The udisks-daemon is running (name-owner :1.8).
  UpgradeStatus: Upgraded to mantic on 2024-01-22 (1 days ago)
  dmi.bios.date: 07/03/2023
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: JB20B001
  dmi.board.asset.tag: Default string
  dmi.board.name: JB20B
  dmi.board.vendor: Default string
  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.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB20B001:bd07/03/2023:br5.19:efr1.2:svnDefaultstring:pnJB20B:pvrDefaultstring:rvnDefaultstring:rnJB20B:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU1:
  dmi.product.family: MiniPC
  dmi.product.name: JB20B
  dmi.product.sku: SKU1
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

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


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

Test packages

[1]: alsa-ucm-conf (1.2.10-1ubuntu3) noble
[1]: alsa-ucm-conf (1.2.9-1ubuntu3.3) mantic
[2]: alsa-ucm-conf (1.2.6.3-1ubuntu1.11) jammy

---
[1] https://launchpad.net/~ethan.hsieh/+archive/ubuntu/sru
[2] https://launchpad.net/~ethan.hsieh/+archive/ubuntu/sru-test

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

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 2051703] Re: Kernel 6.5.0-15-generic: HDMI Screen detected but stays black at 60 Hz on HP Notebook

2024-02-01 Thread Paul White

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

** Tags added: jammy

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

Title:
  Kernel 6.5.0-15-generic: HDMI Screen detected but stays black at 60 Hz
  on HP Notebook

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

Bug description:
  When booting with kernel 6.5.0-15-generic, the screen stays black, but
  it is properly detected since I can move the mouse to it. Moreover, if
  I reduce the framerate to 30Hz (it normally is at 60Hz) the screen is
  visible again.

  The HDMI screen works fine at 60 Hz using kernel 6.2.0-39.

  I'm running Linux Mint 21.2, based on ubuntu 22.04. I'm reporting the
  bug here since it really seems like a kernel issue.

  $ cat /proc/version_signature
  Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3

  
  System:
Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 
5.8.4 tk: GTK 3.24.33
  wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 
22.04 jammy
  Machine:
Type: Laptop System: HP product: HP Notebook v: Type1ProductConfigId
  serial:  Chassis: type: 10 serial: 
Mobo: HP model: 81F9 v: 67.43 serial:  UEFI: Insyde v: 
F.35
  date: 05/27/2019
  Battery:
ID-1: BAT1 charge: 11.2 Wh (100.0%) condition: 11.2/31.1 Wh (35.9%) volts: 
12.3 min: 11.1
  model: Hewlett-Packard PABAS0241231 serial:  status: Full
  CPU:
Info: quad core model: AMD A10-9600P RADEON R5 10 COMPUTE CORES 4C+6G bits: 
64 type: MT MCP
  arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
Speed (MHz): avg: 2526 high: 2585 min/max: 1200/2400 boost: enabled cores: 
1: 2585 2: 2584
  3: 2551 4: 2387 bogomips: 19163
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard 
driver: amdgpu v: kernel
  ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:01.0 chip-ID: 
1002:9874
Device-2: Chicony HP TrueVision HD type: USB driver: uvcvideo bus-ID: 2-1:2 
chip-ID: 04f2:b56c
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
  unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96
Monitor-1: eDP res: 1366x768 dpi: 101 diag: 394mm (15.5")
OpenGL: renderer: CARRIZO (carrizo LLVM 15.0.7 DRM 3.54 6.5.0-15-generic)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
  Audio:
Device-1: AMD Kabini HDMI/DP Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel
  bus-ID: 00:01.1 chip-ID: 1002:9840
Device-2: AMD Family 15h Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel
  bus-ID: 00:09.2 chip-ID: 1022:157a
Device-3: GN Netcom Jabra EVOLVE LINK type: USB driver: 
jabra,snd-usb-audio,usbhid
  bus-ID: 1-1.1:3 chip-ID: 0b0e:0306
Sound Server-1: ALSA v: k6.5.0-15-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: 
Hewlett-Packard driver: r8169
  v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 
chip-ID: 10ec:8136
IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: 
Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: 
Hewlett-Packard
  driver: rtl8723be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 2000 
bus-ID: 02:00.0
  chip-ID: 10ec:b723
IF: wlo1 state: up mac: 
IF-ID-1: br-ba7391f263ca state: down mac: 
IF-ID-2: docker0 state: down mac: 
  Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 
1-1.4:5
  chip-ID: 0bda:b008
Report: hciconfig ID: hci0 rfk-id: 0 state: up address:  bt-v: 2.1 
lmp-v: 4.0
  sub-v: 9f73
  Drives:
Local Storage: total: 953.87 GiB used: 368.09 GiB (38.6%)
ID-1: /dev/sda vendor: Lexar model: SSD NS100 1TB size: 953.87 GiB speed: 
6.0 Gb/s
  serial: 
  Partition:
ID-1: / size: 233.62 GiB used: 66.13 GiB (28.3%) fs: ext4 dev: /dev/sda3
ID-2: /boot/efi size: 486 MiB used: 7 MiB (1.4%) fs: vfat dev: /dev/sda1
ID-3: /home size: 687.66 GiB used: 301.96 GiB (43.9%) fs: ext4 dev: 
/dev/sda4
  Swap:
ID-1: swap-1 type: partition size: 15.26 GiB used: 0 KiB (0.0%) priority: 
-2 dev: /dev/sda2
  Sensors:
System Temperatures: cpu: 52.0 C mobo: 20.0 C gpu: amdgpu temp: 51.0 C
Fan Speeds (RPM): N/A
  Repos:
Packages: 2537 apt: 2530 flatpak: 7
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/docker.list
  1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https: 
//download.docker.com/linux/ubuntu jammy stable
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
  1: deb [arch=amd64] https:

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

2024-02-01 Thread Paul White

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

** Tags added: jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/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 2051703] [NEW] Kernel 6.5.0-15-generic: HDMI Screen detected but stays black at 60 Hz on HP Notebook

You have been subscribed to a public bug:

When booting with kernel 6.5.0-15-generic, the screen stays black, but
it is properly detected since I can move the mouse to it. Moreover, if I
reduce the framerate to 30Hz (it normally is at 60Hz) the screen is
visible again.

The HDMI screen works fine at 60 Hz using kernel 6.2.0-39.

I'm running Linux Mint 21.2, based on ubuntu 22.04. I'm reporting the
bug here since it really seems like a kernel issue.

$ cat /proc/version_signature
Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3


System:
  Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 
5.8.4 tk: GTK 3.24.33
wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 
jammy
Machine:
  Type: Laptop System: HP product: HP Notebook v: Type1ProductConfigId
serial:  Chassis: type: 10 serial: 
  Mobo: HP model: 81F9 v: 67.43 serial:  UEFI: Insyde v: 
F.35
date: 05/27/2019
Battery:
  ID-1: BAT1 charge: 11.2 Wh (100.0%) condition: 11.2/31.1 Wh (35.9%) volts: 
12.3 min: 11.1
model: Hewlett-Packard PABAS0241231 serial:  status: Full
CPU:
  Info: quad core model: AMD A10-9600P RADEON R5 10 COMPUTE CORES 4C+6G bits: 
64 type: MT MCP
arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
  Speed (MHz): avg: 2526 high: 2585 min/max: 1200/2400 boost: enabled cores: 1: 
2585 2: 2584
3: 2551 4: 2387 bogomips: 19163
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard driver: 
amdgpu v: kernel
ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874
  Device-2: Chicony HP TrueVision HD type: USB driver: uvcvideo bus-ID: 2-1:2 
chip-ID: 04f2:b56c
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96
  Monitor-1: eDP res: 1366x768 dpi: 101 diag: 394mm (15.5")
  OpenGL: renderer: CARRIZO (carrizo LLVM 15.0.7 DRM 3.54 6.5.0-15-generic)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: AMD Kabini HDMI/DP Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel
bus-ID: 00:01.1 chip-ID: 1002:9840
  Device-2: AMD Family 15h Audio vendor: Hewlett-Packard driver: snd_hda_intel 
v: kernel
bus-ID: 00:09.2 chip-ID: 1022:157a
  Device-3: GN Netcom Jabra EVOLVE LINK type: USB driver: 
jabra,snd-usb-audio,usbhid
bus-ID: 1-1.1:3 chip-ID: 0b0e:0306
  Sound Server-1: ALSA v: k6.5.0-15-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard 
driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 
chip-ID: 10ec:8136
  IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: 
  Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: 
Hewlett-Packard
driver: rtl8723be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 2000 
bus-ID: 02:00.0
chip-ID: 10ec:b723
  IF: wlo1 state: up mac: 
  IF-ID-1: br-ba7391f263ca state: down mac: 
  IF-ID-2: docker0 state: down mac: 
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 
1-1.4:5
chip-ID: 0bda:b008
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address:  bt-v: 2.1 
lmp-v: 4.0
sub-v: 9f73
Drives:
  Local Storage: total: 953.87 GiB used: 368.09 GiB (38.6%)
  ID-1: /dev/sda vendor: Lexar model: SSD NS100 1TB size: 953.87 GiB speed: 6.0 
Gb/s
serial: 
Partition:
  ID-1: / size: 233.62 GiB used: 66.13 GiB (28.3%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 486 MiB used: 7 MiB (1.4%) fs: vfat dev: /dev/sda1
  ID-3: /home size: 687.66 GiB used: 301.96 GiB (43.9%) fs: ext4 dev: /dev/sda4
Swap:
  ID-1: swap-1 type: partition size: 15.26 GiB used: 0 KiB (0.0%) priority: -2 
dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 52.0 C mobo: 20.0 C gpu: amdgpu temp: 51.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2537 apt: 2530 flatpak: 7
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/docker.list
1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https: 
//download.docker.com/linux/ubuntu jammy stable
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com victoria main upstream import backport
2: deb http: //ubuntu.mirror.iweb.ca jammy main restricted universe 
multiverse
3: deb http: //ubuntu.mirror.iweb.ca jammy-updates main restricted universe 
multiverse
4: deb http: //ubuntu.mirror.iweb.ca jammy-backports main restricted 
universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted 
universe

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

You have been subscribed to a public bug:

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!

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

-- 
Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected at all
https://bugs.launchpad.net/bugs/2051922
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.5 in Ubuntu.

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

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

** Description changed:

  [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. There should be low 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.

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

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 1782709] Re: Updating systemd kills network on bionic

2024-02-01 Thread Dominic Raferd

Despite my comment above, I still have this problem when using netplan.
Here is my /etc/netplan/config.yaml (external IP quatrains have been
changed), the setup is that enp8s1 provides internet access (with metric
49) and enp7s0 provides local lan access *and* (with metric 51) fallback
internet access:

network:
  version: 2
  renderer: networkd
  ethernets:
enp8s1:
  dhcp4: false
  wakeonlan: true
  addresses: [111.94.100.80/24]
  nameservers:
addresses: [111.94.100.1]
  # makes this the default route - deprecated
  #gateway4: 111.94.100.1
  link-local: []
  routes:
  - to: default
via: 111.94.100.1
metric: 49
on-link: true
enp7s0:
  dhcp4: false
  wakeonlan: true
  addresses: [192.168.20.88/24]
  nameservers:
addresses: [192.168.20.1]
  link-local: []
  routes:
  - to: default
via: 192.168.20.1
metric: 51
on-link: true
# to avoid conflict with enp8s1 default route, but makes no difference
#table: 76
  - to: 192.168.20.0/24
via: 192.168.20.1
metric: 48

When working properly:
# ip route show to default
default via 111.94.100.1 dev enp8s1 proto static metric 49 onlink
default via 192.168.20.1 dev enp7s0 proto static metric 51 onlink

But after systemd reconfiguration we have two default routes with a
metric of 0! We have to delete one of them to restore the correct setup
(as above) and get internet access via enp8s1 again. My workaround is
continuous monitoring of syslog for a line indicating that the network
has been (re)configured by systemd and then running some bash code like
this (extract):

if [[ -n $(ip route show to default metric 0 via 192.168.20.1) ]]; then
  NUM_DEFAULT_ROUTES=$(ip route show to default|wc -l)
  if [[ $NUM_DEFAULT_ROUTES -gt 2 ]]; then
ip route delete to default metric 0 via 192.168.20.1
  fi
fi

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

Title:
  Updating systemd kills network on bionic

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

Bug description:
  I do have an ubuntu bionic server installation without a graphical interface. 
The server
  has two active network adapters, both connected to the internet. One is used 
for outgoing
  internet traffic, the other for incoming. The incoming adapter lives on a 
public network segment
  (something like 88.236.133.104/29). I do have multiple servers within this 
segment.

  Typically, I update the server regularly, meaning:

  * ssh to the incoming adapter: ssh 88.236.133.108
  * apt-get update
  * apt-get upgrade
  * apt-get dist-upgrade
  * apt-get clean
  * reboot

  It used to work ok.

  BUT: Today, "apt-get upgrade" seem to take really long when updating systemd.
  After a could of minutes, I realized that the ssh session became inactive. I 
couldn't type
  into it, I had to abort it via ~. .

  * ssh from the internet to the incoming adapter was not working anymore - ssh 
88.236.133.108
  * ssh via another server within the public network segment worked
  * ssh 88.236.133.106 -> ssh 88.236.133.108
  * After running "netplan apply" everything was fine again

  Here my netplan configuration (I changed the ip addresses):

  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes
  eno2:
dhcp4: no
addresses: [88.236.133.108/29]
#gateway4: 88.236.133.105
routes:
 - to: 0.0.0.0/0
   via: 88.236.133.105
   table: 120
routing-policy:
 - from: 88.236.133.108/32
   table: 120
 - to: 88.236.133.108/32
   table: 120

  Unfortunately, I don't have the console output avalable anymore.
  Shall I provide additional info?

  Best regards, Uli
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 20 08:10 seq
   crw-rw 1 root audio 116, 33 Jul 20 08:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-14 (5 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM IBM System x -[794582G]-
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic

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

2024-02-01 Thread Ubuntu Foundations Team Bug Bot

The attachment "noble.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

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. There should be low risk.

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

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

** Patch added: "jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+attachment/5744077/+files/jammy.debdiff

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

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