date:20240417

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

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

Title:
  panel flickering after the i915.psr2 is enabled

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

Bug description:
  SRU verificaton for Noble and oem-6.8-noble:

  [Impact]
  In Dell oem project, we found the graphic is flickering on some
  machines, finally we narrowed down the issue on (some specific panels +
  i915.psr2 enabled), and the issue was reported to Intel, Intel fixed
  the issue in the most recent mainline kernel. Here backporting the
  patches to Noble kernel.

  It is hard to backport the patches to mantic and oem-6.5, so we wrote
  a workaround patch to disable the psr2 for those pannels in the oem-6.5.

  https://gitlab.freedesktop.org/drm/intel/-/issues/9739

  [Fix]
  cherry-pick 8 patches from mainline kernel

  [Test]
  I applied the patches to Noble kernel and built a testing kernel, and
  Dell validated the testing kernel on those machines, the graphic
  didn't flicker anymore.

  I installed the testing kernel on some machines with Intel 13th, 12th
  11th and 10th gen cpu, the grahic worked well too.

  [Where problems could occur]
  This patchset changes the fast wake settings for some gpu, it is
  possible to make the graphic flicker, but this possibility is very
  low, since the patchset comes from mainline kernel and we validated
  the patchset on different gens of Intel cpus.

  ===

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

  [Impact]
  On serveral Dell laptops, the screen often displays garbage or the screen is 
flicking

  This PR is just a workaround, the upstream bug is here:
  https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863

  After the upstream fix this bug with a real fix, I will revert the
  workaround and backport the real fix to Noble and Jammy oem-kernel.

  [Fix]
  There is no real fix so far, ODM recommends to use a workaround to disable 
PSR2, this is a temp solution, after we get the real fix, we could revert the 
temp workaround.

  [Test case]

  booting with the patched kernel, If the pannel's edid is in the qurik
  list, the PSR2 will be disabled (checking
  /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is
  not in the quirk list, the graphic driver will work as before.

  [Where problems could occur]
  It is possible that the temp solution couldn't work, then the screen will 
still show garbage and the screen is flicking, another possible regression is 
the screen has no problem before, but after running patched kernel, the PSR2 is 
disabled and the system cost more power, but this possibility is very low, I 
tested the patched on some dell machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2061953] Re: intel_rapl_common: Add support for ARL and LNL

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

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

Title:
  intel_rapl_common: Add support for ARL and LNL

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.8 package in Ubuntu:
  Fix Committed
Status in linux source package in Noble:
  New
Status in linux-oem-6.8 source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  The installer doesn't work without blacklisting intel_rapl_common
  (snap mounts fail), unless these commits are added.

  Needs a oneliner fix for both platforms:

  4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake
  876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform

  [Test case]

  Check that snaps work.

  [Regression potential]

  Can't regress other platforms, and if these would then fail in other
  ways, it's still likely better than before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061953/+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 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

https://kernel.ubuntu.com/gitea/kernel/kernel-versions/pulls/290

** Changed in: linux-oem-6.8 (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  obsolete out-of-tree ivsc dkms in favor of in-tree one

Status in ipu6-drivers package in Ubuntu:
  New
Status in ivsc-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.8 package in Ubuntu:
  Fix Released
Status in ipu6-drivers source package in Noble:
  New
Status in ivsc-driver source package in Noble:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.8 source package in Noble:
  Fix Released

Bug description:
  Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel
  demands the use of in-tree IVSC drivers instead of out-of-tree dkms
  from https://github.com/intel/ivsc-driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 2062113] [NEW] CIFS SMB does not work on linux-image-5.15.0-102-generic

2024-04-17 Thread Marcus Linux

Public bug reported:

SMB is not working on this kernel version.
I keep getting: [error] Resource temporarily unavailable
The only way I was able to fix it was downgrading the kernel back to 
linux-image-5.15.0-101-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-102-generic 5.15.0-102.112
ProcVersionSignature: Ubuntu 5.15.0-102.112-generic 5.15.148
Uname: Linux 5.15.0-102-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-102-generic.
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/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Apr 18 04:41:33 2024
InstallationDate: Installed on 2024-04-18 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 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=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-102-generic 
root=UUID=fda03d5c-0b7d-49cd-a9b9-7786964456a7 ro
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-102-generic N/A
 linux-backports-modules-5.15.0-102-generic  N/A
 linux-firmware  20220329.git681281e4-0ubuntu3.29
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  CIFS SMB does not work on linux-image-5.15.0-102-generic

Status in linux package in Ubuntu:
  New

Bug description:
  SMB is not working on this kernel version.
  I keep getting: [error] Resource temporarily unavailable
  The only way I was able to fix it was downgrading the kernel back to 
linux-image-5.15.0-101-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-102-generic 5.15.0-102.112
  ProcVersionSignature: Ubuntu 5.15.0-102.112-generic 5.15.148
  Uname: Linux 5.15.0-102-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-102-generic.
  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/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Thu Apr 18 04:41:33 2024
  InstallationDate: Installed on 2024-04-18 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus

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

** Attachment added: "RENEW packets between 9.20.32.85 (server) and 
9.20.120.127 (7.2 client)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+attachment/5767206/+files/7.2nfs.png

-- 
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 2042363] Re: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 ser

** Attachment added: "packets for 9.20.32.85 (server) and 9.20.120.112 (7.3 
client)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+attachment/5767207/+files/7.3nfs.png

-- 
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 2042363] Re: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 ser

Sorry, I can't distinguish which parts of logs in the attachments
(#comment11, #comment12 and #comment13) are belong to the connection
from working 7.2 and non-working 7.3. All the attachments have "TCP
recvfrom got EAGAIN" which should from the connection for 7.3.

$ grep "TCP recvfrom got EAGAIN" 
syslog_16042024_amaliada_primary_adamsongrunter_partner_both_aix73_part1.log 
-r|wc -l
213127
$ grep "TCP recvfrom got EAGAIN" 
syslog_16042024_amaliada_primary_adamsongrunter_partner_both_aix73_part2.log 
-r|wc -l
226005
$ grep "TCP recvfrom got EAGAIN" 
syslog_17042024_adia_primary_amberjack_partner_both_aix72.log -r|wc -l
20233


May I suggest to collect those logs in two separated files? One from 7.2 and 
another from 7.3 instead of mix them together.

Not an network expert, but I see some NFS RENEW ops packets between
9.20.32.85 (server) and 9.20.120.127 (7.2 client) in
tcp_dump17_04_2024_09H_10M, but no such RENEW packets for 9.20.32.85
(server) and 9.20.120.112 (7.3 client) in tcpdump16_04_2024_14H_03M.
Given NFS4 is a stateful fs which is based on leases, without client
send an operation to renew the lease, it is possible for server to
return EAGAIN. And please check if 7.3 client is not same as 7.2 client
regarding lease renewing.

-- 
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 2061949] Re: nouveau error

2024-04-17 Thread Brett Grandbois

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  nouveau error

Status in linux package in Ubuntu:
  New

Bug description:
  Randomly nouveau throw this error in the kernel log:

  # dmesg | grep nouveau
  [   28.273960] nouveau: detected PR support, will not use DSM
  [   28.274007] nouveau :59:00.0: enabling device ( -> 0003)
  [   28.274453] nouveau :59:00.0: NVIDIA TU117 (167000a1)
  [   28.426297] nouveau :59:00.0: bios: version 90.17.61.00.73
  [   28.432619] nouveau :59:00.0: pmu: firmware unavailable
  [   28.438647] nouveau :59:00.0: fb: 2048 MiB GDDR6
  [   28.494446] nouveau :59:00.0: DRM: VRAM: 2048 MiB
  [   28.494450] nouveau :59:00.0: DRM: GART: 536870912 MiB
  [   28.494454] nouveau :59:00.0: DRM: BIT table 'A' not found
  [   28.494456] nouveau :59:00.0: DRM: BIT table 'L' not found
  [   28.494459] nouveau :59:00.0: DRM: Pointer to TMDS table not found
  [   28.495543] nouveau :59:00.0: DRM: MM: using COPY for buffer copies
  [   28.495954] [drm] Initialized nouveau 1.4.0 20120801 for :59:00.0 on 
minor 0
  [   28.496030] nouveau :59:00.0: [drm] No compatible format found
  [   28.496034] nouveau :59:00.0: [drm] Cannot find any crtc or sizes
  [   37.185011] Modules linked in: uhid qrtr cmac algif_hash algif_skcipher 
af_alg bnep snd_ctl_led snd_soc_skl_hda_dsp snd_soc_hdac_hdmi 
snd_soc_intel_hda_dsp_common snd_sof_probes snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match 
snd_soc_acpi soundwire_generic_allocation soundwire_bus xe snd_soc_core 
xt_multiport xt_tcpudp snd_compress ac97_bus xt_conntrack snd_pcm_dmaengine 
nf_conntrack snd_hda_intel nf_defrag_ipv6 intel_uncore_frequency 
snd_intel_dspcfg nf_defrag_ipv4 intel_uncore_frequency_common 
snd_intel_sdw_acpi nft_compat drm_suballoc_helper intel_tcc_cooling 
snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hda_core snd_hwdep 
coretemp nouveau nf_tables binfmt_misc libcrc32c snd_pcm iwlmvm cmdlinepart 
uvcvideo b
 tusb kvm_intel snd_seq_midi spi_nor
  [   37.185418]  nouveau_display_hpd_resume+0x49/0x60 [nouveau]
  [   37.185661]  nouveau_pmops_runtime_resume+0xef/0x1a0 [nouveau]
  [ 4142.358848] nouveau :59:00.0: fifo:PBDMA0: CTXNOTVALID chid:2

  
  [ 4142.358854] nouveau :59:00.0: fifo:00:0002:0002:[Xwayland[20073]] 
errored - disabling channel
  [ 4142.358866] nouveau :59:00.0: Xwayland[20073]: channel 2 killed!


  I think this is a regression, because I remember the same issue was
  fixed by using updated linux-firmware.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-22-generic 6.8.0-22.22
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:neo3076 F pipewire
   /dev/snd/controlC0:  neo3076 F pipewire
neo3079 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 07:27:34 2024
  InstallationDate: Installed on 2024-03-22 (25 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash ipv6.disable=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-22-generic N/A
   linux-backports-modules-6.8.0-22-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago)
  dmi.bios.date: 04/22/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX435EG.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX435EG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias:

[Kernel-packages] [Bug 2061930] Re: linux-nvidia-6.5_6.5.0-1014.14 breaks with earlier BIOS release, and modeset/resolutions are wrong

2024-04-17 Thread Brett Grandbois

** Changed in: linux-nvidia-6.5 (Ubuntu)
 Assignee: (unassigned) => Jose Ogando Justo (joseogando)

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

Title:
  linux-nvidia-6.5_6.5.0-1014.14 breaks with earlier BIOS release, and
  modeset/resolutions are wrong

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

Bug description:
  There are a gigantic number of changes in 1014.14 compared to 1013

  I suspect some of the aspeed fixes have been undone, the mode is
  now... not what it was before, looks like it's falling back to
  1024x768.  This patchset also brings in a bunch of... strange patches
  that don't involve the nvidia tree at all.

  
  When I boot an older BIOS series with 1013, works fine, with this it spits 
out, upon systemd loading some mid-stage stuff:

  
  [^[[0;32m  OK  ^[[ted ^[[0;1;39mRule-based Manager for Device Events and 
Files^[[0m.
  [^[[0;32m  OK  ^[[0m] Mounted ^[[0;1;39mMount unit for snapd, revision 
19459^[[0m.
  Unhandled Exception from EL2
  x0 = 0x11f210305619
  x1 = 0x
  x2 = 0x
  x3 = 0x
  x4 = 0x5fd6a3d5
  x5 = 0x
  x6 = 0x
  x7 = 0x
  x8 = 0x
  x9 = 0xa0a120ea7d6c
  x10= 0x
  x11= 0x
  x12= 0x
  x13= 0x0030
  x14= 0x
  x15= 0x
  x16= 0x
  x17= 0x
  x18=000
  x19c5d66880
  x20= 0x80009be8f760
  x21= 0x80009be8f7d0
  x22= 0xffe3a0a120ea7d6c
  x23= 0x
  x24= 0xa0a123e08aa0
  x25= 0xa0a123440008
  x26= 0xa0a123440008
  x27= 0xa0a0d34a5748
  x28= 0x80009be8f7c0
  x29= 0x80008000fe00
  x30= 0xa0a120ea7d6c
  scr_el3= 0x0407073d
  sctlr_el3  = 0x30cd183f
  cptr_el3   = 0x00100100
  tcr_el3= 0x80853510
  daif   = 0x02c0
  mair_el3   = 0x004404ff
  spsr_el3   = 0x034000el3= 0xa0a0d34a58b4
  ttbr0_el3  = 0x0078734a5001
  esr_el3= 0x622c5c1f
  far_el3= 0x42a4e89076a05490
  spsr_el1   = 0x
  elr_el1= 0x
  spsr_abt   = 0x
  spsr_und   = 0x
  spsr_irq   = 0x
  spsr_fiq   = 0x
  sctlr_el1  = 0x30500980
  actlr_el1  = 0x
  cpacr_el1  = 0x0030
  csselr_el1 = 0x0002
  sp_el1 = 0xa0a123defea0
  esr_el1= 0x
  ttbr0_el1   00f89cd
  ttbr1_el1  000f8af0
  mair_el1   = 0x00040044
  amair_el1  = 0x
  tcr_el1= 0x005000f5f5507dr_el1  = 0x5fd6a3d5
  tpidr_el0  = 0x8000
  tpidrro_el0= 0x
  par_el1= 0x0800
  mpidr_el1  = 0x8102
  afsr0_el1  = 0x
  afsr1_el1  = 0x
  contextidr_el1 = 0x
  vbar_el1   = 0xa0a120cd1000
  cntp_ctl_el0   = 0x
  cntp_cval_el0  = 0x001f0caabc20
  cntv_ctl_el0
  cntv_cval_el0  = 0x
  cntkctl_el1= 0x
  sp_el0 = 0x0078732cf4f0
  isr_el1= 0x0ectlr_el1   = 0x4000340340003000
  gicd_ispendr regs (Offsets 0x200 - 0x278)
   Offset:value
  0200:   0xUnhandled Exception in EL3.
  x30= 0x0078732c4384
  x0 = 0x
  x1 = 0x0078732cb7d8
  x2 = 0x0018
  x3 = 0x0078732b1720
  x4 = 0x
  x5 = 0x003c
  x6 = 0x0078732c9109
  x7 = 0x22000204
  x8 = 0x4000340340003000
  x9 = 0xa0a120cd1000
  x10= 0x
  x11= 0x001f0caabc20
  x12= 0x
  x13= 0x00000
  x15= 0x0078732cf4f0
  x16= 0x2200
  x17= 0x0018
  x18= 0x0407073d
  x19= 0x007873386440
  x20= 0x80009be8f760
  x21= 0x80009be8f7d0
  x22= 0xffe3a0a120ea7d6c
  x23= 0x
  x24

[Kernel-packages] [Bug 2062063] Re: ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package

2024-04-17 Thread Brett Grandbois

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package

Status in linux package in Ubuntu:
  New

Bug description:
  Binary package 'linux-modules-extra'.

  With a Skylake Intel sound chip I get:

  [5.911304] sof-audio-pci-intel-tgl :00:1f.3: Check if you have
  'sof-firmware' package installed.

  The actual Ubuntu package to install is called "firmware-sof-signed" rather 
than "sof-firmware".
  That can be confusing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062063/+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 2060914] Re: kernel NULL pointer dereference in ipu6 driver

2024-04-17 Thread Shih-Yuan Lee

** Also affects: oem-priority
   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/2060914

Title:
  kernel NULL pointer dereference in ipu6 driver

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  pr 11 14:43:43 OCBYM2-DVT1-C3 kernel: BUG: kernel NULL pointer dereference, 
address: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: supervisor read access in kernel 
mode
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: error_code(0x) - not-present 
page
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PGD 0 P4D 0 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Oops:  [#1] PREEMPT SMP NOPTI
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CPU: 16 PID: 568 Comm: (udev-worker) 
Tainted: G   O   6.8.0-22-generic #22-Ubuntu
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Hardware name: Dell Inc. Precision 
5490/, BIOS 1.1.0 02/07/2024
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RIP: 0010:__wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Code: 55 48 89 e5 41 57 41 56 41 55 41 
54 53 48 89 fb 48 83 c3 08 48 83 ec 08 48 8b 47 08 89 75 d4 89 55 d0 48 39 c3 
74 51 4d 89 c7 <4c> 8b 00 41 89 ce 48 8d 78 e8 4d 8d 68 e8 eb 25 74 0c 41 83 e4 
01
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RSP: 0018:b5ebc3063768 EFLAGS: 
00010086
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RAX:  RBX: 
8fb79e181d50 RCX: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RDX:  RSI: 
0003 RDI: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RBP: b5ebc3063798 R08: 
 R09: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R10:  R11: 
 R12: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R13: 0003 R14: 
0246 R15: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: FS:  77cceb6148c0() 
GS:8fc6cf60() knlGS:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CR2:  CR3: 
0001068ae003 CR4: 00f70ef0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR0:  DR1: 
 DR2: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR3:  DR6: 
07f0 DR7: 0400
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PKRU: 5554
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Call Trace:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? show_regs+0x6d/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __die+0x24/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? page_fault_oops+0x99/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? do_user_addr_fault+0x2ee/0x6b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? exc_page_fault+0x83/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? asm_exc_page_fault+0x27/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __wake_up+0x37/0x70
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __vb2_queue_cancel+0xcd/0x300 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_core_queue_release+0x23/0x70 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_queue_release+0xe/0x20 
[videobuf2_v4l2]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_queue_cleanup+0x12/0x20 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_video_cleanup+0x2e/0x40 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
ipu_isys_csi2_be_soc_cleanup+0x37/0x50 [intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_unregister_subdevices+0x40/0xa0 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_probe+0x5c5/0xb80 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? kernfs_create_link+0x66/0xe0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_probe+0x72/0x130 [intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  really_probe+0x1c4/0x410
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_probe_device+0x8c/0x180
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_probe_device+0x24/0xd0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_attach+0x10b/0x210
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx___driver_attach+0x10/0x10
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_for_each_dev+0x8a/0xf0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_attach+0x1e/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_add_driver+0x156/0x260
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_register+0x5e/0x130
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx_isys_driver_init+0x10/0x10 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_register_driver+0x16/0x20 
[intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:

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

2024-04-17 Thread Eric Sheridan

Joseph - thanks for looking into this. Please let me know if I can be of
assistance. I'd be happy to test out the corresponding changes on my
end. Just let me know - thank you!!

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

Title:
   Adding bpf to CONFIG_LSM in linux kernel

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

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

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

  There are already projects trying to leverage that

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

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

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

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

  Arch Linux

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

  Fedora

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

  openSUSE

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

  Debian

  https://salsa.debian.org/kernel-
  team/linux/-/blob/master/debian/config/config?ref_type=heads#L7713

  RedHat

  
https://access.redhat.com/labs/rhcb/RHEL-8.9/kernel-4.18.0-513.18.1.el8/source/blob/redhat/configs/generic/CONFIG_LSM

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

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


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

[Kernel-packages] [Bug 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver

2024-04-17 Thread Cristiano Fraga G. Nunes

I have the same issue:

I recently installed Ubuntu 24.04 for testing purposes and have
encountered an unexpected issue.

The 'Displays' configuration indicates the presence of three monitors, like 
this:
1) Dell Inc. 27"
2) Dell Inc. 27"
3) Unknown Display
However, I only have two displays and not a third one.

When moving the cursor to the extreme right corner of the screen, the
entire display shifts to the right. Below are the pertinent details:

Configuration:
- Utilizing: two monitors
- Graphics Card: NVIDIA GeForce GTX 1660 SUPER
- Environment: Xorg
- Driver Version: Nvidia driver 535.161.07

This behavior disrupts normal workflow and consistency in display
management. Any insights or solutions to address this issue would be
greatly appreciated. Thank you for your attention to this matter.

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

Title:
  Phantom 46" monitor (simpledrm) shown in Settings after installing the
  Nvidia driver

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Confirmed

Bug description:
  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still controlled 
by simpledrm, while Nvidia uses /dev/dri/card1.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble
  Uname: Linux 6.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: RNUC12DCMi7
  dmi.product.version: M30143-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver

2024-04-17 Thread Daniel van Vugt

If you're careful you can just delete /dev/dri/card0 to work around it
:)

** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Phantom 46" monitor (simpledrm) shown in Settings after installing the
  Nvidia driver

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Confirmed

Bug description:
  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still controlled 
by simpledrm, while Nvidia uses /dev/dri/card1.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble
  Uname: Linux 6.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: RNUC12DCMi7
  dmi.product.version: M30143-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-17 Thread Matthew Ruffell

Performing verification for Jammy.

I started two Jammy VMs. One is a server and the other a client.

Server
--

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

Client
--

$ sudo apt update
$ sudo apt install cifs-utils
$ mkdir ~/share
$ sudo mount -t cifs -o username=ubuntu //192.168.122.172/sambashare ~/share

The client is using 5.15.0-102-generic from updates:

$ uname -rv
5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024

$ sudo -s
# while true; do echo "$(date) hallo" >> ./share/hallo.txt; sleep 1 ; done

Launch a separate terminal and run:

$ df -h ~/share
df: /home/ubuntu/share: Resource temporarily unavailable

The issue is seen.

I then enabled -proposed and installed 5.15.0-105-generic.

I had to use the -proposed2 repository due to the packages not being present
in the primary archive -proposed repository.

https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed2

$ uname -rv 
5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024

$ sudo -s
# while true; do echo "$(date) hallo" >> ./share/hallo.txt; sleep 1 ; done

$ df -h ~/share
FilesystemSize  Used Avail Use% Mounted on
//192.168.122.247/sambashare  9.6G  2.1G  7.5G  23% /home/ubuntu/share

CIFS is back to working again, and we can df the share and see the disk
usage.

The respun kernel in -proposed fixes the issue, happy to mark verified
for Jammy.

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

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2062089] Re: [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two)

2024-04-17 Thread Daniel van Vugt

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2060268, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)

** This bug has been marked a duplicate of bug 2060268
   Phantom 46" monitor (simpledrm) shown in Settings after installing the 
Nvidia driver

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

Title:
  [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two)

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  I recently installed Ubuntu 24.04 for testing purposes and have
  encountered an unexpected issue.

  The 'Displays' configuration indicates the presence of three monitors, like 
this:
  1) Dell Inc. 27"
  2) Dell Inc. 27"
  3) Unknown Display
  However, I only have two displays and not a third one.

  
  When moving the cursor to the extreme right corner of the screen, the entire 
display shifts to the right. Below are the pertinent details:

  Configuration:
  - Utilizing: two monitors
  - Graphics Card: NVIDIA GeForce GTX 1660 SUPER
  - Environment: Xorg
  - Driver Version: Nvidia driver 535.161.07

  This behavior disrupts normal workflow and consistency in display
  management. Any insights or solutions to address this issue would be
  greatly appreciated. Thank you for your attention to this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu5
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 21:43:13 2024
  DisplayManager: gdm3
  InstallationDate: Installed on 2024-04-17 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 46.0-1ubuntu7
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2062089/+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 2062089] [NEW] [NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two)

You have been subscribed to a public bug:

I recently installed Ubuntu 24.04 for testing purposes and have
encountered an unexpected issue.

The 'Displays' configuration indicates the presence of three monitors, like 
this:
1) Dell Inc. 27"
2) Dell Inc. 27"
3) Unknown Display
However, I only have two displays and not a third one.


When moving the cursor to the extreme right corner of the screen, the entire 
display shifts to the right. Below are the pertinent details:

Configuration:
- Utilizing: two monitors
- Graphics Card: NVIDIA GeForce GTX 1660 SUPER
- Environment: Xorg
- Driver Version: Nvidia driver 535.161.07

This behavior disrupts normal workflow and consistency in display
management. Any insights or solutions to address this issue would be
greatly appreciated. Thank you for your attention to this matter.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 21:43:13 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-04-17 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 46.0-1ubuntu7
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble
-- 
[NVIDIA] Ubuntu 24.04 detects a third unknown monitor (instead of two)
https://bugs.launchpad.net/bugs/2062089
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-535 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 1383184] Business Opportunity

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board.bin failed with error -2
  [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2
  [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2
  [6.417421] ath10k_pci :02:00.0: could not fetch firmware files (-2)
  [6.417423] ath10k_pci :02:00.0: could not probe fw (-2)

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


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

[Kernel-packages] [Bug 1049466] Business Opportunity

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

Title:
  Need support of Ralink RT3290 wifi support

Status in Linux:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-firmware source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Invalid
Status in linux-firmware source package in Quantal:
  Won't Fix
Status in linux source package in Raring:
  Fix Released
Status in linux-firmware source package in Raring:
  Fix Released
Status in linux package in Baltix:
  Opinion
Status in linux package in Gentoo Linux:
  New

Bug description:
  RT3290 wifi chip is becoming common on consumer notebooks. Its support
  starts from 3.6 so support on 12.10 may need lbm-cw.

  commit a89534edaaa7008992b878680490e9b02a665563
  Author: Woody Hung 
  Date:   Wed Jun 13 15:01:16 2012 +0800

  rt2x00 : RT3290 chip support v4
  
  This patch support the new chipset rt3290 wifi implementation in rt2x00.
  It initailize the related mac, bbp and rf register in startup phase.
  And this patch modify the efuse read/write method for the different efuse 
data offset of rt3290.
  
  Signed-off-by: Woody Hung 
  Signed-off-by: John W. Linville 

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1049466/+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 1240940] Business Opportunity

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

Title:
  Need support for Realtek Wifi  card rtl8723be [10ec:b723]

Status in HWE Next:
  Fix Released
Status in HWE Next trusty series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  This device is appearing in some OEM machines, but driver is not yet
  available upstream.

  This bug is only for the initial support of this WiFi adapter, it's
  not working 100% well yet, please report new "not working bug" or
  contact upstream but not keep posting comments, thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1240940/+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 177235] Business Opportunity

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

Title:
  slow USB 2.0 drive: it's mounted as USB 1.0, not USB 2.0!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  In gutsy 7.10 dist-upgraded to the max:

  Ubuntu 64-bit sometimes does not mount USB 2.0 devices as 2.0.

  1) plugin in the USB drive
  2) mount it if not automounted (sometimes it doesn't)
  3) right-click, properties in nautilus, go to drive tab, see speed "12 Mbps"
  4) umount it, unplug it
  5) sudo rmmod ehci_hcd
  6) plugin the USB drive
  7) sudo modprobe ehci_hcd
  8) mount it if not automounted
  9) right-click, properties in nautilus, go to drive tab, see speed "480 Mbps"

  Something is horribly wrong at recognizing the proper USB speed mode
  of external drives.

  From /var/log/messages: note how the first time the drive is mounted properly 
as high speed, the second time as slow, then as high speed again with the trick 
of modprobe'ing the ehci_hcd driver.
  Somehow, the second time the driver sees the same USB hard drive, it fails to 
recognize it as USB 2.0.
  (when I modprobe the driver, the USB mouse and keyboard are also recognized, 
don't be confused by these).

  If you need more info let me know.

  
  Dec 18 11:46:50 instar kernel: [1089450.444192] usb 1-2: USB disconnect, 
address 3
  Dec 18 11:47:23 instar kernel: [1089483.715043] ehci_hcd :00:1d.7: 
remove, state 4
  Dec 18 11:47:23 instar kernel: [1089483.715053] usb usb5: USB disconnect, 
address 1
  Dec 18 11:47:23 instar kernel: [1089483.719139] ehci_hcd :00:1d.7: USB 
bus 5 deregistered
  Dec 18 11:47:23 instar kernel: [1089483.720334] ACPI: PCI interrupt for 
device :00:1d.7 disabled
  Dec 18 11:47:45 instar kernel: [1089505.912002] usb 1-2: new full speed USB 
device using uhci_hcd and address 4
  Dec 18 11:47:45 instar kernel: [1089506.134623] usb 1-2: configuration #1 
chosen from 1 choice
  Dec 18 11:47:45 instar kernel: [1089506.137630] scsi7 : SCSI emulation for 
USB Mass Storage devices
  Dec 18 11:47:50 instar kernel: [1089511.132544] scsi 7:0:0:0: Direct-Access   
  SEAGATE  ST3320820A   3.AA PQ: 0 ANSI: 2
  Dec 18 11:47:50 instar kernel: [1089511.137515] sd 7:0:0:0: [sde] 625142448 
512-byte hardware sectors (320073 MB)
  Dec 18 11:47:50 instar kernel: [1089511.142502] sd 7:0:0:0: [sde] Write 
Protect is off
  Dec 18 11:47:50 instar kernel: [1089511.147491] sd 7:0:0:0: [sde] 625142448 
512-byte hardware sectors (320073 MB)
  Dec 18 11:47:50 instar kernel: [1089511.152399] sd 7:0:0:0: [sde] Write 
Protect is off
  Dec 18 11:47:50 instar kernel: [1089511.152410]  sde: sde1
  Dec 18 11:47:50 instar kernel: [1089511.171501] sd 7:0:0:0: [sde] Attached 
SCSI disk
  Dec 18 11:47:50 instar kernel: [1089511.171542] sd 7:0:0:0: Attached scsi 
generic sg5 type 0
  Dec 18 11:48:12 instar kernel: [1089532.675957] ACPI: PCI Interrupt 
:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 20
  Dec 18 11:48:12 instar kernel: [1089532.677029] ehci_hcd :00:1d.7: EHCI 
Host Controller
  Dec 18 11:48:12 instar kernel: [1089532.677207] ehci_hcd :00:1d.7: new 
USB bus registered, assigned bus number 5
  Dec 18 11:48:12 instar kernel: [1089532.677244] ehci_hcd :00:1d.7: debug 
port 1
  Dec 18 11:48:12 instar kernel: [1089532.677262] ehci_hcd :00:1d.7: irq 
20, io mem 0xffafbc00
  Dec 18 11:48:12 instar kernel: [1089532.682397] ehci_hcd :00:1d.7: USB 
2.0 started, EHCI 1.00, driver 10 Dec 2004
  Dec 18 11:48:12 instar kernel: [1089532.682516] usb usb5: configuration #1 
chosen from 1 choice
  Dec 18 11:48:12 instar kernel: [1089532.682548] hub 5-0:1.0: USB hub found
  Dec 18 11:48:12 instar kernel: [1089532.682559] hub 5-0:1.0: 8 ports detected
  Dec 18 11:48:12 instar kernel: [1089533.022143] usb 5-2: new high speed USB 
device using ehci_hcd and address 2
  Dec 18 11:48:12 instar kernel: [1089533.154844] usb 5-2: configuration #1 
chosen from 1 choice
  Dec 18 11:48:12 instar kernel: [1089533.155098] scsi8 : SCSI emulation for 
USB Mass Storage devices
  Dec 18 11:48:13 instar kernel: [1089533.521886] usb 1-2: USB disconnect, 
address 4
  Dec 18 11:48:13 instar kernel: [1089533.649595] usb 2-1: USB disconnect, 
address 3
  Dec 18 11:48:13 instar kernel: [1089533.889048] usb 2-1: new low speed USB 
device using uhci_hcd and address 4
  Dec 18 11:48:13 instar kernel: [1089534.065223] usb 2-1: configuration #1 
chosen from 1 choice
  Dec 18 11:48:13 instar kernel: [1089534.082362] input: Logitech USB Receiver 
as /class/input/input12
  Dec 18 11:48:13 instar kernel: [1089534.082393] input: USB HID v1.10 Keyboard 
[Logitech USB Receiver] on usb-:00:1d.1-1
  Dec 18 11:48:13 instar kernel: [1089534.111043] 
/build/buildd/linux-source-2.6.22-2.6.22/drivers/hid/usbhid/hid-core.c: Fixing 
up Logitech keyboard report descriptor
  Dec 18 11:48:13 instar kernel: [1089534.111596] input: Logitech USB Receiver 
as

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

2024-04-17 Thread Andy Gospodarek

Ok, so I think that means this is ready to be closed, right?

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This request is to add support for the patches for the Broadcom RoCE
  driver included in v6.8 to 24.04.

  The thread where these were posted is here:
  https://lore.kernel.org/all/1701946060-13931-1-git-send-email-
  selvin.xav...@broadcom.com/

  These are the commits from linux-rdma:

  07f830ae4913 RDMA/bnxt_re: Adds MSN table capability for Gen P7 adapters
  cdae3936b2fe RDMA/bnxt_re: Doorbell changes
  6027c20dad1a RDMA/bnxt_re: Get the toggle bits from CQ completions
  880a5dd1880a RDMA/bnxt_re: Update the HW interface definitions
  a62d68581441 RDMA/bnxt_re: Update the BAR offsets
  1801d87b3598 RDMA/bnxt_re: Support new 5760X P7 devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046270/+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 2062063] Re: ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package

2024-04-17 Thread Peter Grandi

Oops it is a 'linux' package bug,

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

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

Title:
  ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package

Status in linux package in Ubuntu:
  New

Bug description:
  Binary package 'linux-modules-extra'.

  With a Skylake Intel sound chip I get:

  [5.911304] sof-audio-pci-intel-tgl :00:1f.3: Check if you have
  'sof-firmware' package installed.

  The actual Ubuntu package to install is called "firmware-sof-signed" rather 
than "sof-firmware".
  That can be confusing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062063/+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 2061684] Re: ULTS 24 linux 6.8.0-22 modules misversioned

2024-04-17 Thread Peter Grandi

So there are news after yet another reboot after several hundred package
updates, but not of the kernel (AFAIK).

Both 'modprobe rtw88_8821ce' (the "official" modules) and 'modprobe
rtw_8821ce' (from 'rtw88_lwfinger') succeed.

I think that the 'kmod' package is the same as before
('kmod_31+20240202-2ubuntu5') so I wonder what else has changed.

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

Title:
  ULTS 24 linux 6.8.0-22 modules misversioned

Status in linux package in Ubuntu:
  New

Bug description:
  I get unexpected symbol versioning errors on loading a WiFi module,
  both built-in and external:

  This is the built-in version:

  petal# find /lib/modules/6.8.0-22-generic -name 'rtw88*8821ce*'
  
/lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst
  petal# dpkg -S 
/lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst
  linux-modules-extra-6.8.0-22-generic: 
/lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst
  petal# modinfo 
/lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst
 | head -15
  filename:   
/lib/modules/6.8.0-22-generic/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko.zst
  license:Dual BSD/GPL
  description:Realtek 802.11ac wireless 8821ce driver
  author: Realtek Corporation
  srcversion: D25FEEBE76FF505B9FB2F23
  alias:  pci:v10ECdC821sv*sd*bc*sc*i*
  alias:  pci:v10ECdB821sv*sd*bc*sc*i*
  depends:rtw88_pci,rtw88_8821c
  retpoline:  Y
  intree: Y
  name:   rtw88_8821ce
  vermagic:   6.8.0-22-generic SMP preempt mod_unload modversions 
  sig_id: PKCS#7
  signer: Build time autogenerated kernel key
  sig_key:6B:5D:B5:AB:9C:C5:55:DE:5D:86:F6:60:36:C5:0D:F0:A3:E2:6D:37

  petal# journalctl --since 'Apr 14 15:20:00' --grep rtw _TRANSPORT=kernel |& 
head -10
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version 
of symbol ieee80211_connection_loss
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol 
ieee80211_connection_loss (err -22)
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version 
of symbol ieee80211_report_wowlan_wakeup
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol 
ieee80211_report_wowlan_wakeup (err -22)
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version 
of symbol ieee80211_txq_get_depth
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol 
ieee80211_txq_get_depth (err -22)
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version 
of symbol ieee80211_probereq_get
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol 
ieee80211_probereq_get (err -22)
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: disagrees about version 
of symbol ieee80211_iterate_stations_atomic
  Apr 14 15:20:32 petal.ty.sabi.co.uk kernel: rtw_core: Unknown symbol 
ieee80211_iterate_stations_atomic (err -22)

  petal# grep ieee80211_txq_get_depth 
/lib/modules/6.8.0-22-generic/modules.symbols
  alias symbol:ieee80211_txq_get_depth mac80211
  petal# find /lib/modules/6.8.0-22-generic -name 'mac80211.ko*'
  /lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst
  petal# dpkg -S 
/lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst
  linux-modules-extra-6.8.0-22-generic: 
/lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst
  petal# modinfo 
/lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst | head -14
  filename:   
/lib/modules/6.8.0-22-generic/kernel/net/mac80211/mac80211.ko.zst
  license:GPL
  description:IEEE 802.11 subsystem
  srcversion: B64ACC886876782FBE75414
  depends:cfg80211,libarc4
  retpoline:  Y
  intree: Y
  name:   mac80211
  vermagic:   6.8.0-22-generic SMP preempt mod_unload modversions 
  sig_id: PKCS#7
  signer: Build time autogenerated kernel key
  sig_key:6B:5D:B5:AB:9C:C5:55:DE:5D:86:F6:60:36:C5:0D:F0:A3:E2:6D:37
  sig_hashalgo:   sha512
  signature:  03:6C:13:64:42:90:35:16:C4:D7:5A:CD:DB:46:BC:7A:0C:7A:29:8C:

  
  That looks like to me a packaging error, but then I compiled also an 
unofficial version of the driver from sources:

  petal# git remote -v
  origin  https://github.com/lwfinger/rtw88 (fetch)
  origin  https://github.com/lwfinger/rtw88 (push)
  petal# ls -ld rtw_8821ce.ko 
  -rw--- 1 root src 609816 Apr 14 21:57 rtw_8821ce.ko
  petal# modinfo rtw_8821ce.ko
  filename:   /usr/src/rtw88_lwfinger/rtw_8821ce.ko
  license:Dual BSD/GPL
  description:Realtek 802.11ac wireless 8821ce driver
  author: Realtek Corporation
  srcversion:

[Kernel-packages] [Bug 2062063] [NEW] ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package

You have been subscribed to a public bug:

Binary package 'linux-modules-extra'.

With a Skylake Intel sound chip I get:

[5.911304] sof-audio-pci-intel-tgl :00:1f.3: Check if you have
'sof-firmware' package installed.

The actual Ubuntu package to install is called "firmware-sof-signed" rather 
than "sof-firmware".
That can be confusing.

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

-- 
ULTS 24 linux 6.8.0-22 SOF sound chips wrong name of fw package
https://bugs.launchpad.net/bugs/2062063
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 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Phantom 46" monitor (simpledrm) shown in Settings after installing the
  Nvidia driver

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Confirmed

Bug description:
  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still controlled 
by simpledrm, while Nvidia uses /dev/dri/card1.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble
  Uname: Linux 6.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: RNUC12DCMi7
  dmi.product.version: M30143-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver

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

** Changed in: nvidia-graphics-drivers-545 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Phantom 46" monitor (simpledrm) shown in Settings after installing the
  Nvidia driver

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Confirmed

Bug description:
  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still controlled 
by simpledrm, while Nvidia uses /dev/dri/card1.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble
  Uname: Linux 6.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: RNUC12DCMi7
  dmi.product.version: M30143-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver

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

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

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

Title:
  Phantom 46" monitor (simpledrm) shown in Settings after installing the
  Nvidia driver

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Confirmed

Bug description:
  After installing Nvidia driver 545 on a single (27") monitor system,
  Settings shows a phantom 46" monitor of the same resolution.

  It looks like the phantom monitor is /dev/dri/card0 which is still controlled 
by simpledrm, while Nvidia uses /dev/dri/card1.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:dan4631 F pipewire
   /dev/snd/controlC1:  dan4636 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-01-04 (92 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  MachineType: Intel(R) Client Systems NUC12DCMi7
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 simpledrmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-11-generic N/A
   linux-backports-modules-6.8.0-11-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu1
  Tags: noble
  Uname: Linux 6.8.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/20/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EDADL579.0046.2021.1220.2351
  dmi.board.name: NUC12EDBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M27908-302
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7:
  dmi.product.family: DC
  dmi.product.name: NUC12DCMi7
  dmi.product.sku: RNUC12DCMi7
  dmi.product.version: M30143-302
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2061830] Re: Limit supported pci-id's to the new ones added by 550

This bug was fixed in the package nvidia-graphics-drivers-550-server -
550.54.15-0ubuntu0.22.04.2

---
nvidia-graphics-drivers-550-server (550.54.15-0ubuntu0.22.04.2) jammy; 
urgency=medium

  * Limit supported pci-id's to the new ones added by this release.
(LP: #2061830)

nvidia-graphics-drivers-550-server (550.54.15-0ubuntu0.22.04.1) jammy;
urgency=medium

  * New Upstream release (LP: 2059115)

 -- Timo Aaltonen   Tue, 16 Apr 2024 18:26:19 +0300

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

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

Title:
  Limit supported pci-id's to the new ones added by 550

Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Noble:
  Fix Released

Bug description:
  Since 550 wasn't included in the beta we should limit the potential
  impact on 24.04 stability by limiting the driver to be loaded only on
  the new hw supported by this driver. This will be temporary until we
  are ready to migrate 535 to 550.

  The id list for 'Pmaliases' is not modified, as that only tells gpu-
  manager to enable runtime power management for matching GPUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2061830/+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 1964941] Re: Adding bpf to CONFIG_LSM in 5.13 kernels

2024-04-17 Thread Joseph Salisbury

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

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

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

** This bug has been marked a duplicate of bug 2054810
Adding bpf to CONFIG_LSM in linux kernel

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

Title:
   Adding bpf to CONFIG_LSM in 5.13 kernels

Status in linux package in Ubuntu:
  Triaged

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

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

  There are already projects trying to leverage that

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

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

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

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

  Arch Linux

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

  Fedora

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

  openSUSE

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964941/+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 2061830] Re: Limit supported pci-id's to the new ones added by 550

This bug was fixed in the package nvidia-graphics-drivers-550 -
550.67-0ubuntu1.22.04.2

---
nvidia-graphics-drivers-550 (550.67-0ubuntu1.22.04.2) jammy; urgency=medium

  * Limit supported pci-id's to the new ones added by this release.
(LP: #2061830)

nvidia-graphics-drivers-550 (550.67-0ubuntu1.22.04.1) jammy;
urgency=medium

  * Initial release (LP: #2055384)

 -- Timo Aaltonen   Tue, 16 Apr 2024 18:14:23 +0300

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

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

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

Title:
  Limit supported pci-id's to the new ones added by 550

Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Noble:
  Fix Released

Bug description:
  Since 550 wasn't included in the beta we should limit the potential
  impact on 24.04 stability by limiting the driver to be loaded only on
  the new hw supported by this driver. This will be temporary until we
  are ready to migrate 535 to 550.

  The id list for 'Pmaliases' is not modified, as that only tells gpu-
  manager to enable runtime power management for matching GPUs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2061830/+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 2061830] Re: Limit supported pci-id's to the new ones added by 550

This bug was fixed in the package nvidia-graphics-drivers-550 -
550.67-0ubuntu1.23.10.2

---
nvidia-graphics-drivers-550 (550.67-0ubuntu1.23.10.2) mantic; urgency=medium

  * Limit supported pci-id's to the new ones added by this release.
(LP: #2061830)

nvidia-graphics-drivers-550 (550.67-0ubuntu1.23.10.1) mantic;
urgency=medium

  * Initial release (LP: #2055384)

 -- Timo Aaltonen   Tue, 16 Apr 2024 18:34:17 +0300

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

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

Title:
  Limit supported pci-id's to the new ones added by 550

Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Noble:
  Fix Released

Bug description:
  Since 550 wasn't included in the beta we should limit the potential
  impact on 24.04 stability by limiting the driver to be loaded only on
  the new hw supported by this driver. This will be temporary until we
  are ready to migrate 535 to 550.

  The id list for 'Pmaliases' is not modified, as that only tells gpu-
  manager to enable runtime power management for matching GPUs.

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


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

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

2024-04-17 Thread Joseph Salisbury

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

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

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

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

** Also affects: linux (Ubuntu Noble)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: Confirmed

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

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

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
   Adding bpf to CONFIG_LSM in linux kernel

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

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

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

  There are already projects trying to leverage that

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

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

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

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

  Arch Linux

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

  Fedora

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

  openSUSE

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

  Debian

  https://salsa.debian.org/kernel-
  team/linux/-/blob/master/debian/config/config?ref_type=heads#L7713

  RedHat

  
https://access.redhat.com/labs/rhcb/RHEL-8.9/kernel-4.18.0-513.18.1.el8/source/blob/redhat/configs/generic/CONFIG_LSM

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

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


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

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-17 Thread Kirkland Schlicht

Spent so long troubleshooting a container and Veeam Agent issue just to
find out it was a kernel issueAnd here I was worried that power
outage borked something...

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features

2024-04-17 Thread Brian Murray

** Changed in: chrony (Ubuntu Noble)
   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/2061851

Title:
  linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new
  apparmor profiles/features

Status in chrony package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-ibm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New
Status in chrony source package in Noble:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-aws source package in Noble:
  New
Status in linux-azure source package in Noble:
  New
Status in linux-gcp source package in Noble:
  New
Status in linux-ibm source package in Noble:
  New
Status in linux-oracle source package in Noble:
  New
Status in snapd source package in Noble:
  New

Bug description:
  * Canonical Public Cloud discovered that `chronyc -c sources` now fails with 
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in 
linux-azure and linux-gcp kernels (6.8.0-1005.5)
  * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in 
no regression and `chronyc -c sources` returns as expected
  * Disabling the apparmor profile for `chronyd` only results in no regression 
and `chronyc -c sources` returns as expected
  * There are zero entries in dmesg when this occurs
  * There are zero entries in dmesg when this occurs if the  apparmor profile 
for `chronyd` is placed in complain mode instead of enforce mode
  * We changed the time server from the internal GCP metadata.google.internal 
to the ubuntu time server ntp.ubuntu.com with no change in behaviour

  
  We also noted issues with DNS resolution in snaps like `google-cloud-cli` in 
GCE images. 

  * Disabling apparmor completely for snaps too (`sudo systemctl stop
  snapd.apparmor`) results in no regression and calling the snaps
  returns as expected.

  
  The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and 
the -proposed `6.8.0-25.25` generic kernel. 

  This is a release blocker for Noble release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features

2024-04-17 Thread Brian Murray

** Tags removed: block-proposed block-proposed-noble

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

Title:
  linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new
  apparmor profiles/features

Status in chrony package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-ibm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New
Status in chrony source package in Noble:
  New
Status in linux source package in Noble:
  New
Status in linux-aws source package in Noble:
  New
Status in linux-azure source package in Noble:
  New
Status in linux-gcp source package in Noble:
  New
Status in linux-ibm source package in Noble:
  New
Status in linux-oracle source package in Noble:
  New
Status in snapd source package in Noble:
  New

Bug description:
  * Canonical Public Cloud discovered that `chronyc -c sources` now fails with 
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in 
linux-azure and linux-gcp kernels (6.8.0-1005.5)
  * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in 
no regression and `chronyc -c sources` returns as expected
  * Disabling the apparmor profile for `chronyd` only results in no regression 
and `chronyc -c sources` returns as expected
  * There are zero entries in dmesg when this occurs
  * There are zero entries in dmesg when this occurs if the  apparmor profile 
for `chronyd` is placed in complain mode instead of enforce mode
  * We changed the time server from the internal GCP metadata.google.internal 
to the ubuntu time server ntp.ubuntu.com with no change in behaviour

  
  We also noted issues with DNS resolution in snaps like `google-cloud-cli` in 
GCE images. 

  * Disabling apparmor completely for snaps too (`sudo systemctl stop
  snapd.apparmor`) results in no regression and calling the snaps
  returns as expected.

  
  The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and 
the -proposed `6.8.0-25.25` generic kernel. 

  This is a release blocker for Noble release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3

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

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

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

Title:
  Snaps unable to connect to network under linux-lowlatency
  6.8.0-25.25.3

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
  longer connect to network. I tried downgrading snapd from edge, still
  no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll
  also add apparmor in case this is an apparmor issue as well.

  Marking as "critical" priority as this affects all installs of Ubuntu
  Studio and affects Firefox and Thunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2061912] Re: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04

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

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

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

Title:
  After a very recent update most browsers are not able to load webpages
  in Ubuntu 24.04

Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After a recent update of packages (in the last couple of hours or so)
  neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap)
  are able to load pages. Gnome Web is the only one that seems to work.
  Also, apt loads fine.

  Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 16 18:55:41 2024
  InstallationDate: Installed on 2022-02-02 (804 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago)
  nmcli-nm:
   RUNNING VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
 WIFI  WWAN-HW  WWAN 
   ejecutando  1.46.0   conectado  Iniciado  total activadoactivado 
 activado  missing  activado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2061912/+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 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3

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

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

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

Title:
  Snaps unable to connect to network under linux-lowlatency
  6.8.0-25.25.3

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
  longer connect to network. I tried downgrading snapd from edge, still
  no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll
  also add apparmor in case this is an apparmor issue as well.

  Marking as "critical" priority as this affects all installs of Ubuntu
  Studio and affects Firefox and Thunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2059380] Re: [Ubuntu 24.04-server]- installation failed on FHF-R platform with kernel trace

2024-04-17 Thread Thibf

Was/is it working on previous version that you tried ? On Mantic or Jammy?
I guess you don't have any way to get the console output to a txt file ?

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

Title:
  [Ubuntu 24.04-server]- installation failed on FHF-R platform with
  kernel trace

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

Bug description:
  Description:
  we try Ubuntu 24.04 server version from 
https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/

  installed failed with usb disk and BMC.

  [HW/SW Information]

  Platform: FHF-R workstation (SPR-R CPU)

  [Software Information]
Target Version:
  24.04
Target Kernel:
  TBD
Commit IDs:
  TBD
External Links:

  [Business Justification]
  Installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2059380/+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 2059380] Re: [Ubuntu 24.04-server]- installation failed on FHF-R platform with kernel trace

2024-04-17 Thread Thibf

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

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

** Also affects: Ubuntu Noble
   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/2059380

Title:
  [Ubuntu 24.04-server]- installation failed on FHF-R platform with
  kernel trace

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

Bug description:
  Description:
  we try Ubuntu 24.04 server version from 
https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/

  installed failed with usb disk and BMC.

  [HW/SW Information]

  Platform: FHF-R workstation (SPR-R CPU)

  [Software Information]
Target Version:
  24.04
Target Kernel:
  TBD
Commit IDs:
  TBD
External Links:

  [Business Justification]
  Installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2059380/+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] Comment bridged from LTC Bugzilla

--- Comment From david_pa...@uk.ibm.com 2024-04-17 13:11 EDT---
Here are the details of the IP addresses for the tcpdump files

AIX 7.3
9.20.120.112name = amaliada.v6.hursley.ibm.com   -- Primary
9.20.120.153   name = adamsongrunter.v6.hursley.ibm.com  ? Partner

AIX 7.2
9.20.120.127name = adia.v6.hursley.ibm.com   -- Primary
9.20.121.46 name = amberjack.v6.hursley.ibm.com  ? Partner

NFSv4 server
9.20.32.85 name =   duckseason.hursley.ibm.com

-- 
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 2027848] Re: Soft-lockup caused by snd_hda_intel

2024-04-17 Thread Executenor

The issue is caused by this change: 
https://github.com/torvalds/linux/commit/5aec989
I created a new repository with this fix included: 
https://github.com/nicktelindert/linux

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

Title:
  Soft-lockup caused by snd_hda_intel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I report this bug the the 6.5rc1 kernel.
  Kernel before 6.5 hang even before there is any logging going on.
  The problem is gone when i blacklist snd_hda_core.

  jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: watchdog: BUG: soft lockup 
- CPU#1 stuck for 78s! [kworker/1:1:90]
  jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: Modules linked in: 
snd_seq_dummy snd_hrtimer rfcomm cmac algif_hash algif_skcipher af_alg bnep 
snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_>
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel:  hp_wmi snd_timer videodev 
input_leds spi_nor rapl cec sparse_keymap cfg80211 intel_cstate wmi_bmof 
serio_raw platform_profile videobuf2_common snd mei_>
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: CPU: 1 PID: 90 Comm: 
kworker/1:1 Tainted: G U  WL 6.5.0-060500rc1-generic #202307092131
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Hardware name: HP HP Laptop 
15s-fq4xxx/89BC, BIOS F.31 03/25/2023
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Workqueue: events 
azx_probe_work [snd_hda_intel]
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RIP: 
0010:_raw_spin_unlock_irq+0x15/0x50
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Code: cc cc 0f 1f 00 90 90 
90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 c6 07 00 
0f 1f 00 fb 0f 1f 44 00 00 <65> ff 0d 5c 61 52 >
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RSP: 0018:b450c05dbb30 
EFLAGS: 0246
  jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RAX: 0007 RBX: 
0007 RCX: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027848/+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 2059263] Re: Fix acpi_power_meter accessing IPMI region before it's ready

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

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

Title:
  Fix acpi_power_meter accessing IPMI region before it's ready

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

Bug description:
  [Impact]
  ACPI error can be found in kernel message:
  [3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) 
[IPMI] (20230628/evregion-130)

  [Fix]
  On Dell systems that have IPI0001 device, ensure IPMI region is ready
  before acpi_power_meter invokes any ACPI method.

  [Test]
  With the patch applied, no such error can be found in kernel message.
  acpi_power_meter sysfs also works correctly.

  [Where problems could occur]
  If asynchronous probe is disabled, the device drivers that probe after
  acpi_power_meter needs to wait until the completion is done, hence the
  boot time might be slower.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2059263/+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 2060727] Re: The keyboard does not work after latest kernel update

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

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

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2061830] Re: Limit supported pci-id's to the new ones added by 550

This bug was fixed in the package nvidia-graphics-drivers-550 -
550.67-0ubuntu3

---
nvidia-graphics-drivers-550 (550.67-0ubuntu3) noble; urgency=medium

  * Limit supported pci-id's to the new ones supported by this release.
(LP: #2061830)

 -- Timo Aaltonen   Tue, 16 Apr 2024 13:37:41 +0300

** Changed in: nvidia-graphics-drivers-550 (Ubuntu Noble)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-550-server (Ubuntu Noble)
   Status: Fix Committed => Fix Released

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

Title:
  Limit supported pci-id's to the new ones added by 550

Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550 source package in Jammy:
  New
Status in nvidia-graphics-drivers-550-server source package in Jammy:
  New
Status in nvidia-graphics-drivers-550 source package in Mantic:
  New
Status in nvidia-graphics-drivers-550-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-550 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-550-server source package in Noble:
  Fix Released

Bug description:
  Since 550 wasn't included in the beta we should limit the potential
  impact on 24.04 stability by limiting the driver to be loaded only on
  the new hw supported by this driver. This will be temporary until we
  are ready to migrate 535 to 550.

  The id list for 'Pmaliases' is not modified, as that only tells gpu-
  manager to enable runtime power management for matching GPUs.

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


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

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

2024-04-17 Thread Andrea Righi

According to the information that I collected (asking around,
investigating, etc.), it seems that there are no critical users of
ubuntu-fan.

Moreover, considering the impact of the ubuntu-fan kernel patches (that
would require a major refactoring to avoid breaking the network eBPF
ABI), we decided to proceed with the plan to deprecate this feature in
all the noble kernels.

Therefore, all the user-space components that rely on such feature can
follow the same plan and drop their corresponding ubuntu-fan support
(iproute2 included).

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

Title:
[FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)

Status in iproute2 package in Ubuntu:
Confirmed

Bug description:
iproute2 upstream produces releases coinciding with upstream kernel
releases to support the latest kernel features. Noble's iproute2 is
still back at v6.1 even though it will use the v6.8 kernel. This means
we provide no userspace interface for newer features - some of which
are noted by a networking hardware partner in bug 2060969.

Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu
FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no
longer needed, and we could now just do a merge. We could also port
the FAN patches forward if we can identify a need (see the original
description of this bug to a link to such a port), but I have not done
any testing with that.

I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
smoke tested it on an amd64 virtual machine:

ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb
(Reading database ... 83134 files and directories currently installed.)
Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ...
Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ...
dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d':
Directory not empty
dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d':
Directory not empty
dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not
empty
Setting up iproute2 (6.8.0-1~24.04.1) ...
Removing obsolete conffile /etc/iproute2/group ...
Removing obsolete conffile /etc/iproute2/rt_realms ...
Removing obsolete conffile /etc/iproute2/rt_scopes ...
Removing obsolete conffile /etc/iproute2/rt_tables ...
Removing obsolete conffile /etc/iproute2/rt_tables.d/README ...
Removing obsolete conffile /etc/iproute2/rt_protos.d/README ...
Removing obsolete conffile /etc/iproute2/rt_protos ...
Removing obsolete conffile /etc/iproute2/rt_dsfield ...
Removing obsolete conffile /etc/iproute2/nl_protos ...
Removing obsolete conffile /etc/iproute2/ematch_map ...
Removing obsolete conffile /etc/iproute2/bpf_pinning ...
Processing triggers for man-db (2.12.0-4build1) ...

The system rebooted fine. The ip command seems to behave normally.

Since the upstream test suite only appears to run at autopkgtest time, I
triggered a run in my PPA, and it passed:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-17 Thread Andreas Besold

Hi,

I can confirm that linux-generic 5.15.0.105 is not available yet in
proposed repository. Latest version is 104.

# apt policy linux-generic
linux-generic:
  Installed: 5.15.0.102.99
  Candidate: 5.15.0.104.101
  Version table:
 5.15.0.104.101 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
 *** 5.15.0.102.99 500
500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 5.15.0.25.27 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages


# apt info linux-image-generic
Package: linux-image-generic
Version: 5.15.0.104.101
Priority: optional
Section: kernel
Source: linux-meta
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 21.5 kB
Provides: spl-modules (= 2.1.5-1ubuntu6~22.04.3), v4l2loopback-modules (= 
0.12.7-2ubuntu2~22.04.1), virtualbox-guest-modules (= 5.15.0-104), 
wireguard-modules (= 1.0.0), zfs-modules (= 2.1.5-1ubuntu6~22.04.3)
Depends: linux-image-5.15.0-104-generic, 
linux-modules-extra-5.15.0-104-generic, linux-firmware, intel-microcode, 
amd64-microcode
Recommends: thermald
Download-Size: 2,514 B
APT-Sources: http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
Description: Generic Linux kernel image
 This package will always depend on the latest generic kernel image
 available.

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2031226] Re: Unclaimed Network Controller on Ubuntu 23.04 HP Spectre x360 Convertible 15-eb0xxx

2024-04-17 Thread Student.a

please help

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

Title:
  Unclaimed Network Controller on Ubuntu 23.04 HP Spectre x360
  Convertible 15-eb0xxx

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  # Problem
  I recently tried dual booting my **HP Spectre x360 Convertible 15-eb0xxx** 
machine with *Windows 11* and *Ubuntu 23.04*. Unfortunately, the Ubuntu system 
is never able to connect to the internet via it's wifi card. Wifi works as 
expected when running Windows 11.

  Windows 11 device manager reports my wifi card is an Intel Ax201
  160MhZ device.

  I have obtained the following diagnostic information:

  ## dmesg

  ```
  [2.352442] iwlwifi: unknown parameter 'd0i3_disable' ignored
  [2.352445] iwlwifi: unknown parameter 'lar_disable' ignored
  [2.354883] iwlwifi :00:14.3: enabling device ( -> 0002)
  [2.368115] iwlwifi :00:14.3: Can find a correct rfid for crf id 0x617
  [2.368163] iwlwifi: probe of :00:14.3 failed with error -22
  ```

  
  ## sudo lshw -C network
  ```

  
   *-network UNCLAIMED   
 description: Network controller
 product: Comet Lake PCH CNVi WiFi
 vendor: Intel Corporation
 physical id: 14.3
 bus info: pci@:00:14.3
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix cap_list
 configuration: latency=0
 resources: iomemory:600-5ff memory:606311c000-606311
*-network
 description: Ethernet interface
 physical id: 15
 bus info: usb@1:1
 logical name: enxa0cec8645734
 serial: a0:ce:c8:64:57:34
 size: 100Mbit/s
 capacity: 100Mbit/s
 capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8152 
driverversion=v1.12.13 duplex=full ip=192.168.1.46 link=yes multicast=yes 
port=MII speed=100Mbit/s
  ```

  ## uname -r
  ```
  6.2.0-26-generic
  ```

  ## lsusb
  ```

  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 002: ID 06cb:00c9 Synaptics, Inc. 
  Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
  Bus 001 Device 006: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast 
Ethernet Adapter
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ```

  ## rfkill list all
  ```

  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  ```

  ## lspci
  ```
  00:00.0 Host bridge: Intel Corporation 10th Gen Core Processor Host 
Bridge/DRAM Registers (rev 02)
  00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe 
Controller (x16) (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD 
Graphics] (rev 05)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
  00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH 
Thermal Controller
  00:13.0 Serial controller: Intel Corporation Device 06fc
  00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host 
Controller
  00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
  00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
  00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C 
Controller #0
  00:15.1 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C 
Controller #1
  00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
  00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #17 
(rev f0)
  00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 
(rev f0)
  00:1d.7 PCI bridge: Intel Corporation Device 06b7 (rev f0)
  00:1f.0 ISA bridge: Intel Corporation Comet Lake LPC Controller
  00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS
  00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
  00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
  01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 
1650 Ti Mobile] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
  02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 4C 2018] (rev 06)
  03:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 4C 2018] (rev 06)
  03:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge 4C 2018] (rev 06)
  03:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan 
Ridge

[Kernel-packages] [Bug 2042363] tcpdump for aix 7.2 testing part 3 of 4

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:18 
EDT---


** Attachment added: "tcpdump for aix 7.2 testing part 3 of 4"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766766/+files/tcpdump17_04_2024_09H_10M2.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 2042363] tcpdump for aix 7.2 testing part 4 of 4

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:19 
EDT---


** Attachment added: "tcpdump for aix 7.2 testing part 4 of 4"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766767/+files/tcpdump17_04_2024_09H_10M3.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 2042363] tcpdump for aix 7.2 testing part 2 of 4

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:18 
EDT---


** Attachment added: "tcpdump for aix 7.2 testing part 2 of 4"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766765/+files/tcpdump17_04_2024_09H_10M1.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 2042363] tcpdump for aix 7.3 testing part 5 of 5

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:16 
EDT---


** Attachment added: "tcpdump for aix 7.3 testing part 5 of 5"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766763/+files/tcpdump16_04_2024_14H_03M4.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 2042363] tcpdump for aix 7.3 testing part 4 of 5

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:16 
EDT---


** Attachment added: "tcpdump for aix 7.3 testing part 4 of 5"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766762/+files/tcpdump16_04_2024_14H_03M3.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 2042363] tcpdump for aix 7.2 testing part 1 of 4

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:17 
EDT---


** Attachment added: "tcpdump for aix 7.2 testing part 1 of 4"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766764/+files/tcpdump17_04_2024_09H_10M.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 2042363] tcpdump for aix 7.3 testing part 3 of 5

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:15 
EDT---


** Attachment added: "tcpdump for aix 7.3 testing part 3 of 5"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766761/+files/tcpdump16_04_2024_14H_03M2.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 2042363] tcpdump for aix 7.3 testing part 1 of 5

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:14 
EDT---


** Attachment added: "tcpdump for aix 7.3 testing part 1 of 5"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766759/+files/tcpdump16_04_2024_14H_03M.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 2042363] tcpdump for aix 7.3 testing part 2 of 5

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:15 
EDT---


** Attachment added: "tcpdump for aix 7.3 testing part 2 of 5"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766760/+files/tcpdump16_04_2024_14H_03M1.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 2042363] Syslog for AIX 7.2 primary and partner

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:12 
EDT---


** Attachment added: "Syslog for AIX 7.2 primary and partner"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766758/+files/syslog_17042024_adia_primary_amberjack_partner_both_aix72.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 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver

2024-04-17 Thread Daniel van Vugt

** Changed in: gtk4 (Ubuntu)
   Importance: High => Medium

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

Title:
  GTK-ngl (new default backend) rendering issues with the nvidia 470
  driver

Status in GTK+:
  New
Status in gtk4 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Fix Released

Bug description:
  With nvidia driver, all GTK4 applications have label rendering issues.

  They are not refresh until passing the cursor over them, giving blank
  windows. The corner are white and not themed. Passing from one app
  scren to another one reproduces the issue.

  gnome-control-center or files, for instance, are blank by default.

  As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue.

  Related upstream bugs and discussions are:
  - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411
  - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542

  
  --

  
  $ glxinfo
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  server glx vendor string: NVIDIA Corporation
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, 
  GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  client glx vendor string: NVIDIA Corporation
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, 
  GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_multisample_coverage, 
  GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_context_flush_control, GLX_ARB_create_context, 
  GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, 
  GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, 
  GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
  GLX_SGI_video_sync
  Memory info (GL_NVX_gpu_memory_info):
  Dedicated video memory: 4096 MB
  Total available memory: 4096 MB
  Currently available dedicated video memory: 3041 MB
  OpenGL vendor string: NVIDIA Corporation
  OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2
  OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06
  OpenGL core profile shading language version string: 4.60 NVIDIA
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, 
  GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, 
  GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility,

[Kernel-packages] [Bug 2042363] Syslog and tcpdump file covering a working AIX 7.2 and non-working AIX 7.3 pair of machines using the same NFSv4 server

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:10 
EDT---


** Attachment added: "Syslog and tcpdump file covering a working AIX 7.2 and 
non-working AIX 7.3 pair of machines  using the same NFSv4 server"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766756/+files/syslog_16042024_amaliada_primary_adamsongrunter_partner_both_aix73_part1.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 2042363] Syslog and tcpdump file covering a working AIX 7.2 and non-working AIX 7.3 pair of machines using the same NFSv4 server

--- Comment (attachment only) From david_pa...@uk.ibm.com 2024-04-17 06:11 
EDT---


** Attachment added: "Syslog and tcpdump file covering a working AIX 7.2 and 
non-working AIX 7.3 pair of machines  using the same NFSv4 server"
   
https://bugs.launchpad.net/bugs/2042363/+attachment/5766757/+files/syslog_16042024_amaliada_primary_adamsongrunter_partner_both_aix73_part2.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 2061986] Re: Mount CIFS fails with Permission denied

2024-04-17 Thread Robert Malz

Attaching tcpdump output with patch

** Attachment added: "base_5_15_104_with_patch_filtered.pcap"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766753/+files/base_5_15_104_with_patch_filtered.pcap

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

Title:
Mount CIFS fails with Permission denied

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

Bug description:
[ Impact ]

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

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

* Issue can be reproduced on 5.15 or older Kernels, there is no reproduction
on 6.5 Kernel

* This scenario was fixed in upstream commit
9de0737d5ba0425c3154d5d83da12a8fa8595c0f

* An example of server without Key Exchange capability is Oracle Solaris
11.4 SMB zfs, meaning
mounting share from that server will result in ACCESS_DENIED error.

[ Test Plan ]

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

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

[1]

[2]

[3]

[4]

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

[ Where problems could occur ]

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

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

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

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

[ Other Info ]

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

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

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

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

2024-04-17 Thread Robert Malz

Attaching tcpdump output without patch

** Attachment added: "base_5_15_104_filtered.pcap"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766752/+files/base_5_15_104_filtered.pcap

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

Title:
Mount CIFS fails with Permission denied

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

Bug description:
[ Impact ]

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

* Issue can be reproduced on 5.15 or older Kernels, there is no reproduction
on 6.5 Kernel

* This scenario was fixed in upstream commit
9de0737d5ba0425c3154d5d83da12a8fa8595c0f

* An example of server without Key Exchange capability is Oracle Solaris
11.4 SMB zfs, meaning
mounting share from that server will result in ACCESS_DENIED error.

[ Test Plan ]

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

[1]

[2]

[3]

[4]

[ Where problems could occur ]

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

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

[ Other Info ]

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

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

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

2024-04-17 Thread Robert Malz

Public bug reported:

[ Impact ]

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

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

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

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

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

[1] 
[2] 

[3] 

[4] 


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

[ Where problems could occur ]

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

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

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

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

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

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Robert Malz (rmalz)
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Robert Malz (rmalz)
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Robert Malz (rmalz)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Robert Malz (rmalz)

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Robert Malz (rmalz)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Robert Malz (rmalz)

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

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

-- 
You received

[Kernel-packages] [Bug 2042363] Comment bridged from LTC Bugzilla

--- Comment From david_pa...@uk.ibm.com 2024-04-17 05:37 EDT---
Hi,
I have run the same MQ HA test on a working(AIX 7.2) and non working(AIX 7.3) 
pair of machines with the same Linux NVSv4 Ubuntu 20.04 (kernel updated to 
5.4.0-176-generic). I used the same RPC debug trace options as previously.

Here are the details of the uploaded tar.gz file called
CASE_TS012306761.tar.gz. I do have other trace files if you need them.

AIX 7.3 test was between machine amaliada and partner adamsongrunter on
16/04/2024 starting at 14:01 and failing at 14:04:07:971116 with a
failure to write a file on the shared NFSv4 server.

There is a partial syslog from the Linux NVSv4 server duckseason
covering that period called
TS012306761/syslog_16042024_amaliada_primary_adamsongrunter_partner_both_aix73.log

Covering the same period, there are a set of tcpdump files in subfolder
TS012306761/tcpdumps_amaliada_primary_admasongrunter_partner_both_aix73/


AIX 7.2 test was between primary machine adia and partner amberjack on 
17/04/2024 starting at 09:09:48 and ending successfully at 09:16:29.

There is a partial syslog from the linux NVSv4 server duckseason
covering that period called
TS012306761/syslog_17042024_adia_primary_amberjack_partner_both_aix72.log

Covering the same period, there are a set of tcpdump files in subfolder
TS012306761/tcpdumps_adia_primary_amberjack_partner_both_aix72/

We are happy to supply further info to help resolve this issue. Thanks
for your help and advice.

-- 
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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-17 Thread S

I feel compelled to agree with Axel and Andreas:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/comments/9

This bug is particularly surprising for a stable release, breaking CIFS
is not a pleasant thing to deal with.I tend to stick to the stable
builds to avoid things just like this.


Thank you all for the effort, obviously.  It truly is appreciated but the 
sooner this is fixed up the better, it should really be at critical levels of 
severity.

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2061040] Re: I2C HID device sometimes fails to initialize causing touchpad to not work

This issue is a regression of commit from v6.8-rc1 :

commit af93a167eda90192563bce64c4bb989836afac1f
Author: Hans de Goede 
Date:   Sat Dec 2 23:46:11 2023 +0100

HID: i2c-hid: Move i2c_hid_finish_hwreset() to after reading the
report-descriptor


Fix is still pending in hid repo, once it's in linus's tree, I will SRU it to 
6.8 kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/commit/?h=for-6.9/upstream-fixes=ea36bf1827462e4a52365bf8e3f7d1712c5d9600

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

Title:
  I2C HID device sometimes fails to initialize causing touchpad to not
  work

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

Bug description:
  Hi,

  Touchpad on my new Lenovo X1 Carbon (Gen12) with the Sensel haptic pad
  doesn't work on boot. I see this:

  | [Thu Apr 11 13:57:26 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack 
reset within 1000 ms
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unknown main 
item tag 0x0
  | ...
  | [Thu Apr 11 13:57:26 2024] hid-generic 0018:2C2F:0028.0001: unbalanced 
collection at end of report description
  | [Thu Apr 11 13:57:26 2024] hid-generic: probe of 0018:2C2F:0028.0001 failed 
with error -22

  Per the Arch Linux wiki page[1], removing and reloading the
  `i2c_hid_acpi` seems to fix it:

  | [Thu Apr 11 13:58:02 2024] i2c_hid_acpi i2c-SNSL0028:00: device did not ack 
reset within 1000 ms
  | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input15
  | [Thu Apr 11 13:58:02 2024] input: SNSL0028:00 2C2F:0028 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-15/i2c-SNSL0028:00/0018:2C2F:0028.0002/input/input16
  | [Thu Apr 11 13:58:02 2024] hid-multitouch 0018:2C2F:0028.0002: 
input,hidraw0: I2C HID v1.00 Mouse [SNSL0028:00 2C2F:0028] on i2c-SNSL0028:00
  | [Thu Apr 11 13:58:03 2024] psmouse serio1: trackpoint: Synaptics TrackPoint 
firmware: 0x08, buttons: 3/3
  | [Thu Apr 11 13:58:03 2024] input: TPPS/2 Synaptics TrackPoint as 
/devices/platform/i8042/serio1/input/input18

  From that Arch Linux wiki page, it seems to be a bug upstream[2] with
  the commit fixing this:

  |
  
https://github.com/torvalds/linux/commit/af93a167eda90192563bce64c4bb989836afac1f

  Or

  | https://lore.kernel.org/linux-
  input/20240331182440.14477-1...@kl.wtf/T/#u

  Can we get fix this backported?

  | [hloeung@dharkan tmp]$ apt-cache policy linux-image-generic-hwe-24.04
  | linux-image-generic-hwe-24.04:
  |   Installed: 6.8.0-22.22
  |   Candidate: 6.8.0-22.22
  |   Version table:
  |  *** 6.8.0-22.22 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ uname -a
  | Linux dharkan.local 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 
 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  | [hloeung@dharkan tmp]$

  Thanks,

  Haw

  [1]: https://wiki.archlinux.org/title/Lenovo_ThinkPad_Z16_Gen_2
  [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2271136

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061040/+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 2049570] Re: 10de:28B9 was not supported in nvidia-driver-535

2024-04-17 Thread Bin Li

535.171.04 is supported the 28B9.

available: 535.171.04-0ubuntu0.22.04.1 [distro] non-free
modalias: pci:v10DEd28B9sv17AAsd2234bc03sc02i00
path: /sys/devices/pci:00/:00:01.0/:01:00.0
vendor: NVIDIA Corporation
support level: PB

** Changed in: oem-priority
   Status: New => Fix Released

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

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

Title:
  10de:28B9 was not supported in nvidia-driver-535

Status in OEM Priority Project:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released

Bug description:
  On OEM project, we found the 28B9 is not supported in nvidia-
  driver-535, the version 535.154.05-0ubuntu0.22.04.1 in the proposed
  channel also doesn't include this id.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2049570/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)

2024-04-17 Thread Richard van der Hoff

> And this call trace looks is related to current issue, I guess
snd_power_ref_and_wait was waiting for snd_card_disconnect which wakes
up power_sleep at the end of the code, but snd_card_disconnect ->
snd_device_disconnect_all -> snd_pcm_dev_disconnect was blocked for some
reason.

Yes, interesting. Good spot.

> Looks suspend/resume can be completed sometimes.

Yes. I think what causes the problem is when I disconnect from my USB
dock. After that, I can't suspend until I reboot. Once I reboot, it can
suspend again until I once more disconnect the dock.

> Could you rebuild kernel with CONFIG_PROVE_LOCKING option to discover locking 
> related deadlocks? Then upload the log after reproduce the issue by shut down 
> laptop with the new kernel. Also please attach the output of lsusb given it 
> could be usb relevant.
>
> And it also would be helpful to try with latest noble kernel or recent 
> upstream kernel, thanks.

Sure. I'll try an upstream kernel with CONFIG_PROVE_LOCKING.

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

Title:
  Freezing user space processes failed after 20.008 seconds (1 tasks
  refusing to freeze, wq_busy=0)

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

Bug description:
  Sometimes, when trying to shut down or suspend my laptop, it gets
  stuck on the console screen. If I was suspending, it eventually gives
  up and goes back to the X session. During a shutdown it hangs forever
  and the only solution seems to be to force a reboot with Magic-SysRq.

  The following appears in `kern.log`:

  ```
  Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes 
failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
  Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D 
stack:0 pid:2408  ppid:2398   flags:0x0006
  Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace:
  Apr 12 08:59:54 xps9320 kernel: [173172.521755]  
  Apr 12 08:59:54 xps9320 kernel: [173172.524099]  __schedule+0x2cb/0x750
  Apr 12 08:59:54 xps9320 kernel: [173172.526333]  schedule+0x63/0x110
  Apr 12 08:59:54 xps9320 kernel: [173172.528585]  
snd_power_ref_and_wait+0xe5/0x140 [snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.530825]  ? 
__pfx_autoremove_wake_function+0x10/0x10
  Apr 12 08:59:54 xps9320 kernel: [173172.533103]  snd_ctl_elem_info+0x4f/0x1b0 
[snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.535354]  
snd_ctl_elem_info_user+0x59/0xc0 [snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.537598]  snd_ctl_ioctl+0x1d4/0x650 
[snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.539846]  ? __fget_light+0xa5/0x120
  Apr 12 08:59:54 xps9320 kernel: [173172.542082]  __x64_sys_ioctl+0xa0/0xf0
  Apr 12 08:59:54 xps9320 kernel: [173172.544334]  do_syscall_64+0x58/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.546566]  ? 
syscall_exit_to_user_mode+0x37/0x60
  Apr 12 08:59:54 xps9320 kernel: [173172.548838]  ? do_syscall_64+0x67/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.551085]  ? do_syscall_64+0x67/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.553342]  ? 
syscall_exit_to_user_mode+0x37/0x60
  Apr 12 08:59:54 xps9320 kernel: [173172.96]  ? do_syscall_64+0x67/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.557828]  ? common_interrupt+0x54/0xb0
  Apr 12 08:59:54 xps9320 kernel: [173172.560075]  
entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f
  Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 
EFLAGS: 0246 ORIG_RAX: 0010
  Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 
7ffef20729b0 RCX: 70f3adb1a94f
  Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: 
c1105511 RDI: 0022
  Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 
65107d2b6070 R09: 0004
  Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 
0246 R12: 65107d2ee100
  Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 
7ffef2072b30 R15: 7ffef2072ad0
  Apr 12 08:59:54 xps9320 kernel: [173172.578308]  
  ```

  
  Another point of interest is that, when in this situation:
   * `lsusb` hangs after printing out a few lines
   * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent 
appears to be trying to check for smartcards.

  So I guess there is some sort of deadlock in the USB subsystem which
  is causing all the other problems?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop:

[Kernel-packages] [Bug 2053194] Re: latest kernel update breaks sata hotplug on z690

Could someone do git bisect to check which commit could cause the regression? 
My wild guess would be
the commit which add Intel Alder Lake-P AHCI controller to low power chipsets 
list or others in the following.


$ git log --oneline Ubuntu-5.15.0-92.102..Ubuntu-5.15.0-94.104 |grep "ata: ahci"
c553eda3bac6 ata: ahci: Add Intel Alder Lake-P AHCI controller to low power 
chipsets list
0e2b3a2aa29d ata: ahci: Add Elkhart Lake AHCI controller
6fd0f4242184 ata: ahci: Rename board_ahci_mobile
65ecbaa1fe47 ata: ahci: Add support for AMD A85 FCH (Hudson D4)
c21705b5ee4f ata: ahci: Drop pointless VPRINTK() calls and convert the 
remaining ones

$ git log --oneline  
Ubuntu-hwe-6.5-6.5.0-15.15_22.04.1..Ubuntu-hwe-6.5-6.5.0-17.17_22.04.1|grep 
"ata: ahci"
df508bb822f9 ata: ahci: Add Intel Alder Lake-P AHCI controller to low power 
chipsets list
2a4dad1ecdf3 ata: ahci: Add Elkhart Lake AHCI controller

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

Title:
  latest kernel update breaks sata hotplug on z690

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

Bug description:
  SATA hotplug is not working on these kernels:
  linux-image-6.5.0-17-generic
  linux-image-5.15.0-94-generic

  SATA hotplug is working on these kernels:
  linux-image-6.5.0-15-generic
  linux-image-5.15.0-92-generic

  Affected platform:
  Gigabyte Z690 AORUS PRO
  BIOS Version: F28

  Note that I can only repro this on Z690. I also tried Z390 and Z370
  platforms and SATA hotplug it is working there.

  Steps to repro:
  1. Enable SATA hotplug in BIOS
  2. Boot to affected kernel
  3. Hotplug a SATA drive while monitoring kernel messages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 13:20:34 2024
  InstallationDate: Installed on 2024-01-26 (18 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2024-01-26T15:01:36.495491

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2053194/+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 2048951] Re: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux-image-6.5.0-18-generic (linux-image-generic-hwe-22.04)

2024-04-17 Thread lousuan

Same Problem here. I'm using 6.5.0-25-generic.
Heres what i get by `dmesg -T`.

** Attachment added: "dmesg-2024-04-17.log"

https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+attachment/5766711/+files/dmesg-2024-04-17.log

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

Title:
Kernel Oops - kernel NULL pointer dereference
(apparmor_bprm_creds_for_exec, profile_transition) with linux-
image-6.5.0-18-generic (linux-image-generic-hwe-22.04)

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

Bug description:
Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few
minutes after the boot.
I can't find anything in the journal for the previous boot it just ends
without any error. Remote syslog server does not receive any error log from
this host. I've tried running journalctl on the local console and wait for the
hang got nothing.
On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the
screen and the rest is what was on the console before the hang:
ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
so it is definitely the new kernel.

I don't have enough time to generate report with ubuntu-bug on the new
kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
one.

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

[Kernel-packages] [Bug 2048951] Re: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux-image-6.5.0-18-generic (linux-image-generic-hwe-22.04)

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

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

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

Title:
  Kernel Oops - kernel NULL pointer dereference
  (apparmor_bprm_creds_for_exec, profile_transition) with linux-
  image-6.5.0-18-generic (linux-image-generic-hwe-22.04)

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

Bug description:
  Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few 
minutes after the boot.
  I can't find anything in the journal for the previous boot it just ends 
without any error. Remote syslog server does not receive any error log from 
this host. I've tried running journalctl on the local console and wait for the 
hang got nothing.
  On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the 
screen and the rest is what was on the console before the hang:
   ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48

  Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue,
  so it is definitely the new kernel.

  I don't have enough time to generate report with ubuntu-bug on the new
  kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older
  one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+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 2060727] Re: The keyboard does not work after latest kernel update

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

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

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

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

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)

Looks suspend/resume can be completed sometimes.

Apr 15 12:49:26 xps9320 kernel: [10214.971688] Freezing user space processes 
completed (elapsed 0.002 seconds)
Apr 15 21:45:23 xps9320 kernel: [30355.137512] Freezing user space processes 
completed (elapsed 0.015 seconds)
Apr 15 23:02:59 xps9320 kernel: [47737.172847] Freezing user space processes 
failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:03:19 xps9320 kernel: [47757.538206] Freezing user space processes 
failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:03:49 xps9320 kernel: [47787.948230] Freezing user space processes 
failed after 20.010 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:04:10 xps9320 kernel: [47808.293913] Freezing user space processes 
failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:04:40 xps9320 kernel: [47838.963650] Freezing user space processes 
failed after 20.011 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:05:01 xps9320 kernel: [47859.321047] Freezing user space processes 
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:05:31 xps9320 kernel: [47889.930764] Freezing user space processes 
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:05:52 xps9320 kernel: [47910.270362] Freezing user space processes 
failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:06:22 xps9320 kernel: [47940.942995] Freezing user space processes 
failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:06:43 xps9320 kernel: [47961.284299] Freezing user space processes 
failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:07:13 xps9320 kernel: [47991.938673] Freezing user space processes 
failed after 20.003 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:07:34 xps9320 kernel: [48012.283148] Freezing user space processes 
failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:07:54 xps9320 kernel: [48032.682674] Freezing user space processes 
failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:08:15 xps9320 kernel: [48053.066382] Freezing user space processes 
failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:08:37 xps9320 kernel: [48075.379470] Freezing user space processes 
failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:08:57 xps9320 kernel: [48095.707188] Freezing user space processes 
failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:09:18 xps9320 kernel: [48116.090956] Freezing user space processes 
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:09:38 xps9320 kernel: [48136.438119] Freezing user space processes 
failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:09:59 xps9320 kernel: [48157.256494] Freezing user space processes 
failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:10:19 xps9320 kernel: [48177.593855] Freezing user space processes 
failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:10:41 xps9320 kernel: [48199.473829] Freezing user space processes 
failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:11:01 xps9320 kernel: [48219.806060] Freezing user space processes 
failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:11:22 xps9320 kernel: [48240.188072] Freezing user space processes 
failed after 20.011 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 15 23:11:42 xps9320 kernel: [48260.947835] Freezing user space processes 
failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0):
Apr 16 12:52:21 xps9320 kernel: [13407.856663] Freezing user space processes 
completed (elapsed 0.002 seconds)

Could you rebuild kernel with CONFIG_PROVE_LOCKING option to discover
locking related deadlocks? Then upload the log after reproduce the issue
by shut down laptop with the new kernel. Also please attach the output
of lsusb given it could be usb relevant.

And it also would be helpful to try with latest noble kernel or recent
upstream kernel, thanks.

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

Title:
  Freezing user space processes failed after 20.008 seconds (1 tasks
  refusing to freeze, wq_busy=0)

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

Bug description:
  Sometimes, when trying to shut down or suspend my laptop, it gets
  stuck on the console screen. If I was suspending, it eventually gives
  up and goes back to the X session. During a shutdown it hangs forever
  and the only solution seems to be to force a reboot with Magic-SysRq.

  The following appears in `kern.log`:

  ```
  Apr 12 08:59:54 xps9320 kernel:

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

** Description changed:

  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.
  
  --
  
  In /var/log/apt/history.log , the latest we can see is:
  
  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51
  
  --
  
  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10
  
  $ # Note: It's Kubuntu 23.10
  
  --
  
  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
+ 
+ SRU Justification:
+ ==
+ [Impact]
+ Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
+ versions.
+ 
+ [Fix]
+ Regression commit is found commit:
+ 936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")
+ 
+ Fixes:
+ 9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
+ skipping ATKBD_CMD_GETID
+ 683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
+ ATKBD_CMD_GETID
+ 
+ [Test]
+ Tested on hardware, keyboard works fine after bootup.
+ 
+ [Where problems could occur]
+ It may break keyboard.

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

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

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

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

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

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

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

** Description changed:

  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.
  
  --
  
  In /var/log/apt/history.log , the latest we can see is:
  
  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51
  
  --
  
  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10
  
  $ # Note: It's Kubuntu 23.10
  
  --
  
  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  
  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.
  
  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")
  
  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID
  
  [Test]
  Tested on hardware, keyboard works fine after bootup.
  
+ The regression commit is only in 6.5 stable, so SRU for 6.5 only.
+ 
  [Where problems could occur]
  It may break keyboard.

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  Confirmed

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

The regression commit is:
commit a6cb9c9b40551d61bb6fb3b24ef27563947360b7
Author: Hans de Goede 
Date:   Fri Nov 24 19:59:24 2023 -0800

Input: atkbd - skip ATKBD_CMD_GETID in translated mode

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

[ Upstream commit 936e4d49ecbc8c404790504386e1422b599dec39 ]

It's in v6.8-rc1. The fix might be in v6.8-rc3:

commit 9cf6e24c9fbf17e52de9fff07f12be7565ea6d61
Author: Hans de Goede 
Date:   Fri Jan 26 17:07:24 2024 +0100

Input: atkbd - do not skip atkbd_deactivate() when skipping
ATKBD_CMD_GETID

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2061953] [NEW] intel_rapl_common: Add support for ARL and LNL