[Kernel-packages] [Bug 2060919] Re: cifs: Copying file to same directory results in page fault

[Matthew Ruffell]

Hi everyone,

The kernel team has built the patch into the s2024.04.1 SRU cycle, as
6.5.0-35-generic.

An ETA for this is the week of 13th of May, as per
https://kernel.ubuntu.com/

Would anyone be able to help test the kernel by installing
6.5.0-35-generic from -proposed and doing a cifs mount and copying
files?

Currently only the Mantic kernel is built. The HWE kernel for Jammy
hasn't been built yet, but I will write back once it is available.

The kernel is currently in the kernel team's proposed2 ppa, instead of
the usual -proposed pocket, but you can have a look here:

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

Instructions to install (On a mantic system):
1) sudo add-apt-repository ppa:canonical-kernel-team/proposed2
2) sudo apt update
3) sudo apt install linux-image-6.5.0-35-generic linux-modules-6.5.0-35-generic 
linux-modules-extra-6.5.0-35-generic linux-headers-6.5.0-35-generic
4) sudo rm 
/etc/apt/sources.list.d/canonical-kernel-team-ubuntu-proposed2-mantic.sources
5) sudo apt update
6) sudo reboot
7) uname -rv
6.5.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 26 11:23:57 UTC 2024

Let me know if this kernel fixes the issue for you, and if it does, I'll
mark the bug as verified.

Thanks,
Matthew

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

Title:
  cifs: Copying file to same directory results in page fault

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

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

  [Impact]

  Copying or modifying a file to the same directory within a cifs mount
  results in a page fault, and the process that initiated the copy being
  killed. This could be cp, nautilus, etc.

  This results in the following oops:

  BUG: unable to handle page fault for address: fffe
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x) - not-present page
  PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0
  Oops:  [#1] PREEMPT SMP NOPTI
  CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic 
#28-Ubuntu
  RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 
89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 
f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  RAX:  RBX: fffe RCX: 
  RDX:  RSI:  RDI: 
  RBP: aab6865ffc28 R08: 0001 R09: 
  R10: 00023854 R11:  R12: 
  R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70
  FS: 7bd4d594b6c0() GS:90753f80() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: fffe CR3: 00017022a000 CR4: 00750ef0
  PKRU: 5554
  Call Trace:
  
  ? show_regs+0x6d/0x80
  ? __die+0x24/0x80
  ? page_fault_oops+0x99/0x1b0
  ? kernelmode_fixup_or_oops+0xb2/0x140
  ? __bad_area_nosemaphore+0x1a5/0x2c0
  ? bad_area_nosemaphore+0x16/0x30
  ? do_kern_addr_fault+0x7b/0xa0
  ? exc_page_fault+0x1a4/0x1b0
  ? asm_exc_page_fault+0x27/0x30
  ? cifs_flush_folio+0x41/0xf0 [cifs]
  ? cifs_flush_folio+0x37/0xf0 [cifs]
  cifs_remap_file_range+0x172/0x660 [cifs]
  do_clone_file_range+0x101/0x2d0
  vfs_clone_file_range+0x3f/0x150
  ioctl_file_clone+0x52/0xc0
  do_vfs_ioctl+0x68f/0x910
  ? __fget_light+0xa5/0x120
  __x64_sys_ioctl+0x7d/0xf0
  do_syscall_64+0x59/0x90
  ? kmem_cache_free+0x22/0x3e0
  ? putname+0x5b/0x80
  ? exit_to_user_mode_prepare+0x30/0xb0
  ? syscall_exit_to_user_mode+0x37/0x60
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90

  There is no known workaround.

  [Fix]

  The stacktrace is very similar to a regression reported to upstream
  6.1.y:

  https://lore.kernel.org/linux-
  mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/

  The thread mentions that:

  commit 7b2404a886f8b91250c31855d287e632123e1746
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746

  introduced the issue to Debian's 6.1 kernel.

  This got backported to Ubuntu in:

  commit 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()

  $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Ubuntu-6.5.0-20.20~107

  Which we have been using for some time now, and is not the culprit.

  Reading the regression mailing list thread, 

[Kernel-packages] [Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[Daniel van Vugt]

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

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

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in linux package in Ubuntu:
  New

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2024
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1UET46W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21B4S4QB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76465 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
  dmi.product.family: ThinkPad L13 Gen 3
  dmi.product.name: 21B4S4QB00
  dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
  dmi.product.version: ThinkPad L13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062950/+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 2064017] Re: Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)

[Daniel van Vugt]

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

** Tags added: flicker

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

Title:
  Xserver Display flickers when mouse pointer is inside narrow
  horizontal range band (kernel related)

Status in linux package in Ubuntu:
  New

Bug description:
  
  My machine information is following :
  HP EliteBook 840 G3
  Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520]
  xrandr -q active mode on laptop display : 1368x768  60.01

  Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped 
kernel 6.8.0-31), same issue.
  Rolling back the kernel to 6.7 fixed the problem,maybe there were some video 
driver changes from kernel 6.7 to 6.8 ?

  While using the 6.8 kernel I did some experiments:

  disabled picom in startup , no effect

  Tried changing display resolution, just moves vertical position of band.
  (at the above resolution 1368x768 vertical mouse pointer flicker range is 
around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from 
a bash terminal)

  Tried moving refresh rate slightly around 60 Hz by creating a new
  modeline using cvt tool and adding new mode with xrandr, no effect.

  tried connecting external display on laptop VGA port and duplicating
  screen and the issue seems to disappear.

  tried capturing a video of the desktop  using ffmpeg with x11grab, but
  it does not show the issue.

  I attached a short video of the laptop display flicker I recorded
  using my phone

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Sun Apr 28 09:44:42 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
  InstallationDate: Installed on 2024-04-25 (3 days ago)
  InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 
(20240425.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP HD Camera
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP EliteBook 840 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.release: 1.42
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.42
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.78
  dmi.chassis.asset.tag: 5CG7042V5J
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.120
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: Z2A57UT#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064017/+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 2064064] Re: Add support of TAS2781 amp of audio

[Juerg Haefliger]

** Tags added: kern-10802

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

Title:
  Add support of TAS2781 amp of audio

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

Bug description:
  [Impact]
  No output from the right speaker.

  [Fix]
  Add driver for TAS2781 and firmware to support the new hardware.

  [Test]
  Tested on hardware, the output of speakers works fine
  on bootup and resume for 10 times.

  [Where problems could occur]
  It may break audio output.

  It includes 7 commits from 6.8 kernel and 1 from 6.9-rc5 as a new driver.
  SRU for OEM-6.5 and Noble only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2064064/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Jens Glathe]

Hmm an additional data point: I accidentally updated the Windows Dev Kit
instead of the X13s to 24.04 (yes, really) and it installed the
6.8.0-31-generic kernel, however no dtb - but that's to be expected when
flash-kernel is not installed, and being an unsupported device. After
symlinking my dtb, and updating initramfs (as described above #25) this
kernel also boots and is quite usable. qseecom / efivar support appears
to be missing or not compatible, and there are more error messages
regarding pmic glink. qrtr-ns and pd-mapper are up ,though.

`Linux volterra 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr
20 02:32:42 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux`

My additional kernel cmdline parameters are `pd_ignore_unused
clk_ignore_unused arm64.nopauth efi=noruntime`, like on the X13s.

So... kernel config appears to be about okay when booting from nvme.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

[Juerg Haefliger]

** Changed in: linux-raspi2 (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Won't Fix

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857760/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~juergh/ubuntu-seeds/+git/ubuntu/+merge/465215

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Aaron Honeycutt]

@juergh

I'm now able to boot 6.8.0-31-generic with that package (from that PPA)
added to my system! Nicely done!

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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)

[GuoqingJiang]

Thanks for the update, could you bisect which commit fixes the issue
since upstream 6.8 works?

https://git-scm.com/docs/git-bisect

-- 
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: ubuntu:GNOME
  Date: Fri Apr 12 09:42:52 2024
  InstallationDate: Installed on 2022-06-28 (653 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+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 2063228] Re: screen sometimes blinking

[Daniel van Vugt]

Please try adding this to /etc/environment:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

and then reboot.

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

Title:
  screen sometimes blinking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Pavilion Laptop 14-ce2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2022
  dmi.bios.release: 15.27
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84BB
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 14-ce2xxx
  dmi.product.sku: 8KZ34EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+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 2061376] Re: Touchpad scroll bounces back 22.04.4

[Kai-Heng Feng]

Also, does different browsers have the same issue?

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

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

Title:
  Touchpad scroll bounces back 22.04.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When scrolling anywhere using 2 fingers the scroll bounces back if
  fingers are lifted up from touchpad. Soft finger point muscles have
  some flex to them and I strongly believe this causes the scroll bounce
  back. Easily repeated to both directions. In bounce scroll rapidly
  moves to the opposite direction of where user wanted to scroll when
  lifting up fingers.

  Attached is log file evtest_event5.log from single scroll where there
  was bounce at lifting fingers.

  Hardware details:
  xinput --list
  WARNING: running xinput against an Xwayland server. See the xinput man page 
for details.
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-pointer:16 id=6[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-relative-pointer:16id=7[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-pointer-gestures:16id=8[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-touch:16   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet stylus:16   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet eraser:16   id=12   [slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet cursor:16   id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ xwayland-keyboard:16id=9[slave  
keyboard (3)]

  lshw
    *-input:0
     product: Sleep Button
     physical id: 2
     logical name: input0
     logical name: /dev/input/event0
     capabilities: platform
    *-input:1
     product: Lid Switch
     physical id: 3
     logical name: input1
     logical name: /dev/input/event1
     capabilities: platform
    *-input:2
     product: Intel HID events
     physical id: 4
     logical name: input17
     logical name: /dev/input/event9
     capabilities: platform
    *-input:3
     product: ThinkPad Extra Buttons
     physical id: 5
     logical name: input18
     logical name: /dev/input/event10
     capabilities: platform
    *-input:4
     product: SYNA8007:00 06CB:CD8C Mouse
     physical id: 6
     logical name: input19
     logical name: /dev/input/event4
     logical name: /dev/input/mouse0
     capabilities: i2c
    *-input:5
     product: Power Button
     physical id: 7
     logical name: input2
     logical name: /dev/input/event2
     capabilities: platform
    *-input:6
     product: SYNA8007:00 06CB:CD8C Touchpad
     physical id: 8
     logical name: input20
     logical name: /dev/input/event5
     logical name: /dev/input/mouse1
     capabilities: i2c
    *-input:7
     product: Video Bus
     physical id: 9
     logical name: input22
     logical name: /dev/input/event11
     capabilities: platform
    *-input:8
     product: sof-hda-dsp Mic
     physical id: a
     logical name: input23
     logical name: /dev/input/event12
    *-input:9
     product: sof-hda-dsp Headphone
     physical id: b
     logical name: input24
     logical name: /dev/input/event13
    *-input:10
     product: sof-hda-dsp HDMI/DP,pcm=3
     physical id: c
     logical name: input25
     logical name: /dev/input/event14
    *-input:11
     product: sof-hda-dsp HDMI/DP,pcm=4
     physical id: d
     logical name: input26
     logical name: /dev/input/event15
    *-input:12
     product: sof-hda-dsp HDMI/DP,pcm=5
     physical id: e
     logical name: input27
     logical name: /dev/input/event16
    *-input:13
     product: AT Translated Set 2 keyboard
     physical id: f
     logical name: input3
     logical name: /dev/input/event3
     logical name: input3::capslock
     logical name: input3::numlock
     logical name: input3::scrolllock
     capabilities: i8042
    *-input:14
     product: TPPS/2 ALPS TrackPoint
     physical id: 10
     logical name: input5
     logical name: /dev/input/event6
     logical name: /dev/input/mouse2
     capabilities: i8042

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


-- 
Mailing list: 

[Kernel-packages] [Bug 2061376] Re: Touchpad scroll bounces back 22.04.4

[Kai-Heng Feng]

Please run `apport-collect 2061376` to attach logs here.

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

Title:
  Touchpad scroll bounces back 22.04.4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When scrolling anywhere using 2 fingers the scroll bounces back if
  fingers are lifted up from touchpad. Soft finger point muscles have
  some flex to them and I strongly believe this causes the scroll bounce
  back. Easily repeated to both directions. In bounce scroll rapidly
  moves to the opposite direction of where user wanted to scroll when
  lifting up fingers.

  Attached is log file evtest_event5.log from single scroll where there
  was bounce at lifting fingers.

  Hardware details:
  xinput --list
  WARNING: running xinput against an Xwayland server. See the xinput man page 
for details.
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-pointer:16 id=6[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-relative-pointer:16id=7[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-pointer-gestures:16id=8[slave  pointer 
 (2)]
  ⎜   ↳ xwayland-touch:16   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet stylus:16   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet eraser:16   id=12   [slave  pointer 
 (2)]
  ⎜   ↳ xwayland-tablet cursor:16   id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ xwayland-keyboard:16id=9[slave  
keyboard (3)]

  lshw
    *-input:0
     product: Sleep Button
     physical id: 2
     logical name: input0
     logical name: /dev/input/event0
     capabilities: platform
    *-input:1
     product: Lid Switch
     physical id: 3
     logical name: input1
     logical name: /dev/input/event1
     capabilities: platform
    *-input:2
     product: Intel HID events
     physical id: 4
     logical name: input17
     logical name: /dev/input/event9
     capabilities: platform
    *-input:3
     product: ThinkPad Extra Buttons
     physical id: 5
     logical name: input18
     logical name: /dev/input/event10
     capabilities: platform
    *-input:4
     product: SYNA8007:00 06CB:CD8C Mouse
     physical id: 6
     logical name: input19
     logical name: /dev/input/event4
     logical name: /dev/input/mouse0
     capabilities: i2c
    *-input:5
     product: Power Button
     physical id: 7
     logical name: input2
     logical name: /dev/input/event2
     capabilities: platform
    *-input:6
     product: SYNA8007:00 06CB:CD8C Touchpad
     physical id: 8
     logical name: input20
     logical name: /dev/input/event5
     logical name: /dev/input/mouse1
     capabilities: i2c
    *-input:7
     product: Video Bus
     physical id: 9
     logical name: input22
     logical name: /dev/input/event11
     capabilities: platform
    *-input:8
     product: sof-hda-dsp Mic
     physical id: a
     logical name: input23
     logical name: /dev/input/event12
    *-input:9
     product: sof-hda-dsp Headphone
     physical id: b
     logical name: input24
     logical name: /dev/input/event13
    *-input:10
     product: sof-hda-dsp HDMI/DP,pcm=3
     physical id: c
     logical name: input25
     logical name: /dev/input/event14
    *-input:11
     product: sof-hda-dsp HDMI/DP,pcm=4
     physical id: d
     logical name: input26
     logical name: /dev/input/event15
    *-input:12
     product: sof-hda-dsp HDMI/DP,pcm=5
     physical id: e
     logical name: input27
     logical name: /dev/input/event16
    *-input:13
     product: AT Translated Set 2 keyboard
     physical id: f
     logical name: input3
     logical name: /dev/input/event3
     logical name: input3::capslock
     logical name: input3::numlock
     logical name: input3::scrolllock
     capabilities: i8042
    *-input:14
     product: TPPS/2 ALPS TrackPoint
     physical id: 10
     logical name: input5
     logical name: /dev/input/event6
     logical name: /dev/input/mouse2
     capabilities: i8042

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


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

[Kernel-packages] [Bug 2064189] [NEW] Screen flickers after installing Ubuntu 24.04

[Melquisedeque Nunes Lopes]

Public bug reported:

I've been struggling with some random screen flickering after a fresh
install of Ubuntu 24.04.

My laptop is running the Mesa Intel(R) HD Graphics 620 (KBL GT2F)
integrated graphics.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-31-generic 6.8.0-31.31
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:melk   2393 F pipewire
 /dev/snd/controlC0:  melk   2401 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 29 22:22:53 2024
InstallationDate: Installed on 2024-04-29 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Dell Inc. Inspiron 3584
ProcEnviron:
 LANG=pt_BR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=2e0a4d2b-a47f-4fff-8c17-c90f6816b03e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-31-generic N/A
 linux-backports-modules-6.8.0-31-generic  N/A
 linux-firmware20240318.git3b128b60-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2023
dmi.bios.release: 1.24
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.24.0
dmi.board.name: 05RCHV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd09/12/2023:br1.24:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr:sku08D1:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3584
dmi.product.sku: 08D1
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Screen flickers after installing Ubuntu 24.04

Status in linux package in Ubuntu:
  New

Bug description:
  I've been struggling with some random screen flickering after a fresh
  install of Ubuntu 24.04.

  My laptop is running the Mesa Intel(R) HD Graphics 620 (KBL GT2F)
  integrated graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-31-generic 6.8.0-31.31
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:melk   2393 F pipewire
   /dev/snd/controlC0:  melk   2401 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 22:22:53 2024
  InstallationDate: Installed on 2024-04-29 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Dell Inc. Inspiron 3584
  ProcEnviron:
   LANG=pt_BR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=2e0a4d2b-a47f-4fff-8c17-c90f6816b03e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-31-generic N/A
   linux-backports-modules-6.8.0-31-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 05RCHV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd09/12/2023:br1.24:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr:sku08D1:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3584
  dmi.product.sku: 08D1
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064189/+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 2064184] [NEW] sdhci_of_dwcmshc: sync up "disable PM runtime in dwcmshc_remove()" from upstream

[Liming Sun]

Public bug reported:

SRU Justification:

[Impact]
It shouldn't affect normal functionalities. With this fix, it'll remove a 
warning when unloading and loading the sdhci_of_dwcmshc kernel driver.

[Fix]
The fix unload the runtime PM when unloading the sdhci_of_dwcmshc driver.

[Test Case]
Normal regression;
Unload and load sdhci_of_dwcmshc.ko again.

[Regression Potential]
Same behavior from user perspective.

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

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

Title:
  sdhci_of_dwcmshc: sync up "disable PM runtime in dwcmshc_remove()"
  from upstream

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  It shouldn't affect normal functionalities. With this fix, it'll remove a 
warning when unloading and loading the sdhci_of_dwcmshc kernel driver.

  [Fix]
  The fix unload the runtime PM when unloading the sdhci_of_dwcmshc driver.

  [Test Case]
  Normal regression;
  Unload and load sdhci_of_dwcmshc.ko again.

  [Regression Potential]
  Same behavior from user perspective.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2064184/+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 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04

[Adrian Wilkins]

Confirmed ; reboot ...

- Asked for elevation because of a process inhibiting shutdown
- This was cancelled
- I then got logged out of my session
- I logged in again and got prompted for a system program crash dump elevation
- This was provided but _then_ my system rebooted
- Same issue, unresponsive to power button until a long-press was completed 
first


Last entries in log from a lid-close are ...

2024-04-29T07:54:52.626549+01:00 hitomi systemd[1]: Reached target sleep.target 
- Sleep.
2024-04-29T07:54:52.640520+01:00 hitomi systemd[1]: Starting 
systemd-suspend.service - System Suspend...
2024-04-29T07:54:52.705918+01:00 hitomi kernel: PM: suspend entry (deep)
2024-04-29T07:54:52.706135+01:00 hitomi systemd-sleep[8809]: Performing sleep 
operation 'suspend'...

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

Title:
  Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  [Overview]
  I have been testing installations of a number of Lubuntu and Xubuntu Noble 
Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more 
latterly focused on Lubuntu.

  It would appear that since introduction of Kernel 6.8 into the daily
  builds, the installed system fails to carry out a successful reboot or
  power off  when commanded from the desktop or the command line

  [Symptoms]
  When selecting either Leave-->Shutdown or Leave-->Reboot from the control 
panel, the process starts shutting down processes in an orderly fashion, until 
it gets to the part where it needs to power off hardware, where it hangs.

  shutdown -H now also fails in the same manner
  shutdown -r now also fails in the same manner

  With quiet bootflag disabled, the last system message on display before the 
hang is
  "Starting reboot..." or "Starting power-off..."

  [Workaround]
  The power button must be pressed for 5 secs to power down the hardware

  [Possibly related bugs]
  #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04
  #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10

  [Unsuccessful Workarounds]
  Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No 
effect

  [Observations]
  I do believe that shutdown/reboot was working correctly on a live USB Lubuntu 
Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024.  This 
release had an earlier kernel than 6.8. Sadly i no longer have the .iso to 
confirm this.  

  All Lubuntu Noble daily builds since kernel 6.8 was introduced appear
  to exhibit the symptoms as above

  [System info]
  Operating System: Ubuntu Noble Numbat (development branch)
Kernel: Linux 6.8.0-11-generic
  Architecture: x86-64
   Hardware Vendor: Dell Inc.
Hardware Model: Wyse 3040 Thin Client
  Firmware Version: 1.2.5
 Firmware Date: Mon 2018-08-20

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2059738/+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 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04

[Adrian Wilkins]

Seeing this on my T460s as well

Suspend (on lid close) ; the machine reaches the state where the lid
light and the light on the power button "throb" as they would with
22.04, but the machine will not resume from suspend in response to
keyboard events, mouse events, or a brief press to the power button.

Poweroff : the machine reaches a state where everything appears "off",
no lights, no screen activity etc, but the machine does not restart in
response to a brief press of the power button.

In both cases, a long-press of the power button is required. You can
tell this has "taken" when the lights on the hardwire ethernet port
blink briefly on release.

Then a normal brief press will restart the machine.

Both of these conditions happen reliably on lid close (suspend) or
poweroff (from menu or command). Going to test reboot now since this is
mentioned above.

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

Title:
  Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  [Overview]
  I have been testing installations of a number of Lubuntu and Xubuntu Noble 
Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more 
latterly focused on Lubuntu.

  It would appear that since introduction of Kernel 6.8 into the daily
  builds, the installed system fails to carry out a successful reboot or
  power off  when commanded from the desktop or the command line

  [Symptoms]
  When selecting either Leave-->Shutdown or Leave-->Reboot from the control 
panel, the process starts shutting down processes in an orderly fashion, until 
it gets to the part where it needs to power off hardware, where it hangs.

  shutdown -H now also fails in the same manner
  shutdown -r now also fails in the same manner

  With quiet bootflag disabled, the last system message on display before the 
hang is
  "Starting reboot..." or "Starting power-off..."

  [Workaround]
  The power button must be pressed for 5 secs to power down the hardware

  [Possibly related bugs]
  #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04
  #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10

  [Unsuccessful Workarounds]
  Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No 
effect

  [Observations]
  I do believe that shutdown/reboot was working correctly on a live USB Lubuntu 
Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024.  This 
release had an earlier kernel than 6.8. Sadly i no longer have the .iso to 
confirm this.  

  All Lubuntu Noble daily builds since kernel 6.8 was introduced appear
  to exhibit the symptoms as above

  [System info]
  Operating System: Ubuntu Noble Numbat (development branch)
Kernel: Linux 6.8.0-11-generic
  Architecture: x86-64
   Hardware Vendor: Dell Inc.
Hardware Model: Wyse 3040 Thin Client
  Firmware Version: 1.2.5
 Firmware Date: Mon 2018-08-20

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2059738/+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 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached

[Dave Jones]

That's a different issue, LP: #2063365, which only started occurring
after the recent wifi firmware bump

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

Title:
  RPI4 wifi unreliable when usb3 storage is attached

Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  Expired

Bug description:
  On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage
  device to one of the 2x usb3 ports (the ones closest to the ethernet
  port), wifi will sudden stop working. If you unplug the usb stick
  while running a ping, it will usually start working again almost
  instantaneously.

  Kernel version I have is: 5.3.0-1017-raspi2
  and I've confirmed this happens on both armhf and arm64

  The only thing I found in journalctl that looks suspicious is this, but it 
seems to have happened before plugging in the usb stick:
  Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from 
/dev/random: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Seth Arnold]

I'm having trouble seeing what the consequences are:

> the result is a permanently failed service

vs

> this is was a major annoyance on my m2 air after upgrading to noble

Was it it more than a red line in systemctl status output? Does it have
annoying logging behaviour or break some other service if it isn't
running?

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2054296] Re: Don't restrict to linux-laptop

[Seth Arnold]

@Tobias, that bug is 15 years old. Perhaps you meant another one?

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

Title:
  Don't restrict to linux-laptop

Status in protection-domain-mapper package in Ubuntu:
  Fix Released
Status in qrtr package in Ubuntu:
  Fix Released

Bug description:
  The generic arm64 kernel now support some Qualcomm platforms so the
  services need to run with that kernel as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2064179] [NEW] Forward port linux-xlnx 6.6 patches to Noble

[Portia Stephens]

Public bug reported:

Xilinx vendor tree patches need to be forward ported from their 6.6
branch to 6.8 for Noble.

https://github.com/Xilinx/linux-xlnx/tree/xlnx_rebase_v6.6

We cherry-picked every commit from
a3ea85714695 "xilinx: Add a github template telling people to not use pull 
requests there" ^ .. 24eec56fe5bd "arm64: zynqmp: Remove arm,cortex-a53-edac 
node"

Upstream work was done on net: axienet that Xilinx has reverted on 6.6
in order to apply their own changes. Xilinx squashed these reverts into
one commit "Revert "net: axienet: Revert following mainline commits to
be in sync with downstream implementation." There were additional
patches that were added between 6.6 and 6.8 that we also reverted. We
removed the squashed revert and individually reverted the patches to
make maintenance easier. The following commits were reverted:

67f10a9bef6c Revert "net: axienet: make use of axistream-connected attribute 
optional"
947a44219b1e Revert "net: axienet: Clean up DMA start/stop and error handling"
2fafbc9b412e Revert "net: axienet: implement NAPI and GRO receive"
e5a7818b8d04 Revert "net: axienet: Use NAPI for TX completion path"
de765a372712 Revert "net: axienet: Switch to 64-bit RX/TX statistics"
34311bc5920f Revert "net: ethernet: xilinx: Convert to platform remove callback 
returning void"
1f35754c5be3 Revert "net: axienet: Preparatory changes for dmaengine support"
1e3ba4732475 Revert "net: axienet: Introduce dmaengine support"
6e93b87de0ce Revert "net: axienet: Fix check for partial TX checksum"

Upstream also added erase die capability to mtd: spi-nor which had major
conflicts with stacked and parallel memory support added by Xilinx.
These should be revisited once Xilinx upstreams  the stacked and
parallel memory support since this will make maintenance difficult.  We
reverted the following patches in mtd: spi-nor:

ac2881fb1d4d Revert "mtd: spi-nor: add erase die (chip) capability"
f044dd43a1b4 Revert "mtd: spi-nor: spansion: enable die erase for multi die 
flashes"
c072086fdce3 Revert "mtd: spi-nor: micron-st: enable die erase for multi die 
flashes"
6be57acc37df Revert "mtd: spi-nor: remove NO_CHIP_ERASE flag"
6bbd61fc0eef Revert "mtd: spi-nor: micron-st: Add support for mt25qu01g"

A few patches were skipped because we were just unsure how to apply
them. We should go back and revisit these:

usb: gadget: uvc_video: unlock before submitting a request to ep
usb: gadget: webcam: Add support for Full HD and 4K UHD Raw Video
v4l: xilinx: xcsi2rxss: Fix warnings for NULL_RETURNS

In total of the 860 patches we tried to apply 121 were skipped because
they had been upstreamed between v6.6 and v6.8.

The kernel will use the Ubuntu configs with Xilinx' configs applied on
top. To do this we imported the .config built on Xilinx tree for
xilinx_zynqmp_defconfig.

** Affects: linux-xilinx-zynqmp (Ubuntu)
 Importance: Medium
 Assignee: Portia Stephens (portias)
 Status: In Progress

** Description changed:

  Xilinx vendor tree patches need to be forward ported from their 6.6
  branch to 6.8 for Noble.
  
  https://github.com/Xilinx/linux-xlnx/tree/xlnx_rebase_v6.6
  
- We cherry-picked every commit from 
+ We cherry-picked every commit from
  a3ea85714695 "xilinx: Add a github template telling people to not use pull 
requests there" ^ .. 24eec56fe5bd "arm64: zynqmp: Remove arm,cortex-a53-edac 
node"
  
- 
- Upstream work was done on net: axienet that Xilinx has reverted on 6.6 in 
order to apply their own changes. There were additional patches that were added 
between 6.6 and 6.8 that we also reverted:
+ Upstream work was done on net: axienet that Xilinx has reverted on 6.6
+ in order to apply their own changes. Xilinx squashed these reverts into
+ one commit "Revert "net: axienet: Revert following mainline commits to
+ be in sync with downstream implementation." There were additional
+ patches that were added between 6.6 and 6.8 that we also reverted. We
+ removed the squashed revert and individually reverted the patches to
+ make maintenance easier. The following commits were reverted:
  
  67f10a9bef6c Revert "net: axienet: make use of axistream-connected attribute 
optional"
  947a44219b1e Revert "net: axienet: Clean up DMA start/stop and error handling"
  2fafbc9b412e Revert "net: axienet: implement NAPI and GRO receive"
  e5a7818b8d04 Revert "net: axienet: Use NAPI for TX completion path"
  de765a372712 Revert "net: axienet: Switch to 64-bit RX/TX statistics"
  34311bc5920f Revert "net: ethernet: xilinx: Convert to platform remove 
callback returning void"
  1f35754c5be3 Revert "net: axienet: Preparatory changes for dmaengine support"
  1e3ba4732475 Revert "net: axienet: Introduce dmaengine support"
  6e93b87de0ce Revert "net: axienet: Fix check for partial TX checksum"
  
  Upstream also added erase die capability to mtd: spi-nor which had major
- conflicts with stacked and parallel memory support added by Xilinx. We
+ conflicts with stacked and parallel memory support added by 

[Kernel-packages] [Bug 2041782] Re: spi: spi-cadence-quadspi: Fix ospi resume failures conflicts

[Portia Stephens]

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

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

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

Title:
  spi: spi-cadence-quadspi: Fix ospi resume failures conflicts

Status in linux-xilinx-zynqmp package in Ubuntu:
  Invalid
Status in linux-xilinx-zynqmp source package in Jammy:
  Invalid

Bug description:
  jammy:xilinx-zynqmp is carrying a patch subject "spi: spi-cadence-
  quadspi: Fix ospi resume failure" from the Xilinx tree , branch
  xlnx_rebase_v5.15_LTS_2022.1_update . This commit hasn't been
  upstreamed and completely rewrites the function cqspi_resume(). A
  change has landed in the v5.15.111 upstream stable release which
  conflicts with this Xilinx patch in such a way that we don't know how
  to resolve the conflicts and keep the functionality intact.

  We have found where Xlinx resolved the merge on the XIlinx 6.1 branch
  but it doesn't seem correct. In the original commit:

  (https://github.com/Xilinx/linux-
  xlnx/commit/6edac18033db445439ca57c23b8cee29a6bbdf0f)

  in the function cqspi_resume() ,  the call to cqspi_controller_enable()   is 
removed and ZynqMP specific controls are added. Upstream fixed an issue with 
suspend-resume 
(https://github.com/torvalds/linux/commit/2087e85bb66ee3652dafe732bb9b9b896229eafc).
 The upstream fix replaces the cqspi_controller_enable() with some clock 
initializations and a call to cqspi_controller_init() which does some register 
writes before calling cqspi_controller_enable(). Xilinx resolve the conflict by 
concatenating the two commit's changes to
  cqspi_resume() 
(https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v6.1_LTS_2023.1_update/drivers/spi/spi-cadence-quadspi.c#L2271),
 the end result is that cqspi_resume() consists of ZynqMP specific controls 
followed by a (nested) call to cqspi_controller_enable(), the exact function 
call that was removed in XIlinx's original commit.

  This bug is to track how this merge conflict is resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2041782/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.

[Portia Stephens]

** Changed in: linux-xilinx-zynqmp (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.

Status in linux-xilinx-zynqmp package in Ubuntu:
  New
Status in linux-xilinx-zynqmp source package in Focal:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression 
test due to kernel config options. The kernel configs were changed to
  match the Xilinx provided kernel configs which resulted in these configs 
being disabled.

  [Fix]

  Enable all configs checked in ubuntu_qrt_kernel_security.

  
  [Testcase]

  ubuntu_qrt_kernel caught this isuse and will continue to test whether
  these configs are enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/1995465/+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 2040354] Re: Add K24 device tree

[Portia Stephens]

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

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

Title:
  Add K24 device tree

Status in linux-xilinx-zynqmp package in Ubuntu:
  Fix Released
Status in linux-xilinx-zynqmp source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]
  * This ports the K24 device trees from the Xilinx 6.1 kernel 
(xlnx_rebase_v6.1_LTS_2023.1_update) 
  * This will allow the same image.its file and thus flash-kernel package to be 
used for the K24 development images  and the stable release.

  [ Test Plan ]
  * The k24 platform does not need to be tested since it is not a certified 
platform. The normal regression testing on K26 and ZCU platforms is sufficient. 

  [ Where problems could occur ]
  * A bug in the device tree could cause a build error in the kernel. The 
device tree is not used by any certified images.

  [ Other Info ]
  The change squashes together the following changes from Xilinx 
xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree 
other than:

  arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts
  arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts
  arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts

  were modified to remove the other changes.

  a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms
  f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240
  f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240
  41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs
  958f20d8445e arm64: zynqmp: Fix memory size on k24
  c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA
  9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board
  646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2040354/+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 2044554] Re: Turn off non-zynqmp arch support

[Portia Stephens]

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

** Changed in: linux-xilinx-zynqmp (Ubuntu Noble)
 Assignee: (unassigned) => Portia Stephens (portias)

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

Title:
  Turn off non-zynqmp arch support

Status in linux-xilinx-zynqmp package in Ubuntu:
  Fix Committed
Status in linux-xilinx-zynqmp source package in Jammy:
  Fix Released
Status in linux-xilinx-zynqmp source package in Noble:
  New

Bug description:
  [ Impact ]

   * This is an optimized kernel for zynqmp range of devices.
   * Currently about 14% of kernel build is targeting non-zynqmp devices, which 
is dead code unused in production
   * This reduces kernel build time, kernel image & modules size, amount of 
required firmware, and makes initrd smaller.
   * This reduces peak memory usage on boot as well
   * This will loose ability to execute this exact same kernel build on 
non-zynqmp device, for benchmarking purposes generic kernel should be used 
instead.

  [ Test Plan ]

   * Ensure newly produced kernel installs and boots on Ubuntu Server
  and Ubuntu Core target devices without any loss of peripherals and
  stock devices.

  [ Where problems could occur ]

   * This changes may limit ability to smoke-test this kernel on non-zynqmp 
devices, if needed support for individual CPUs can be turned back on. Or 
ideally any such testing should move to zynqmp devices. (examples of 
potentially interesting things to turn back on upon request are QCOM APPLE 
suppport for running this kernel on Arm Laptops for developer convenience)
   * It is expected for KVM and QEMU to continue to work as both host and guest

  [ Other Info ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+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 2049442] Re: Enable symbols for all Xilinx device trees

[Portia Stephens]

** Changed in: linux-xilinx-zynqmp (Ubuntu Noble)
 Assignee: (unassigned) => Portia Stephens (portias)

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

Title:
  Enable symbols for all Xilinx device trees

Status in linux-xilinx-zynqmp package in Ubuntu:
  New
Status in linux-xilinx-zynqmp source package in Jammy:
  Fix Released
Status in linux-xilinx-zynqmp source package in Noble:
  New

Bug description:
  [ Impact ]

  * This enables symbols for all device trees built for Xilinx products.
  * Currently only device trees which have overlays applied have symbols 
enabled.
  * Most Xilinx device trees are currently overlayed (thus have the symbols 
already included) so this should have minimal size impact.

  [ Test Plan ]

  * Xilinx will verify they can load the dtbo's for the FPGA during
  runtime

  [ Where problems could occur ]

  * There could be an unexpected impact on other FPGA runtime overlays
  that are already working.

  [ Other Info ]

  * Xilinx platforms apply dtbo's during runtime when loading FPGA firmware.
  * Xilinx Yocto distribution handle's this in the yocto recipes which is why 
this change is not upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2049442/+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 1279699] Re: AER: Corrected error received: id=00e4 / PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e4

[Bjorn Helgaas]

Turns out "pcie_aspm=off" effectively disables AER because Linux doesn't
request AER control when it doesn't advertise ASPM support (see
ACPI_PCIE_REQ_SUPPORT).  That explains why "pcie_aspm=off" would avoid
the error reporting.

This report was from a v3.11-based kernel.  v3.11 is from Mon Sep 2
13:46:10 2013, so it should contain
https://git.kernel.org/linus/dce87b960cf4 ("netxen: mask correctable
error"), which should mask all Correctable Errors for this device (see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/qlogic/netxen/netxen_nic_main.c?id=v3.11#n1420),
so I don't know why this flood happened.

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

Title:
  AER: Corrected error received: id=00e4 / PCIe Bus Error:
  severity=Corrected, type=Physical Layer, id=00e4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 13.10
  Release:13.10 (Ubuntu 3.11.0-15.25-generic 3.11.10)

  On Ubuntu 3.11.0-15.25-generic 3.11.10 I am getting the following
  error:

  [   11.749109] bonding: bond0: Setting MII monitoring interval to 100.
  [   11.797258] bonding: bond1 is being created...
  [   11.797320] bonding: bond1 is being created...
  [   11.797322] bonding: bond1 is being created...
  [   11.797653] bonding: bond1 already exists.
  [   11.797658] bonding: bond1 already exists.
  [   11.808146] bonding: bond1: Setting MII monitoring interval to 100.
  [   11.824060] bonding: bond0: setting mode to 802.3ad (4).
  [   11.824063] bonding: bond1: setting mode to 802.3ad (4).
  [   11.825177] bonding: bond1: Setting LACP rate to fast (1).
  [   11.825259] bonding: bond0: Setting LACP rate to fast (1).
  [   11.825527] IPv6: ADDRCONF(NETDEV_UP): bond1: link is not ready
  [   11.825674] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
  [   11.871240] bonding: bond0: Adding slave p2p1.
  [   12.124239] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
  [   12.211592] init: avahi-cups-reload main process (823) terminated with 
status 1
  [   12.714726] bonding: bond0: enslaving p2p1 as a backup interface with a 
down link.
  [   12.715620] bonding: bond1: Adding slave p4p3.
  [   13.072966] bonding: bond1: enslaving p4p3 as a backup interface with a 
down link.
  [   13.072970] bonding: bond1: Adding slave p4p2.
  [   13.608930] bonding: bond1: enslaving p4p2 as a backup interface with a 
down link.
  [   13.608934] bonding: bond0: Adding slave p3p1.
  [   13.976911] netxen_nic: p4p2 NIC Link is up
  [   14.008903] netxen_nic: p4p3 NIC Link is up
  [   14.450454] bonding: bond0: enslaving p3p1 as a backup interface with a 
down link.
  [   14.450459] bonding: bond1: Adding slave p4p1.
  [   14.544862] bonding: bond1: enslaving p4p1 as a backup interface with a 
down link.
  [   14.544866] bonding: bond1: Adding slave p4p4.
  [   14.624820] bonding: bond1: Warning: No 802.3ad response from the link 
partner for any adapters in the bond
  [   14.677889] igb: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
RX/TX
  [   14.824864] bonding: bond1: enslaving p4p4 as a backup interface with a 
down link.
  [   14.824871] IPv6: ADDRCONF(NETDEV_CHANGE): bond1: link becomes ready
  [   14.844792] bonding: bond0: link status down again after 0 ms for 
interface p2p1.
  [   14.862650] igb :05:00.0: changing MTU from 1500 to 9000
  [   14.924798] bonding: bond1: Warning: No 802.3ad response from the link 
partner for any adapters in the bond
  [   14.938826] igb :06:00.0: changing MTU from 1500 to 9000
  [   15.024843] bonding: bond1: Warning: No 802.3ad response from the link 
partner for any adapters in the bond
  [   15.148767] bonding: bond1: link status definitely up for interface p4p3, 
1000 Mbps full duplex.
  [   15.148770] bonding: bond1: link status definitely up for interface p4p2, 
1000 Mbps full duplex.
  [   15.940783] netxen_nic: p4p1 NIC Link is up
  [   15.948787] bonding: bond1: link status definitely up for interface p4p1, 
0 Mbps full duplex.
  [   17.657721] igb: p3p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
RX/TX
  [   17.724664] bonding: bond0: Warning: No 802.3ad response from the link 
partner for any adapters in the bond
  [   17.724676] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   17.748653] bonding: bond0: link status definitely up for interface p3p1, 
1000 Mbps full duplex.
  [   18.201714] igb: p2p1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: 
RX/TX
  [   18.248622] bonding: bond0: link status definitely up for interface p2p1, 
1000 Mbps full duplex.

  [   41.932293] pcieport :00:1c.4: AER: Multiple Corrected error received: 
id=00e4
  [   41.932337] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e4(Receiver ID)
  [   41.937340] pcieport :00:1c.4:   device [8086:8c18] error 

[Kernel-packages] [Bug 2064176] Re: LXD fan bridge causes blocked tasks

[Wesley Hershberger]

** Attachment added: "apport.linux-image-6.5.0-28-generic._9l2i4n1.apport"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064176/+attachment/5772647/+files/apport.linux-image-6.5.0-28-generic._9l2i4n1.apport

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

Title:
  LXD fan bridge causes blocked tasks

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, cross posting this from
  https://github.com/canonical/lxd/issues/12161

  I've got a lxd cluster running across 3 VMs using the fan bridge. I'm
  using a dev revision of LXD based on 6413a948. Creating a container
  causes the trace in the attached syslog snippet; this causes the
  container creation process to hang indefinitely. ssh logins, `lxc
  shell cluster1`, and `ps -aux` also hang.

  Apr 29 17:15:01 cluster1 kernel: [  161.250951] [ cut here 
]
  Apr 29 17:15:01 cluster1 kernel: [  161.250957] Voluntary context switch 
within RCU read-side critical section!
  Apr 29 17:15:01 cluster1 kernel: [  161.250990] WARNING: CPU: 2 PID: 510 at 
kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x2a7/0x2f0
  Apr 29 17:15:01 cluster1 kernel: [  161.251003] Modules linked in: nft_masq 
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vxlan 
ip6_udp_tunnel udp_tunnel dummy br
  idge stp llc zfs(PO) spl(O) nf_tables libcrc32c nfnetlink vhost_vsock vhost 
vhost_iotlb binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common 
kvm_intel kvm irqbypass crct10dif
  _pclmul crc32_pclmul virtio_gpu polyval_clmulni polyval_generic 
ghash_clmulni_intel sha256_ssse3 sha1_ssse3 virtio_dma_buf aesni_intel 
vmw_vsock_virtio_transport 9pnet_virtio xhci_
  pci drm_shmem_helper i2c_i801 ahci 9pnet vmw_vsock_virtio_transport_common 
xhci_pci_renesas drm_kms_helper libahci crypto_simd joydev virtio_input cryptd 
lpc_ich virtiofs i2c_smbus
   vsock psmouse input_leds mac_hid serio_raw rapl qemu_fw_cfg vmgenid nfsd 
dm_multipath auth_rpcgss scsi_dh_rdac nfs_acl lockd scsi_dh_emc scsi_dh_alua 
grace sch_fq_codel drm sunrpc
   efi_pstore virtio_rng ip_tables x_tables autofs4
  Apr 29 17:15:01 cluster1 kernel: [  161.251085] CPU: 2 PID: 510 Comm: nmbd 
Tainted: P   O   6.5.0-28-generic #29~22.04.1-Ubuntu
  Apr 29 17:15:01 cluster1 kernel: [  161.251089] Hardware name: QEMU Standard 
PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022
  Apr 29 17:15:01 cluster1 kernel: [  161.251091] RIP: 
0010:rcu_note_context_switch+0x2a7/0x2f0
  Apr 29 17:15:01 cluster1 kernel: [  161.251095] Code: 08 f0 83 44 24 fc 00 48 
89 de 4c 89 f7 e8 d1 af ff ff e9 1e fe ff ff 48 c7 c7 d0 60 56 88 c6 05 e6 27 
40 02 01 e8 79 b2 f2 ff
  <0f> 0b e9 bd fd ff ff a9 ff ff ff 7f 0f 84 75 fe ff ff 65 48 8b 3c
  Apr 29 17:15:01 cluster1 kernel: [  161.251098] RSP: 0018:b9cbc11dbbc8 
EFLAGS: 00010046
  Apr 29 17:15:01 cluster1 kernel: [  161.251101] RAX:  RBX: 
941ef7cb3f80 RCX: 
  Apr 29 17:15:01 cluster1 kernel: [  161.251103] RDX:  RSI: 
 RDI: 
  Apr 29 17:15:01 cluster1 kernel: [  161.251104] RBP: b9cbc11dbbe8 R08: 
 R09: 
  Apr 29 17:15:01 cluster1 kernel: [  161.251106] R10:  R11: 
 R12: 
  Apr 29 17:15:01 cluster1 kernel: [  161.25] R13: 941d893e9980 R14: 
 R15: 941d80ad7a80
  Apr 29 17:15:01 cluster1 kernel: [  161.251113] FS:  7c7dcbdb8a00() 
GS:941ef7c8() knlGS:
  Apr 29 17:15:01 cluster1 kernel: [  161.251115] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr 29 17:15:01 cluster1 kernel: [  161.251117] CR2: 5a30877ae488 CR3: 
000105888003 CR4: 00170ee0
  Apr 29 17:15:01 cluster1 kernel: [  161.251122] Call Trace:
  Apr 29 17:15:01 cluster1 kernel: [  161.251128]  
  Apr 29 17:15:01 cluster1 kernel: [  161.251133]  ? show_regs+0x6d/0x80
  Apr 29 17:15:01 cluster1 kernel: [  161.251145]  ? __warn+0x89/0x160
  Apr 29 17:15:01 cluster1 kernel: [  161.251152]  ? 
rcu_note_context_switch+0x2a7/0x2f0
  Apr 29 17:15:01 cluster1 kernel: [  161.251155]  ? report_bug+0x17e/0x1b0
  Apr 29 17:15:01 cluster1 kernel: [  161.251172]  ? handle_bug+0x46/0x90
  Apr 29 17:15:01 cluster1 kernel: [  161.251187]  ? exc_invalid_op+0x18/0x80
  Apr 29 17:15:01 cluster1 kernel: [  161.251190]  ? 
asm_exc_invalid_op+0x1b/0x20
  Apr 29 17:15:01 cluster1 kernel: [  161.251202]  ? 
rcu_note_context_switch+0x2a7/0x2f0
  Apr 29 17:15:01 cluster1 kernel: [  161.251205]  ? 
rcu_note_context_switch+0x2a7/0x2f0
  Apr 29 17:15:01 cluster1 kernel: [  161.251208]  __schedule+0xcc/0x750
  Apr 29 17:15:01 cluster1 kernel: [  161.251218]  schedule+0x63/0x110
  Apr 29 17:15:01 cluster1 kernel: [  161.251222]  
schedule_hrtimeout_range_clock+0xbc/0x130
  Apr 29 17:15:01 cluster1 kernel: [  161.251238]  ? 

[Kernel-packages] [Bug 2064176] [NEW] LXD fan bridge causes blocked tasks

[Wesley Hershberger]

Public bug reported:

Hi, cross posting this from
https://github.com/canonical/lxd/issues/12161

I've got a lxd cluster running across 3 VMs using the fan bridge. I'm
using a dev revision of LXD based on 6413a948. Creating a container
causes the trace in the attached syslog snippet; this causes the
container creation process to hang indefinitely. ssh logins, `lxc shell
cluster1`, and `ps -aux` also hang.

Apr 29 17:15:01 cluster1 kernel: [  161.250951] [ cut here 
]
Apr 29 17:15:01 cluster1 kernel: [  161.250957] Voluntary context switch within 
RCU read-side critical section!
Apr 29 17:15:01 cluster1 kernel: [  161.250990] WARNING: CPU: 2 PID: 510 at 
kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [  161.251003] Modules linked in: nft_masq 
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vxlan 
ip6_udp_tunnel udp_tunnel dummy br
idge stp llc zfs(PO) spl(O) nf_tables libcrc32c nfnetlink vhost_vsock vhost 
vhost_iotlb binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common 
kvm_intel kvm irqbypass crct10dif
_pclmul crc32_pclmul virtio_gpu polyval_clmulni polyval_generic 
ghash_clmulni_intel sha256_ssse3 sha1_ssse3 virtio_dma_buf aesni_intel 
vmw_vsock_virtio_transport 9pnet_virtio xhci_
pci drm_shmem_helper i2c_i801 ahci 9pnet vmw_vsock_virtio_transport_common 
xhci_pci_renesas drm_kms_helper libahci crypto_simd joydev virtio_input cryptd 
lpc_ich virtiofs i2c_smbus
 vsock psmouse input_leds mac_hid serio_raw rapl qemu_fw_cfg vmgenid nfsd 
dm_multipath auth_rpcgss scsi_dh_rdac nfs_acl lockd scsi_dh_emc scsi_dh_alua 
grace sch_fq_codel drm sunrpc
 efi_pstore virtio_rng ip_tables x_tables autofs4
Apr 29 17:15:01 cluster1 kernel: [  161.251085] CPU: 2 PID: 510 Comm: nmbd 
Tainted: P   O   6.5.0-28-generic #29~22.04.1-Ubuntu
Apr 29 17:15:01 cluster1 kernel: [  161.251089] Hardware name: QEMU Standard PC 
(Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022
Apr 29 17:15:01 cluster1 kernel: [  161.251091] RIP: 
0010:rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [  161.251095] Code: 08 f0 83 44 24 fc 00 48 
89 de 4c 89 f7 e8 d1 af ff ff e9 1e fe ff ff 48 c7 c7 d0 60 56 88 c6 05 e6 27 
40 02 01 e8 79 b2 f2 ff
<0f> 0b e9 bd fd ff ff a9 ff ff ff 7f 0f 84 75 fe ff ff 65 48 8b 3c
Apr 29 17:15:01 cluster1 kernel: [  161.251098] RSP: 0018:b9cbc11dbbc8 
EFLAGS: 00010046
Apr 29 17:15:01 cluster1 kernel: [  161.251101] RAX:  RBX: 
941ef7cb3f80 RCX: 
Apr 29 17:15:01 cluster1 kernel: [  161.251103] RDX:  RSI: 
 RDI: 
Apr 29 17:15:01 cluster1 kernel: [  161.251104] RBP: b9cbc11dbbe8 R08: 
 R09: 
Apr 29 17:15:01 cluster1 kernel: [  161.251106] R10:  R11: 
 R12: 
Apr 29 17:15:01 cluster1 kernel: [  161.25] R13: 941d893e9980 R14: 
 R15: 941d80ad7a80
Apr 29 17:15:01 cluster1 kernel: [  161.251113] FS:  7c7dcbdb8a00() 
GS:941ef7c8() knlGS:
Apr 29 17:15:01 cluster1 kernel: [  161.251115] CS:  0010 DS:  ES:  
CR0: 80050033
Apr 29 17:15:01 cluster1 kernel: [  161.251117] CR2: 5a30877ae488 CR3: 
000105888003 CR4: 00170ee0
Apr 29 17:15:01 cluster1 kernel: [  161.251122] Call Trace:
Apr 29 17:15:01 cluster1 kernel: [  161.251128]  
Apr 29 17:15:01 cluster1 kernel: [  161.251133]  ? show_regs+0x6d/0x80
Apr 29 17:15:01 cluster1 kernel: [  161.251145]  ? __warn+0x89/0x160
Apr 29 17:15:01 cluster1 kernel: [  161.251152]  ? 
rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [  161.251155]  ? report_bug+0x17e/0x1b0
Apr 29 17:15:01 cluster1 kernel: [  161.251172]  ? handle_bug+0x46/0x90
Apr 29 17:15:01 cluster1 kernel: [  161.251187]  ? exc_invalid_op+0x18/0x80
Apr 29 17:15:01 cluster1 kernel: [  161.251190]  ? asm_exc_invalid_op+0x1b/0x20
Apr 29 17:15:01 cluster1 kernel: [  161.251202]  ? 
rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [  161.251205]  ? 
rcu_note_context_switch+0x2a7/0x2f0
Apr 29 17:15:01 cluster1 kernel: [  161.251208]  __schedule+0xcc/0x750
Apr 29 17:15:01 cluster1 kernel: [  161.251218]  schedule+0x63/0x110
Apr 29 17:15:01 cluster1 kernel: [  161.251222]  
schedule_hrtimeout_range_clock+0xbc/0x130
Apr 29 17:15:01 cluster1 kernel: [  161.251238]  ? 
__pfx_hrtimer_wakeup+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [  161.251245]  
schedule_hrtimeout_range+0x13/0x30
Apr 29 17:15:01 cluster1 kernel: [  161.251248]  ep_poll+0x33f/0x390
Apr 29 17:15:01 cluster1 kernel: [  161.251254]  ? 
__pfx_ep_autoremove_wake_function+0x10/0x10
Apr 29 17:15:01 cluster1 kernel: [  161.251257]  do_epoll_wait+0xdb/0x100
Apr 29 17:15:01 cluster1 kernel: [  161.251259]  __x64_sys_epoll_wait+0x6f/0x110
Apr 29 17:15:01 cluster1 kernel: [  161.251265]  do_syscall_64+0x5b/0x90
Apr 29 17:15:01 cluster1 kernel: [  161.251270]  ? 

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

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~simpoir/livecd-rootfs/+git/livecd-rootfs/+merge/465193

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Miguel Elias Machado]

> GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash
initcall_blacklist=simpledrm_platform_driver_init”

This workaround worket for me too.

Thanks.

-- 
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 "Unknown Display" 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
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  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.

  [ Workaround ]

  1. sudo rm /dev/dri/card0
  2. Log in again.

  [ Test Plan ]

  Open Settings and verify the only monitors shown are your real
  monitors.

  [ Where problems could occur ]

  Removing the simpledrm card is only safe when it's not being used. If
  somehow a machine wasn't using the installed Nvidia driver then there
  could be a risk of deleting the only working display.

  [ Other Info ]

  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 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

[twelfth]

Screenshot of my grub-customizer configuration that resolved my boot to
blackscreen issue.

** Description changed:

  Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card.
  
  Using xUbuntu.
  
  I had been daily driving the 24.04 nightly iso since March. About a week
  ago, I took a kernel update via apt and rebooted. The result was that
  the system would hard freeze to a black screen after the initial kernel
  messages cleared from the screen. Ctrl-Alt-Del did nothing, switching
  terminals (ctrl-alt-f#) did nothing, had to hard power off to regain
  control of the system.
  
  I tried various fixes, none of which permanently stuck. This includes
  nomodeset in grub, rebooting into safe mode, checking for proprietary
  drivers. Safe mode allowed me to reboot once more into desktop, but then
  any subsequent reboots would result in a black screen lockup.
  
  Suspending while able to use the desktop before reboot would cause a
  black screen lockup did not seem to cause any issues.
  
  3 days before 24.04 was officially released, I reflashed the most recent
  installer iso to my thumbdrive, copied my home folder to my RAID and did
  a full wipe and fresh install.
  
  First reboot after installation always went to the desktop. Subsequent
  reboots always resulted in a black screen lockup.
  
  Memtest cleared without errors.
  
  Again tried various fixes, nomodeset, safe mode, drivers. The only
  consistency was that regardless of what I could do to regain control or
  what I did differently when doing a wipe and reinstall, I would always
  reboot to a black screen.
  
  Once 24.04 was officially released, I again did a full wipe and
  reinstall and encountered all of the above same issues as before.
  
  After mentioning this in #ubuntu on libera, someone suggested a kernel
  downgrade.
  
  24.04 as installed was using 6.8.0-31.31
  
  Using Mainline, I downgraded to the next minor version below 6.8 that
  was considered stable. 6.7.10
  
  Problem went away. No more black screen on boot, no more hard power offs
  required to be able to use my system again, no suspend issues. Was not
  necessary for me to do anything else to maintain a consistent successful
  reboot to desktop.
  
  Did yet another full wipe and fresh install of 24.04, only installing
  Mainline upon first reboot to install 6.7.10, using Grub Customizer to
  edit the default grub option to boot the 6.7.10 kernel instead.
  
  No issues.
  
  I apologise that I did not collect logs during this process.
+ 
+ 
+ ---
+ 
+ 
+ For those affected by this issue, this was my fix:
+ 
+ Install 24.04, reboot, at the desktop, open a terminal window and add
+ the following PPAs:
+ 
+ sudo add-apt-repository ppa:cappelikan/ppa
+ sudo apt update
+ sudo apt install mainline
+ 
+ sudo add-apt-repository ppa:danielrichter2007/grub-customizer
+ sudo apt-get update
+ sudo apt-get install grub-customizer
+ 
+ Run mainline-gtk, install kernel version 6.7.10
+ 
+ run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to
+ top of list, making it the default option. Save and reboot.

** Attachment added: "Screenshot_2024-04-29_15-10-10.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+attachment/5772645/+files/Screenshot_2024-04-29_15-10-10.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/2063983

Title:
  24.04 Upgrade/Fresh Install results in black screen on reboot on
  AMDGPU system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card.

  Using xUbuntu.

  I had been daily driving the 24.04 nightly iso since March. About a
  week ago, I took a kernel update via apt and rebooted. The result was
  that the system would hard freeze to a black screen after the initial
  kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
  switching terminals (ctrl-alt-f#) did nothing, had to hard power off
  to regain control of the system.

  I tried various fixes, none of which permanently stuck. This includes
  nomodeset in grub, rebooting into safe mode, checking for proprietary
  drivers. Safe mode allowed me to reboot once more into desktop, but
  then any subsequent reboots would result in a black screen lockup.

  Suspending while able to use the desktop before reboot would cause a
  black screen lockup did not seem to cause any issues.

  3 days before 24.04 was officially released, I reflashed the most
  recent installer iso to my thumbdrive, copied my home folder to my
  RAID and did a full wipe and fresh install.

  First reboot after installation always went to the desktop. Subsequent
  reboots always resulted in a black screen lockup.

  Memtest cleared without errors.

  Again tried various fixes, nomodeset, safe mode, drivers. The only
  consistency was that regardless of what I could do to regain control
  or what 

[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Tobias Heider]

I don't think that's enough since it also gets pulled in by ubuntu-
desktop and ubuntu-desktop-minimal as recommends. It would also be nice
if we found a solution that fixes the issue on existing installations
since upgrades from mantic to noble will trigger the bug.

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+

[Daniel Letzeisen]

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

Okay, I can confirm that the 390 driver is causing boot issues on 24.04, both 
laptop and desktop. 
I've removed the Noble package from the PPA for now because I don't want to 
break anyone else's shiny new Noble install. I apologize for any inconvenience 
this caused.

Looking at the log, I see the nvidia kernel module(s) loaded okay, but
there's some some sort of crash involving nvidia-smi (invalid stack
frame pointer).

I don't know if I'll be able to resolve this. If anyone wants me to
reupload the Noble package to a different PPA so that they can play with
it, let me know.

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

Title:
  Nvidia 390 Needs Patched for Kernel 6.5+

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Supposedly, this was solved in Ubuntu 23.10, but the package never made it 
out of the mantic-proposed repository: 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16
  Nor was it backported to Ubuntu 22.04 

  As a temporary measure, I uploaded a patched version to a PPA for
  Ubuntu 22.04 (and added a patch for 6.6/6.7):
  https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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: Backport iproute2 6.8.0 to noble

[dann frazier]

Hi Andrea - since this is now a stable release update, I *think* the
next steps should be:

1) Edit this bug to use the SRU Template
  https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
(now done)
Since your team owns this package, please review that and let me know if you 
have any concerns with that text.

2) Wait for 24.10 ('oracular') to open for devel and forcesync iproute2
w/ Debian
(https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First).

3) Upload the SRU, and wait for feedback from the sru team. If approved,
we'll need to run the tests in the [Test Case] section and make sure
there are no regressions from 6.1.

-- 
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:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.

  Normally iproute2 is updated during the devel cycle to align with the
  kernel version, but it was missed this cycle and discovered too late
  for an FFe. We request an exception from the SRU team to do this as an
  SRU. This includes dropping the Ubuntu Fan patches, which adds
  features to iproute2 that no longer work since noble's kernels no
  longer support Ubuntu Fan.

  [Test Case]
  We'll run the 6.8 kernel self tests, which make use of a number of iproute2 
features (see comment #17). NVIDIA's networking organization (Mellanox) has 
offered to put this through their QA process (details TBD). The upstream test 
suite will also run in the autopkgtests, though that suite is fairly stale.

  [What Could Go Wrong]
  Users who may be running noble userspace with a non-noble kernel that 
supports Ubuntu Fan would lose support for configuring it. If the SRU team 
considers this to be a regression we should avoid, then we can add the Ubuntu 
Fan patches back.

  iproute2 6.8 upstream retains backwards compatibility with earlier
  releases (see comment #17). There are no commits with a Fixes:
  annotation since the v6.8.0 tag was applied upstream.

  iproute2 is obviously a key package, and any upstream version bump
  carries risk. This includes the possibility of breaking networking for
  users of an Ubuntu LTS release.

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 2051672] Re: Backport iproute2 6.8.0 to noble

[dann frazier]

** Description changed:

- 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.
+ [Impact]
+ Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.
  
- 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.
+ Normally iproute2 is updated during the devel cycle to align with the
+ kernel version, but it was missed this cycle and discovered too late for
+ an FFe. We request an exception from the SRU team to do this as an SRU.
+ This includes dropping the Ubuntu Fan patches, which adds features to
+ iproute2 that no longer work since noble's kernels no longer support
+ Ubuntu Fan.
  
- I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
- smoke tested it on an amd64 virtual machine:
+ [Test Case]
+ We'll run the 6.8 kernel self tests, which make use of a number of iproute2 
features (see comment #17). NVIDIA's networking organization (Mellanox) has 
offered to put this through their QA process (details TBD). The upstream test 
suite will also run in the autopkgtests, though that suite is fairly stale.
  
- 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) ...
+ [What Could Go Wrong]
+ Users who may be running noble userspace with a non-noble kernel that 
supports Ubuntu Fan would lose support for configuring it. If the SRU team 
considers this to be a regression we should avoid, then we can add the Ubuntu 
Fan patches back.
  
- The system rebooted fine. The ip command seems to behave normally.
+ iproute2 6.8 upstream retains backwards compatibility with earlier
+ releases (see comment #17). There are no commits with a Fixes:
+ annotation since the v6.8.0 tag was applied upstream.
  
- 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
+ iproute2 is obviously a key package, and any upstream version bump
+ carries risk. This includes the possibility of breaking networking for
+ users of an Ubuntu LTS release.

-- 
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:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.

  Normally iproute2 is updated during the devel cycle to align with the
  kernel version, but it was missed this cycle and discovered too late
  for an FFe. We request an 

[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)

[Richard van der Hoff]

Ok, I reproduced this on a rebuild of 6.5.0-34 with
CONFIG_PROVE_LOCKING. Here are some relevant-looking bits of the logs.
It looks like the wireplumber process and the usb_disconnect process
have deadlocked?

[Thinking about this further, possibly the action that triggers it is to
disconnect the dock while the system is suspended, then resume the
system.]

Apr 29 21:24:36 xps9320 kernel: [280990.641315] INFO: task wireplumber:3263 
blocked for more than 241 seconds.
Apr 29 21:24:36 xps9320 kernel: [280990.641334]   Tainted: G   OE   
   6.5.13+ #18
Apr 29 21:24:36 xps9320 kernel: [280990.641341] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 29 21:24:36 xps9320 kernel: [280990.641346] task:wireplumber state:D 
stack:0 pid:3263  ppid:3253   flags:0x0002
Apr 29 21:24:36 xps9320 kernel: [280990.641360] Call Trace:
Apr 29 21:24:36 xps9320 kernel: [280990.641367]  
Apr 29 21:24:36 xps9320 kernel: [280990.641382]  __schedule+0x4cc/0x1ad0
Apr 29 21:24:36 xps9320 kernel: [280990.641401]  ? trace_hardirqs_on+0x65/0xc0
Apr 29 21:24:36 xps9320 kernel: [280990.641414]  ? 
_raw_spin_unlock_irqrestore+0x31/0x70
Apr 29 21:24:36 xps9320 kernel: [280990.641424]  ? 
__wake_up_common_lock+0x8d/0xd0
Apr 29 21:24:36 xps9320 kernel: [280990.641442]  schedule+0x68/0x110
Apr 29 21:24:36 xps9320 kernel: [280990.641456]  
snd_power_ref_and_wait+0xbd/0x120 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641486]  ? 
__pfx_autoremove_wake_function+0x10/0x10
Apr 29 21:24:36 xps9320 kernel: [280990.641501]  snd_ctl_elem_info+0x4f/0x1b0 
[snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641532]  
snd_ctl_elem_info_user+0x4e/0xb0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641581]  snd_ctl_ioctl+0x1ec/0x850 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.641608]  ? __fget_files+0xde/0x1d0
Apr 29 21:24:36 xps9320 kernel: [280990.641625]  __x64_sys_ioctl+0x9d/0xe0
Apr 29 21:24:36 xps9320 kernel: [280990.641637]  x64_sys_call+0x1fe9/0x2570
Apr 29 21:24:36 xps9320 kernel: [280990.641646]  do_syscall_64+0x56/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641657]  ? do_syscall_64+0x63/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641665]  ? do_syscall_64+0x63/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.641675]  
entry_SYSCALL_64_after_hwframe+0x73/0xdd
Apr 29 21:24:36 xps9320 kernel: [280990.641683] RIP: 0033:0x70991f71a94f
Apr 29 21:24:36 xps9320 kernel: [280990.641692] RSP: 002b:7ffc84003090 
EFLAGS: 0246 ORIG_RAX: 0010
Apr 29 21:24:36 xps9320 kernel: [280990.641701] RAX: ffda RBX: 
7ffc84003100 RCX: 70991f71a94f
Apr 29 21:24:36 xps9320 kernel: [280990.641707] RDX: 7ffc84003100 RSI: 
c1105511 RDI: 0022
Apr 29 21:24:36 xps9320 kernel: [280990.641713] RBP: 7ffc840032e0 R08: 
6231bc666330 R09: 0004
Apr 29 21:24:36 xps9320 kernel: [280990.641718] R10: f314 R11: 
0246 R12: 6231bc90dc50
Apr 29 21:24:36 xps9320 kernel: [280990.641723] R13: 6231bc7c9140 R14: 
7ffc84003280 R15: 7ffc84003220
Apr 29 21:24:36 xps9320 kernel: [280990.641745]  
Apr 29 21:24:36 xps9320 kernel: [280990.64] INFO: task kworker/2:3:67822 
blocked for more than 241 seconds.
Apr 29 21:24:36 xps9320 kernel: [280990.642229]   Tainted: G   OE   
   6.5.13+ #18
Apr 29 21:24:36 xps9320 kernel: [280990.642234] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 29 21:24:36 xps9320 kernel: [280990.642239] task:kworker/2:3 state:D 
stack:0 pid:67822 ppid:2  flags:0x4000
Apr 29 21:24:36 xps9320 kernel: [280990.642250] Workqueue: usb_hub_wq hub_event
Apr 29 21:24:36 xps9320 kernel: [280990.642262] Call Trace:
Apr 29 21:24:36 xps9320 kernel: [280990.642266]  
Apr 29 21:24:36 xps9320 kernel: [280990.642274]  __schedule+0x4cc/0x1ad0
Apr 29 21:24:36 xps9320 kernel: [280990.642285]  ? mark_held_locks+0x4d/0x90
Apr 29 21:24:36 xps9320 kernel: [280990.642303]  schedule+0x68/0x110
Apr 29 21:24:36 xps9320 kernel: [280990.642312]  
schedule_preempt_disabled+0x15/0x30
Apr 29 21:24:36 xps9320 kernel: [280990.642321]  
rwsem_down_write_slowpath+0x2bc/0x820
Apr 29 21:24:36 xps9320 kernel: [280990.642342]  down_write+0xde/0xe0
Apr 29 21:24:36 xps9320 kernel: [280990.642353]  
snd_pcm_dev_disconnect+0x1cb/0x280 [snd_pcm]
Apr 29 21:24:36 xps9320 kernel: [280990.642386]  
snd_device_disconnect_all+0x47/0xa0 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.642411]  
snd_card_disconnect.part.0+0x10d/0x270 [snd]
Apr 29 21:24:36 xps9320 kernel: [280990.642439]  snd_card_disconnect+0x13/0x30 
[snd]
Apr 29 21:24:36 xps9320 kernel: [280990.642462]  
usb_audio_disconnect+0x116/0x290 [snd_usb_audio]
Apr 29 21:24:36 xps9320 kernel: [280990.642504]  usb_unbind_interface+0x90/0x280
Apr 29 21:24:36 xps9320 kernel: [280990.642518]  device_remove+0x69/0x80
Apr 29 21:24:36 xps9320 kernel: [280990.642528]  
device_release_driver_internal+0x20d/0x280
Apr 29 21:24:36 xps9320 kernel: [280990.642539]  

[Kernel-packages] [Bug 2051672] Re: Backport iproute2 6.8.0 to noble

[dann frazier]

** Summary changed:

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

-- 
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:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

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 2064163] Re: mlxbf-gige: Vitesse PHY stuck in a bad state during reboot test

[Asmaa Mnebhi]

** Description changed:

  SRU Justification:
  
  [Impact]
  
- During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad
- state, resulting in no ip provisioning. The only way to recover is to
- toggle the PHY hard reset pin via GPIO17 (or powercycle cycle since it
- achieves just that). We might have found a software workaround to avoid
- getting in this state in the first place: suspend the PHY during
- graceful shutdown. Suspend the PHY = Power down = set bit 11 to 1 in reg
- 0 of the PHY. This WA passed 1800 reboots on QA's setup.
+ During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad state, 
resulting in no ip provisioning. The only way to recover is to powercycle.
+ We might have found a software workaround to avoid getting in this state in 
the first place: suspend the PHY during graceful shutdown. Suspend the PHY = 
Power down = set bit 11 to 1 in reg 0 of the PHY. This WA passed 1800 reboots 
on QA's setup.
  
  [Fix]
  
  * During reboot, the mlxbf_gige_shutdown() function makes a call to 
phy_stop(). phy_stop() calls phy_suspend().
  * Certain Linux PHY drivers, like the Vitesse PHY, don't support suspend() to 
power down the PHY during shutdown.
- * Our Hardware also does not toggle the hard reset signal of the PHY during 
reboot. 
+ * Our Hardware also does not toggle the hard reset signal of the PHY during 
reboot.
  * Hence, when the PHY is in a bad state, it stays in its bad state until 
powercycle.
  * We have found a way to prevent the PHY from entering this bad state by 
suspending the PHY in the case of reboot.
  
- 
  [Test Case]
  
- * do the reboot test (at least 2000 reboots): run 'reboot' from linux. 
+ * do the reboot test (at least 2000 reboots): run 'reboot' from linux.
  * Check that the oob_net0 interface is up and the ip is assigned.
- * please note that if the the OOB doesn't get an ip, try reloading the driver 
(rmmod/modprobe). it that solves the issue, that would be a different bug. In 
the bug at stake, nothing recovers the OOB ip except power cycle. 
+ * please note that if the the OOB doesn't get an ip, try reloading the driver 
(rmmod/modprobe). it that solves the issue, that would be a different bug. In 
the bug at stake, nothing recovers the OOB ip except power cycle.
  
  [Regression Potential]
  
  * Make sure the redfish DHCP is still working during the reboot test
- * Make sure the OOB gets an ip 
+ * Make sure the OOB gets an ip
  
  [Other]
  
  These changes were made both in the mlxbf-gige driver and UEFI

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

Title:
  mlxbf-gige: Vitesse PHY stuck in a bad state during reboot test

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad state, 
resulting in no ip provisioning. The only way to recover is to powercycle.
  We might have found a software workaround to avoid getting in this state in 
the first place: suspend the PHY during graceful shutdown. Suspend the PHY = 
Power down = set bit 11 to 1 in reg 0 of the PHY. This WA passed 1800 reboots 
on QA's setup.

  [Fix]

  * During reboot, the mlxbf_gige_shutdown() function makes a call to 
phy_stop(). phy_stop() calls phy_suspend().
  * Certain Linux PHY drivers, like the Vitesse PHY, don't support suspend() to 
power down the PHY during shutdown.
  * Our Hardware also does not toggle the hard reset signal of the PHY during 
reboot.
  * Hence, when the PHY is in a bad state, it stays in its bad state until 
powercycle.
  * We have found a way to prevent the PHY from entering this bad state by 
suspending the PHY in the case of reboot.

  [Test Case]

  * do the reboot test (at least 2000 reboots): run 'reboot' from linux.
  * Check that the oob_net0 interface is up and the ip is assigned.
  * please note that if the the OOB doesn't get an ip, try reloading the driver 
(rmmod/modprobe). it that solves the issue, that would be a different bug. In 
the bug at stake, nothing recovers the OOB ip except power cycle.

  [Regression Potential]

  * Make sure the redfish DHCP is still working during the reboot test
  * Make sure the OOB gets an ip

  [Other]

  These changes were made both in the mlxbf-gige driver and UEFI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2064163/+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 2064163] [NEW] mlxbf-gige: Vitesse PHY stuck in a bad state during reboot test

[Asmaa Mnebhi]

Public bug reported:

SRU Justification:

[Impact]

During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad
state, resulting in no ip provisioning. The only way to recover is to
toggle the PHY hard reset pin via GPIO17 (or powercycle cycle since it
achieves just that). We might have found a software workaround to avoid
getting in this state in the first place: suspend the PHY during
graceful shutdown. Suspend the PHY = Power down = set bit 11 to 1 in reg
0 of the PHY. This WA passed 1800 reboots on QA's setup.

[Fix]

* During reboot, the mlxbf_gige_shutdown() function makes a call to phy_stop(). 
phy_stop() calls phy_suspend().
* Certain Linux PHY drivers, like the Vitesse PHY, don't support suspend() to 
power down the PHY during shutdown.
* Our Hardware also does not toggle the hard reset signal of the PHY during 
reboot. 
* Hence, when the PHY is in a bad state, it stays in its bad state until 
powercycle.
* We have found a way to prevent the PHY from entering this bad state by 
suspending the PHY in the case of reboot.


[Test Case]

* do the reboot test (at least 2000 reboots): run 'reboot' from linux. 
* Check that the oob_net0 interface is up and the ip is assigned.
* please note that if the the OOB doesn't get an ip, try reloading the driver 
(rmmod/modprobe). it that solves the issue, that would be a different bug. In 
the bug at stake, nothing recovers the OOB ip except power cycle. 

[Regression Potential]

* Make sure the redfish DHCP is still working during the reboot test
* Make sure the OOB gets an ip 

[Other]

These changes were made both in the mlxbf-gige driver and UEFI

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

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

Title:
  mlxbf-gige: Vitesse PHY stuck in a bad state during reboot test

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  During the QA reboot test, the BF3 Vitesse PHY gets stuck in a bad
  state, resulting in no ip provisioning. The only way to recover is to
  toggle the PHY hard reset pin via GPIO17 (or powercycle cycle since it
  achieves just that). We might have found a software workaround to
  avoid getting in this state in the first place: suspend the PHY during
  graceful shutdown. Suspend the PHY = Power down = set bit 11 to 1 in
  reg 0 of the PHY. This WA passed 1800 reboots on QA's setup.

  [Fix]

  * During reboot, the mlxbf_gige_shutdown() function makes a call to 
phy_stop(). phy_stop() calls phy_suspend().
  * Certain Linux PHY drivers, like the Vitesse PHY, don't support suspend() to 
power down the PHY during shutdown.
  * Our Hardware also does not toggle the hard reset signal of the PHY during 
reboot. 
  * Hence, when the PHY is in a bad state, it stays in its bad state until 
powercycle.
  * We have found a way to prevent the PHY from entering this bad state by 
suspending the PHY in the case of reboot.

  
  [Test Case]

  * do the reboot test (at least 2000 reboots): run 'reboot' from linux. 
  * Check that the oob_net0 interface is up and the ip is assigned.
  * please note that if the the OOB doesn't get an ip, try reloading the driver 
(rmmod/modprobe). it that solves the issue, that would be a different bug. In 
the bug at stake, nothing recovers the OOB ip except power cycle. 

  [Regression Potential]

  * Make sure the redfish DHCP is still working during the reboot test
  * Make sure the OOB gets an ip 

  [Other]

  These changes were made both in the mlxbf-gige driver and UEFI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2064163/+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 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

[Lukasz]

It's still happening, Raspberry Pi 4 ( Raspberry Pi RAS-4-4G - Model B / 4 GB 
SDRAM (1822096))
and Ubuntu Core Servier 23.10

When I connect SSD drive to USB3 port (booted from SDCard), internal
WiFi doesn't work, and most of the time I can see error:

brcmfmac: brcmf_set_channel: set chanspec 0xd0.. fail, reason -52


(random data in place of 2 dots)
I don't think it's a power problem, I use official 3A power supply,
Also, I can use my additional USB Wifi adapter connected to other USB3 port - 
it works, when internal not.

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857760/+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 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

[Launchpad Bug Tracker]

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

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

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857760/+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 1857760] Re: Raspberry Pi 4 loose Wifi connection when connecting external SSD

[Launchpad Bug Tracker]

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

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

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

Title:
  Raspberry Pi 4 loose Wifi connection when connecting external SSD

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Confirmed

Bug description:
  When I connect an external SSD (Samsung 850 EVO 500 Go in a UGREEN USB
  3.1 case) on my Raspberry Pi 4 (4Go) the Wifi stop working. It is easy
  to reproduce, either en USB3 or USB2 connectors.

  The SSD is mounted, only the Wifi fails.

  The problem does not occurs on a fresh Rasbian.

  The problem does not occurs if I connect the SSD case on my keyboard
  (a R.Pi keyboard including a USB hub). Only if I connect the SSD
  directly on the R.Pi.

  When I disconnect the SSD case, the Wifi generally gets back, but
  sometimes I had to set the wifi OFF then ON (through gnome gui
  tooling). I don't have to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1014-raspi2 5.3.0-1014.16
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 28 14:16:44 2019
  SourcePackage: linux-raspi2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1857760/+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 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached

[Lukasz]

It's still happening, Raspberry Pi 4 ( Raspberry Pi RAS-4-4G - Model B / 4 GB 
SDRAM (1822096))
and Ubuntu Core Servier 23.10

When I connect SSD drive to USB3 port (booted from SDCard), internal
WiFi doesn't work, and most of the time I can see error:

brcmfmac: brcmf_set_channel: set chanspec 0xd0.. fail, reason -52


(random data in place of 2 dots)
I don't think it's a power problem, I use official 3A power supply,
Also, I can use my additional USB Wifi adapter connected to other USB3 port - 
it works, when internal not.

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

Title:
  RPI4 wifi unreliable when usb3 storage is attached

Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  Expired

Bug description:
  On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage
  device to one of the 2x usb3 ports (the ones closest to the ethernet
  port), wifi will sudden stop working. If you unplug the usb stick
  while running a ping, it will usually start working again almost
  instantaneously.

  Kernel version I have is: 5.3.0-1017-raspi2
  and I've confirmed this happens on both armhf and arm64

  The only thing I found in journalctl that looks suspicious is this, but it 
seems to have happened before plugging in the usb stick:
  Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from 
/dev/random: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+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 2060919] Re: cifs: Copying file to same directory results in page fault

[Ubuntu Kernel Bot]

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


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


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


** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-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/2060919

Title:
  cifs: Copying file to same directory results in page fault

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

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

  [Impact]

  Copying or modifying a file to the same directory within a cifs mount
  results in a page fault, and the process that initiated the copy being
  killed. This could be cp, nautilus, etc.

  This results in the following oops:

  BUG: unable to handle page fault for address: fffe
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x) - not-present page
  PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0
  Oops:  [#1] PREEMPT SMP NOPTI
  CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic 
#28-Ubuntu
  RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 
89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 
f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  RAX:  RBX: fffe RCX: 
  RDX:  RSI:  RDI: 
  RBP: aab6865ffc28 R08: 0001 R09: 
  R10: 00023854 R11:  R12: 
  R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70
  FS: 7bd4d594b6c0() GS:90753f80() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: fffe CR3: 00017022a000 CR4: 00750ef0
  PKRU: 5554
  Call Trace:
  
  ? show_regs+0x6d/0x80
  ? __die+0x24/0x80
  ? page_fault_oops+0x99/0x1b0
  ? kernelmode_fixup_or_oops+0xb2/0x140
  ? __bad_area_nosemaphore+0x1a5/0x2c0
  ? bad_area_nosemaphore+0x16/0x30
  ? do_kern_addr_fault+0x7b/0xa0
  ? exc_page_fault+0x1a4/0x1b0
  ? asm_exc_page_fault+0x27/0x30
  ? cifs_flush_folio+0x41/0xf0 [cifs]
  ? cifs_flush_folio+0x37/0xf0 [cifs]
  cifs_remap_file_range+0x172/0x660 [cifs]
  do_clone_file_range+0x101/0x2d0
  vfs_clone_file_range+0x3f/0x150
  ioctl_file_clone+0x52/0xc0
  do_vfs_ioctl+0x68f/0x910
  ? __fget_light+0xa5/0x120
  __x64_sys_ioctl+0x7d/0xf0
  do_syscall_64+0x59/0x90
  ? kmem_cache_free+0x22/0x3e0
  ? putname+0x5b/0x80
  ? exit_to_user_mode_prepare+0x30/0xb0
  ? syscall_exit_to_user_mode+0x37/0x60
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90

  There is no known workaround.

  [Fix]

  The stacktrace is very similar to a regression reported to upstream
  6.1.y:

  https://lore.kernel.org/linux-
  mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/

  The thread mentions that:

  commit 7b2404a886f8b91250c31855d287e632123e1746
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746

  introduced the issue to Debian's 6.1 kernel.

  This got backported to Ubuntu in:

  commit 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()

  $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Ubuntu-6.5.0-20.20~107

  Which we have been using for some time now, and is not the culprit.

  Reading the regression mailing list thread, they mention that things
  work differently in 6.1:

  > Yeah.  __filemap_get_folio() works differently in v6.1.y. There it returns a
  > folio or NULL.  In 6.7 it returns a folio or a negative error code.  The 
error
  > check in cifs_flush_folio() needs to change to something like:
  >
  > folio = filemap_get_folio(inode->i_mapping, index);
  > if (!folio)
  > return -ENOMEM;
  >
  > David 

  6.1.y then got a specific patch to fix the issue in 6.1, which is:

  commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1

[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

[Martin D. Weinberg]

Sorry, just trying to help by providing reports an following the rules.
I'll refrain from posting moving forward.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta 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:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-meta-oem-6.8 package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-meta source package in Noble:
  In Progress
Status in linux-meta-oem-6.8 source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
  ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The main fixes are in kernel & dkms packages. This adds ivsc-modules to
  Provides list of linux-image-generic as other built-in linux-modules-foo
  packages do.

  [Test Case]

  The generated meta package linux-image-generic should then provides
  "ivsc-modules".

  [Where problems could occur]

  Meta package changes only. No real effect but in package dependency.

  [Other Info]

  While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
  only be nominated for Unstable/Noble/OEM-6.8.

  == ipu6-drivers, linux, linux-oem-6.8 ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.

  == original 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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Juerg Haefliger]

We should drop it from the seed since we're not building ARM ISOs
anymore.

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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

[You-Sheng Yang]

** Description changed:

  [SRU Justification]
  
  BugLink: https://bugs.launchpad.net/bugs/2061747
  
  == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
  ==
  
  [Impact]
  
  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.
  
  [Fix]
  
  The main fixes are in kernel & dkms packages. This adds ivsc-modules to
  Provides list of linux-image-generic as other built-in linux-modules-foo
  packages do.
  
  [Test Case]
  
  The generated meta package linux-image-generic should then provides
  "ivsc-modules".
  
  [Where problems could occur]
  
  Meta package changes only. No real effect but in package dependency.
  
  [Other Info]
  
  While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
  only be nominated for Unstable/Noble/OEM-6.8.
  
- == ipu6-drivers ==
+ == ipu6-drivers, linux, linux-oem-6.8 ==
  
  [Impact]
  
  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.
  
  [Fix]
  
  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the
  same support level to launch Intel IPU6 Camera devices. Commit 1,3, and
  4 are to add supported devices and platforms. Commit 2 resolves an issue
  after resumed.
  
  [Test Case]
  
  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.
  
  [Where problems could occur]
  
  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and probably
  never will, the provided functions and verified stability issues may
  vary.
  
  [Other Info]
  
  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.
  
  == original 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta 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:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-meta-oem-6.8 package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-meta source package in Noble:
  In Progress
Status in linux-meta-oem-6.8 source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
  ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The main fixes are in kernel & dkms packages. This adds ivsc-modules to
  Provides list of linux-image-generic as other built-in linux-modules-foo
  packages do.

  [Test Case]

  The generated meta package linux-image-generic should then provides
  "ivsc-modules".

  [Where problems could occur]

  Meta package changes only. No real effect but in package dependency.

  [Other Info]

  While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
  only be nominated for Unstable/Noble/OEM-6.8.

  == ipu6-drivers, linux, linux-oem-6.8 ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the 

[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

[You-Sheng Yang]

Please don't fail the verification for things you're not sure.

** Tags removed: verification-failed-noble verification-needed
** Tags added: verification-done verification-done-noble

** Description changed:

  [SRU Justification]
  
  BugLink: https://bugs.launchpad.net/bugs/2061747
+ 
+ == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
+ ==
+ 
+ [Impact]
+ 
+ Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
+ instead of the out-of-tree dkms originated from
+ https://github.com/intel/ivsc-driver.
+ 
+ [Fix]
+ 
+ The main fixes are in kernel & dkms packages. This adds ivsc-modules to
+ Provides list of linux-image-generic as other built-in linux-modules-foo
+ packages do.
+ 
+ [Test Case]
+ 
+ The generated meta package linux-image-generic should then provides
+ "ivsc-modules".
+ 
+ [Where problems could occur]
+ 
+ Meta package changes only. No real effect but in package dependency.
+ 
+ [Other Info]
+ 
+ While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
+ only be nominated for Unstable/Noble/OEM-6.8.
+ 
+ == ipu6-drivers ==
  
  [Impact]
  
  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.
  
  [Fix]
  
  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the
  same support level to launch Intel IPU6 Camera devices. Commit 1,3, and
  4 are to add supported devices and platforms. Commit 2 resolves an issue
  after resumed.
  
  [Test Case]
  
  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.
  
  [Where problems could occur]
  
  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and probably
  never will, the provided functions and verified stability issues may
  vary.
  
  [Other Info]
  
  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.
  
  == original 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta 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:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-meta-oem-6.8 package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-meta source package in Noble:
  In Progress
Status in linux-meta-oem-6.8 source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
  ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The main fixes are in kernel & dkms packages. This adds ivsc-modules to
  Provides list of linux-image-generic as other built-in linux-modules-foo
  packages do.

  [Test Case]

  The generated meta package linux-image-generic should then provides
  "ivsc-modules".

  [Where problems could occur]

  Meta package changes only. No real effect but in package dependency.

  [Other Info]

  While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
  only be nominated for Unstable/Noble/OEM-6.8.

  == ipu6-drivers, linux, linux-oem-6.8 ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install 

[Kernel-packages] [Bug 2058485] Re: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter

[Thibf]

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

Title:
   [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with
  percpu counter

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

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

  Backport: ipc/msg: mitigate the lock contention with percpu counter
  (merged upstream in 6.1) to jammy

  [Impact]

  The msg_bytes and msg_hdrs atomic counters are frequently updated when IPC 
msg queue is in heavy use, causing heavy
  cache bounce and overhead. Change them to percpu_counter greatly improve the 
performance. Since there is one percpu
  struct per namespace, additional memory cost is minimal. Reading of the count 
done in msgctl call, which is infrequent.
  So the need to sum up the counts in each CPU is infrequent.

  [Fix]

  Backport:
72d1e611082e ipc/msg: mitigate the lock contention with percpu counter

  For clean backport/build, those are also required:

  5d0ce3595ab75 percpu: add percpu_counter_add_local and 
percpu_counter_sub_local
  38cd5b12b7854 ipc: Remove extra braces
  0889f44e28103 ipc: Check permissions for checkpoint_restart sysctls at open 
time
  dd141a4955d5e ipc: Remove extra1 field abuse to pass ipc namespace
  def7343ff03bb ipc: Use the same namespace to modify and validate
  1f5c135ee509e ipc: Store ipc sysctls in the ipc namespace
  dc55e35f9e810 ipc: Store mqueue sysctls in the ipc namespace
  0e9beb8a96f21 ipc/ipc_sysctl.c: remove fallback for !CONFIG_PROC_SYSCTL
  5563cabdde7ee ipc: check checkpoint_restore_ns_capable() to modify C/R proc 
files

  
  [Test Plan]

  Test as the original patch, with pts/stress-ng message passing
  and compare performance.

  [Where problems could occur]

  Performance regression in IPC communication/workload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058485/+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 2058109] Re: Kernel 5.15.0-100 breaks Intel NIC

[Anthony Wong]

The latest version in jammy-updates is now 5.15.0-105.115 and 5.15.0-106.116 in 
proposed.
Paul, could you give them a try?

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

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

Title:
  Kernel 5.15.0-100 breaks Intel NIC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From syslog:
  Mar 15 12:11:18 kvmMini systemd[1]: Starting Refresh fwupd metadata and 
update motd...
  Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Updating lvfs
  Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Downloading…: 0%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 0%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 1%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 2%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 3%
  ...trimmed content
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 97%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 98%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:20 kvmMini fwupdmgr[284042]: Successfully downloaded new 
metadata: 0 local devices supported
  Mar 15 12:11:20 kvmMini systemd[1]: fwupd-refresh.service: Deactivated 
successfully.
  Mar 15 12:11:20 kvmMini systemd[1]: Finished Refresh fwupd metadata and 
update motd.
  Mar 15 12:17:01 kvmMini CRON[284549]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Mar 15 12:23:59 kvmMini kernel: [3519186.337746] x86/split lock detection: 
#AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3
  Mar 15 12:26:49 kvmMini kernel: [3519356.515727] x86/split lock detection: 
#AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3
  Mar 15 13:05:00 kvmMini systemd[1]: 
run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.5pHMXa.mount:
 Deactivated successfully.
  Mar 15 13:07:48 kvmMini kernel: [3521815.001961] x86/split lock detection: 
#AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3
  Mar 15 13:17:01 kvmMini CRON[289583]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Mar 15 13:20:49 kvmMini kernel: [3522596.527060] x86/split lock detection: 
#AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3
  Mar 15 13:30:01 kvmMini systemd[1]: 
run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.I79KlX.mount:
 Deactivated successfully.
  Mar 15 13:43:22 kvmMini kernel: [3523948.983970] x86/split lock detection: 
#AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3
  Mar 15 13:53:22 kvmMini kernel: [3524549.046156] x86/split lock detection: 
#AC: CPU 0/KVM/1774 took a split_lock trap at address: 0xf8041de42fb3
  Mar 15 14:07:33 kvmMini systemd[1]: 
run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.K8Zq9M.mount:
 Deactivated successfully.
  Mar 15 14:17:01 kvmMini CRON[294744]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] e1000e :00:1f.6 eno2: 
Detected Hardware Unit Hang:
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   TDH  <9f>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   TDT  <9>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_use  <9>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_clean<9e>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] buffer_info[next_to_clean]:
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   time_stamp   
<1348a0aab>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_watch<9f>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   jiffies  
<1348a0bb0>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_watch.status <0>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] MAC Status 
<40080083>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Status <796d>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY 1000BASE-T Status  <3800>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Extended Status<3000>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PCI Status <10>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] e1000e :00:1f.6 eno2: 
Detected Hardware Unit Hang:
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   TDH  <9f>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   TDT  <9>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   next_to_use

[Kernel-packages] [Bug 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+

[Ginés Utrera Pavón]

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

@Daniel: It happened to me with a laptop. If it's any consolation, it
has also happened to me with the nvidia-340 driver on another laptop...

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

Title:
  Nvidia 390 Needs Patched for Kernel 6.5+

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Supposedly, this was solved in Ubuntu 23.10, but the package never made it 
out of the mantic-proposed repository: 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16
  Nor was it backported to Ubuntu 22.04 

  As a temporary measure, I uploaded a patched version to a PPA for
  Ubuntu 22.04 (and added a patch for 6.6/6.7):
  https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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 2058208] Re: OpenGL renderer AMD defaults to Intel

[Anthony Wong]

** Changed in: linux-signed-oem-6.5 (Ubuntu)
 Assignee: Anthony Wong (anthonywong) => (unassigned)

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

Title:
  OpenGL renderer AMD defaults to Intel

Status in linux-signed-oem-6.5 package in Ubuntu:
  Invalid

Bug description:
  Checkbox job "
  com.canonical.certification::graphics/2_valid_opengl_renderer_PCI_ID_0x743f"
  fails with error:

  ```
  Setting up PRIME GPU offloading for AMD discrete GPU
  OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S)
  ERROR: renderer is Intel when DRI_PRIME=1
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-1016-oem 6.5.0-1016.17
  ProcVersionSignature: Ubuntu 6.5.0-1016.17-oem 6.5.13
  Uname: Linux 6.5.0-1016-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Mar 18 14:46:23 2024
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-abra+X102
  InstallationDate: Installed on 2024-03-15 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  SourcePackage: linux-signed-oem-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058208/+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 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)

[Anthony Wong]

Felipe, thanks for testing.

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

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

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

Title:
  Keyboard does not work after waking up from suspend with 5.15.0-105
  (but works with 5.15.0-101)

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Dear Ubuntu maintainers, I think I found a regression in linux
  5.15.0-105.

  In the past few days, my keyboard stopped working after waking up from
  suspend (sleep), so I couldn't unlock my laptop. Various workarounds
  found on the internet helped, but I wanted to investigate if it was a
  gdm issue, grub, or a hardware failure. I managed to narrow it down to
  the kernel, which is why I'm filing this bug report.

  AFAICT the only keys that work are the keyboard lights and the
  brightness knobs (in the Fn functions). I can confirm that 5.15.0-105
  has the issue, and I can consistently reproduce it with the following
  steps:

  1. boot fresh with 5.15.0-105
  2. login to my account
  3. choose suspend from the power menu
  4. wake up

  
  Following the same steps above with the last kernel available does not cause 
the issue (package version 5.15.0-101.111). I'll keep using that one for the 
time being.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-105-generic 5.15.0-105.115
  ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148
  Uname: Linux 5.15.0-105-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philsf 5465 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 02:58:26 2024
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc
  InstallationDate: Installed on 2018-06-07 (2145 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic 
root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-105-generic N/A
   linux-backports-modules-5.15.0-105-generic  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.29
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2023
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 0TXW78
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+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 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+

[Daniel Letzeisen]

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

@Ginés: Thanks for the feedback. Are you using a laptop or desktop? I've gotten 
a few reports of black screens this week on 24.04
I guess I'll have to pull out the old GTX950 and try to troubleshoot it :(

If anyone else reading this has gotten the 390 driver working on 24.04,
please let me know.

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

Title:
  Nvidia 390 Needs Patched for Kernel 6.5+

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Supposedly, this was solved in Ubuntu 23.10, but the package never made it 
out of the mantic-proposed repository: 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16
  Nor was it backported to Ubuntu 22.04 

  As a temporary measure, I uploaded a patched version to a PPA for
  Ubuntu 22.04 (and added a patch for 6.6/6.7):
  https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[J K]

I tried and that the issue is still the same as before

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

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2024
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1UET46W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21B4S4QB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76465 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
  dmi.product.family: ThinkPad L13 Gen 3
  dmi.product.name: 21B4S4QB00
  dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
  dmi.product.version: ThinkPad L13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062950/+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

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-April/150635.html 
(linux-meta: noble, unstable)
* https://lists.ubuntu.com/archives/kernel-team/2024-April/150637.html 
(linux-meta-oem-6.8)

** Changed in: linux-meta (Ubuntu Noble)
   Status: Triaged => In Progress

** Changed in: linux-meta-oem-6.8 (Ubuntu Noble)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta 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:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-meta-oem-6.8 package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-meta source package in Noble:
  In Progress
Status in linux-meta-oem-6.8 source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.

  == original 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 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+

[Ginés Utrera Pavón]

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

Thank you @Daniel. I just installed it on Xubuntu 24.04 (with X11
obviously), and when it restarted I had a black screen, so I have to
purge the package from recovery mode to get back to normal. ;(

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

Title:
  Nvidia 390 Needs Patched for Kernel 6.5+

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Supposedly, this was solved in Ubuntu 23.10, but the package never made it 
out of the mantic-proposed repository: 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16
  Nor was it backported to Ubuntu 22.04 

  As a temporary measure, I uploaded a patched version to a PPA for
  Ubuntu 22.04 (and added a patch for 6.6/6.7):
  https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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 2054296] Re: Don't restrict to linux-laptop

[Tobias Heider]

It looks like this change did indeed cause issues for non-qualcomm
hardware, see https://bugs.launchpad.net/ubuntu/+source/ubuntu-
meta/+bug/206266

We should definitely check if we can restrict the service to supported
qualcomm devices only. Currently it causes systemd errors and a
noticeable boot delay on at least raspi and apple silicon.

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

Title:
  Don't restrict to linux-laptop

Status in protection-domain-mapper package in Ubuntu:
  Fix Released
Status in qrtr package in Ubuntu:
  Fix Released

Bug description:
  The generic arm64 kernel now support some Qualcomm platforms so the
  services need to run with that kernel as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Tobias Heider]

Looking at the diff between mantic and noble I think the regression was
cause by a change to pd-mapper.service.in for
https://bugs.launchpad.net/ubuntu/+source/qrtr/+bug/2054296

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Aaron Honeycutt]

Once I'm back with the system I'll test and let you know ASAP!

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+

[Daniel Letzeisen]

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

@Ginés: Theoretically, it should. I made a package for Noble/24.04 in the PPA 
and it seemed to build/install correctly in my Xubuntu 24.04 VM
Keep in mind that the only Nvidia card I own is sitting in my closet, so I 
personally can't test whether the driver functions correctly once installed. If 
you have issues with it, the only thing I can suggest is making sure you're 
using Xserver and not Wayland.

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

Title:
  Nvidia 390 Needs Patched for Kernel 6.5+

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Supposedly, this was solved in Ubuntu 23.10, but the package never made it 
out of the mantic-proposed repository: 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16
  Nor was it backported to Ubuntu 22.04 

  As a temporary measure, I uploaded a patched version to a PPA for
  Ubuntu 22.04 (and added a patch for 6.6/6.7):
  https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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 2064017] Re: Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)

[GLAUCO RIZZO]

Hello Daniel,
I tried passing that kernel parameter to grub, but it did not help:

This is the echo of my kernel command line passed to grub from bash
terminal:

more /proc/cmdline

BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic
root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash
i915.enable_psr=0 vt.handoff=7

Let me know if you have any other suggestions to try.
Thank you for your support

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

Title:
  Xserver Display flickers when mouse pointer is inside narrow
  horizontal range band (kernel related)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  My machine information is following :
  HP EliteBook 840 G3
  Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520]
  xrandr -q active mode on laptop display : 1368x768  60.01

  Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped 
kernel 6.8.0-31), same issue.
  Rolling back the kernel to 6.7 fixed the problem,maybe there were some video 
driver changes from kernel 6.7 to 6.8 ?

  While using the 6.8 kernel I did some experiments:

  disabled picom in startup , no effect

  Tried changing display resolution, just moves vertical position of band.
  (at the above resolution 1368x768 vertical mouse pointer flicker range is 
around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from 
a bash terminal)

  Tried moving refresh rate slightly around 60 Hz by creating a new
  modeline using cvt tool and adding new mode with xrandr, no effect.

  tried connecting external display on laptop VGA port and duplicating
  screen and the issue seems to disappear.

  tried capturing a video of the desktop  using ffmpeg with x11grab, but
  it does not show the issue.

  I attached a short video of the laptop display flicker I recorded
  using my phone

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Sun Apr 28 09:44:42 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
  InstallationDate: Installed on 2024-04-25 (3 days ago)
  InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 
(20240425.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP HD Camera
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP EliteBook 840 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.release: 1.42
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.42
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.78
  dmi.chassis.asset.tag: 5CG7042V5J
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.120
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: Z2A57UT#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

[Martin D. Weinberg]

Thanks, I tried the NVidia kernel 6.8.0-1005.5+1 from noble-proposed;
still no detection.  Could be that this predates that patch series?  Not
sure.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta 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:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-oem-6.8 package in Ubuntu:
  Triaged
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-meta source package in Noble:
  Triaged
Status in linux-meta-oem-6.8 source package in Noble:
  Triaged
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.

  == original 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 2054855] Re: Azure: Network doesn't get configured after triggering kdump

[Tim Gardner]

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

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

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

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

Bug description:
  SRU Justification

  [Impact]

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

  [Fix]

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

  [Test Plan]

  Microsoft tested.

  [[Where things could go wrong]

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

  [Other Info]

  SF: #00378199

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


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

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

[Andrea Righi]

Hello, any progress on this? Now that ubuntu-fan is officially
deprecated in Noble can we simply sync iproute2 with Debian? Is there
any pending activity / requirement that are preventing this? Thanks!

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

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 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+

[Ginés Utrera Pavón]

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

Daniel, the Experimental version of Nvidia 390.xx driver for kernels up
to 6.8, would it work on Ubuntu 24.04?

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

Title:
  Nvidia 390 Needs Patched for Kernel 6.5+

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Supposedly, this was solved in Ubuntu 23.10, but the package never made it 
out of the mantic-proposed repository: 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16
  Nor was it backported to Ubuntu 22.04 

  As a temporary measure, I uploaded a patched version to a PPA for
  Ubuntu 22.04 (and added a patch for 6.6/6.7):
  https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

[Tobias Heider]

Can confirm that this is was a major annoyance on my m2 air after
upgrading to noble. it seems like this worked better in previous
releases. Looking at my logs it seems like it was already installed on
mantic but didn't cause startup problems. I think it gets pulled in by
being in Recommends for ubuntu-desktop.

I'm all for making it device specific instead. IMO there is no point in
having it installed on non Qualcomm devices.

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

[Jarmo Ilonen]

Some additional information on my system with AMD Ryzen 5 8600G w/
Radeon 760M Graphics.

This is a new system originally installed with Ubuntu 23.10 which worked
ok. After upgrading to 24.04 the same thing started happening: blank
screen after boot. Works when booted from 24.04 live USB, but after
installation I could not figure out permanent fix for blank screen. It
does work in safe mode (nomodeset), but of course quite slowly.

When I installed SSH server in safe mode and rebooted back to blank
screen, I could login remotely even though the system looked dead.
Nothing stood out in the logs, looked like the system thought it was
working normally. Magic sysrq also works.

I went back to 23.10 for now, but a couple of week old logs from booting
24.04 are available if they might be useful.

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

Title:
  24.04 Upgrade/Fresh Install results in black screen on reboot on
  AMDGPU system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card.

  Using xUbuntu.

  I had been daily driving the 24.04 nightly iso since March. About a
  week ago, I took a kernel update via apt and rebooted. The result was
  that the system would hard freeze to a black screen after the initial
  kernel messages cleared from the screen. Ctrl-Alt-Del did nothing,
  switching terminals (ctrl-alt-f#) did nothing, had to hard power off
  to regain control of the system.

  I tried various fixes, none of which permanently stuck. This includes
  nomodeset in grub, rebooting into safe mode, checking for proprietary
  drivers. Safe mode allowed me to reboot once more into desktop, but
  then any subsequent reboots would result in a black screen lockup.

  Suspending while able to use the desktop before reboot would cause a
  black screen lockup did not seem to cause any issues.

  3 days before 24.04 was officially released, I reflashed the most
  recent installer iso to my thumbdrive, copied my home folder to my
  RAID and did a full wipe and fresh install.

  First reboot after installation always went to the desktop. Subsequent
  reboots always resulted in a black screen lockup.

  Memtest cleared without errors.

  Again tried various fixes, nomodeset, safe mode, drivers. The only
  consistency was that regardless of what I could do to regain control
  or what I did differently when doing a wipe and reinstall, I would
  always reboot to a black screen.

  Once 24.04 was officially released, I again did a full wipe and
  reinstall and encountered all of the above same issues as before.

  After mentioning this in #ubuntu on libera, someone suggested a kernel
  downgrade.

  24.04 as installed was using 6.8.0-31.31

  Using Mainline, I downgraded to the next minor version below 6.8 that
  was considered stable. 6.7.10

  Problem went away. No more black screen on boot, no more hard power
  offs required to be able to use my system again, no suspend issues.
  Was not necessary for me to do anything else to maintain a consistent
  successful reboot to desktop.

  Did yet another full wipe and fresh install of 24.04, only installing
  Mainline upon first reboot to install 6.7.10, using Grub Customizer to
  edit the default grub option to boot the 6.7.10 kernel instead.

  No issues.

  I apologise that I did not collect logs during this process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+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 2063529] Re: Add support for Quectel RM520N-GL modem

[Bin Li]

** Description changed:

  [Impact]
  
- * Add support for Quectel RM520N-GL modem, so the device could be
- properly probed.
+ * Add support for Quectel RM520N-GL modem, so the device could be properly 
+ probed.
+ 
+ 08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:1007]
+ Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:100b]
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
  * These commits only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
  * Upstream commits:
    
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
    
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

** Summary changed:

- Add support for Quectel RM520N-GL modem
+ Add support for Quectel RM520N-GL modem [1eac:1007]

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

Title:
  Add support for Quectel RM520N-GL modem [1eac:1007]

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  In Progress

Bug description:
  [Impact]

  * Add support for Quectel RM520N-GL modem, so the device could be properly 
  probed.

  08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:1007]
  Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:100b]

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * These commits only introduces a PID, it won't impact devices which
  are supported originally.

  [Other Info]

  * Upstream commits:
    
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
    
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063529/+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 2063399] Re: Add support for Quectel EM160R-GL modem [1eac:100d]

[Bin Li]

** Summary changed:

- Add support for Quectel EM160R-GL modem
+ Add support for Quectel EM160R-GL modem [1eac:100d]

** Description changed:

  [Impact]
  
  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.
+ 
+ 08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:100d]
+ Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:5004]
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
  * The commit only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

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

Title:
  Add support for Quectel EM160R-GL modem [1eac:100d]

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Won't Fix
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:
  In Progress

Bug description:
  [Impact]

  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.

  08:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. Device 
[1eac:100d]
  Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:5004]

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * The commit only introduces a PID, it won't impact devices which are
  supported originally.

  [Other Info]

  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

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

[Anthony Wong]

This fix also requires kernel patches in this series:
https://lists.ubuntu.com/archives/kernel-team/2024-April/150378.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta 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:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-oem-6.8 package in Ubuntu:
  Triaged
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-meta source package in Noble:
  Triaged
Status in linux-meta-oem-6.8 source package in Noble:
  Triaged
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.

  == original 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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Per Overgaard]

Another Workaround:
This is using the Nvidia driver and not nouveau, right? I believe this is a 
driver in the Nvidia driver that is not asking for the conflicting framebuffers 
to be unregistered.
You can try to add "initcall_blacklist=simpledrm_platform_driver_init" to your  
kernel command line parameters to prevent the simpledrm driver to not be loaded.

Add to your kernel command line this. Open your terminal:
sudo nano /etc/default/grub
add "initcall_blacklist=simpledrm_platform_driver_init" to where it says 
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash..., so it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash 
initcall_blacklist=simpledrm_platform_driver_init”
ctrl+O for save and ctrl+X for quit. Back in the terminal write:
sudo update-grub
rebbot


This fixed the issue for me.

-- 
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 "Unknown Display" 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
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  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.

  [ Workaround ]

  1. sudo rm /dev/dri/card0
  2. Log in again.

  [ Test Plan ]

  Open Settings and verify the only monitors shown are your real
  monitors.

  [ Where problems could occur ]

  Removing the simpledrm card is only safe when it's not being used. If
  somehow a machine wasn't using the installed Nvidia driver then there
  could be a risk of deleting the only working display.

  [ Other Info ]

  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 2063074] Re: Waydroid breaks nouveau

[Anthony Wong]

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

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

Title:
  Waydroid breaks nouveau

Status in linux package in Ubuntu:
  Triaged

Bug description:
  https://waydro.id/

  The session is forced to logout.

  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 
RenderThread[30070]] subc 0 class c597 mthd 0d78 data 0004
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 
RenderThread[30070]] subc 0 class c597 mthd 17e0 data 0018
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 
RenderThread[30107]] subc 0 class c597 mthd 0d78 data 0004
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 
RenderThread[30107]] subc 0 class c597 mthd 17e0 data 0018
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 
RenderThread[30145]] subc 0 class c597 mthd 0d78 data 0004
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 
RenderThread[30145]] subc 0 class c597 mthd 17e0 data 0018
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 
RenderThread[26039]] subc 0 class c597 mthd 0d78 data 0004
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 
RenderThread[26039]] subc 0 class c597 mthd 17e0 data 000c
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 
RenderThread[26039]] subc 0 class c597 mthd 17e0 data 0060
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 
RenderThread[26090]] subc 0 class c597 mthd 0d78 data 0004
  nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 
RenderThread[26090]] subc 0 class c597 mthd 17e0 data 0018

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-31-generic 6.8.0-31.31
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:neo3373 F pipewire
   /dev/snd/controlC0:  neo3373 F pipewire
    neo3377 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 07:32:35 2024
  InstallationDate: Installed on 2024-03-22 (30 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash ipv6.disable=1
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-31-generic N/A
   linux-backports-modules-6.8.0-31-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-04-11 (11 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: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX435EG_UX435EG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063074/+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

[You-Sheng Yang]

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

This should have been fixed by updating ipu6-drivers in bug 2061747.

** This bug has been marked a duplicate of bug 2061747
   obsolete out-of-tree ivsc dkms in favor of in-tree one

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

[Kernel-packages] [Bug 2040106] Re: firmware broken after upgrade to Ubuntu 23.10

[Petter Sundlöf]

The fix in https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2040106/comments/3 used to work for me, but no longer
does. Upgraded to latest packages as of 2024-04-29. Bluetooth still
broken

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

Title:
  firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * Focal preinstalled systems with OEM kernel, if force upgraded to
  interim releases, before transitional packages have been made
  available resulted in systems having been stuck on focal oem kernel
  and not getting any kernel updates.

   * Reintroduce all focal oem kernel transitionals to trigger upgrade
  to hwe kernel in all stable releases for the oem-20.04* kernels

  [ Test Plan ]

   * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
   * Force upgrade to mantic
   * Observe that all oem-20.04 meta packages got upgraded and rolled to 
generic hwe kernel (of appropriate version for jammy & mantic)

  [ Where problems could occur ]

   * This may trigger dkms package recompilation, and nvidia driver missmatches
   * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
   * Users may experience jump from v5.10 kernel to v6.5 kernel

  [ Other Info ]

   * Original bug report

  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 20230919.git3672ccab-0ubuntu2.1
    Candidate: 20230919.git3672ccab-0ubuntu2.1
    Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0NG7N9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Juerg Haefliger]

The problem is that on upgrade to Noble the package linux-image-laptop
is removed which contains config settings for the machine. I'm in the
process of creating a new package (ubuntu-x13s-settings) for Noble that
provide these settings. Can you try to install ubuntu-x13s-settings from
PPA:ubuntu-concept/x13s (https://launchpad.net/~ubuntu-
concept/+archive/ubuntu/x13s) and report back?

One of the issues is that ARM pointer authentication is not working
(broken Lenovo firmware) and needs to be disabled for the 6.8 kernel
(arm64.nopauth kernel commandline option). The above package should set
that (amongst other things).

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

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

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

[Bogdan Mitrea]

i have done again. It says that it might take minutes to send data but
was done in seconds :)

can you please check again?

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 6.5 the external Bluetooth USB dongle based on
  Realtek stop working.

  This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
  version is > 6.5. On a lower kernel version it works as we were using
  it for almost 2 years without issues.

  Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
  USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

  ```
  $ uname -a
  Linux bomi-edge 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
  ```

  ```
  $ lsusb | grep -i bluetooth
  Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
  ```

  Journalctl logs after the OS is starting
  ```
  journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  ```

  I have installed BlueZ package https://www.bluez.org/ and trying to
  discover the device which worked but i am always getting errors when
  trying to connect to the device via BT (after pairing)

  ```
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Changed settings: 0x0008
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Pending settings: 0x0002
  Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] event 0x000b
  Apr 18 09:23:07 

[Kernel-packages] [Bug 2064017] Re: Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)

[Daniel van Vugt]

Please try adding kernel parameter:

  i915.enable_psr=0

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

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

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

Title:
  Xserver Display flickers when mouse pointer is inside narrow
  horizontal range band (kernel related)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  My machine information is following :
  HP EliteBook 840 G3
  Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520]
  xrandr -q active mode on laptop display : 1368x768  60.01

  Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped 
kernel 6.8.0-31), same issue.
  Rolling back the kernel to 6.7 fixed the problem,maybe there were some video 
driver changes from kernel 6.7 to 6.8 ?

  While using the 6.8 kernel I did some experiments:

  disabled picom in startup , no effect

  Tried changing display resolution, just moves vertical position of band.
  (at the above resolution 1368x768 vertical mouse pointer flicker range is 
around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from 
a bash terminal)

  Tried moving refresh rate slightly around 60 Hz by creating a new
  modeline using cvt tool and adding new mode with xrandr, no effect.

  tried connecting external display on laptop VGA port and duplicating
  screen and the issue seems to disappear.

  tried capturing a video of the desktop  using ffmpeg with x11grab, but
  it does not show the issue.

  I attached a short video of the laptop display flicker I recorded
  using my phone

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Sun Apr 28 09:44:42 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
  InstallationDate: Installed on 2024-04-25 (3 days ago)
  InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 
(20240425.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP HD Camera
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP EliteBook 840 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.release: 1.42
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.42
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.78
  dmi.chassis.asset.tag: 5CG7042V5J
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.120
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: Z2A57UT#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064017/+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 2064019] Re: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-28-generic package pre-removal script subprocess ret

[Juerg Haefliger]

Package configuration┌─┤ 
Removing linux-image-6.5.0-28-generic ├─┐│  
 
│ │ You are running a kernel (version 
6.5.0-28-generic) and attempting to │ │ remove 
the same version.  │ 
│   
│ │ This can make the system unbootable 
as it will remove │ │ 
/boot/vmlinuz-6.5.0-28-generic and all modules under the directory
│ │ /lib/modules/6.5.0-28-generic. This can only be 
fixed with a copy of the  │ │ kernel image and the 
corresponding modul es.   │ 
│  
 │ │ It is highly recommended to abort 
the kernel removal unless you are   │ │ prepared 
to fix the system after removal. │ 
│  
 │ │ Abort kernel removal?   
  │ │
   │ 
│ 
 │ │ 
  │ 
└─ 
──┘    
  
[?12l[?25h(B

[?1049lE: Aborting removal of the running kernel

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

Title:
  package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to
  install/upgrade: installed linux-image-6.5.0-28-generic package pre-
  removal script subprocess returned error exit status 1

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

Bug description:
  This kernel version has error on api Eclipse when I use the assistant
  help.

  Esta versión presenta fallos al utilizar el asistente de ayuda de Eclipse. 
Por lo visto, al escribir un comando por ejemplo System. entonces se despliegan 
todas las posibilidades para este comando, y luego Ecliplse desaparece. 
  He podido comprobar que al deshabilitar esta función, Eclipse no desaparece, 
pero se hace complicado programar sin ayudas.

  Thanks for your support.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-compute-390_390.154-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-compute-510_510.85.02-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.85.02-0ubuntu0.22.04.1_amd64.deb
  CasperMD5CheckResult: fail
  Date: Sun Apr 28 16:34:42 2024
  ErrorMessage: installed linux-image-6.5.0-28-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-04-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.12
  SourcePackage: linux-signed-hwe-6.5
  Title: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to 
install/upgrade: installed linux-image-6.5.0-28-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2064019/+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 2063228] Re: screen sometimes blinking

[Daniel van Vugt]

After editing /etc/default/grub, please also run:

  sudo update-grub

and then reboot.

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

Title:
  screen sometimes blinking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Pavilion Laptop 14-ce2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2022
  dmi.bios.release: 15.27
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84BB
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 14-ce2xxx
  dmi.product.sku: 8KZ34EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+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 2064019] Re: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: installed linux-image-6.5.0-28-generic package pre-removal script subprocess ret

[Juerg Haefliger]

You chose to not remove the running kernel, hence the 'failure' to
remove the package.

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

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

Title:
  package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to
  install/upgrade: installed linux-image-6.5.0-28-generic package pre-
  removal script subprocess returned error exit status 1

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

Bug description:
  This kernel version has error on api Eclipse when I use the assistant
  help.

  Esta versión presenta fallos al utilizar el asistente de ayuda de Eclipse. 
Por lo visto, al escribir un comando por ejemplo System. entonces se despliegan 
todas las posibilidades para este comando, y luego Ecliplse desaparece. 
  He podido comprobar que al deshabilitar esta función, Eclipse no desaparece, 
pero se hace complicado programar sin ayudas.

  Thanks for your support.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-compute-390_390.154-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-compute-510_510.85.02-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.85.02-0ubuntu0.22.04.1_amd64.deb
  CasperMD5CheckResult: fail
  Date: Sun Apr 28 16:34:42 2024
  ErrorMessage: installed linux-image-6.5.0-28-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-04-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.12
  SourcePackage: linux-signed-hwe-6.5
  Title: package linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to 
install/upgrade: installed linux-image-6.5.0-28-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2064019/+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 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[Daniel van Vugt]

Please try adding this to /etc/environment:

  MUTTER_DEBUG_FORCE_KMS_MODE=simple

and reboot.

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

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2024
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1UET46W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21B4S4QB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76465 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
  dmi.product.family: ThinkPad L13 Gen 3
  dmi.product.name: 21B4S4QB00
  dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
  dmi.product.version: ThinkPad L13 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062950/+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 2064017] [NEW] Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:


My machine information is following :
HP EliteBook 840 G3
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520]
xrandr -q active mode on laptop display : 1368x768  60.01

Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped 
kernel 6.8.0-31), same issue.
Rolling back the kernel to 6.7 fixed the problem,maybe there were some video 
driver changes from kernel 6.7 to 6.8 ?

While using the 6.8 kernel I did some experiments:

disabled picom in startup , no effect

Tried changing display resolution, just moves vertical position of band.
(at the above resolution 1368x768 vertical mouse pointer flicker range is 
around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from 
a bash terminal)

Tried moving refresh rate slightly around 60 Hz by creating a new
modeline using cvt tool and adding new mode with xrandr, no effect.

tried connecting external display on laptop VGA port and duplicating
screen and the issue seems to disappear.

tried capturing a video of the desktop  using ffmpeg with x11grab, but
it does not show the issue.

I attached a short video of the laptop display flicker I recorded using
my phone

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: LXQt
Date: Sun Apr 28 09:44:42 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
InstallationDate: Installed on 2024-04-25 (3 days ago)
InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP HD Camera
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP EliteBook 840 G3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2019
dmi.bios.release: 1.42
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.42
dmi.board.name: 8079
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.78
dmi.chassis.asset.tag: 5CG7042V5J
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 133.120
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 840 G3
dmi.product.sku: Z2A57UT#ABA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption noble ubuntu
-- 
Xserver Display flickers when mouse pointer is inside narrow horizontal range 
band (kernel related)
https://bugs.launchpad.net/bugs/2064017
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 2060984] Re: FFe: New firmware release

[Timo Aaltonen]

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  FFe: New firmware release

Status in linux-firmware package in Ubuntu:
  Won't Fix

Bug description:
  A new upstream release of linux-firmware was tagged on 2024.04.10,
  this would sync us with that. Changes:

   - imx: sdma: update firmware to v3.6/v4.6
   - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260
   - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201
   - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203
   - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101
   - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200
   - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B
   - Montage: update firmware for Mont-TSSE
   - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops
   - rtw88: Add RTL8703B firmware v11.0.0
   - rtw89: 8922a: add firmware v0.35.18.0
   - rtw89: 8852c: update fw to v0.27.56.14
   - mekdiatek: Update mt8186 SOF firmware to v2.0.1
   - linux-firmware: update firmware for en8811h 2.5G ethernet phy
   - amdgpu: DMCUB updates for various AMDGPU ASICs
   - i915: Add DG2 HuC 7.10.15
   - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
   - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2062502] Re: linux-firmware package breaks iwlwifi

[Anthony Wong]

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: linux-firmware (Ubuntu)
 Assignee: Anthony Wong (anthonywong) => En-Wei Wu (rickywu)

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

Title:
  linux-firmware package breaks iwlwifi

Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  This package version works:

  20230919.git3672ccab-0ubuntu2.1

  This one causes firmware SW errors and resets - breaking wifi in
  iwlwifi driver:

  20230919.git3672ccab-0ubuntu2.9

  I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
  to ...2.9 of the linux-firmware package, I saw many errors that begin
  like this in syslog:

  2024-04-18T22:30:20.975204-07:00 stormy kernel: [  886.503389] iwlwifi 
:00:14.3: Queue 1 is stuck 0 12
  2024-04-18T22:30:20.979152-07:00 stormy kernel: [  886.503652] iwlwifi 
:00:14.3: Microcode SW error detected. Restarting 0x0.
  2024-04-18T22:30:20.979167-07:00 stormy kernel: [  886.503764] iwlwifi 
:00:14.3: Start IWL Error Log Dump:
  2024-04-18T22:30:20.979169-07:00 stormy kernel: [  886.503768] iwlwifi 
:00:14.3: Transport status: 0x004A, valid: 6
  2024-04-18T22:30:20.979170-07:00 stormy kernel: [  886.503772] iwlwifi 
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode

  Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  been   2559 F wireplumber
   /dev/snd/controlC1:  been   2559 F wireplumber
   /dev/snd/seq:been   2554 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-11-17 (162 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  PackageArchitecture: amd64
  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.5.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-28-generic N/A
   linux-backports-modules-6.5.0-28-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  Tags: mantic
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2024-04-05 (22 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCTGL357.0040.2021.1126.1843
  dmi.board.name: LAPKC71F
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M2-402
  dmi.chassis.type: 10
  dmi.chassis.vendor: Intel(R) Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCTGL357.0040.2021.1126.1843:bd11/26/2021:br5.19:efr1.11:svnADATA:pnXENIA15:pvrM37957-402:rvnIntelCorporation:rnLAPKC71F:rvrM2-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuXENIA15I7G11H3070LX-BKCUS:
  dmi.product.family: XENIA
  dmi.product.name: XENIA 15
  dmi.product.sku: XENIA15I7G11H3070LX-BKCUS
  dmi.product.version: M37957-402
  dmi.sys.vendor: ADATA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+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