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

[FL140]

@mafoelffen I also filed a bug report here, but it looks like it never showed 
up anywhere. Anyways, since the 2.2.1 HotFix never made it to mantic and I 
needed this fixed ASAP I made a script for building the deb packages, so if you 
also like to build your own until there is an official HotFix 2.2.2 from Ubuntu 
have a look here: 
https://github.com/openzfs/zfs/issues/15586#issuecomment-1836806381
(There seems to be a little (wrong path) bug at the end on the final deb 
packages install command, but this should be easy to fix by hand.)


** Bug watch added: github.com/openzfs/zfs/issues #15586
   https://github.com/openzfs/zfs/issues/15586

-- 
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 Committed
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:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

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

  [ 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 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy

[Masahiro Nakagawa]

No they cannot use 22-hwe/stable.

I talked to this customer and they cannot accept kernel version change.
(ABI interface and other minor changes maybe introduced by 6.2 kernel
and they cannot take this risk)

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [ Impact ]

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

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

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

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

  [ Test Plan ]

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

  [ Where problems could occur ]

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

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

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


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

[Kernel-packages] [Bug 2045817] Re: [Intel AX211] Bluetooth issues in Ubuntu 23.10

[Daniel van Vugt]

** Summary changed:

- [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10
+ [Intel AX211] Bluetooth issues in Ubuntu 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/2045817

Title:
  [Intel AX211] Bluetooth issues in Ubuntu 23.10

Status in linux package in Ubuntu:
  New

Bug description:
  similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14
  generic kernels.

  ❯ uname -a; lsb_release -a
  Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC 
Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 23.10
  Release: 23.10
  Codename: mantic

  2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c
  2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception 
info failed (-16)
  2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
  2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 6
  2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware 
version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode
  2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | 
trm_hw_status0
  2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | 
trm_hw_status1
  2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | 
branchlink2
  2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink1
  2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink2
  2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1
  2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2
  2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3
  2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon 
time
  2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low
  2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi
  2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1
  2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2
  2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode 
revision type
  2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode 
version major
  2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode 
version minor
  2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version
  2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board 
version
  2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd
  2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0
  2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1
  2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2
  2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3
  2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4
  2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd 
Id
  2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event
  2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | 
l2p_control
  2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | 
l2p_duration
  2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | 
l2p_mhvalid
  2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | 
l2p_addr_match
  2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | 
lmpm_pmg_sel
  2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp
  2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | 
flow_handler
  2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 7
  2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | 
ADVANCED_SYSASSERT
  2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac 
branchlink1
  2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac 
branchlink2
  2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac 
interruptlink1
  2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac 
interruptlink2
  2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1
  2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2
  2023-12-06T16:03:58,985187-06:00 

[Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Ken Sharp]

Are you still having this issue?

** Tags added: amd64 bionic

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

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

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


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

[Kernel-packages] [Bug 1949359] Re: crash-utility segfault in ubuntu20.04

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  crash-utility segfault in ubuntu20.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  [environment]
  * ubuntu version
  ```
  jeff-kvm@ubuntu:/var/crash$ uname -r
  5.13.0-17-generic
  ```
  * crash version
  ```
  jeff-kvm@ubuntu:/var/crash$ crash -v

  crash 7.2.8
  ...
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu".

  ```

  
  [Description of problem:]
  ```
  root@ubuntu:/var/crash/202110312024# crash dump.202110312024 
/home/jeff-kvm/Downloads/jeff/usr/lib/debug/boot/vmlinux-5.13.0-17-generic

  crash 7.2.8
  Copyright (C) 2002-2020  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-unknown-linux-gnu"...

  WARNING: kernel relocated [362MB]: patching 139284 gdb minimal_symbol
  values

  please wait... (patching 139284 gdb minimal_symbol values) Segmentation fault 
(core dumped)
  ```
  And we can see the following error report(see dmesg):
  ```
  [ 1198.548759] crash[3580]: segfault at 7c57dff8 ip 560ea1af5ec0 sp 
7c57e000 error 6 in crash[560ea1ad9000+43f000]
  [ 1198.548768] Code: 05 a5 3d 6c 00 48 39 78 08 0f 97 c0 0f b6 c0 c3 66 2e 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa 41 57 41 89 f7 41 56 41 55 49 89 cd <41> 54 49 
89 fc 55 48 89 d5 53 4c 89 cb 48 83 ec 48 4c 89 04 24 64
  ```
  And we can see the crash-utility proc mem map(_usr_bin_crash.0.crash):
  ```
  

   7fb97b7d4000-7fb97b7d5000 rw-p 0002d000 08:05 2234671
/usr/lib/x86_64-linux-gnu/ld-2.31.so
   7fb97b7d5000-7fb97b7d6000 rw-p  00:00 0
   7c57e000-7cd7e000 rw-p  00:00 0  
[stack]
   7cdb1000-7cdb5000 r--p  00:00 0  
[vvar]
   7cdb5000-7cdb7000 r-xp  00:00 0  
[vdso]
   ff60-ff601000 --xp  00:00 0  
[vsyscall]
  ...
  ProcStatus:
  ```
   it seems that it's stack overflow,because  segfault at 7c57dff8,but the 
[stack]: 7c57e000-7cd7e000

  
  [How to reproducible]
  always
  Steps to Reproduce:
  1. Generate a vmcore with the sysrq
  2. crash vmlinux vmcore
  3.

  Actual results:

  Segmentation fault (core dumped)

  Expected results:

  crash can work as expected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-16 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  

[Kernel-packages] [Bug 2038410] Re: after kernel upgrade today to 6.2.0-33 network and bluetooth stopped waorking

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  after kernel upgrade today to 6.2.0-33 network and bluetooth stopped
  waorking

Status in linux package in Ubuntu:
  Expired

Bug description:
  had to go back to 6.2.0-33

  i have amd ryzen 5700g machine with a ASUS Prime B550 motherboard

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:14275453:2023-10-01 12:57:00.819613695 +0200:2023-10-01 
12:57:01.819613695 +0200:/var/crash/_usr_bin_nautilus.1000.crash
   640:1000:124:5824531:2023-10-03 16:49:20.932747125 +0200:2023-10-03 
16:49:21.932747125 +0200:/var/crash/_usr_bin_gnome-panel.1000.crash
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Oct  4 09:08:31 2023
  InstallationDate: Installed on 2023-09-19 (14 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2045754] Re: [A770] Graphics card driver crash

[Daniel van Vugt]

It looks like kwin didn't crash until after the kernel errors started so
let's make this about the kernel errors.

** Summary changed:

- Graphics card driver crash
+ [A770] Graphics card driver crash

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

** Summary changed:

- [A770] Graphics card driver crash
+ [Arc A770] Graphics card driver crash

** Tags added: i915

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

Title:
  [Arc A770] Graphics card driver crash

Status in linux package in Ubuntu:
  New

Bug description:
  I was just browsing the web when the bottom half of the display became black, 
the cursor froze, and everything started flickering.
  I think eventually KDE crashed and some terminal messages were shown.

  I Ctrl+alt+f3 to a terminal and shut down from there.
  The terminal was glitchy with random artifacts but visible.

  After reboot everything is working again for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Dec  6 12:03:24 2023
  DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
  InstallationDate: Installed on 2022-10-30 (402 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet 
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
  dmi.bios.date: 05/18/2023
  dmi.bios.release: 16.18
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1618
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X670E-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2045754] [NEW] [A770] Graphics card driver crash

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I was just browsing the web when the bottom half of the display became black, 
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.

I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.

After reboot everything is working again for now.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec  6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet 
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
dmi.bios.date: 05/18/2023
dmi.bios.release: 16.18
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1618
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X670E-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze kubuntu mantic ubuntu wayland-session
-- 
[A770] Graphics card driver crash
https://bugs.launchpad.net/bugs/2045754
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2045817] Re: [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10

[Daniel van Vugt]

** Summary changed:

- Bluetooth issues in Ubuntu 23.10
+ [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10

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

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

Title:
  [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in
  Ubuntu 23.10

Status in linux package in Ubuntu:
  New

Bug description:
  similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14
  generic kernels.

  ❯ uname -a; lsb_release -a
  Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC 
Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 23.10
  Release: 23.10
  Codename: mantic

  2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c
  2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception 
info failed (-16)
  2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
  2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 6
  2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware 
version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode
  2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | 
trm_hw_status0
  2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | 
trm_hw_status1
  2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | 
branchlink2
  2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink1
  2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink2
  2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1
  2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2
  2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3
  2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon 
time
  2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low
  2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi
  2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1
  2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2
  2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode 
revision type
  2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode 
version major
  2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode 
version minor
  2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version
  2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board 
version
  2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd
  2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0
  2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1
  2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2
  2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3
  2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4
  2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd 
Id
  2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event
  2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | 
l2p_control
  2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | 
l2p_duration
  2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | 
l2p_mhvalid
  2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | 
l2p_addr_match
  2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | 
lmpm_pmg_sel
  2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp
  2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | 
flow_handler
  2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 7
  2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | 
ADVANCED_SYSASSERT
  2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac 
branchlink1
  2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac 
branchlink2
  2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac 
interruptlink1
  2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac 
interruptlink2
  2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1
  2023-12-06T16:03:58,985185-06:00 iwlwifi 

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

[Michael Reed]

These patches were also needed.

924cb24df4fcscsi: fnic: Stop using the SCSI pointer
b559b99a5c081   scsi: fnic: Replace DMA mask of 64 bits with 47 bits

** Description changed:

  [Impact]
  
  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.
  
  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.
  
  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.
  
  Below are the kernel patches which picked for the newer version of fins
  driver.
  
  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
  
  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
  
  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/
  
  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.
  
  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.
  
  [ Where problems could occur ]
  
  [ Other Info ]
+ 
+ Jammy
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/fnic_11_10_23
+ 
+ Mantic
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fnic_update_2036777

** Description changed:

  [Impact]
  
  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.
  
  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.
  
  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.
  
  Below are the kernel patches which picked for the newer version of fins
  driver.
  
- https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
+ 924cb24df4fcscsi: fnic: Stop using the SCSI pointer
+ b559b99a5c081   scsi: fnic: Replace DMA mask of 64 bits with 47 bits
+ 5a43b07a87835   scsi: fnic: Replace return codes in 
fnic_clean_pending_aborts()
+ 15924b0503630   scsi: fnic: Replace sgreset tag with max_tag_id
+ 514f0c400bde6   scsi: fnic: Fix sg_reset success path
  
- https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
- 
- https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/
  
  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.
  
  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.
  
  [ Where problems could occur ]
  
  [ Other Info ]
  
- Jammy
- 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/fnic_11_10_23
  
- Mantic
- 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fnic_update_2036777
+ 
+ Links to first 3 patches
+ https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
+ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
+ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

** Description changed:

  [Impact]
  
  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.
  
  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  

[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

[Daniel van Vugt]

Please open a new bug about that because this one is closed.

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Fix Released
Status in metacity package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup

[Michael Reed]

I created a 6.2 test kernel for Lunar.Please test

https://people.canonical.com/~mreed/lenovo/lp_2020022_vmd/lunar/12062023/

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

Title:
  [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
  in UEFI setup

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:

  [  166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
  [  166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID 
  [  166.612445] DMAR: VT-d detected Invalidation Completion Error: SID 
  [  166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
  [  166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
  ...

  Additional info:
    * The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.

  Debugging info and fix commit info:
    * `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: 
Clean up domain before enumeration"). The root cause is that VMD driver tries 
to clear a PCI configuration space range when resetting a VMD domain 
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
 which leads to the failure.

  [Fix]
    * Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: 
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this 
commit can fix the issue.

  Would it be possible to include the commit 20f3337d350c in Ubuntu
  22.04.2/23.10 kernel?

  [Test Plan]

  Reproduce Step
  1.Disable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Disabled

  2.Install OS

  3.Enable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Enabled

  4.Rebooting will reproduce this issue

  [ Where problems could occur ]
  * Lenovo SE350 server and Lenovo SR850 v2 server
  * The regression leads to the boot failure (cannot boot info OS 
successfully). 

  [ Other Info ]
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022

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


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

[Kernel-packages] [Bug 1917813] Re: HWP and C1E are incompatible - Intel processors

[Bug Watch Updater]

Launchpad has imported 45 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=210741.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2020-12-17T01:13:11+00:00 dsmythies wrote:

Created attachment 294171
Graph of load sweep up and down at 347 Hertz.

Consider a steady state periodic single threaded workflow, with a work/sleep 
frequency of 347 Hertz and a load somewhere in the ~75% range at the steady 
state operating point.
For the intel-cpufreq CPU frequency scaling driver and powersave governor and 
hwp disabled, it goes indefinitely without any issues.
For the acpi-cpufreq CPU frequency scaling driver and ondemand governor, it 
goes indefinitely without any issues.
For the intel-cpufreq CPU frequency scaling driver and powersave governor and 
hwp enabled, it suffers from overruns.

Why?

For unknown reasons, HWP seems to incorrectly decide that the processor
is idle and spins the PLL down to a very low frequency. Upon exit from
the sleep portion of the periodic workflow it takes a very long time (on
the order of 20 milliseconds (supporting data for that statement will
added in a later posting)), resulting in the periodic job no being able
to complete its work before the next interval, whereas it normally has
plenty of time to do its work. Actually, typical worst case overruns are
around 12 milliseconds, or several work/sleep periods (i.e. it takes a
very long time to catch up.)

The probability of this occurring is about 3%, but varies significantly.
Obviously, the recovery time is also a function of EPP, but mostly this
work has been done with the default EPP of 128. I believe this to be a
sampling and anti-aliasing issue, but can not prove it because HWP is
black box. My best GUESS is:

If the periodic load is busy on a jiffy boundary, such that the tick is on.
Then if it is sleeping at the next jiffy boundary, with a pending wake such 
that idle state 2 was used.
  Then if the rest of the system was idle such that HWP decides to spin down 
the PLL.
Then it is highly probable that upon that idle state 2 exit, the PLL is too 
slow to ramp up and the task will overrun as a result.
Else everything will be fine.

For a 1000 Hz kernel the above suggests that a work/sleep frequency of 500 Hz 
should behave in a binary way, either lots of overruns or none. It does.
For a 1000 Hz kernel the above suggests that a work/sleep frequency of 333.333 
Hz should behave in a binary way, either lots of overruns or none. It does.
Note: in all cases the sleep time has to be within the window of opportunity.

Now, actually I can not prove if the idle state 2 part is a cause or
consequence, but it never happens with it disabled, but at the cost of
significant power.

Another way this issue would manifest itself is as seeming to be an
extraordinary idle exit latency, but would be rather difficult to
isolate as the cause.

processors tested:
Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz (mine)
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (not mine)

HWP has been around for years, why am I just reporting this now?

I never owned an HWP capable processor before. My older i7-2600K based
test computer was getting a little old, so I built a new test computer.
I noticed this issue the same day I first enabled HWP. That was months
ago (notice the dates on the graphs that will eventually be added to
this), and I tried, repeatedly, to get help from Intel via the linux-pm
e-mail list.

Now, given the above system response issue, a new test was developed to
focus specifically on this issue, dubbed the "Inverse Impulse Response"
test. It examines in great detail the CPU frequency rise time after a
brief, less than 1 millisecond, gap in an otherwise continuous workflow.
I'll attach graphs and details in subsequent postings to this bug
report.

While I believe this is an issue entirely within HWP, I have not been
able to prove that there was nothing sent from the kernel somehow
telling HWP to spin down.

Notes:

CPU affinity does not need to be forced, but sometimes is for data
acquisition.

1000 hertz kernels were tested back to kernel 5.2, all failed.

Kernel 5.10-rc7 (I have yet to compile 5.10) also fails.

A 250 hertz kernel was tested, and it did not have this issue in this
area. Perhaps elsewhere, I didn't look.

Both teo and menu idle governors were tested, and while both suffer from
the unexpected CPU frequency drop, teo seems much worse. However failure
points for both governors are repeatable.

The test computers were always checked for any throttling log sticky
bits, and regardless were never anywhere even close to throttling.

Note, however that every HWP capable computer I was to acquire data from
has at least one of those sticky bits set after boot, so 

[Kernel-packages] [Bug 2045722] Re: Ubuntu freeze randomly

[Daniel van Vugt]

Yes I noticed that but it's already covered by the nvidia-graphics-
drivers-535 and linux-hwe-6.2 tasks here.

Assuming this isn't a hardware problem I think you're probably waiting
for a driver fix from Nvidia, or a kernel fix.

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

Title:
  Ubuntu freeze randomly

Status in linux-hwe-6.2 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  Sometimes happens when I leave it (probably screen lock), sometimes
  happens when I about to shutdown, sometimes happens when running. The
  log shows it is related to xorg or nvidia.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 10:53:21 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.129.03, 5.15.0-89-generic, x86_64: installed
   nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed
   nvidia/535.129.03, 6.2.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] 
[103c:878e]
   NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] 
[103c:878e]
  InstallationDate: Installed on 2021-06-05 (913 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ENVY Laptop 15-ep0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2021
  dmi.bios.release: 15.7
  dmi.bios.vendor: AMI
  dmi.bios.version: F.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878E
  dmi.board.vendor: HP
  dmi.board.version: 18.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 18.33
  dmi.modalias: 
dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6:
  dmi.product.family: 103C_5335KV HP ENVY
  dmi.product.name: HP ENVY Laptop 15-ep0xxx
  dmi.product.sku: 16P91PA#AR6
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression

[Chengen Du]

This bug only involves a revert to LP#2032164. We are actively working
on finding a comprehensive solution to address the live migration issue.

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

Title:
  5.15.0-85 live migration regression

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

Bug description:
  
  Fixes added for LP 2032164 [0] to resolve an issue in live migration have 
  unfortunately introduced a regression, causing a previously working live 
  migration pattern to fail when tested with the 5.15.0-85 kernel from 
-proposed.

  Specifically, live migration from a PKRU-enabled host running a kernel older
  than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail.  The
  destination can be either with or without PKRU; both cases fail, although
  in different ways (one hangs, the other fails due to a PCID flag issue).

  The commits in question are

  commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0
  Author: Dr. David Alan Gilbert 
  Date:   Mon Aug 21 14:47:28 2023 +0800

  KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES

  commit 27a189b881278c8ad9c16b0ee05668d724352733
  Author: Leonardo Bras 
  Date:   Mon Aug 21 14:47:27 2023 +0800

  x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0

  
  [0]   https://bugs.launchpad.net/bugs/2032164

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


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

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

[Michael Reed]

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

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

Title:
  [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]

  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.

  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.

  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.

  Below are the kernel patches which picked for the newer version of
  fins driver.

  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.

  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.

  [ Where problems could occur ]

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2045722] Re: Ubuntu freeze randomly

[Fikrul Arif]

There is also something like this repeating in /var/log/syslog:

kernel: [ 6983.891059] [ cut here ]
kernel: [ 6983.891060] WARNING: CPU: 2 PID: 8427 at 
/var/lib/dkms/nvidia/535.129.03/build/nvidia/nv.c:4769 nvidia_dev_put+0xb9/0xc0 
[nvidia]
kernel: [ 6983.891259] Modules linked in: rfcomm snd_ctl_led 
snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi 
snd_sof_probes snd_hda_codec_realtek snd_hda_codec_generic le
dtrig_audio ccm cmac algif_hash algif_skcipher af_alg nvidia_uvm(PO) 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defr
ag_ipv4 nf_tables libcrc32c nfnetlink bridge stp llc bnep snd_soc_dmic 
snd_sof_pci_intel_cnl snd_sof_intel_hda_common nvidia_drm(PO) soundwire_intel 
nvidia_modeset(PO) soundwire_generic_allocation soundwire_cade
nce snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils 
snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_acpi_intel_match 
intel_rapl_common snd_soc_acpi intel_tcc_cooling soundwire_bus
 nvidia(PO) x86_pkg_temp_thermal intel_powerclamp snd_soc_core snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg 
snd_intel_sdw_acpi i915 snd_hda_codec
kernel: [ 6983.891291]  snd_hda_core snd_hwdep coretemp crct10dif_pclmul 
snd_pcm kvm_intel iwlmvm polyval_clmulni polyval_generic snd_seq_midi 
ghash_clmulni_intel btusb kvm mei_hdcp mei_pxp
 snd_seq_midi_event binfmt_misc drm_buddy sha512_ssse3 btrtl irqbypass mac80211 
snd_rawmidi ttm btbcm aesni_intel btintel drm_display_helper snd_seq 
crypto_simd cec btmtk cryptd libarc4 nls_iso8859_1 hp_wmi rc_c
ore snd_seq_device bluetooth cmdlinepart rapl iwlwifi sparse_keymap snd_timer 
spi_nor drm_kms_helper i2c_algo_bit intel_cstate platform_profile serio_raw 
wmi_bmof intel_wmi_thunderbolt mxm_wmi mtd ee1004 syscopy
area mei_me snd ecdh_generic joydev input_leds cfg80211 sysfillrect ecc mei 
hid_multitouch soundcore sysimgblt intel_pch_thermal mac_hid acpi_pad 
sch_fq_codel msr parport_pc ppdev drm lp parport efi_pstore ip_ta
bles x_tables autofs4 usbhid hid_generic nvme ucsi_acpi ucsi_ccg sdhci_pci 
intel_lpss_pci i2c_hid_acpi spi_intel_pci cqhci i2c_i801 nvme_core ahci 
intel_lpss typec_ucsi crc32_pclmul
kernel: [ 6983.891335]  thunderbolt xhci_pci i2c_nvidia_gpu i2c_hid spi_intel 
sdhci i2c_smbus nvme_common libahci idma64 typec xhci_pci_renesas i2c_ccgx_ucsi 
hid video wmi pinctrl_cannonlak
e
kernel: [ 6983.891344] CPU: 2 PID: 8427 Comm: Sw-Signaling Tainted: PW  
O   6.2.0-37-generic #38~22.04.1-Ubuntu
kernel: [ 6983.891345] Hardware name: HP HP ENVY Laptop 15-ep0xxx/878E, BIOS 
F.07 07/30/2021
kernel: [ 6983.891346] RIP: 0010:nvidia_dev_put+0xb9/0xc0 [nvidia]
kernel: [ 6983.891530] Code: 31 f6 31 ff c3 cc cc cc cc 48 c7 c7 c0 8a bd c4 e8 
dc 27 26 e2 5b 41 5c 41 5d 41 5e 5d 31 c0 31 d2 31 f6 31 ff c3 cc cc cc cc <0f> 
0b eb be 0f 1f 00 90 90 90 90
 90 90 90 90 90 90 90 90 90 90 90
kernel: [ 6983.891531] RSP: 0018:a17d46867bf8 EFLAGS: 00010202
kernel: [ 6983.891533] RAX: 0026 RBX: 0100 RCX: 

kernel: [ 6983.891534] RDX:  RSI:  RDI: 
a17d46867b28
kernel: [ 6983.891534] RBP: a17d46867c18 R08:  R09: 

kernel: [ 6983.891535] R10:  R11:  R12: 
9304c93aa000
kernel: [ 6983.891536] R13: 9304d2a83000 R14: 9304c93aa638 R15: 
9304e996c6c0
kernel: [ 6983.891537] FS:  () GS:93084e28() 
knlGS:
kernel: [ 6983.891539] CS:  0010 DS:  ES:  CR0: 80050033
kernel: [ 6983.891540] CR2: 7fbc657fc910 CR3: 000107856006 CR4: 
007726e0
kernel: [ 6983.891541] PKRU: 5554
kernel: [ 6983.891542] Call Trace:
kernel: [ 6983.891542]  
kernel: [ 6983.891543]  ? show_regs+0x72/0x90
kernel: [ 6983.891545]  ? nvidia_dev_put+0xb9/0xc0 [nvidia]
kernel: [ 6983.891739]  ? __warn+0x8d/0x160
kernel: [ 6983.891742]  ? nvidia_dev_put+0xb9/0xc0 [nvidia]
kernel: [ 6983.891940]  ? report_bug+0x1bb/0x1d0
kernel: [ 6983.891942]  ? handle_bug+0x46/0x90
kernel: [ 6983.891944]  ? exc_invalid_op+0x19/0x80
kernel: [ 6983.891945]  ? asm_exc_invalid_op+0x1b/0x20
kernel: [ 6983.891948]  ? nvidia_dev_put+0xb9/0xc0 [nvidia]
kernel: [ 6983.892144]  ? nvidia_dev_put+0x77/0xc0 [nvidia]
kernel: [ 6983.892393]  nvidia_close+0x1c7/0x330 [nvidia]
kernel: [ 6983.892590]  nvidia_frontend_close+0x44/0x80 [nvidia]
kernel: [ 6983.892802]  __fput+0x9c/0x290
kernel: [ 6983.892805]  fput+0xe/0x20
kernel: [ 6983.892807]  task_work_run+0x5e/0xa0
kernel: [ 6983.892809]  do_exit+0x2a3/0x6c0
kernel: [ 6983.892811]  do_group_exit+0x35/0x90
kernel: [ 6983.892814]  get_signal+0x8a5/0x8d0
kernel: [ 6983.892817]  arch_do_signal_or_restart+0x2a/0x120
kernel: [ 6983.892819]  exit_to_user_mode_loop+0xaf/0x140
kernel: [ 6983.892821]  

[Kernel-packages] [Bug 2045817] Re: Bluetooth issues in Ubuntu 23.10

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  Bluetooth issues in Ubuntu 23.10

Status in bluez package in Ubuntu:
  New

Bug description:
  similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14
  generic kernels.

  ❯ uname -a; lsb_release -a
  Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC 
Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 23.10
  Release: 23.10
  Codename: mantic

  2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c
  2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception 
info failed (-16)
  2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
  2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 6
  2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware 
version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode
  2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | 
trm_hw_status0
  2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | 
trm_hw_status1
  2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | 
branchlink2
  2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink1
  2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink2
  2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1
  2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2
  2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3
  2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon 
time
  2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low
  2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi
  2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1
  2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2
  2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode 
revision type
  2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode 
version major
  2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode 
version minor
  2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version
  2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board 
version
  2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd
  2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0
  2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1
  2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2
  2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3
  2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4
  2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd 
Id
  2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event
  2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | 
l2p_control
  2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | 
l2p_duration
  2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | 
l2p_mhvalid
  2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | 
l2p_addr_match
  2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | 
lmpm_pmg_sel
  2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp
  2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | 
flow_handler
  2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log 
Dump:
  2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 7
  2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | 
ADVANCED_SYSASSERT
  2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac 
branchlink1
  2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac 
branchlink2
  2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac 
interruptlink1
  2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac 
interruptlink2
  2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1
  2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2
  2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 0x0053 | umac 

[Kernel-packages] [Bug 2045817] [NEW] Bluetooth issues in Ubuntu 23.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14
generic kernels.

❯ uname -a; lsb_release -a
Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic

2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c
2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception 
info failed (-16)
2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump:
2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 6
2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 
83.e8f84e98.0 so-a0-gf-a0-83.ucode
2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | 
trm_hw_status0
2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | 
trm_hw_status1
2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2
2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink1
2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink2
2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1
2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2
2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3
2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time
2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low
2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi
2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1
2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2
2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode 
revision type
2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode 
version major
2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode 
version minor
2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version
2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board 
version
2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd
2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0
2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1
2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2
2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3
2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4
2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id
2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event
2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control
2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration
2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid
2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | 
l2p_addr_match
2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel
2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp
2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler
2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump:
2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 7
2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | 
ADVANCED_SYSASSERT
2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac 
branchlink1
2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac 
branchlink2
2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac 
interruptlink1
2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac 
interruptlink2
2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1
2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2
2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3
2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 0x0053 | umac major
2023-12-06T16:03:58,985191-06:00 iwlwifi :00:14.3: 0xE8F84E98 | umac minor
2023-12-06T16:03:58,985193-06:00 iwlwifi :00:14.3: 0x7C0B3384 | frame 
pointer
2023-12-06T16:03:58,985195-06:00 iwlwifi :00:14.3: 0xC0886BE0 | stack 
pointer
2023-12-06T16:03:58,985197-06:00 iwlwifi :00:14.3: 0x00ED019C | last host 
cmd
2023-12-06T16:03:58,985199-06:00 iwlwifi :00:14.3: 0x | 

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

[Anthony Wong]

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

** Changed in: thermald (Ubuntu)
 Assignee: koba (kobako) => (unassigned)

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

Title:
  CPU frequency governor broken after upgrading from 22.10 to 23.04,
  stuck at 400Mhz on Alder Lake

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  I've tried to include as much detail as possible in this bug report, I
  originally assembled it just after the release of ubuntu 23.04.  There
  has been no change since then.

  
  I have had substantial performance problems since updating from ubuntu 22.10 
to 23.04.
  The computer in question is the 17 inch Razer Blade laptop from 2022 with an 
intel i7-12800H.
  Current kernel is 6.2.0-20-generic.  (now I'm on 6.2.0-24-generic and nothing 
has changed.)
  This issue occurs regardless of whether the OpenRazer 
(https://openrazer.github.io/) drivers etc are installed.

  
  Description of problem:
  I have discovered what may be two separate bugs involving low level power 
management details on the cpu, they involve the cpu entering different types of 
throttled states and never recovering. These issues appeared immediately after 
upgrading from ubuntu 22.10.  The computer is a large ~gaming laptop with 
plenty of thermal headroom, cpu temperatures cannot reach concerning values 
except when using stress testing tools.

  (I don't know how to propery untangle these two issues, so I'm posting
  them as one. I apologize for the review complexity this causes, but I
  think posting the information all in one spot is more constructive
  here.)

  
  High level testing notes:
  - This issue occurs with use of both the intel_pstate driver and the cpufreq 
driver. (I don't have the same level of detail for cpufreq, but the issue still 
occurs.)
  - I have additionally tested a handful of intel_pstate parameters (and 
others) via grub kernel command line arguments to no effect. All testing 
reported here was done with:
GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau"
GRUB_CMDLINE_LINUX=""
(loading nouveau caused problems for me on 22.10, I have not bothered 
reinvestigating it on 23.04)
  - There is a firmware update available from the manufacture when I boot into 
Windows, I have not installed it (yet).
  - - Update: I installed it. No change.
  - Changing the cpu governor setting from "powersave" to "performance" using 
`cpupower frequency-set -g performance` has no effect. (Note: this action is 
separate from the intel_pstate's power-saver/balanced/performance setting 
visible with the `powerprofilesctl` utility. It doesn't seem to be a governor 
bug.
  - - (There is a tertiary issue where I also see substantial (+50%) 
performance degredation using the "performance" profile in a test suite I run 
constantly for my job; that is clearly a problem but it is an unrelated bug 
that has existed for quite some time.)

  
  Summary and my own conclusions:
  These are my takeaways, the ~raw data is in the followup section.

  
  Bug 1)
  The reported cpu power limits are progressively constrained over time. Once 
this failure mode starts the performance never recovers.
- As this situation progresses the observed cpu speeds (I'm using htop) 
list as 2800Mhz at idle, but the instant any load at all is placed on a cpu 
core that core immediately drops to exactly 400Mhz.
- This situation occurs quite quickly in human terms, frequently within 20 
minutes of normal usage after a boot, but it will also occur when the computer 
is just sitting there unused for a handful of hours.
- This occurs when using the cpufreq gevernor (by including 
"intel_pstate=disable" on the grub command line args.)
- At boot the default value for short_term_time looks wrong to me. This is 
the duration of higher thermal targets in seconds, ~0.002 seconds seems 
extremely short. A normal value would be a handful of seconds.
- This situation can be remedied by running the following python script. It 
uses the undervolt package (pip install undervolt==0.3.0) to force particular 
power limits (the provided values are intentional overkill):
   1   │ from undervolt import read_power_limit, set_power_limit, 
PowerLimit, ADDRESSES
   2   │ from pprint import pprint
   3   │ 
   4   │ limits = read_power_limit(ADDRESSES)
   5   │ pprint(vars(limits))  # print current values before setting them
   6   │ 
   7   │ POWER_LIMITS = PowerLimit()
   8   │ POWER_LIMITS.locked = True  # lock means don't allow the value to 
be reset until a reboot.
   9   │ POWER_LIMITS.backup_rest = 281474976776192  # afaik this is just a 
backup-on-failure setting, it has no effect here.
  10   │ POWER_LIMITS.long_term_enabled = True
  11   │ 

[Kernel-packages] [Bug 2019152] Re: [btintel] Bluetooth crashes in Ubuntu 23.04

[Phil Buckley]

I tried updating to a later kernel -- now running 6.6.1 and the problem
has gone away.

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

Title:
  [btintel] Bluetooth crashes in Ubuntu 23.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth stops working.
  Mouse (logitech M720) stopped mid scroll. Never had any problems with this 
mouse under Ubuntu before.

  Workaround:
  Reboot fixes the problem.
  Switching in and out of airplane mode gets bluetooth working again 

  Frequency:
  Second time this has happened since upgrade from 22.10 (about 2 weeks ago)

  Limited knowledge fault tracing:

  >sudo systemctl restart bluetooth 
  doesn't make any difference

  >rfkill
  shows no bluetooth device

  >lspci
  ...
  3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  ...

  Ubuntu settings - show bluetooth is off, but I didn't disable it and
  it can't be re-enabled.

  So I assume the driver has crashed, but I don't know how to find out
  more about this. Could collect some more info next time it happens if
  someone tells me what to do.

  >lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

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


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

[Kernel-packages] [Bug 2019152] Re: [btintel] Bluetooth crashes in Ubuntu 23.04

[Jonathan Terry]

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019152/+attachment/5726878/+files/journal.txt

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

Title:
  [btintel] Bluetooth crashes in Ubuntu 23.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth stops working.
  Mouse (logitech M720) stopped mid scroll. Never had any problems with this 
mouse under Ubuntu before.

  Workaround:
  Reboot fixes the problem.
  Switching in and out of airplane mode gets bluetooth working again 

  Frequency:
  Second time this has happened since upgrade from 22.10 (about 2 weeks ago)

  Limited knowledge fault tracing:

  >sudo systemctl restart bluetooth 
  doesn't make any difference

  >rfkill
  shows no bluetooth device

  >lspci
  ...
  3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  ...

  Ubuntu settings - show bluetooth is off, but I didn't disable it and
  it can't be re-enabled.

  So I assume the driver has crashed, but I don't know how to find out
  more about this. Could collect some more info next time it happens if
  someone tells me what to do.

  >lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

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


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

[Kernel-packages] [Bug 2019152] Re: [btintel] Bluetooth crashes in Ubuntu 23.04

[Jonathan Terry]

Having a similar experience in 23.10 with 6.5.0-12 thru 6.5.0-14 generic
kernels.

❯ uname -a; lsb_release -a
Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.10
Release:23.10
Codename:   mantic

2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c
2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception 
info failed (-16)
2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump:
2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 6
2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 
83.e8f84e98.0 so-a0-gf-a0-83.ucode
2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | 
trm_hw_status0
2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | 
trm_hw_status1
2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2
2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink1
2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | 
interruptlink2
2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1
2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2
2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3
2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time
2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low
2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi
2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1
2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2
2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode 
revision type
2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode 
version major
2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode 
version minor
2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version
2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board 
version
2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd
2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0
2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1
2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2
2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3
2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4
2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id
2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event
2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control
2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration
2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid
2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | 
l2p_addr_match
2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel
2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp
2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler
2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump:
2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 
0x004A, valid: 7
2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | 
ADVANCED_SYSASSERT
2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac 
branchlink1
2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac 
branchlink2
2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac 
interruptlink1
2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac 
interruptlink2
2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1
2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2
2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3
2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 0x0053 | umac major
2023-12-06T16:03:58,985191-06:00 iwlwifi :00:14.3: 0xE8F84E98 | umac minor
2023-12-06T16:03:58,985193-06:00 iwlwifi :00:14.3: 0x7C0B3384 | frame 
pointer
2023-12-06T16:03:58,985195-06:00 iwlwifi :00:14.3: 0xC0886BE0 | stack 
pointer
2023-12-06T16:03:58,985197-06:00 iwlwifi :00:14.3: 0x00ED019C | last host 
cmd
2023-12-06T16:03:58,985199-06:00 iwlwifi :00:14.3: 0x | isr status 
reg

[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup

[Michael Reed]

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
 Assignee: Jeff Lane  (bladernr)
   Status: Fix Released

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

Title:
  [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
  in UEFI setup

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:

  [  166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
  [  166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID 
  [  166.612445] DMAR: VT-d detected Invalidation Completion Error: SID 
  [  166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
  [  166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
  ...

  Additional info:
    * The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.

  Debugging info and fix commit info:
    * `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: 
Clean up domain before enumeration"). The root cause is that VMD driver tries 
to clear a PCI configuration space range when resetting a VMD domain 
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
 which leads to the failure.

  [Fix]
    * Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: 
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this 
commit can fix the issue.

  Would it be possible to include the commit 20f3337d350c in Ubuntu
  22.04.2/23.10 kernel?

  [Test Plan]

  Reproduce Step
  1.Disable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Disabled

  2.Install OS

  3.Enable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Enabled

  4.Rebooting will reproduce this issue

  [ Where problems could occur ]
  * Lenovo SE350 server and Lenovo SR850 v2 server
  * The regression leads to the boot failure (cannot boot info OS 
successfully). 

  [ Other Info ]
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022

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


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

[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

[Rodrigo]

I am using 545.23.08 and this problem is still affecting me. It's
surreal to buy a graphics card for over a thousand dollars and have the
drivers be unable to move a window without lag

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Fix Released
Status in metacity package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2045809] [NEW] Jammy update: v5.15.135 upstream stable release

[Kamal Mostafa]

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:

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

spi: zynqmp-gqspi: Convert to platform remove callback returning void
spi: zynqmp-gqspi: fix clock imbalance on probe failure
ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol
ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
NFS: Cleanup unused rpc_clnt variable
NFS: rename nfs_client_kset to nfs_kset
NFSv4: Fix a state manager thread deadlock regression
ring-buffer: remove obsolete comment for free_buffer_page()
ring-buffer: Fix bytes info in per_cpu buffer stats
arm64: Avoid repeated AA64MMFR1_EL1 register read on pagefault path
iommu/arm-smmu-v3: Set TTL invalidation hint better
iommu/arm-smmu-v3: Avoid constructing invalid range commands
rbd: move rbd_dev_refresh() definition
rbd: decouple header read-in from updating rbd_dev->header
rbd: decouple parent info read-in from updating rbd_dev
rbd: take header_rwsem in rbd_dev_refresh() only when updating
block: fix use-after-free of q->q_usage_counter
scsi: zfcp: Fix a double put in zfcp_port_enqueue()
qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info
wifi: mwifiex: Fix tlv_buf_left calculation
net: replace calls to sock->ops->connect() with kernel_connect()
net: prevent rewrite of msg_name in sock_sendmsg()
drm/amd: Fix detection of _PR3 on the PCIe root port
arm64: Add Cortex-A520 CPU part definition
HID: sony: Fix a potential memory leak in sony_probe()
ubi: Refuse attaching if mtd's erasesize is 0
wifi: iwlwifi: dbg_ini: fix structure packing
iwlwifi: avoid void pointer arithmetic
wifi: iwlwifi: mvm: Fix a memory corruption issue
wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet
bpf: Fix tr dereferencing
drivers/net: process the result of hdlc_open() and add call of hdlc_close() in 
uhdlc_close()
wifi: mt76: mt76x02: fix MT76x0 external LNA gain handling
regmap: rbtree: Fix wrong register marked as in-cache when creating new node
ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig
UBUNTU: [Config] updateconfigs for IMA_BLACKLIST_KEYRING
scsi: target: core: Fix deadlock due to recursive locking
ima: rework CONFIG_IMA dependency block
NFSv4: Fix a nfs4_state_manager() race
bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets
modpost: add missing else to the "of" check
net: fix possible store tearing in neigh_periodic_work()
ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
ptp: ocp: Fix error handling in ptp_ocp_device_init
net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is absent
net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg
net: nfc: llcp: Add lock when modifying device list
net: ethernet: ti: am65-cpsw: Fix error code in am65_cpsw_nuss_init_tx_chns()
ibmveth: Remove condition to recompute TCP header checksum.
netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp
netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure
ipv4: Set offload_failed flag in fibmatch results
net: stmmac: dwmac-stm32: fix resume on STM32 MCU
tipc: fix a potential deadlock on >lock
tcp: fix quick-ack counting to count actual ACKs of new data
tcp: fix delayed ACKs for MSS boundary condition
sctp: update transport state when processing a dupcook packet
sctp: update hb timer immediately after users change hb_interval
HID: sony: remove duplicate NULL check before calling usb_free_urb()
HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit
dm zoned: free dmz->ddev array in dmz_put_zoned_devices
RDMA/core: Require admin capabilities to set system parameters
of: dynamic: Fix potential memory leak in of_changeset_action()
IB/mlx4: Fix the size of a buffer in add_port_entries()
gpio: aspeed: fix the GPIO number passed to pinctrl_gpio_set_config()
gpio: pxa: disable pinctrl calls for MMP_GPIO
RDMA/cma: Initialize ib_sa_multicast structure to 0 when join
RDMA/cma: Fix truncation compilation warning in make_cma_ports
RDMA/uverbs: Fix typo of sizeof argument
RDMA/siw: Fix connection failure handling
RDMA/mlx5: Fix NULL string error
ksmbd: fix uaf in smb20_oplock_break_ack
parisc: Restore __ldcw_align for PA-RISC 2.0 processors
xen/events: replace evtchn_rwlock with RCU
Linux 5.15.135
UBUNTU: Upstream stable to v5.15.135

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

[Gordon Lack]

These messages get displayed when a btrfs file system is unmounted (note
they appear 16s after the mount, which would be the unmount).

I have one that is mounted (and unmounted) every 15 minutes and these
show up at every unmount.


[1254622.716595] BTRFS: device label Lacknet-Freq devid 1 transid 447446 
/dev/sdb1 scanned by (udev-worker) (641179)
[1255506.889750] BTRFS info (device sdb1): using crc32c (crc32c-intel) checksum 
algorithm
[1255506.889760] BTRFS info (device sdb1): disk space caching is enabled
[1255506.894559] BTRFS info (device sdb1): enabling ssd optimizations
[1255506.894565] BTRFS info (device sdb1): auto enabling async discard
[1255522.602675] evict_inodes inode d0474694, i_count = 1, was skipped!
[1255522.602679] evict_inodes inode eed5437e, i_count = 1, was skipped!
[1255522.602681] evict_inodes inode 34452673, i_count = 1, was skipped!
[1255522.602682] evict_inodes inode 6cef2072, i_count = 1, was skipped!
[1255522.602683] evict_inodes inode 37f015ca, i_count = 1, was skipped!
[1255522.602684] evict_inodes inode dcab3d4c, i_count = 1, was skipped!
[1255522.602685] evict_inodes inode 0267b235, i_count = 1, was skipped!
[1255522.602686] evict_inodes inode a76faacf, i_count = 1, was skipped!
[1255522.602687] evict_inodes inode 7448e65b, i_count = 1, was skipped!
[1255522.602688] evict_inodes inode 92488dbd, i_count = 1, was skipped!
[1255522.602689] evict_inodes inode 309d70e6, i_count = 1, was skipped!
[1255522.604942] evict_inodes inode 2f985da7, i_count = 1, was skipped!
[1255522.605046] evict_inodes inode 8c056c2d, i_count = 1, was skipped!
[1255522.768786] BTRFS: device label Lacknet-Freq devid 1 transid 447449 
/dev/sdb1 scanned by (udev-worker) (641763)
[1256406.952345] BTRFS info (device sdb1): using crc32c (crc32c-intel) checksum 
algorithm
[1256406.952355] BTRFS info (device sdb1): disk space caching is enabled
[1256406.960879] BTRFS info (device sdb1): enabling ssd optimizations
[1256406.960885] BTRFS info (device sdb1): auto enabling async discard
[1256422.696551] evict_inodes inode 1d632894, i_count = 1, was skipped!
[1256422.696556] evict_inodes inode f9a54040, i_count = 1, was skipped!
[1256422.696557] evict_inodes inode f6ce5746, i_count = 1, was skipped!
[1256422.696558] evict_inodes inode 49a39285, i_count = 1, was skipped!
.

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

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

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

Bug description:
  Hi,

  during boot the kernel logs the following messages:

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro 

[Kernel-packages] [Bug 2041996] Re: pwr-mlxbf: Several bug fixes for focal

[Feysel Mohammed]

** Tags removed: verification-needed-focal-linux-bluefield
** Tags added: verification-done-focal-linux-bluefield

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

Title:
  pwr-mlxbf: Several bug fixes for focal

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

Bug description:
  SRU Justification:

  [Impact]

  There is are several changes that needs to be made to pwr-mlxbf in focal:
  * There is a race condition between gpio-mlxbf2.c driver being loaded and 
pwr-mlxbf.c being loaded
  * When the module is removed, there is a panic due to NULL pointer access
  * soft reset needs to be replaced by graceful reboot

  [Fix]

  * Fix race condition between gpio-mlxbf2.c driver being loaded and 
pwr-mlxbf.c being loaded
  * Fix panic due to access to NULL pointer when driver is removed via rmmod
  * support graceful reboot instead of soft reset 

  [Test Case]

  * all test cases are for BF2:
  * trigger the gpio toggling from the BMC: ipmitool raw 0x32 0xA1 0x02
This should trigger a graceful reboot of the DPU.
  * rmmod/modprobe
  * reboot test and make sure the driver is always loaded

  [Regression Potential]

  * Run the 100 reboot test and make sure that the driver is loaded with
  no issues. That the gpio graceful reboot works.

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


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

[Kernel-packages] [Bug 2045806] [NEW] Mantic update: v6.5.7 upstream stable release

[Kamal Mostafa]

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:

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

ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol
ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
maple_tree: add mas_is_active() to detect in-tree walks
mptcp: Remove unnecessary test for __mptcp_init_sock()
mptcp: rename timer related helper to less confusing names
mptcp: fix dangling connection hang-up
scsi: core: Improve type safety of scsi_rescan_device()
scsi: Do not attempt to rescan suspended devices
ata: libata-scsi: Fix delayed scsi_rescan_device() execution
btrfs: remove btrfs_writepage_endio_finish_ordered
btrfs: remove end_extent_writepage
btrfs: don't clear uptodate on write errors
arm64: add HWCAP for FEAT_HBC (hinted conditional branches)
arm64: cpufeature: Fix CLRBHB and BC detection
net: add sysctl accept_ra_min_rtr_lft
net: change accept_ra_min_rtr_lft to affect all RA lifetimes
net: release reference to inet6_dev pointer
iommu/arm-smmu-v3: Avoid constructing invalid range commands
maple_tree: reduce resets during store setup
maple_tree: add MAS_UNDERFLOW and MAS_OVERFLOW states
iommu/apple-dart: Handle DMA_FQ domains in attach_dev()
scsi: zfcp: Fix a double put in zfcp_port_enqueue()
iommu/vt-d: Avoid memory allocation in iommu_suspend()
net: mana: Fix TX CQE error handling
net: ethernet: mediatek: disable irq before schedule napi
mptcp: fix delegated action races
mptcp: userspace pm allow creating id 0 subflow
qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info
Bluetooth: hci_codec: Fix leaking content of local_codecs
wifi: brcmfmac: Replace 1-element arrays with flexible arrays
Bluetooth: hci_sync: Fix handling of HCI_QUIRK_STRICT_DUPLICATE_FILTER
wifi: rtw88: rtw8723d: Fix MAC address offset in EEPROM
wifi: mwifiex: Fix tlv_buf_left calculation
md/raid5: release batch_last before waiting for another stripe_head
PCI/PM: Mark devices disconnected if upstream PCIe link is down on resume
PCI: qcom: Fix IPQ8074 enumeration
platform/x86/intel/ifs: release cpus_read_lock()
net: replace calls to sock->ops->connect() with kernel_connect()
btrfs: always print transaction aborted messages with an error level
net: prevent rewrite of msg_name in sock_sendmsg()
drm/i915: Don't set PIPE_CONTROL_FLUSH_L3 for aux inval
drm/amd: Fix detection of _PR3 on the PCIe root port
drm/amd: Fix logic error in sienna_cichlid_update_pcie_parameters()
arm64: Add Cortex-A520 CPU part definition
UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2966298
arm64: errata: Add Cortex-A520 speculative unprivileged load workaround
HID: sony: Fix a potential memory leak in sony_probe()
wifi: mt76: fix lock dependency problem for wed_lock
ubi: Refuse attaching if mtd's erasesize is 0
erofs: fix memory leak of LZMA global compressed deduplication
wifi: cfg80211/mac80211: hold link BSSes when assoc fails for MLO connection
iwlwifi: mvm: handle PS changes in vif_cfg_changed
wifi: iwlwifi: dbg_ini: fix structure packing
wifi: iwlwifi: mvm: Fix a memory corruption issue
wifi: cfg80211: fix cqm_config access race
rtla/timerlat_aa: Zero thread sum after every sample analysis
rtla/timerlat_aa: Fix negative IRQ delay
rtla/timerlat_aa: Fix previous IRQ delay for IRQs that happens after thread 
sample
wifi: cfg80211: add missing kernel-doc for cqm_rssi_work
wifi: mac80211: fix mesh id corruption on 32 bit systems
wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet
HID: nvidia-shield: add LEDS_CLASS dependency
erofs: allow empty device tags in flatdev mode
s390/bpf: Let arch_prepare_bpf_trampoline return program size
leds: Drop BUG_ON check for LED_COLOR_ID_MULTI
bpf: Fix tr dereferencing
bpf: unconditionally reset backtrack_state masks on global func exit
regulator: mt6358: split ops for buck and linear range LDO regulators
Bluetooth: Delete unused hci_req_prepare_suspend() declaration
Bluetooth: Fix hci_link_tx_to RCU lock usage
Bluetooth: ISO: Fix handling of listen for unicast
drivers/net: process the result of hdlc_open() and add call of hdlc_close() in 
uhdlc_close()
wifi: mt76: mt76x02: fix MT76x0 external LNA gain handling
perf/x86/amd/core: Fix overflow reset on hotplug
rtla/timerlat: Do not stop user-space if a cpu is offline
regmap: rbtree: Fix wrong register marked as in-cache when creating new node
wifi: mac80211: fix potential key use-after-free
perf/x86/amd: Do not WARN() on every IRQ
iommu/mediatek: Fix share pgtable for iova over 4GB
wifi: mac80211: Create resources for disabled links
regulator/core: regulator_register: set device->class earlier
ima: 

[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Adapters to 24.04 (patches in 6.8)

[Andy Gospodarek]

>> Is there any chance of these being backported upstream into 6.7?

Since this is new hardware support there is almost no chance it will be
added to upstream v6.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/2045796

Title:
  Add Support for Broadcom 5760X Adapters to 24.04 (patches in 6.8)

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

Bug description:
  These patches are needed on top of v6.7 to support Broadcom 5760X
  Adapters.  These patches currently reside in the net-next tree and
  will be included in v6.8.

  Prerequisite commits in net-next today:

  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for 
TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field

  These 13 patches below were submitted on 11/20/23 and accepted on
  11/21/23.  These are the initial patches with 5760X contents.

  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware 
calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
  035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
  76087d997a84 bnxt_en: Restructure context memory data structures
  e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
  aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free 
bp->ctx

  The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23.
  These are all the basic L2 patches for 5760X including the PCI IDs:

  2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
  047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware 
interface
  7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
  30c0bb63c2ea bnxt_en: Support new firmware link parameters
  cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
  a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types 
for P7
  39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
  c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
  13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions

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


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

[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Adapters

[Jeff Lane ]

Is there any chance of these being backported upstream into 6.7?

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

** Summary changed:

- Add Support for Broadcom 5760X Adapters
+ Add Support for Broadcom 5760X Adapters to 24.04 (patches in 6.8)

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

Title:
  Add Support for Broadcom 5760X Adapters to 24.04 (patches in 6.8)

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

Bug description:
  These patches are needed on top of v6.7 to support Broadcom 5760X
  Adapters.  These patches currently reside in the net-next tree and
  will be included in v6.8.

  Prerequisite commits in net-next today:

  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for 
TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field

  These 13 patches below were submitted on 11/20/23 and accepted on
  11/21/23.  These are the initial patches with 5760X contents.

  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware 
calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
  035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
  76087d997a84 bnxt_en: Restructure context memory data structures
  e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
  aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free 
bp->ctx

  The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23.
  These are all the basic L2 patches for 5760X including the PCI IDs:

  2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
  047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware 
interface
  7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
  30c0bb63c2ea bnxt_en: Support new firmware link parameters
  cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
  a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types 
for P7
  39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
  c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
  13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions

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


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

[Kernel-packages] [Bug 2045796] [NEW] Add Support for Broadcom 5760X Adapters

[Andy Gospodarek]

Public bug reported:

These patches are needed on top of v6.7 to support Broadcom 5760X
Adapters.  These patches currently reside in the net-next tree and will
be included in v6.8.

Prerequisite commits in net-next today:

c1056a59aee1 bnxt_en: Optimize xmit_more TX path
ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
f07b58801bef bnxt_en: Add macros related to TC and TX rings
f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX 
rings
0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
5a3c585fa83f bnxt_en: New encoding for the TX opaque field
ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field

These 13 patches below were submitted on 11/20/23 and accepted on
11/21/23.  These are the initial patches with 5760X contents.

1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
c09d22674b94 bnxt_en: Modify RX ring indexing logic.
6d1add95536b bnxt_en: Modify TX ring indexing logic.
b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct.
236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware 
calls
6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
76087d997a84 bnxt_en: Restructure context memory data structures
e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free 
bp->ctx

The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23.
These are all the basic L2 patches for 5760X including the PCI IDs:

2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware 
interface
7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
30c0bb63c2ea bnxt_en: Support new firmware link parameters
cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for 
P7
39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions

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

Title:
  Add Support for Broadcom 5760X Adapters

Status in linux package in Ubuntu:
  New

Bug description:
  These patches are needed on top of v6.7 to support Broadcom 5760X
  Adapters.  These patches currently reside in the net-next tree and
  will be included in v6.8.

  Prerequisite commits in net-next today:

  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for 
TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field

  These 13 patches below were submitted on 11/20/23 and accepted on
  11/21/23.  These are the initial patches with 5760X contents.

  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware 
calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in 

[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

[Manuel Diewald]

dpkg -X linux-buildinfo-6.2.0-1020-gcp_6.2.0-1020.22_arm64.deb unpack
grep wwan unpack/usr/lib/linux/6.2.0-1020-gcp/modules
...
wwan
wwan_hwsim

** Tags removed: verification-needed-lunar-linux-gcp
** Tags added: verification-done-lunar-linux-gcp

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

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

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

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


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

[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids

[Manuel Diewald]

Installed linux-tools-6.2.0-1020-gcp from lunar-proposed and verified
that hwdata is installed as a dependency.

** Tags removed: verification-needed-lunar-linux-gcp
** Tags added: verification-done-lunar-linux-gcp

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

Title:
  usbip: error: failed to open /usr/share/hwdata//usb.ids

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

Bug description:
  [Impact]

  usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which
  is provided by the hwdata package which is not installed by default.

  $ usbip list -l
  usbip: error: failed to open /usr/share/hwdata//usb.ids
   - busid 1-1.1.1 (0424:7800)
     unknown vendor : unknown product (0424:7800)

  [Test Case]

  $ apt install linux-tools-
  $ usbip list -l
   - busid 1-1.1.1 (0424:7800)
 Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800)

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

  A trivial package (hwdata) is installed as a dependency. Can't think
  of any problems this could cause other than a theoretical package
  installation failure.

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


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

[Mike Ferreira]

@xnox --

Thank you!!!

This is what I see in Noble right now:
>>>
mafoelffen@noble-d05:~$ apt list -a zfsutils-linux
Listing... Done
zfsutils-linux/noble-proposed 2.2.2-0ubuntu1 amd64
zfsutils-linux/noble,now 2.2.1-0ubuntu1 amd64 [installed]
>>>
So it 2.2.1 got pushed to Noble main, with 2.2.2 to Noble Proposed (so far)...

Rick S and I can start testing/verifying that today from Noble Proposed.

Any idea on when it might hit the Snap 'ubuntu-desktop-installer' beta
channel, so we can start testing it in the Noble installer?

-- 
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 Committed
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:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

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

  [ 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

[Andre Ruiz]

@Bartosz

$ ethtool -i enp65s0f0 |grep firmware-version
firmware-version: 4.20 0x8001784b 22.0.9

This is the latest firmware supported by Dell. You will find 4.3
available on Intel website, but it is not available yet through dell
firmware tools.

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

Bug description:
  
  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: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 15 03:13 seq
   crw-rw 1 root audio 116, 33 Sep 15 03:13 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: Cannot stat file /proc/215602/fd/10: Permission denied
   Cannot stat file /proc/323635/fd/10: Permission denied
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.3.4.7:5248/MAAS/metadata/)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'

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

[Dimitri John Ledkov]

** Changed in: zfs-linux (Ubuntu Mantic)
   Status: Confirmed => In Progress

-- 
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 Committed
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:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  In Progress
Status in zfs-linux source package in Noble:
  Fix Committed

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

  [ 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 1199217] Re: Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer) [pnp:8810] cannot be detected at all

[Rehan Shakeel]

I'm here to help, whether you need expert camping gear or specific guidance.
 https://camping-pantheratec.com/collections/spulen-waschbecken

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

Title:
  Dell laptops' ST Microelectronics Free Fall Sensor (accelerometer)
  [pnp:8810] cannot be detected at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201201-10339 Dell Latitude E6530 [1]
  CID: 201307-13941 Dell Latitude E5440 [2]

  According to the information provided by Dell, these systems should have an 
accelerometer on the motherboard (Free-Fall sensor), but it cannot be detected 
at all
  (cannot be found in  /proc/bus/input/devices)

  If using windows, it shows ACPI/SMO8810 in device manager
  If you run "lspnp", you can see: 
  00:0c SMO8810 (unknown)

  [1] 
http://www.dell.com/downloads/global/products/latit/dell_latitude_e6530_spec_sheet.pdf
  [2] http://www.dell.com/us/business/p/latitude-e5440-laptop/pd

  This issue has also been verified with 12.04.4, see bug 1310879

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1635 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 49'
     Mixer name : 'IDT 92HD93BXX'
     Components : 'HDA:111d76df,10280535,00100203 
HDA:14f12c06,14f1000f,0010'
     Controls  : 20
     Simple ctrls  : 10
  Date: Tue Jul  9 11:09:52 2013
  HibernationDevice: RESUME=UUID=8ee31955-e727-4041-b013-ddde9c2533a6
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=81b802b0-1e06-43e7-8c92-b241adf7768c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/19/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2045778] [NEW] panic due to unhandled page fault via BPF_PROG_RUN syscall

[Lorenz Bauer]

Public bug reported:

Here is a kernel oops triggered from user space by invoking a BPF
program:

[ 1191.051531] BUG: unable to handle page fault for address: ea053c70
[ 1191.053848] #PF: supervisor read access in kernel mode
[ 1191.055183] #PF: error_code(0x) - not-present page
[ 1191.056513] PGD 334e15067 P4D 334e15067 PUD 334e17067 PMD 0 
[ 1191.058016] Oops:  [#1] SMP NOPTI
[ 1191.058984] CPU: 1 PID: 2557 Comm: ebpf.test Not tainted 6.2.0-1016-azure 
#16~22.04.1-Ubuntu
[ 1191.061167] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
[ 1191.063804] RIP: 0010:bpf_test_run+0x104/0x2e0
[ 1191.065064] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89 10
[ 1191.069766] RSP: 0018:a64e03053c50 EFLAGS: 00010246
[ 1191.071117] RAX: 0001 RBX: a64e0005a000 RCX: a64e03053c3f
[ 1191.073415] RDX: 0001 RSI: a64e03053c3f RDI: 8a468580
[ 1191.075351] RBP: ea053cf0 R08:  R09: 
[ 1191.077722] R10:  R11:  R12: 97dc75673c00
[ 1191.079681] R13: a64e0005a048 R14: a64e03053d34 R15: 0001
[ 1191.081636] FS:  7fd4a2ffd640() GS:97df6fc8() 
knlGS:
[ 1191.083866] CS:  0010 DS:  ES:  CR0: 80050033
[ 1191.085455] CR2: ea053c70 CR3: 00019ff80001 CR4: 00370ee0
[ 1191.087405] Call Trace:
[ 1191.088121]  
[ 1191.088745]  ? show_regs+0x6a/0x80
[ 1191.089710]  ? __die+0x25/0x70
[ 1191.090591]  ? page_fault_oops+0x79/0x180
[ 1191.091708]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.093027]  ? search_exception_tables+0x61/0x70
[ 1191.094421]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.095686]  ? kernelmode_fixup_or_oops+0xa2/0x120
[ 1191.097014]  ? __bad_area_nosemaphore+0x16f/0x280
[ 1191.098323]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.099584]  ? apparmor_file_alloc_security+0x1f/0xd0
[ 1191.100989]  ? bad_area_nosemaphore+0x16/0x20
[ 1191.102235]  ? do_kern_addr_fault+0x62/0x80
[ 1191.103393]  ? exc_page_fault+0xd8/0x160
[ 1191.104505]  ? asm_exc_page_fault+0x27/0x30
[ 1191.105669]  ? bpf_test_run+0x104/0x2e0
[ 1191.106745]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.108010]  ? bpf_prog_test_run_skb+0x2e4/0x4f0
[ 1191.109350]  ? __fdget+0x13/0x20
[ 1191.110304]  ? __sys_bpf+0x706/0xea0
[ 1191.111299]  ? __x64_sys_bpf+0x1a/0x30
[ 1191.112307]  ? do_syscall_64+0x5c/0x90
[ 1191.113366]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.114634]  ? exit_to_user_mode_loop+0xec/0x160
[ 1191.115929]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.117466]  ? __set_task_blocked+0x29/0x70
[ 1191.118904]  ? exit_to_user_mode_prepare+0x49/0x100
[ 1191.120482]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.122073]  ? sigprocmask+0xb8/0xe0
[ 1191.123360]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.124868]  ? exit_to_user_mode_prepare+0x49/0x100
[ 1191.126523]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.128028]  ? syscall_exit_to_user_mode+0x27/0x40
[ 1191.129599]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.131033]  ? do_syscall_64+0x69/0x90
[ 1191.132242]  ? srso_alias_return_thunk+0x5/0x7f
[ 1191.134199]  ? do_syscall_64+0x69/0x90
[ 1191.135504]  ? entry_SYSCALL_64_after_hwframe+0x73/0xdd
[ 1191.137137]  
[ 1191.137942] Modules linked in: nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp 
llc xt_tcpudp tls xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink overlay nvme_fabrics 
udf crc_itu_t binfmt_misc nls_iso8859_1 kvm_amd ccp joydev kvm hid_generic 
irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd hyperv_drm 
drm_kms_helper syscopyarea sysfillrect serio_raw sysimgblt drm_shmem_helper 
hid_hyperv hv_netvsc hid hyperv_keyboard pata_acpi dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua sch_fq_codel drm efi_pstore i2c_core ip_tables 
x_tables autofs4
[ 1191.156484] CR2: ea053c70
[ 1191.158026] ---[ end trace  ]---
[ 1191.159518] RIP: 0010:bpf_test_run+0x104/0x2e0
[ 1191.160912] Code: 00 00 48 89 90 50 14 00 00 48 89 b5 60 ff ff ff eb 3e 0f 
1f 44 00 00 48 8b 53 30 4c 89 ee 4c 89 e7 e8 50 8c f8 ff 89 c2 66 90 <48> 8b 45 
80 4d 89 f0 48 8d 4d 8c be 01 00 00 00 48 8d 7d a0 89 10
[ 1191.166336] RSP: 0018:a64e03053c50 EFLAGS: 00010246
[ 1191.168046] RAX: 0001 RBX: a64e0005a000 RCX: a64e03053c3f
[ 1191.170129] RDX: 0001 RSI: a64e03053c3f RDI: 8a468580
[ 1191.172210] RBP: ea053cf0 R08:  R09: 
[ 1191.174546] R10:  R11:  R12: 97dc75673c00
[ 1191.176719] R13: a64e0005a048 R14: a64e03053d34 R15: 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Bartosz Woronicz]

What is the cards firmware ?

$ ethtool -i  |grep firmware-version

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

Bug description:
  
  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: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 15 03:13 seq
   crw-rw 1 root audio 116, 33 Sep 15 03:13 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: Cannot stat file /proc/215602/fd/10: Permission denied
   Cannot stat file /proc/323635/fd/10: Permission denied
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.3.4.7:5248/MAAS/metadata/)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7525
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 

[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device

[Artur Pak]

Below was performed to verify the -proposed package.

1. Reproduce the problem: used the same environment as in description
- downgrade the package to 1.2.6.3-1ubuntu1.8
- remove file: /var/lib/alsa/asound.state
- power off the machine (not reboot) and power up again
- verify no sound (play youtube)

2. Install jammy-proposed 1.2.6.3-1ubuntu1.9 and verify the same test cases as 
in description:
- sound can play
- $ sudo alsactl init - does not throw any errors
- $ amixer contents values=on

3. Power cycle and check if any regressions:
- power off and on again
- sound can play
- adjust sound lower/higher works
- $ sudo alsactl init - does not throw any errors

Same steps were performed for mantic-proposed 1.2.9-1ubuntu3.1 and
lunar-proposed 1.2.6.3-1ubuntu9.3.

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

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

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

Title:
  ucm2: soundwire: add rt713 SDCA device

Status in OEM Priority Project:
  In Progress
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed
Status in alsa-ucm-conf source package in Mantic:
  Fix Committed
Status in alsa-ucm-conf source package in Noble:
  Fix Released

Bug description:
  [ Impact ]
  Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack 
Codec-ALC713.
  Without correct configurations in userspace above codecs cannot be used. Thus 
in Settings > Sound > Output test doesn't produce sounds and Input device is 
greyed out.

  [ Fix ]
  Adding rt713 config files in ucm2 will allow to utilize those codecs.
  Upstream commit added support: 
https://github.com/alsa-project/alsa-ucm-conf/pull/363

  [ Test Plan ]
  Device with the soundwire card

  $ cat /proc/asound/cards
   0 [sofsoundwire   ]: sof-soundwire - sof-soundwire
    Intel Soundwire SOF

  Before fix:

  1. $ alsactl init
  alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration 
file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf
  alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file 
/usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2
  alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -2
  Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" 
"HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 
mic:rt713-dmic" "" ""
  Hardware is initialized using a generic method

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off

  After fix: after adding patch files

  1. $ alsactl init
  alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf 
/var/lib/alsa/card0.conf.d' failed (exit code 1)

  (note: assuming that failed to remove the empty directory is not a
  critical problem)

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on

  [Where problems could occur]

   * This change adds new hardware support.

   * The change only adds new hardware support,
     it will not affect other codec device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions


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

[Dimitri John Ledkov]

** Description changed:

- OpenZFS linux kernel module currently has multiple potential data
- corruption issues identified to have been present since at least 0.6
- (?!).
+ [ Impact ]
  
- This bug report will track upgrades to releases 2.2.2, OR 2.1.14, OR
- backport/cherry-pick of dirty dnode patch.
+  * 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).
+ 
+ [ 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

-- 
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 Committed
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:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  Confirmed
Status in zfs-linux source package in Noble:
  Fix Committed

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

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

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

[Dimitri John Ledkov]

Please use 22-hwe/stable if you can, please let us know if that's
acceptable.

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [ Impact ]

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

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

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

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

  [ Test Plan ]

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

  [ Where problems could occur ]

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

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

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


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

[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression

[Dmitriy Rabotyagov]

Eventually, I see failures even with kernel 5.15.0-84-generic which
means there's smth else involved then commits in question, as they
shouldn't be there yet.

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

Title:
  5.15.0-85 live migration regression

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

Bug description:
  
  Fixes added for LP 2032164 [0] to resolve an issue in live migration have 
  unfortunately introduced a regression, causing a previously working live 
  migration pattern to fail when tested with the 5.15.0-85 kernel from 
-proposed.

  Specifically, live migration from a PKRU-enabled host running a kernel older
  than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail.  The
  destination can be either with or without PKRU; both cases fail, although
  in different ways (one hangs, the other fails due to a PCID flag issue).

  The commits in question are

  commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0
  Author: Dr. David Alan Gilbert 
  Date:   Mon Aug 21 14:47:28 2023 +0800

  KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES

  commit 27a189b881278c8ad9c16b0ee05668d724352733
  Author: Leonardo Bras 
  Date:   Mon Aug 21 14:47:27 2023 +0800

  x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0

  
  [0]   https://bugs.launchpad.net/bugs/2032164

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


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

[Kernel-packages] [Bug 2045694] Re: package linux-headers-6.5.0-14-generic 6.5.0-14.14 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.5.0-14-generic script post-insta

[Juerg Haefliger]

Building module:
Cleaning build area...
'make' -j4 KVER=6.5.0-14-generic..(bad exit status: 2)
ERROR (dkms apport): binary package for rtl8821ce: v5.5.2_34066.20200325 not 
found
Error! Bad return status for module build on kernel: 6.5.0-14-generic (x86_64)
Consult /var/lib/dkms/rtl8821ce/v5.5.2_34066.20200325/build/make.log for more 
information.
dkms autoinstall on 6.5.0-14-generic/x86_64 failed for rtl8821ce(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/2045694

Title:
  package linux-headers-6.5.0-14-generic 6.5.0-14.14 failed to
  install/upgrade: il sottoprocesso installato pacchetto linux-
  headers-6.5.0-14-generic script post-installation ha restituito lo
  stato di errore 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  non installa aggiornamento google chrome

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicola 2482 F wireplumber
   /dev/snd/seq:nicola 2469 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Tue Dec  5 21:33:41 2023
  ErrorMessage: il sottoprocesso installato pacchetto 
linux-headers-6.5.0-14-generic script post-installation ha restituito lo stato 
di errore 1
  InstallationDate: Installed on 2020-09-24 (1167 days ago)
  InstallationMedia: Ubuntu 20.04.0 LTS "Focal Fossa" (20200917)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=a59f5b1e-c2d3-4d62-9639-811cc7db604a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  SourcePackage: linux
  Title: package linux-headers-6.5.0-14-generic 6.5.0-14.14 failed to 
install/upgrade: il sottoprocesso installato pacchetto 
linux-headers-6.5.0-14-generic script post-installation ha restituito lo stato 
di errore 1
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (30 days ago)
  dmi.bios.date: 09/19/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL116
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL116:bd09/19/2020:br5.13:svnMicrotech:pnCoreBookLite:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuCBL15:
  dmi.product.family: Default string
  dmi.product.name: CoreBookLite
  dmi.product.sku: CBL15
  dmi.product.version: Default string
  dmi.sys.vendor: Microtech

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


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

[Kernel-packages] [Bug 2045694] Re: package linux-headers-6.5.0-14-generic 6.5.0-14.14 failed to install/upgrade: il sottoprocesso installato pacchetto linux-headers-6.5.0-14-generic script post-insta

[Juerg Haefliger]

You have an unsupported DKMS installed that breaks the kernel header
installation.

$ dkms remove rtl8821ce/v5.5.2_34066.20200325


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

Title:
  package linux-headers-6.5.0-14-generic 6.5.0-14.14 failed to
  install/upgrade: il sottoprocesso installato pacchetto linux-
  headers-6.5.0-14-generic script post-installation ha restituito lo
  stato di errore 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  non installa aggiornamento google chrome

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicola 2482 F wireplumber
   /dev/snd/seq:nicola 2469 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Tue Dec  5 21:33:41 2023
  ErrorMessage: il sottoprocesso installato pacchetto 
linux-headers-6.5.0-14-generic script post-installation ha restituito lo stato 
di errore 1
  InstallationDate: Installed on 2020-09-24 (1167 days ago)
  InstallationMedia: Ubuntu 20.04.0 LTS "Focal Fossa" (20200917)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=a59f5b1e-c2d3-4d62-9639-811cc7db604a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  SourcePackage: linux
  Title: package linux-headers-6.5.0-14-generic 6.5.0-14.14 failed to 
install/upgrade: il sottoprocesso installato pacchetto 
linux-headers-6.5.0-14-generic script post-installation ha restituito lo stato 
di errore 1
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (30 days ago)
  dmi.bios.date: 09/19/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL116
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL116:bd09/19/2020:br5.13:svnMicrotech:pnCoreBookLite:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuCBL15:
  dmi.product.family: Default string
  dmi.product.name: CoreBookLite
  dmi.product.sku: CBL15
  dmi.product.version: Default string
  dmi.sys.vendor: Microtech

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


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

[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression

[Dmitriy Rabotyagov]

Folks, is there any way to revive the patch and see actual source code of the 
change proposed here?
As I assume the bug was closed due to inactivity, but I'm quite ready to test 
it out.

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

Title:
  5.15.0-85 live migration regression

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

Bug description:
  
  Fixes added for LP 2032164 [0] to resolve an issue in live migration have 
  unfortunately introduced a regression, causing a previously working live 
  migration pattern to fail when tested with the 5.15.0-85 kernel from 
-proposed.

  Specifically, live migration from a PKRU-enabled host running a kernel older
  than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail.  The
  destination can be either with or without PKRU; both cases fail, although
  in different ways (one hangs, the other fails due to a PCID flag issue).

  The commits in question are

  commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0
  Author: Dr. David Alan Gilbert 
  Date:   Mon Aug 21 14:47:28 2023 +0800

  KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES

  commit 27a189b881278c8ad9c16b0ee05668d724352733
  Author: Leonardo Bras 
  Date:   Mon Aug 21 14:47:27 2023 +0800

  x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0

  
  [0]   https://bugs.launchpad.net/bugs/2032164

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


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

[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

[Leon Lessing]

I am using an HP G3 450 with 6th gen i7
I have tried it all
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 
intel_idle.max_cstate=2"

Kernels up to 6.6.4

It does not work, external monitor flashes like a disco.

I cannot believe this issue is years old already on the i915 gfx

uname -a
Linux lap5 6.6.4-060604-generic #202312030734 SMP PREEMPT_DYNAMIC Sun Dec  3 
07:46:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

lshw | grep -A2 display
*-display
 description: VGA compatible controller
 product: Skylake GT2 [HD Graphics 520]

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-hwe-5.19 source package in Lunar:
  Invalid
Status in linux-hwe-6.2 source package in Lunar:
  Invalid

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel parameter i915.enable_dc=0 intel_idle.max_cstate=2
  fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
    lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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


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

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

[Dimitri John Ledkov]

** Description changed:

+ [ Impact ]
+ 
+  * Multiple kernel flavours are conflicting with each on .deb / file
+ level via their tools packages
+ 
+  * Resolve the conflicting private libcpupower.so by statically linking
+ it into the only C binary that uses said library in the linux-tools
+ 
+ [ Test Plan ]
+ 
+  * co-install tools packages from multiple kernel flavours of the same
+ major version and abi, it should be successful
+ 
+ [ Where problems could occur ]
+ 
+  * If one tries really hard to find the private location of
+ libcpupower.so and dlopen it by ever changing abi name, that will not be
+ possible, until the separate bug report is fixed to introduce the public
+ stable libcpupower.so.1 which so far ubuntu has never yet provided.
+ 
+ [ Other Info ]
+  
+  * original bug report
+ 
  Taking linux-kvm and linux-gcp for example:
  
  $ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103384 2023-07-25 20:00 
./usr/lib/libcpupower.so.6.2.0-1011
  $ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103392 2023-08-16 15:08 
./usr/lib/libcpupower.so.6.2.0-1011
  
  linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain a
  libcpupower.so.6.2.0-1011 shared library used by their own cpupower
  utilities, and yet files of the same full path cannot be installed from
  two distinct debian packages, which follows we won't be able to install
  two linux-tools packages of two different derived kernels on the same
  system.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
  Uname: Linux 6.5.0-9004-generic x86_64
  NonfreeKernelModules: zfs wl
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  vicamo 6331 F wireplumber
-  /dev/snd/controlC0:  vicamo 6331 F wireplumber
-  /dev/snd/seq:vicamo 6315 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  vicamo 6331 F wireplumber
+  /dev/snd/controlC0:  vicamo 6331 F wireplumber
+  /dev/snd/seq:vicamo 6315 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Sep 14 23:31:16 2023
  InstallationDate: Installed on 2022-04-10 (522 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic 
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
-  linux-restricted-modules-6.5.0-9004-generic N/A
-  linux-backports-modules-6.5.0-9004-generic  N/A
-  linux-firmware  20230815.git0e048b06-0ubuntu1
+  linux-restricted-modules-6.5.0-9004-generic N/A
+  linux-backports-modules-6.5.0-9004-generic  N/A
+  linux-firmware  20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.60.3.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

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

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

  [ Test Plan ]

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

  [ Where problems could occur ]

   * If one tries 

[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final

[Dimitri John Ledkov]

Note the 10.30 cycle mantic kernels were built with this zfs-linux dkms
prebuilt, vendored in, and passing kernel regresstion testing, adt-
matrix testing and so on, for all kernels.

Mantic kernels that contain this update of zfs.ko have now been mostly
released.

 * autopkgtest pass

As seen on 
https://ubuntu-archive-team.ubuntu.com/proposed-migration/mantic/update_excuses.html#zfs-linux
And due to lack of automated comments of autopkgtest regressions
And also via adt matrix at for example 
https://kernel.ubuntu.com/adt-matrix/mantic-linux-meta.html for zfs-linux 
results with generic kernel, but also all other mantic kernels.

 * kernel regression zfs testsuite pass

(Canonical only URL i believe) http://10.246.75.167/2023.10.30/tc-stats-
lvl1.html shows all RT testing stats for the 2013.10.30 cycle, and you
can see that zfs ones are all green (apart from one stress-ng test case
which seems to have passed, but failed to clean up with a timeout, and
is being investigated). Clicking through to the zfs test case name you
can see break-down of tests per release / kernel flavour / target
hardware / arch etc. For this SRU only mantic one matters.

 * zsys integration test pass

Tested that existing installs upgrade fine, and new ones are also
possible by upgrading zfs-linux userspace tooling in live desktop
session to proposed.

 * LXD support retested

That was done by lxd team, and they have shipped upgrade to 2.0 final
inside lxd snap already.

In practice this SRU is already released to most users via LXD and via
kernel upgrades. The change this sru release will introduce is userspace
tooling update, which was minor in this update.

Note there will be a new zfs-linux sru, right after this one to address
the recently identified and patched up issues. See
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657

It is still worth it to release this sru, before staging the next one in
proposed.

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

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

Title:
  upgrade zfs-linux to 2.2.0 final

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

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  [ Where problems could occur ]

   * LXD snap in edge shipped zfs tooling of RC5 version until 16th
  October when they upgraded to 2.2.0 final, there are no kernel-
  userspace incompatiblities between RC & final, but we should
  explicitly test this.

  [ Other Info ]

   * Upstream is alerting us to the potential data loss and requesting
  upgrade to 2.2.0-rc5 or better.

  [ Abbriviated changes being introduced ]

  $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
  810fc49a3e Ensure we call fput when cloning fails due to different devices.
  a80e1f1c90 zvol: Temporally disable blk-mq
  33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
  8015e2ea66 Add '-u' - nomount flag for zfs set
  c53bc3837c Improve the handling of sharesmb,sharenfs properties
  e9dc31c74e Update the behavior of mountpoint property
  608741d062 Report ashift of L2ARC devices in zdb
  0ce1b2ca19 Invoke zdb by guid to avoid import errors
  0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
  a199cac6cd status: report pool suspension state under failmode=continue
  729507d309 Fix occasional rsend test crashes
  3af63683fe cmd: add 'help' subcommand to zpool and zfs
  9aa1a2878e Fix incorrect expected error in ztest
  f7a07d76ee Retire z_nr_znodes
  54c6fbd378 zed: Allow autoreplace and fault LEDs for 

[Kernel-packages] [Bug 2038859] Re: No driver for 14c3:7902

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  No driver for 14c3:7902

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

Bug description:
  I bought a new Asus Vivobook Notebook X1504ZA-NJ205 and installed ubuntu on 
it, but I couldn't use my wifi card: Network controller [0280]: MEDIATEK Corp. 
Device [14c3:7902].
  After posting on that on the Ubuntu forum someone suggested me to file a bug 
report: https://ubuntuforums.org/showthread.php?t=2490705=14157764 so that's 
what I'm doing now.
  Can you please write a driver for this card?
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 21:51:08 2023
  InstallationDate: Installed on 2023-09-08 (31 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-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] Trace of NFSv4 server

[bugproxy]

--- Comment on attachment From jrum...@uk.ibm.com 2023-12-06 04:38 
EDT---


AIX NFS client returns ESTALE at approximately 11:17:24.

** Attachment added: "Trace of NFSv4 server"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5726664/+files/syslog_amaliada_trace_nfsv4_debug.zip

-- 
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 2031412] Re: Support mipi camera on Intel Meteor Lake platform

[Viral Wang]

We will fix lp:2044991 in a separate SRU cycle run, please proceed the
SRU cycle for lp:2031412 first. Thank you!

LP#2031412
- ipu6
  - noble: done
  - mantic: to be submitted into -proposed for review
- ivsc
  - noble: done
  - mantic: already in -proposed, verified, should move to -updates in a couple 
days
LP#2044991
- ipu6:
  - noble: to create debdiff when LP#2031412 in -proposed
  - mantic: TBD.
- ivsc
  - noble: nothing blocked. WIP
  - mantic: TBD

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  In Progress
Status in ivsc-driver source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

  Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on
  MTL.

  [Fix]