[Kernel-packages] [Bug 2047698] [NEW] I have no audio.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Audio isn't working, I have tried everything including this bug report.
Still no audio.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 29 13:58:32 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:2212]
InstallationDate: Installed on 2023-12-28 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Default string Default string
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=b5301c3d-1b26-47f8-ad4f-90997f62a480 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 5.19
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd04/21/2023:br5.19:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: linux-hwe-6.2 (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
I have no audio.
https://bugs.launchpad.net/bugs/2047698
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.2 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 2047388] Re: System reboots automatically when lock screen screen enabled.

[Daniel van Vugt]

Only the kernel can crash that hard, so reassigning there.

** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)

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

Title:
  System reboots automatically when lock screen screen enabled.

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

Bug description:
  System reboots automatically when lock screen screen enabled. The same
  is tested on ubuntu-20.04 as well as ubuntu-22.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 11:42:52 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company CometLake-S GT2 [UHD Graphics 630] 
[103c:85a2]
  InstallationDate: Installed on 2023-12-07 (19 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: HP HP  ProOne 400 G5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=3a72d508-3f06-4b45-a814-8d4bef8b43d0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2021
  dmi.bios.release: 9.0
  dmi.bios.vendor: HP
  dmi.bios.version: R12 Ver. 02.09.00
  dmi.board.name: 85A2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 08.98.00
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 8.152
  dmi.modalias: 
dmi:bvnHP:bvrR12Ver.02.09.00:bd04/21/2021:br9.0:efr8.152:svnHP:pnHPProOne400G5:pvr:rvnHP:rn85A2:rvrKBCVersion08.98.00:cvnHP:ct13:cvr:sku6AE46AV:
  dmi.product.family: 103C_53307F HP ProOne
  dmi.product.name: HP  ProOne 400 G5
  dmi.product.sku: 6AE46AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2047511] Re: [Lenovo IdeaPad Z500] Screen brightness

[Daniel van Vugt]

** Summary changed:

- Screen brightness
+ [Lenovo IdeaPad Z500] Screen brightness

** Summary changed:

- [Lenovo IdeaPad Z500] Screen brightness
+ [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't 
change it

** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)

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

Title:
  [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and
  I can't change it

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

Bug description:
  Ubuntu 22.04.3 LTS
  Release: 22.04

  Brightness of the screen is down to minimum and I can't change it.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 11:15:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904]
   NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 645M] [17aa:3904]
  InstallationDate: Installed on 2023-12-10 (16 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 20202
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.release: 0.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN31WW(V1.10)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN31WW(V1.10):bd11/16/2012:br0.49:efr1.49:svnLENOVO:pn20202:pvrLenovoIdeaPadZ500:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500:skuLENOVO_MT_20202:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20202
  dmi.product.sku: LENOVO_MT_20202
  dmi.product.version: Lenovo IdeaPad Z500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2047154] Re: [drm] *ERROR* flip_done timed out

[Daniel van Vugt]

** Tags added: amdgpu

** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)

** Summary changed:

- [drm] *ERROR* flip_done timed out
+ [amdgpu][drm] *ERROR* flip_done timed out

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

Title:
  [amdgpu][drm] *ERROR* flip_done timed out

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

Bug description:
  amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out
  gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[CRTC:84:crtc-0] commit wait timed out
  gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
flip_done timed out
  gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[CONNECTOR:119:HDMI-A-1] commit wait timed out
  gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=2>
  gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
flip_done timed out
  gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[PLANE:67:plane-5] commit wait timed out
  gru 21 16:32:46 karol.home.prv kernel: [ cut here ]
  gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at 
/var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di>
  gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i>
  gru 21 16:32:46 karol.home.prv kernel:  reed_solomon pstore_zone efi_pstore 
sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp>
  gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: 
PW  OE  6.2.0-26-generic #26~22.04.1-Ubuntu
  gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. 
To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29>
  gru 21 16:32:46 karol.home.prv kernel: RIP: 
0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu]
  gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 
00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5>
  gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 
00010002
  gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 
00013195 RCX: 
  gru 21 16:32:46 karol.home.prv kernel: RDX:  RSI: 
 RDI: 
  gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: 
 R09: 
  gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: 
 R12: 0246
  gru 21 16:32:46 karol.home.prv kernel: R13:  R14: 
9710a5d8d118 R15: 9710a5d8d000
  gru 21 16:32:46 karol.home.prv kernel: FS:  7f3267b4ea80() 
GS:97179eac() knlGS:
  gru 21 16:32:46 karol.home.prv kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 
000250f4e000 CR4: 003506e0
  gru 21 16:32:46 karol.home.prv kernel: Call Trace:
  gru 21 16:32:46 karol.home.prv kernel:  
  gru 21 16:32:46 karol.home.prv kernel:  commit_tail+0xc5/0x1a0 
[drm_kms_helper]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper]
  gru 21 16:32:46 karol.home.prv kernel:  drm_atomic_helper_commit+0x137/0x160 
[drm_kms_helper]
  gru 21 16:32:46 karol.home.prv kernel:  drm_atomic_commit+0x99/0xd0 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? __pfx___drm_printfn_info+0x10/0x10 
[drm]
  gru 21 16:32:46 karol.home.prv kernel:  
drm_mode_obj_set_property_ioctl+0x179/0x430 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
drm_mode_createblob_ioctl+0xff/0x130 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
__pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  drm_ioctl_kernel+0xc3/0x160 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  drm_ioctl+0x27b/0x4c0 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
__pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? __pm_runtime_suspend+0x7b/0x110
  gru 21 16:32:46 karol.home.prv kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  gru 21 16:32:46 karol.home.prv kernel:  __x64_sys_ioctl+0x9d/0xe0
  gru 21 16:32:46 karol.home.prv kernel:  do_syscall_64+0x5c/0x90
  gru 21 16:32:46 karol.home.prv kernel:  ? do_syscall_64+0x69/0x90
  gru 21 16:32:46 karol.home.prv kernel:  ? exit_to_user_mode_prepare+0x3b/0xd0
  gru 21 16:32:46 karol.home.prv kernel:  ? syscall_exit_to_user_mode+0x2a/0x50
  ? do_syscall_64+0x69/0x90
  gru 21 16:32:46 karol.home.prv kernel:  
entry_SYSCALL_64_after_hwframe+0x72/0xdc
  gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f
  gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89 44 

[Kernel-packages] [Bug 2047511] [NEW] [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't change it

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu 22.04.3 LTS
Release: 22.04

Brightness of the screen is down to minimum and I can't change it.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 27 11:15:19 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904]
 NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107M [GeForce GT 645M] [17aa:3904]
InstallationDate: Installed on 2023-12-10 (16 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: LENOVO 20202
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2012
dmi.bios.release: 0.49
dmi.bios.vendor: LENOVO
dmi.bios.version: 71CN31WW(V1.10)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Z500
dmi.ec.firmware.release: 1.49
dmi.modalias: 
dmi:bvnLENOVO:bvr71CN31WW(V1.10):bd11/16/2012:br0.49:efr1.49:svnLENOVO:pn20202:pvrLenovoIdeaPadZ500:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500:skuLENOVO_MT_20202:
dmi.product.family: IDEAPAD
dmi.product.name: 20202
dmi.product.sku: LENOVO_MT_20202
dmi.product.version: Lenovo IdeaPad Z500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu
-- 
[Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't 
change it
https://bugs.launchpad.net/bugs/2047511
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.2 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 2047388] [NEW] System reboots automatically when lock screen screen enabled.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

System reboots automatically when lock screen screen enabled. The same
is tested on ubuntu-20.04 as well as ubuntu-22.04.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 26 11:42:52 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company CometLake-S GT2 [UHD Graphics 630] 
[103c:85a2]
InstallationDate: Installed on 2023-12-07 (19 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: HP HP  ProOne 400 G5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=3a72d508-3f06-4b45-a814-8d4bef8b43d0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2021
dmi.bios.release: 9.0
dmi.bios.vendor: HP
dmi.bios.version: R12 Ver. 02.09.00
dmi.board.name: 85A2
dmi.board.vendor: HP
dmi.board.version: KBC Version 08.98.00
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 8.152
dmi.modalias: 
dmi:bvnHP:bvrR12Ver.02.09.00:bd04/21/2021:br9.0:efr8.152:svnHP:pnHPProOne400G5:pvr:rvnHP:rn85A2:rvrKBCVersion08.98.00:cvnHP:ct13:cvr:sku6AE46AV:
dmi.product.family: 103C_53307F HP ProOne
dmi.product.name: HP  ProOne 400 G5
dmi.product.sku: 6AE46AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
System reboots automatically when lock screen screen enabled.
https://bugs.launchpad.net/bugs/2047388
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.2 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 2047154] [NEW] [drm] *ERROR* flip_done timed out

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out
gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[CRTC:84:crtc-0] commit wait timed out
gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
flip_done timed out
gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[CONNECTOR:119:HDMI-A-1] commit wait timed out
gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=2>
gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
flip_done timed out
gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[PLANE:67:plane-5] commit wait timed out
gru 21 16:32:46 karol.home.prv kernel: [ cut here ]
gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at 
/var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di>
gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i>
gru 21 16:32:46 karol.home.prv kernel:  reed_solomon pstore_zone efi_pstore 
sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp>
gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: P 
   W  OE  6.2.0-26-generic #26~22.04.1-Ubuntu
gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. To 
Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29>
gru 21 16:32:46 karol.home.prv kernel: RIP: 
0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu]
gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 
00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5>
gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 
00010002
gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 
00013195 RCX: 
gru 21 16:32:46 karol.home.prv kernel: RDX:  RSI: 
 RDI: 
gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: 
 R09: 
gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: 
 R12: 0246
gru 21 16:32:46 karol.home.prv kernel: R13:  R14: 
9710a5d8d118 R15: 9710a5d8d000
gru 21 16:32:46 karol.home.prv kernel: FS:  7f3267b4ea80() 
GS:97179eac() knlGS:
gru 21 16:32:46 karol.home.prv kernel: CS:  0010 DS:  ES:  CR0: 
80050033
gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 
000250f4e000 CR4: 003506e0
gru 21 16:32:46 karol.home.prv kernel: Call Trace:
gru 21 16:32:46 karol.home.prv kernel:  
gru 21 16:32:46 karol.home.prv kernel:  commit_tail+0xc5/0x1a0 [drm_kms_helper]
gru 21 16:32:46 karol.home.prv kernel:  ? 
drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper]
gru 21 16:32:46 karol.home.prv kernel:  drm_atomic_helper_commit+0x137/0x160 
[drm_kms_helper]
gru 21 16:32:46 karol.home.prv kernel:  drm_atomic_commit+0x99/0xd0 [drm]
gru 21 16:32:46 karol.home.prv kernel:  ? __pfx___drm_printfn_info+0x10/0x10 
[drm]
gru 21 16:32:46 karol.home.prv kernel:  
drm_mode_obj_set_property_ioctl+0x179/0x430 [drm]
gru 21 16:32:46 karol.home.prv kernel:  ? drm_mode_createblob_ioctl+0xff/0x130 
[drm]
gru 21 16:32:46 karol.home.prv kernel:  ? 
__pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
gru 21 16:32:46 karol.home.prv kernel:  drm_ioctl_kernel+0xc3/0x160 [drm]
gru 21 16:32:46 karol.home.prv kernel:  drm_ioctl+0x27b/0x4c0 [drm]
gru 21 16:32:46 karol.home.prv kernel:  ? 
__pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
gru 21 16:32:46 karol.home.prv kernel:  ? __pm_runtime_suspend+0x7b/0x110
gru 21 16:32:46 karol.home.prv kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
gru 21 16:32:46 karol.home.prv kernel:  __x64_sys_ioctl+0x9d/0xe0
gru 21 16:32:46 karol.home.prv kernel:  do_syscall_64+0x5c/0x90
gru 21 16:32:46 karol.home.prv kernel:  ? do_syscall_64+0x69/0x90
gru 21 16:32:46 karol.home.prv kernel:  ? exit_to_user_mode_prepare+0x3b/0xd0
gru 21 16:32:46 karol.home.prv kernel:  ? syscall_exit_to_user_mode+0x2a/0x50
? do_syscall_64+0x69/0x90
gru 21 16:32:46 karol.home.prv kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f
gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 
24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 2>
gru 21 16:32:46 karol.home.prv kernel: RSP: 002b:7ffedd454d30 EFLAGS: 
0246 ORIG_RAX: 0010
gru 21 16:32:46 karol.home.prv kernel: RAX: ffda RBX: 
7ffedd454dc0 RCX: 7f3267f1a75f
gru 21 16:32:46 karol.home.prv kernel: RDX: 7ffedd454dc0 RSI: 
c01864ba RDI: 000e
gru 21 16:32:46 karol.home.prv kernel: RBP: c01864ba R08: 
0084 R09: 
gru 21 16:32:46 

[Kernel-packages] [Bug 2038259] Re: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support

[Timo Aaltonen]

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

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

Title:
  Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing usb serial interface for FM101R-GL.

  [Fix]

  * commit 52480e1f1a25 ("USB: serial: option: add Fibocom to DELL custom modem 
FM101R-GL"): in v6.6-rc7
  * commit a1092619dd28 ("USB: serial: option: fix FM101R-GL defines"): in 
v6.7-rc3

  [Test Case]

  1. check lsusb & dmesg output
  ```
  $ lsusb
  Bus 004 Device 002: ID 413c:8215 Dell Computer Corp. Fibocom FM101-GL Module
  ...
  $ sudo dmesg
  [8.460678] usbcore: registered new interface driver usbserial_generic
  [8.460690] usbserial: USB Serial support registered for generic
  [8.549734] usbcore: registered new interface driver option
  [8.550108] usbserial: USB Serial support registered for GSM modem (1-port)
  [8.550266] option 4-4:1.2: GSM modem (1-port) converter detected
  [8.553584] usb 4-4: GSM modem (1-port) converter now attached to ttyUSB0
  [8.556445] usbcore: registered new interface driver cdc_ncm
  [8.601187] usbcore: registered new interface driver cdc_wdm
  [9.059744] cdc_mbim 4-4:1.0: setting rx_max = 16384
  [9.060079] cdc_mbim 4-4:1.0: cdc-wdm0: USB WDM device
  [9.060338] wwan wwan0: port wwan0mbim0 attached
  ```

  2. make sure ModemManager has probed it:
  ```
  $ mmcli -L
  /org/freedesktop/ModemManager1/Modem/0 [Fibocom Wireless Inc.] Fibocom 
FM101-GL Module
  ```

  [Where problems could occur]

  New hardware, still under development. Maybe we'll have to
  enable/patch for its vendor specific interface or so.

  [Other Info]

  The first patch is available for v6.6, and the second for v6.7. While
  we're enabling it on linux-oem-6.5/jammy, nominate for linux/noble,
  which is currently on v6.6, and linux-oem-6.5.

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


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

[Kernel-packages] [Bug 2043964] Re: New China SRRC compliance readiness check for Realtek WLAN

[Timo Aaltonen]

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

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

Title:
  New China SRRC compliance readiness check for Realtek WLAN

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

Bug description:
  [SRU Justification]

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

  [Impact]

  SRRC (State Radio Regulation of China)  compliance readiness check for
  Realtek WLAN.

  [Fix]

  Capability for Realtek WiFi TX power tables load and report from RFE
  (RF front end) parameters is needed. Multiple commits from vanilla
  kernel.

  [Test Case]

  ```
  $ sudo iw reg set CN
  # manually connect to 5G ap : center channel 155 bw 80 M
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/rtw89/txpwr_table | grep -E 
'MCS_2TX_80M_0|Regulatory' 
  ```
  The expected output s
  ```
  Regulatory: CN
  MCS_2TX_80M_0 - NON_BF BF | 10, 9, dbm
  ```
  And verification fail output:
  ```
  Regulatory: CN
  MCS_2TX_80M_0 - NON_BF BF | 15, 10, dbm
  ```

  [Where problems could occur]

  This updates the behaviors and constraints of radio device power
  transmission for rtw89 driver, and must be done for regulatory
  compliance.

  [Other Info]

  As needed for oem-6.5/jammy, nominate only for Noble and
  oem-6.5/jammy.

  == original bug report ==

  New China SRRC compliance readiness check

  Proposed Change:
   - China SRRC updates the testing requirement for 2.4/5GHz, the major changes 
are the in-band RSE limit, and EIRP limits.

   - The SRRC updates impact both WLAN modules and platforms. The WLAN
  modules need to complete the new SRRC testing then platform can start
  to apply / renew the new SRRC cert. If platform took several WLAN
  modules but not all of the modules have completed the new SRRC testing
  updates, platform cannot renew/apply the new SRRC cert.

   - The platforms which apply/renew SRRC new standards need to ensure
  the TX power can meet the new RSE/EIRP limits.

  IHV confirmed below driver version can support these requirements.

  Realtek:
  The upstream driver can support SRRC compliance.
  
https://lore.kernel.org/linux-wireless/20230927072156.26336-1-pks...@realtek.com/T/#m4d8acb2697ff2bc07485a6119839e1f96a822340
 [lore.kernel.org]

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


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

[Kernel-packages] [Bug 2046802] Re: External display stay blank when connected through the docking station (HP USB-C Dock G5) but is OK when directly connected

[Daniel van Vugt]

Indeed the kernel seems to be crashing in drm graphics code so I'd
recommend trying some newer kernels such as
https://kernel.ubuntu.com/mainline/?C=M;O=D

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

** Tags added: amdgpu dock multimonitor

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

Title:
  External display stay blank when connected through the docking station
  (HP USB-C Dock G5) but is OK when directly connected

Status in linux package in Ubuntu:
  New

Bug description:
  External display is detected and X believes it is OK as the desktop
  correctly extends to the 2nd monitor but said monitor remains blank.
  It used to work a couple of days ago but I guess some upgrade is the
  cause. I tried to downgrade amd64-microcode and linux-firmware, to no
  avail : dmesg still shows issues with drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Dec 18 12:14:54 2023
  DistUpgraded: 2023-12-18 10:58:52,052 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Barcelo [103c:8b5c]
  InstallationDate: Installed on 2023-08-08 (132 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=d29d3432-7c6f-4376-a050-c86365d7b922 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-12-18 (0 days ago)
  dmi.bios.date: 04/25/2023
  dmi.bios.release: 2.1
  dmi.bios.vendor: HP
  dmi.bios.version: V78 Ver. 01.02.01
  dmi.board.name: 8B5C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 53.1D.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 83.29
  dmi.modalias: 
dmi:bvnHP:bvrV78Ver.01.02.01:bd04/25/2023:br2.1:efr83.29:svnHP:pnHPProBook44514inchG10NotebookPC:pvr:rvnHP:rn8B5C:rvrKBCVersion53.1D.00:cvnHP:ct10:cvr:sku852U8ES#UUZ:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 445 14 inch G10 Notebook PC
  dmi.product.sku: 852U8ES#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
  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/2046802/+subscriptions


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

[Kernel-packages] [Bug 2046802] [NEW] External display stay blank when connected through the docking station (HP USB-C Dock G5) but is OK when directly connected

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

External display is detected and X believes it is OK as the desktop
correctly extends to the 2nd monitor but said monitor remains blank. It
used to work a couple of days ago but I guess some upgrade is the cause.
I tried to downgrade amd64-microcode and linux-firmware, to no avail :
dmesg still shows issues with drivers.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 18 12:14:54 2023
DistUpgraded: 2023-12-18 10:58:52,052 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c5) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Barcelo [103c:8b5c]
InstallationDate: Installed on 2023-08-08 (132 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=d29d3432-7c6f-4376-a050-c86365d7b922 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-18 (0 days ago)
dmi.bios.date: 04/25/2023
dmi.bios.release: 2.1
dmi.bios.vendor: HP
dmi.bios.version: V78 Ver. 01.02.01
dmi.board.name: 8B5C
dmi.board.vendor: HP
dmi.board.version: KBC Version 53.1D.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 83.29
dmi.modalias: 
dmi:bvnHP:bvrV78Ver.01.02.01:bd04/25/2023:br2.1:efr83.29:svnHP:pnHPProBook44514inchG10NotebookPC:pvr:rvnHP:rn8B5C:rvrKBCVersion53.1D.00:cvnHP:ct10:cvr:sku852U8ES#UUZ:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 445 14 inch G10 Notebook PC
dmi.product.sku: 852U8ES#UUZ
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu
-- 
External display stay blank when connected through the docking station (HP 
USB-C Dock G5) but is OK when directly connected
https://bugs.launchpad.net/bugs/2046802
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 1970672] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for makedumpfile has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.7-1ubuntu2.5

---
makedumpfile (1:1.6.7-1ubuntu2.5) focal; urgency=medium

  * makedumpfile falls back to cp with 5.12 kernel (LP: #1970672)
- can also fail with __vtop4_x86_64: Can't get a valid pmd_pte.
- d/p/lp1970672-PATCH-Increase-SECTION_MAP_LAST_BIT-to-5.patch

 -- Heather Lemon   Tue, 21 Nov 2023
15:19:22 +

** Changed in: makedumpfile (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

[Chris Halse Rogers]

Ok. My understanding of this is that when (3) fails it fails for the
same reason that (2) would. We've verified that making a dumpfile works
in general, and definitely fixed (3), so I'm going to release this now.

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

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Released

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

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


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

[Kernel-packages] [Bug 2047492] Re: Dell Precision 5680 audio is not working

[Chris Chiu]

It's a Dell 0C11 SKU with  link_mask 0x7.
All patches for 0C11 are found on mantic base
1. ASoC: Intel: soc-acpi-intel-rpl-match: add rt711-l0-rt1316-l12 support
2. ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product
3. ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product
4. ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration

I can't reproduce the same with the kernel built on top of
mantic/master-next.

It shows `[5.074670] sof-audio-pci-intel-tgl :00:1f.3: SoundWire
machine driver sof_sdw topology sof-rpl-rt711-l0-rt1316-l12.tplg` with
the test kernel.

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

Title:
  Dell Precision 5680 audio is not working

Status in linux package in Ubuntu:
  New

Bug description:
  Can't find machine driver for the platform.

  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: use msi interrupt mode
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: No SoundWire machine driver found
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: hda codecs found, mask 4
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: DMICs detected in NHLT tables: 0
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: Firmware info: version 2:2:0-57864
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: unknown sof_ext_man header type 3 size 0x30
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: Firmware info: version 2:2:0-57864
  Dec 26 17:31:51 ubuntu-Precision-5680 kernel: sof-audio-pci-intel-tgl 
:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2112 F wireplumber
   /dev/snd/controlC0:  ubuntu 2112 F wireplumber
   /dev/snd/seq:ubuntu 2108 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-12-26 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=aa5c8910-576d-4f2e-b5a8-0bb2bce922e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  Tags: mantic
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/12/2023
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.asset.tag: SUBPASS
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd09/12/2023:br1.6:efr1.6:svnDellInc.:pnPrecision5680:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C11:
  dmi.product.family: Precision
  dmi.product.name: Precision 5680
  dmi.product.sku: 0C11
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2046553] Re: i am unable to pair and connect bluetooth

[Daniel van Vugt]

Please check that you have Bluetooth enabled because this shows it is
disabled in software:

2: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no

Also is this a new problem since the last software update?


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

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

Title:
  i am unable to pair and connect bluetooth

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install fwupd
  sudo fwupdmgr update
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  fwupd is already the newest version (1.7.9-1~22.04.3).
  fwupd set to manually installed.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Devices with no available firmware updates


  i have configered also but no problem found
  Type: Primary  Bus: USB
BD Address: 34:41:5D:32:F1:53  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:19216 acl:0 sco:0 events:2629 errors:0
TX bytes:603774 acl:0 sco:0 commands:2570 errors:0

  please fix this

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 18:29:38 2023
  InstallationDate: Installed on 2023-08-31 (106 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ca Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless 
rechargeable vertical mouse [More]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=3e546dec-b6ab-4cff-9ae6-19d09ccec9e4 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/06/2023:br1.33:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.
  hciconfig:

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


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

[Kernel-packages] [Bug 2046485] Re: [HP Pavilion dv6] Screen is too bright

[Daniel van Vugt]

Does "screen is too bright" mean the backlight brightness can't be
adjusted?

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

Title:
  [HP Pavilion dv6] Screen is too bright

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  when i try this command

  sudo apt-get install xserver-xorg-video-intel

  i get this

  xserver-xorg-video-intel is already the newest version
  (2:2.99.917+git20210115-1).

  
  i have intel 3000 hd graphics built-in in my laptop.

  but my screen is too bright and i am getting 3rd class video quality
  in youtube in browser, i checked videos in 720p, 1080p, but same
  issue.

  when i check some videos in my laptop, that are in good quality
  downloaded from internet. issue is same.

  i have no issue in windows 7, 10.

  but only i have issue is in Linux mint, and Lubuntu

  Lubuntu 22.04 LTS

  Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  CasperVersion: 1.470.2
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Dec 14 23:55:58 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1658]
  LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: fsck.mode=skip noprompt boot=casper 
floppy.allowed_drive_mask=0 ignore_uuid --
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2011
  dmi.bios.release: 15.27
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1658
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 16.49
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:br15.27:efr16.49:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3X35UA#ABA:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.sku: A3X35UA#ABA
  dmi.product.version: 058C11244720001620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2046553] Re: i am unable to pair and connect bluetooth

[Daniel van Vugt]

** Summary changed:

- i am unable to pair and connect blutoothsudo apt-get install fwupd 
sudo fwupdmgr update Reading package lists... Done Building dependency tree... 
Done Reading state information... Done fwupd is already the newest version 
(1.7.9-1~22.04.3). fwupd set to manually installed. 0 upgraded, 0 newly 
installed, 0 to remove and 0 not upgraded. Devices with no available firmware 
updates  ** i have done this no updatws found but i am unable to 
connect bt devices such as earbud
+ i am unable to pair and connect bluetooth

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

Title:
  i am unable to pair and connect bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  sudo apt-get install fwupd
  sudo fwupdmgr update
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  fwupd is already the newest version (1.7.9-1~22.04.3).
  fwupd set to manually installed.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Devices with no available firmware updates


  i have configered also but no problem found
  Type: Primary  Bus: USB
BD Address: 34:41:5D:32:F1:53  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:19216 acl:0 sco:0 events:2629 errors:0
TX bytes:603774 acl:0 sco:0 commands:2570 errors:0

  please fix this

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 18:29:38 2023
  InstallationDate: Installed on 2023-08-31 (106 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ca Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless 
rechargeable vertical mouse [More]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=3e546dec-b6ab-4cff-9ae6-19d09ccec9e4 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/06/2023:br1.33:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.
  hciconfig:

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


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

[Kernel-packages] [Bug 2046224] Re: Resolutions lower than max results in corrupted screen

[Daniel van Vugt]

On laptop screens, non-max resolutions are faked. They should work
obviously, but it's up to the display server and kernel driver to fake
it properly.

Do you experience the same issue in a Wayland session?

** Tags added: amdgpu

** Summary changed:

- Resolutions lower than max results in corrupted screen
+ [amdgpu] Resolutions lower than max results in corrupted screen

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  [amdgpu] Resolutions lower than max results in corrupted screen

Status in linux package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Upgrading from 23.04 to 23.10 resulted in corrupt screen when
  switching to lower resolutions. Only maximum resolution works.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Tue Dec 12 01:21:01 2023
  DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Phoenix [17aa:3c92]
  InstallationDate: Installed on 2023-11-04 (38 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash 
amd_pstate=guided vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
  dmi.bios.date: 06/16/2023
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M3CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Slim 5 16APH8
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
  dmi.product.family: Legion Slim 5 16APH8
  dmi.product.name: 82Y9
  dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
  dmi.product.version: Legion Slim 5 16APH8
  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.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2046485] [NEW] [HP Pavilion dv6] Screen is too bright

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

when i try this command

sudo apt-get install xserver-xorg-video-intel

i get this

xserver-xorg-video-intel is already the newest version
(2:2.99.917+git20210115-1).


i have intel 3000 hd graphics built-in in my laptop.

but my screen is too bright and i am getting 3rd class video quality in
youtube in browser, i checked videos in 720p, 1080p, but same issue.

when i check some videos in my laptop, that are in good quality
downloaded from internet. issue is same.

i have no issue in windows 7, 10.

but only i have issue is in Linux mint, and Lubuntu

Lubuntu 22.04 LTS

Lubuntu 22.04.3 LTS JAMMY JELLYFISH RELEASE AMD 20230807

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
 {
   "result": "skip"
 }
CasperVersion: 1.470.2
CompositorRunning: None
CurrentDesktop: LXQt
Date: Thu Dec 14 23:55:58 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1658]
LiveMediaBuild: Lubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcKernelCmdLine: fsck.mode=skip noprompt boot=casper 
floppy.allowed_drive_mask=0 ignore_uuid --
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2011
dmi.bios.release: 15.27
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1658
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 16.49
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:br15.27:efr16.49:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3X35UA#ABA:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.sku: A3X35UA#ABA
dmi.product.version: 058C11244720001620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu
-- 
[HP Pavilion dv6] Screen is too bright
https://bugs.launchpad.net/bugs/2046485
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 2046217] Re: Some machines can't pass the pm-graph test

[Kai-Heng Feng]

Issue on 201711-25989 is also different. There's a timeout between
Docker and Checkbox. The system is well and alive.

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

Title:
  Some machines can't pass the pm-graph test

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.5 source package in Jammy:
  New
Status in linux-signed-hwe-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux-hwe-6.5 source package in Mantic:
  New
Status in linux-signed-hwe-6.5 source package in Mantic:
  New
Status in linux source package in Noble:
  Confirmed
Status in linux-hwe-6.5 source package in Noble:
  New
Status in linux-signed-hwe-6.5 source package in Noble:
  In Progress

Bug description:
  == SRU Justification ==
  [Impact]
  When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system
  resume, NULL pointer dereference occurs and the system stops working.

  [Fix]
  Rescan the bus in order to reprobe the device to avoid mac80211 layer
  gets messed up.

  [Test]
  With the fix in place, system keeps working after firmware issue occurs.
  Verified with thousand times of suspend.

  [Where problems could occur]
  If the firmware/hardware is really dead and beyond recoverable, the same
  process can be triggered again and again.

  == Original bug report ==
  During the jammy-hwe migration test, I found some machines failed to run the 
pm-graph. 
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)

  One of machine when I rerun it locally, it passed, but others are
  still failed.

  Following are the machines failed to run pm-graph.
  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201702-25401/
  https://certification.canonical.com/hardware/202002-27718/
  https://certification.canonical.com/hardware/201711-25989/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Tue Dec 12 02:48:24 2023
  InstallationDate: Installed on 2023-02-22 (293 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2046217] Re: Some machines can't pass the pm-graph test

[Kai-Heng Feng]

Issue on 201702-25401 is different. Quite likely caused by faulty CPU
fan and faulty memory.

** Description changed:

- During the jammy-hwe migration test, I found some machines failed to run
- the pm-graph.
- 
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)
+ == SRU Justification ==
+ [Impact]
+ When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system
+ resume, NULL pointer dereference occurs and the system stops working.
+ 
+ [Fix]
+ Rescan the bus in order to reprobe the device to avoid mac80211 layer
+ gets messed up.
+ 
+ [Test]
+ With the fix in place, system keeps working after firmware issue occurs.
+ Verified with thousand times of suspend.
+ 
+ [Where problems could occur]
+ If the firmware/hardware is really dead and beyond recoverable, the same
+ process can be triggered again and again.
+ 
+ == Original bug report ==
+ During the jammy-hwe migration test, I found some machines failed to run the 
pm-graph. 
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)
  
  One of machine when I rerun it locally, it passed, but others are still
  failed.
  
  Following are the machines failed to run pm-graph.
  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201702-25401/
  https://certification.canonical.com/hardware/202002-27718/
  https://certification.canonical.com/hardware/201711-25989/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Tue Dec 12 02:48:24 2023
  InstallationDate: Installed on 2023-02-22 (293 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: linux-signed-hwe-6.5 (Ubuntu)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

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

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

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

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

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

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

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

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

** Also affects: linux-signed-hwe-6.5 (Ubuntu Noble)
   Importance: Medium
   Status: In Progress

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

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

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

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

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

Title:
  Some machines can't pass the pm-graph test

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.5 source package in Jammy:
  New
Status in linux-signed-hwe-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Confirmed
Status in linux-hwe-6.5 source package in Mantic:
  New
Status in linux-signed-hwe-6.5 source package in Mantic:
  New
Status in linux source package in Noble:
  Confirmed
Status in linux-hwe-6.5 source package in Noble:
  New
Status in linux-signed-hwe-6.5 source package in Noble:
  In Progress

Bug description:
  == SRU Justification ==
  [Impact]
  When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system
  resume, NULL pointer dereference occurs and the system stops working.

  [Fix]
  Rescan the bus in order to reprobe the device to avoid mac80211 layer
  gets messed up.

  [Test]
  With the fix in place, system keeps working after firmware issue occurs.
  Verified with thousand times of 

[Kernel-packages] [Bug 2046345] Re: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation s

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to
  install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic
  package post-installation script subprocess returned error exit status
  1

Status in linux-restricted-modules package in Ubuntu:
  Confirmed

Bug description:
  Occurs when upgrading to an unreleased version
  Setting up linux-modules-nvidia-535-6.5.0-9-generic (6.5.0-9.9) ...
  linux-image-nvidia-6.5.0-9-generic: constructing .ko files
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-peermem.ko: OK
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  dpkg: error processing package linux-modules-nvidia-535-6.5.0-9-generic 
(--configure):
   installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation 
script subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-535-generic-hwe-22.04:
   linux-modules-nvidia-535-generic-hwe-22.04 depends on 
linux-modules-nvidia-535-6.5.0-9-generic (= 6.5.0-9.9); however:
Package linux-modules-nvidia-535-6.5.0-9-generic is not configured yet.

  dpkg: error processing package linux-modules-nvidia-535-generic-hwe-22.04 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-530-generic-hwe-22.04:
   linux-modules-nvidia-530-generic-hwe-22.04 depends on 
linux-modules-nvidia-535-generic-hwe-22.04; however:
Package linux-modules-nvidia-535-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-modules-nvidia-530-generic-hwe-22.04 
(--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   linux-modules-nvidia-535-6.5.0-9-generic
   linux-modules-nvidia-535-generic-hwe-22.04
   linux-modules-nvidia-530-generic-hwe-22.04

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Dec 13 14:36:34 2023
  ErrorMessage: installed linux-modules-nvidia-535-6.5.0-9-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-17 (299 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonDetails: /usr/bin/python3.11, Python 3.11.7, python-is-python3, 3.11.4-1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.1ubuntu3
   apt  2.7.6
  SourcePackage: linux-restricted-modules
  Title: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to 
install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to noble on 2023-12-13 (0 days ago)
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


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

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

[Andy Gospodarek]

** Summary changed:

- Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)
+ Add Support for Broadcom 5760X Network Controllers

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

Title:
  Add Support for Broadcom 5760X Network Controllers

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

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

  Prerequisite commits in net-next today:

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2046074] Re: The monitor screen appears black when connecting the PC through the sound bar to the monitor

[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/2046074

Title:
  The monitor screen appears black when connecting the PC through the
  sound bar to the monitor

Status in linux package in Ubuntu:
  New

Bug description:
  When I connect the laptop to the sound bar hdmi and the sound bar to
  the monitor, it tries to connect and Ubuntu detects it, but nothing
  appears on the screen.

  My HDMI works as it should, tested directly when it's connected to the
  monitor. I have tried on a laptop other than my computer with Windows
  to test if it is something of the sound bar and it works perfectly
  without problems.

  Don't really know what package should be interfering here. Mesa?
  Mutter?

  
  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  OS: Ubuntu 23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  Uname: Linux 6.6.5-060605-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 10 17:39:27 2023
  InstallationDate: Installed on 2023-10-13 (58 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled

[Kai-Heng Feng]

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

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

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

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when hardware rotation is used.

  [Test]
  With the patch applied, the issue can't be observed when the screen is 
rotated 180 degree.
  90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

  [Where problems could occur]
  The power consumption in theory will higher for 180 degree rotation because 
now the full screen may need to be redrawn when cursor moves.

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


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

[Kernel-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device

[Steve Langasek]

** Tags added: regression-security

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

Title:
  bluetooth device connected but not recognised as output device

Status in bluez package in Ubuntu:
  New

Bug description:
  bluetooth device connected but not recognised as output device

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 15:28:00 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 81EK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2018
  dmi.bios.release: 1.28
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7QCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 530-14IKB
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB:
  dmi.product.family: YOGA 530-14IKB
  dmi.product.name: 81EK
  dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB
  dmi.product.version: Lenovo YOGA 530-14IKB
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 0C:54:15:91:FA:4F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:83770 acl:295 sco:0 events:4208 errors:0
TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0

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


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

[Kernel-packages] [Bug 2047137] Re: nvidia 390 driver from ppa segfault

[Mikhail Belkin]

"stick to Ubuntu 22.04"
Almost, Debian 12.

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

Title:
  nvidia 390 driver from ppa segfault

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

Bug description:
  I tried to build and install package form binaries, 
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
  Now, I am writing this bug report with nouveau, because I commented blacklist 
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
  But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were 
working). On 23.04/23.10 it crashes.

  There is an error in xorg log, it runs wrong mode, and writes:

  [34.950] (II) NVIDIA(0): Validated MetaModes:
  [34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
  [34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
  [34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi" 
X config
  [34.956] (--) NVIDIA(0): option
  [34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect 
memory
  [34.957] (II) NVIDIA: access.
  [34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event 
daemon; the daemon
  ...
  [35.115] (II) Initializing extension DRI2
  [35.115] (II) Initializing extension GLX
  [35.115] (II) Initializing extension GLX
  [35.115] (II) Indirect GLX disabled.

  Then, in lightdm log an error with segfault appears:

  malloc(): unaligned tcache chunk detected

  I tried different configs of xorg, so I made a conclusion that nvidia drivers 
are built wrong again.
  My /etc/X11/xorg.conf.d/10-nvidia.conf:

  Section "Files"
   ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
   ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
   ModulePath "/usr/lib/x86_64-linux-gnu/"
   ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
   ModulePath "/usr/lib/xorg/modules/extensions"
   ModulePath "/usr/lib/xorg/modules/drivers"
   ModulePath "/usr/lib/xorg/modules/input"
   ModulePath "/usr/lib/xorg/modules"
  EndSection

  Section "OutputClass"
  Identifier "nvidia"
  MatchDriver "nvidia-drm"
  Driver "nvidia"
  Option "AllowEmptyInitialConfiguration"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Dec 21 16:55:06 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/390.157, 6.5.0-14-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
  InstallationDate: Installed on 2023-12-16 (5 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=ru_RU.UTF-8
   LANGUAGE=ru_RU
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2010
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.name: IC780M-A2
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
  dmi.product.name: IC780M-A2
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
  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/nvidia-graphics-drivers-390/+bug/2047137/+subscriptions


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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Started the work to merge crash 8.0.4 in bug 2047861.

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  In Progress
Status in crash source package in Jammy:
  Incomplete
Status in crash source package in Lunar:
  Incomplete
Status in crash source package in Mantic:
  Incomplete

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
  

[Kernel-packages] [Bug 2047861] Re: Merge crash 8.0.4-1 into Noble

[Mauricio Faria de Oliveira]

Merge is in git branch
https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+ref/merge-lp2047861-noble

Building/testing from PPA
https://launchpad.net/~mfo/+archive/ubuntu/lp2047861-noble-crash

Still in progress.

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

Title:
   Merge crash 8.0.4-1 into Noble

Status in crash package in Ubuntu:
  In Progress

Bug description:
  $ rmadison -a source crash | grep noble
   crash | 8.0.3+ds1-3ubuntu1 | noble  | source

  $ rmadison -a source -u debian -s unstable crash
  crash  | 8.0.4-1   | unstable   | source

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


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

[Kernel-packages] [Bug 2047861] Re: Merge crash 8.0.4-1 into Noble

[Mauricio Faria de Oliveira]

Work in progress.

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

Title:
   Merge crash 8.0.4-1 into Noble

Status in crash package in Ubuntu:
  In Progress

Bug description:
  $ rmadison -a source crash | grep noble
   crash | 8.0.3+ds1-3ubuntu1 | noble  | source

  $ rmadison -a source -u debian -s unstable crash
  crash  | 8.0.4-1   | unstable   | source

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


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

[Kernel-packages] [Bug 2047861] [NEW] Merge crash 8.0.4-1 into Noble

[Mauricio Faria de Oliveira]

Public bug reported:

$ rmadison -a source crash | grep noble
 crash | 8.0.3+ds1-3ubuntu1 | noble  | source

$ rmadison -a source -u debian -s unstable crash
crash  | 8.0.4-1   | unstable   | source

** Affects: crash (Ubuntu)
 Importance: Medium
 Assignee: Mauricio Faria de Oliveira (mfo)
 Status: In Progress

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

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

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

Title:
   Merge crash 8.0.4-1 into Noble

Status in crash package in Ubuntu:
  In Progress

Bug description:
  $ rmadison -a source crash | grep noble
   crash | 8.0.3+ds1-3ubuntu1 | noble  | source

  $ rmadison -a source -u debian -s unstable crash
  crash  | 8.0.4-1   | unstable   | source

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


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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

Hi Chengen!

Thank you very much for the detailed test plan! It's really good.

Apologies for the extended delay in getting back to your changes.

There are some points to address in the debdiffs. In order of
importance:

1) The debdiff for Lunar and Jammy (equivalent) are for kernel 6.2, but
Jammy now has the 6.5 HWE kernel [1] too.

I suspect that the users/original reporter that looked for HWE kernel
support back at 6.2 would likely switch to 6.5 too, so it would be
beneficial and time saving to incorporate the 6.5 patches now, since you
already have them in the Mantic debdiff [2]. What do you think?

2) There are 12 patches from crash 8.0.4 [3] in the Mantic debdiff, but
these are not yet in Ubuntu (not even in Noble, the development
release), which has 8.0.3.

I will provide another Merge from Debian to crash, since upstream has now 
released 8.0.4 and Debian pulled it in. 
But for the future it's important to keep this in mind, as it may save the time 
of a review round trip, and more debdiff/build/test work.

3) The version numbers are incorrect for stable releases.

Please see [4].

In general, you should increment by 'ubuntu0.1' in stable releases (and
'ubuntu1' in the development release), and if multiple stable releases
have the same package version, increment by 'ubuntu0.YY.MM.1' to
differentiate among them.

i.e.,

$ rmadison -a source crash
...
 crash | 8.0.0-1ubuntu1 | jammy  | source
 crash | 8.0.0-1ubuntu1 | lunar  | source
 crash | 8.0.2-1ubuntu1 | mantic | source
 crash | 8.0.3+ds1-3ubuntu1 | noble  | source

debdiffs:

$ grep -o '.crash (.*)' *.debdiff
lp2038249-crash-jammy.debdiff:+crash (8.0.0-1ubuntu2)
lp2038249-crash-jammy.debdiff: crash (8.0.0-1ubuntu1)
lp2038249-crash-lunar.debdiff:+crash (8.0.0-1ubuntu2)
lp2038249-crash-lunar.debdiff: crash (8.0.0-1ubuntu1)
lp2038249-crash-mantic.debdiff:+crash (8.0.2-1ubuntu2)
lp2038249-crash-mantic.debdiff: crash (8.0.2-1ubuntu1)

per [4]:

jammy: 8.0.0-1ubuntu1.22.04.1
lunar: 8.0.0-1ubuntu1.23.04.1
mantic: 8.0.2-1ubuntu1.1

4) The changes to 'debian/Makefile.ori' are not listed or explained
in the changelog.

If this is unintended (i.e., post-build noise in debian/, it should
be removed), but if it's intended/required, then it should be listed
and slightly documented, please.

5) The itemization in changelog is a bit weird.

This is a style/cosmetic suggestion, not a requirement, but in practice,
when you have multiple patches, the first item is the description with
the LP bug number, and the sub items are the patches; e.g.,

  +  * Fix the dump file parsing issue arises from structural changes in Linux
  +kernel 6.5 (LP: #2038249)
  +- d/p/lp2038249-arm64-handle-vabits_actual-symbol-missing-case.patch
  +- 
d/p/lp2038249-x86_64-Fix-for-move-of-per-cpu-variables-into-struct.patch
  +- ... more patches

6) The patches are not numbered

Again, a style/cosmetic suggestion; but it does help with parsing/organization
over time for longer patch series like this one.

You can use 'quilt rename' and a shell loop to easily adjust this, of course.
Please let me know if you would like some help (I don't think so, but just in 
case!).

7) Special thanks for paying attention to 'upstream/backport' keyword in
the 'Origin:' DEP-3 header!

$ grep -ho 'Origin: [^ ]*' *.debdiff | sort | uniq -c
 12 Origin: backport,
 66 Origin: upstream,

...

So, for now, if you have a chance, please feel free to adjust the debdiffs,
and I'll work on merging 8.0.4 in Noble, to unblock the needed 12 patches.

Thanks again,
Mauricio

[1] https://launchpad.net/ubuntu/+source/linux-hwe-6.5

[2]

$ diff -U0 \
  <(filterdiff --remove-timestamps lp2038249-crash-mantic.debdiff -i 
'*/debian/changelog') \
  <(filterdiff --remove-timestamps lp2038249-crash-lunar.debdiff -i 
'*/debian/changelog')
...
@@ -18,7 +29,0 @@
-+
d/p/lp2038249-Fix-kmem-n-option-to-display-memory-blocks-on-Linux-.patch
-+
d/p/lp2038249-Fix-failure-of-dev-d-D-options-on-Linux-6.4-and-late.patch
-+
d/p/lp2038249-Fix-kmem-v-option-displaying-no-regions-on-Linux-6.3.patch
-+
d/p/lp2038249-x86_64-Fix-bt-command-printing-stale-entries-on-Linu.patch
-+
d/p/lp2038249-Support-module-memory-layout-change-on-Linux-6.4.patch
-+
d/p/lp2038249-Fix-failure-of-gathering-task-table-on-Linux-6.5-rc1.patch
-+
d/p/lp2038249-Fix-compilation-error-due-to-new-strlcpy-function-th.patch
@@ -26,2 +30,0 @@
-+
d/p/lp2038249-Exclude-zero-entries-from-do_maple_tree-return-value.patch
-+d/p/lp2038249-Fix-irq-a-s-options-on-Linux-6.5-rc1-and-later.patch
@@ -32 +35 @@
-+kernel 6.5 (LP: #2038249)
++kernel 6.2 (LP: #2038249)
...

[3]

$ grep 'Origin: ' 

[Kernel-packages] [Bug 2047853] [NEW] mlxbf_gige: replace SAUCE patch for RX race condition

[David Thompson]

Public bug reported:

SRU Justification:

[Impact]

There is a SAUCE patch that addresses a mlxbf-gige RX race condition
   "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
This SAUCE patch should be reverted and replaced with upstream content.

[Fix]

Bring in the following upstream commit from linux-next:
  "mlxbf_gige: fix receive packet race condition"

[Test Case]

Boot BF3 platform and ensure oob_net0 interface is up and has IP address
Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls occur

[Regression Potential]

Low risk change, cherry pick of upstream approved commit

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

Title:
  mlxbf_gige: replace SAUCE patch for RX race condition

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  There is a SAUCE patch that addresses a mlxbf-gige RX race condition
 "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
  This SAUCE patch should be reverted and replaced with upstream content.

  [Fix]

  Bring in the following upstream commit from linux-next:
"mlxbf_gige: fix receive packet race condition"

  [Test Case]

  Boot BF3 platform and ensure oob_net0 interface is up and has IP address
  Send heavy level of traffic into the BF3 oob_net0 and make sure no stalls 
occur

  [Regression Potential]

  Low risk change, cherry pick of upstream approved commit

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


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

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

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  HP ProBook 450 G8 Notebook fail to wifi test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-signed-hwe-5.15 source package in Jammy:
  Invalid

Bug description:
  I'm reviewing the SRU test result on this machine.
  I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

  It's not a regression, since according to previous test run it has failed 
already.
  Just because we missed reviewing it for a while.

  The journal log is attach, please check further hardware informations
  at https://certification.canonical.com/hardware/202106-29176/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 27 15:47:37 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
  InstallationDate: Installed on 2023-09-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220621-04:14
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

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

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


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

[Kernel-packages] [Bug 2035123] Re: scripts/pahole-flags.sh change return to exit 0

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  scripts/pahole-flags.sh change return to exit 0

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

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

  [Impact]

  When building the Jammy linux-bluefield kernel tree on a system
  without pahole installed, the following warning is emitted:

  ./scripts/pahole-flags.sh: line 7: return: can only `return' from a
  function or sourced script

  scripts/pahole-flags.sh attempts to return from an if statement that
  is not within a function, and generates a warning.

  The fix is straightforward, changing return to an exit 0.

  --- a/scripts/pahole-flags.sh
  +++ b/scripts/pahole-flags.sh
  @@ -4,7 +4,7 @@
   extra_paholeopt=

   if ! [ -x "$(command -v ${PAHOLE})" ]; then
  -   return
  +   exit 0
   fi

  [Testcase]

  Clone the linux-bluefield kernel tree and build it on a arm64 system without
  pahole installed.

  A test kernel is available with the fix applied in:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test

  Both linux-bluefield and ubuntu-jammy build correctly.

  [Fix]

  This was fixed by Linus Torvalds in the following merge commit:

  commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
  Merge: bfc484fe6abb 84882cf72cd7
  Author: Linus Torvalds 
  Date:   Tue Nov 2 06:20:58 2021 -0700
  Subject: Merge tag 'net-next-for-5.16' of 
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4

  Note, the original commit does not have the fix included:

  commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
  Author: Jiri Olsa 
  Date:   Fri Oct 29 14:57:29 2021 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8

  The Ubuntu kernel cherry-picked the original commit and did not pick up the
  silent fix made in the merge commit. Submitting the silent fix as a SAUCE 
patch
  with changelog describing the change.

  Note: I know SAUCE patches are bad, but in this scenario, to revert
  the initial commit and re-apply the fixed version would require us to
  revert two additional dependency commits, making six patches to
  review, vs, a one line change in a SAUCE commit that has a real
  changelog entry.

  [Where problems could occur]

  The Ubuntu kernel is built with pahole enabled, and requires pahole to
  be installed as a build dependency. It is extremely unlikely that any
  users are disabling pahole at build time, apart from linux-bluefield
  engineers.

  If a regression were to occur, engineers would see errors during build
  time about scripts/pahole-flags.sh not executing properly.

  [Other info]

  Linus remarked about the issue in the following lkml discussion:

  
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
  
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/

  This was silently Incorporated into the linux-stable commit:

  commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
  From: Jiri Olsa 
  Date: Sun, 4 Sep 2022 15:19:00 +0200
  Subject: kbuild: Unify options for BTF generation for vmlinux and modules
  Link: 
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7

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


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

[Kernel-packages] [Bug 2042935] Re: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1

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

Bug description:
  Apply pull requests from NVIDIA received on 2023-11-02.
  
  Ankur Pawar (1):
    NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234

  Fabrice Gasnier (1):
    usb: typec: ucsi: don't print PPM init deferred errors

  Gautham Srinivasan (1):
    NVIDIA: SAUCE: arm64: configs: enable NTFS fs

  Jim Lin (1):
    NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control

  Jon Hunter (1):
    NVIDIA: SAUCE: Remove support for summation channel control

  Ninad Malwade (1):
    NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable

  Revanth Kumar Uppala (1):
    NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver

  Ulf Hansson (1):
    mmc: sdhci-tegra: Add runtime PM and OPP support
  

  Apply pull requests from NVIDIA received on 2023-11-13
  
  Gautham Srinivasan (1):
    NVIDIA: SAUCE: arm64: configs: disable LOGO

  Laxman Dewangan (1):
    NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY

  Narayan Reddy (1):
    NVIDIA: SAUCE: aquantia: issue PHY reset during phy init

  Sandipan Patra (1):
    NVIDIA: SAUCE: arm64: config: Disable DMI config

  Shubhi Garg (1):
    NVIDIA: SAUCE: configs: defconfig: enable TPM configs

  Vince Hsu (1):
    NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota
  

  Apply pull request from NVIDIA received on 2023-11-27
  
  EJ Hsu (1):
NVIDIA: SAUCE: pinctrl: tegra: Set SFIO mode to Mux Register

  Linus Walleij (1):
Revert "pinctrl: tegra: Add support to display pin function"

  Penny Chiu (3):
NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig
NVIDIA: SAUCE: arm64: configs: Enable NFS server support
NVIDIA: SAUCE: arm64: configs: Enable dm_multipath driver

  Thierry Reding (1):
pinctrl: tegra: Display pin function in pinconf-groups

  Vince Hsu (1):
NVIDIA: SAUCE: arm64: configs: enable few matches for netfliter
  

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


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

[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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 removed: verification-done
** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * There is a wrong bucket calculation for payload of exactly 4096 bytes
 in SMC stats counters.

   * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues.

   * The impact is that a system silently updates an incorrect stats counter
 in case the underlying kernel is not UBSAN enabled.
 (Difficult to detect.)

   * But if a kernel is UBSAN enabled, one will see a UBSAN
 'array-index-out-of-bounds' warning every time this occurs, like:
 [ 26.335381] UBSAN: array-index-out-of-bounds in 
/build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3
 [ 26.335385] index -1 is out of range for type 'u64 [9]'
 [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic 
#86-Ubuntu
 [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux)
 [ 26.335393] Call Trace:
 [ 26.335397] [] dump_stack_lvl+0x62/0x80
 [ 26.335404] [] ubsan_epilogue+0x1c/0x48
 [ 26.335406] [] __ubsan_handle_out_of_bounds+0x94/0xa0
 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc]
 [ 26.335425] [] sock_sendmsg+0x64/0x80
 [ 26.335431] [] sock_write_iter+0x72/0xa0
 [ 26.335433] [] new_sync_write+0x100/0x190
 [ 26.335438] [] vfs_write+0x1e8/0x280
 [ 26.335440] [] ksys_write+0xb4/0x100
 [ 26.335442] [] __do_syscall+0x1bc/0x1f0
 [ 26.335446] [] system_call+0x78/0xa0

  [Fix]

   * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix
  pos miscalculation in statistics"

  [Test Plan]

   * Since this got identified while the livepatch for jammy patches got added,
 one could run a simiar (or the same) test like mentioned at LP#1639924
 (but only jammy comes with official livepatch support).

   * Alternatively a dedicated SMC stats counters test with a payload of
 exactly 4096 bytes could be done (which is probably easier):

   * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf).
 (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!)

   * Reset SMC-D stats on client and server side.

   * Start uperf at the server side using: # uperf -vs

   * Update profile with remote IP (server IP)
 and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml
 with uperf profile:
 # cat rr1c-4kx4k---1.xml
 
 
  
  
  
  
   

   
   


   
   

   
  
 
   
   * The smcd stats output is:
 # smcd -d stats reset
 SMC-D Connections Summary
   Total connections handled 2
   SMC connections 2 (client 2, server 0)
 v1 0
 v2 2
   Handshake errors 0 (client 0, server 0)
   Avg requests per SMC conn 14.0
   TCP fallback 0 (client 0, server 0)
 RX Stats
   Data transmitted (Bytes) 5796 (5.796K)
   Total requests 9
   Buffer full 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   Bufs 0 0 0 2 0 0 0 1
   Reqs 8 0 0 0 0 0 0 0
 TX Stats
   Data transmitted (Bytes) 9960 (9.960K)
   Total requests 19
   Buffer full 0 (0.00%)
   Buffer full (remote) 0 (0.00%)
   Buffer too small 0 (0.00%)
   Buffer too small (remote) 0 (0.00%)
   Buffer downgrades 0
   Buffer reuses 0
 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB
   

[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

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

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

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

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  USB bus error after upgrading to proposed kernel on lunar, jammy and
  focal

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel.

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

  [Test]
  With the patch applied, SuperSpeed devices can be enumerated across
  several reboots.

  [Where problems could occur]
  The switch case for Wireless USB (not USB WiFi dongle) was removed by
  the fix. I am not aware of the existence of any Wireless USB device. But
  if they do exist, this patch may the packet size encoding on them.

  == Original Bug Report ==
  [Summary]
  Some of machines in cert lab after upgrading to proposed kernel on jammy and 
lunar, all usb devices were gone.

  I found this issue on linux-image-6.2.0-38-generic and linux-
  image-5.15.0-90-generic on some specific machines.

  Since some of machines are using usb ethernet adapter so after
  upgrading, those machines are not accessible.

  Following are the machine list I've seen impacted by this issue, I
  believe there will be more if I check further.

  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201903-26881/
  https://certification.canonical.com/hardware/201903-26932/
  https://certification.canonical.com/hardware/202005-27944/
  https://certification.canonical.com/hardware/202008-28166/
  https://certification.canonical.com/hardware/202008-28167/
  https://certification.canonical.com/hardware/202102-28728/
  https://certification.canonical.com/hardware/202008-28176/
  https://certification.canonical.com/hardware/202008-28177/
  https://certification.canonical.com/hardware/202202-29946/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Fri Nov 10 12:04:10 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
   Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Wide Vision HD Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProOne 600 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-90-generic N/A
   

[Kernel-packages] [Bug 2045080] Re: apply nvidia igx patches for Oct 19 - Nov 28 2023

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  apply nvidia igx patches for Oct 19 - Nov 28 2023

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

Bug description:
  Patches for IGX.  These are intended for releases that come after the
  r36.2 DP release.

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


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

[Kernel-packages] [Bug 2046011] Re: apply nvidia igx patches for Nov 29 - Dec 8 2023

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


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


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


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

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

Title:
  apply nvidia igx patches for Nov 29 - Dec 8 2023

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

Bug description:
  Additional patches for IGX kernel.

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


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

[Kernel-packages] [Bug 2046657] Re: mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits

[Bartlomiej Zolnierkiewicz]

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

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

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

Title:
  mmc: sdhci-of-dwcmshc: Replace sauce patches with upstream commits

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  SRU Justification:

  [Impact]
  The msdhci-of-dwcmshc driver in the Jammy repo
  consists of some SAUCE patches. These need to be replaced.

  [Fix]
  The fix is to revert the four SAUCE patches, replacing them with
  upstream commits for the same functionality. 

  [Test Case]
  * Boot BF3 platform, verify no new errors

  
  [Regression Potential]
  The upstream commits are not exactly the same as the SAUCE patches,
  so technically there is a chance of regression, but its been
  well-tested and the functionality is the same.

  [Other]
  n/a

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


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

[Kernel-packages] [Bug 2044427] Re: Kernel panic in restart driver after configuring IPsec full offload

[Bartlomiej Zolnierkiewicz]

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

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

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

Title:
  Kernel panic in restart driver after configuring  IPsec full offload

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  Bug description:

  Restarting the driver with IPsec full offload transparent mode configuration 
causes kernel panic.
  Kernel version is linux-bluefield 5.15

  Test step:
  1) configure xfrm rules
  2) configure VF
  3) configure FW steering mode
  4) restart driver
  5) check dmesg

  Test result:
   [  937.989359] [ cut here ]
   [  937.989786] WARNING: CPU: 11 PID: 60463 at 
/tmp/23.10-0.1.8/6.5.0-rc6_mlnx/fedora_32/mlnx-ofa_kernel/BUILD/mlnx-ofa_kernel-23.10/obj/default/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_fs.c:1828
 mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core]
   [  937.991650] Modules linked in: esp4_offload esp4 esp6_offload esp6 
act_tunnel_key vxlan act_mirred act_skbedit cls_matchall act_gact cls_flower 
sch_ingress vringh vhost_iotlb udp_diag tcp_diag inet_diag iptable_raw 
mst_pciconf(OE) bonding ip6_gre ip6_tunnel tunnel6 vfio_pci vfio_pci_core 
vfio_iommu_type1 vfio ipip tunnel4 geneve ip6_udp_tunnel udp_tunnel ip_gre 
ip_tunnel gre rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) 
ib_umad(OE) ib_uverbs(OE) mlx5_core(OE-) mlxdevm(OE) ib_core(OE) mlx_compat(OE) 
mlxfw(OE) memtrack(OE) pci_hyperv_intf openvswitch nsh nf_conncount nfsv3 
nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache 
netfs xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype 
iptable_filter iptable_nat nf_nat br_netfilter bridge stp llc rfkill overlay 
kvm_intel sch_fq_codel kvm iTCO_wdt irqbypass iTCO_vendor_support crc32_pclmul 
pcspkr ghash_clmulni_intel i2c_i801 lpc_ich sha512_ssse3 i2c_smbus mfd_core 
sunrpc drm i2c_
 core ip_tables crc32c_intel serio_raw
   [  937.991698]  fuse virtio_net net_failover failover [last unloaded: vdpa]
   [  937.999155] CPU: 11 PID: 60463 Comm: modprobe Tainted: G   OE 
 6.5.0-rc6_mlnx #1
   [  937.999891] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014
   [  938.000823] RIP: 0010:mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core]
   [  938.001459] Code: f6 45 31 c0 48 89 ea 31 ff e8 d4 d5 df ff 59 e9 8c fe 
ff ff c3 0f 0b e9 3b fe ff ff 0f 0b e9 e8 fd ff ff 0f 0b e9 07 fe ff ff <0f> 0b 
e9 65 fe ff ff 0f 0b e9 82 fe ff ff 66 2e 0f 1f 84 00 00 00
   [  938.002949] RSP: 0018:c90001183c08 EFLAGS: 00010202
   [  938.003418] RAX:  RBX: 8882f3869c00 RCX: 
0001
   [  938.004024] RDX: 82a305c0 RSI: 0002 RDI: 
888103aa2b30
   [  938.004624] RBP: 888103aa2d80 R08: 0001 R09: 
888100042800
   [  938.005238] R10: 0002 R11: c90001183ba8 R12: 
8881312e6800
   [  938.005836] R13: 8881127401a0 R14: 8881312e6800 R15: 
888148bbd160
   [  938.006444] FS:  7fd22b82c740() GS:5fac() 
knlGS:
   [  938.009456] CS:  0010 DS:  ES:  CR0: 80050033
   [  938.009970] CR2: 7f26ca697000 CR3: 00012e73f003 CR4: 
00770ee0
   [  938.010568] DR0:  DR1:  DR2: 

   [  938.011173] DR3:  DR6: fffe0ff0 DR7: 
0400
   [  938.011772] PKRU: 5554
   [  938.012065] Call Trace:
   [  938.012333]  
   [  938.012583]  ? __warn+0x7d/0x120
   [  938.012921]  ? mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core]
   [  938.013494]  ? report_bug+0xf1/0x1c0
   [  938.013850]  ? handle_bug+0x44/0x70
   [  938.014201]  ? exc_invalid_op+0x13/0x60
   [  938.014568]  ? asm_exc_invalid_op+0x16/0x20
   [  938.014970]  ? mlx5e_accel_ipsec_fs_cleanup+0x298/0x2b0 [mlx5_core]
   [  938.015532]  ? mlx5e_accel_ipsec_fs_cleanup+0xf2/0x2b0 [mlx5_core]
   [  938.016093]  mlx5e_ipsec_cleanup+0x1e/0x100 [mlx5_core]
   [  938.016594]  mlx5e_detach_netdev+0x46/0x80 [mlx5_core]
   [  938.017098]  mlx5e_vport_rep_unload+0x147/0x1a0 [mlx5_core]
   [  938.017623]  mlx5_eswitch_unregister_vport_reps+0x13e/0x190 [mlx5_core]
   [  938.018221]  auxiliary_bus_remove+0x18/0x30
   [  938.018616]  device_release_driver_internal+0xaa/0x130
   [  938.019076]  bus_remove_device+0xc3/0x130
   [  938.019451]  device_del+0x157/0x380
   [  938.019792]  ? kobject_put+0xb3/0x200
   [  938.020153]  delete_drivers+0x72/0xa0 [mlx5_core]
   [  938.020608]  mlx5_unregister_device+0x34/0x70 [mlx5_core]
   [  938.021113]  mlx5_uninit_one+0x25/0x130 [mlx5_core]
   [  938.021572]  remove_one+0x72/0xc0 

[Kernel-packages] [Bug 2045919] Re: mlxbf-bootctl: fails to report info about cards using dev keys

[Bartlomiej Zolnierkiewicz]

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

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

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

Title:
  mlxbf-bootctl: fails to report info about cards using dev keys

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  SRU Justification:

  [Impact]

  There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
  report when a secure boot enabled card is using development keys. The program
  will instead report lifecycle state as "GA Secured" which is misleading.

  [Fix]

  Bring in the following upstream commit from linux-next:
"mlxbf-bootctl: correctly identify secure boot with development keys"

  [Test Case]

  Enable secure boot on a BF3 card that is using development keys
  Login as root on BF3
  Run the command "mlxbf-bootctl"
  Verify that the "lifecycle state" row shows "Secured (development)"

  [Regression Potential]

  Low risk change, cherry pick of upstream approved commit

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


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

[Kernel-packages] [Bug 2047692] Re: "Disable RNG for all AMD fTPMs" breaks TPM on some Intel devices

[Peter Treman]

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

** This bug has been marked a duplicate of bug 2046434
   TPM2 Problem in 6.2.0 kernel

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

Title:
  "Disable RNG for all AMD fTPMs" breaks TPM on some Intel devices

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

Bug description:
  6.2.0-39.40~22.04.1 includes upstream stable patchset 2023-10-10
  (https://launchpad.net/bugs/2038969) with the TPM changes 'Disable RNG
  for all AMD fTPMs' and 'Add a helper for checking hwrng enabled'.

  This causes on some Intel devices that TPM does not work (in my case a
  Gigabyte Brix GB-BSi5-1135G7) with the error

  "
  tpm_crb: probe of MSFT0101:00 failed with error 378
  "

  Upstream discussed this issue in
  https://bugzilla.kernel.org/show_bug.cgi?id=217804 and a fix was
  found:
  
https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8

  Full disclosure: I report this issue based only on above links. I did
  not try to run my affected device with a patched kernel and switched
  for the time being back to the HWE kernel 6.2.0-37. But the
  deswcription of the issue is a very good fit to the behaviour I see
  with the Gigabyte PC.

  LSB release infos:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

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


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

[Kernel-packages] [Bug 1918085] Re: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump

[Dmitry-a-durnev]

The same in 22.04.3:

[0.049372] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic 
root=UUID=... ro quiet splash crashkernel=512M-:192M vt.handoff=7
[0.049461] Unknown kernel command line parameters "splash 
BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic", will be passed to user space.

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

Title:
  Package linux-crashdump in 20.04 configures kernel cmdline crashkernel
  incorrectly causing lock-up on kernel dump

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  Package linux-crashdump in 20.04 configures kernel cmdline crashkernel
  incorrectly causing lock-up on kernel dump.

  It is very simple to replicate. I was testing using QEmu
  virtualisation software, where I had QEmu running a 20.04 install
  within another 20.04 install.

  Within the virtualisation install, simply install the package 
"linux-crashdump":
  $ sudo apt install linux-crashdump

  Answering Yes and Yes to the two questions asked:

   || Configuring kexec-tools ||
   |   |
   |   |
   | If you choose this option, a system reboot will trigger a restart into a  |
   | kernel loaded by kexec instead of going through the full system boot  |
   | loader process.   |
   |   |
   | Should kexec-tools handle reboots (sysvinit only)?|
   |   |
   |  |
   |   |
   |---|

   || Configuring kdump-tools ||
   |   |
   |   |
   | If you choose this option, the kdump-tools mechanism will be enabled.  A  |
   | reboot is still required in order to enable the crashkernel kernel|
   | parameter.|
   |   |
   | Should kdump-tools be enabled be default? |
   |   |
   |  |
   |   |
   |---|

  Check the kernel command-line Grub configured by package install:
  $ cat /proc/cmdline 
  BOOT_IMAGE=/vmlinuz-5.4.0-66-lowlatency root=/dev/mapper/rootlvm-rootpart ro 
crashkernel=512M-:192M

  As you can see "crashkernel=512M-:192M" is definitely a syntax error.

  Furthermore, when I test with this default configuration by forcing a crash:
  Enable dump then reboot testing with the following command:
  sudo sysctl -w kernel.sysrq=1
  Once this is done, you must become root, as just using sudo will not be 
sufficient. As the root user, you will have to issue the command echo c > 
/proc/sysrq-trigger.

  Once the "echo c > /proc/sysrq-trigger" command is issued as root, the
  virtual host being tested locks-up at 100% CPU indefinitely. Forcing
  shutdown and reboot shows no crash file in /var/crash folder however I
  can only see files "kexec_cmd" and "kdump_lock".

  To manually fix this issue I changed to "crashkernel=512M-:192M" to 
"crashkernel=384M-:512M" by editing (i.e. make the small number/larger number 
order correct):
  $ sudo vim /etc/default/grub.d/kdump-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=384M-:512M"

  After reboot and retest of the forced crash commands, the kdump works and all 
the needed files are present after self-reboot:
  $ ls /var/crash/
  202103081345  kdump_lock  kexec_cmd  
linux-image-5.4.0-66-lowlatency-202103081345.crash
  $ ls /var/crash/202103081345/
  dmesg.202103081345  dump.202103081345

  In summary the problem is that the default kernel command-line
  configured by default "crashkernel=512M-:192M" is faulty in some way
  or other and causes the kernel to lock-up at 100% CPU indefinitely
  when kdump is triggered.

  This can be manually fixed giving a workaround but future user will
  suffer until the default installation configuration is fixed.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

[J C Nash]

My issue with the zfs-dkms bug was raised by Linux Mint update giving an error 
message each time
an upgrade was run. The error message has now stopped appearing. I've not seen 
any news that the
issue is fixed. Does anyone have information that the corrections have migrated 
through from the
upstream repos?   JN

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

Title:
  zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
  kernel module.

  Genrated Crash report, but couldn't send it on it's own.

  Error it kept throwing was:
  >>>
  Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
  Loading new zfs-2.1.5 DKMS files...
  Building for 6.2.0-36-generic 6.2.0-37-generic
  Building initial module for 6.2.0-36-generic
  configure: error:
   *** None of the expected "iops->get_acl()" interfaces were detected.
   *** This may be because your kernel version is newer than what is
   *** supported, or you are using a patched custom kernel with
   *** incompatible modifications.
   ***
   *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2
   *** Compatible Kernels: 3.10 - 5.19

  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/zfs-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64)
  Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information.
  dpkg: error processing package zfs-dkms (--configure):
   installed zfs-dkms package post-installation script subprocess returned 
error exit status 10
  >>>

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Nov 25 21:00:27 2023
  InstallationDate: Installed on 2021-09-23 (793 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago)

  To recreate:
  - Install Ubuntu 22.04.3.
  - Update to current.
  - Install package 'zfs-dkms'

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


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

[Kernel-packages] [Bug 1117804] Re: ausearch doesn't show AppArmor denial messages

[Jarkko Toivonen]

Any news on this? It has been open for over ten years now. AppArmor is
on by default on Ubuntu, and if auditd is used, then the events are
logged using it. Isn't it a security bug if the events don't show up
when queried using ausearch?

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

Title:
  ausearch doesn't show AppArmor denial messages

Status in AppArmor:
  Confirmed
Status in audit package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following command should display all AVC denials:

  ausearch -m avc

  However, it doesn't work with AppArmor denials. Here's a quick test
  case to generate a denial, search for it with ausearch, and see that
  no messages are displayed:

  $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current
  cat: /proc/self/attr/current: Permission denied
  $ sudo ausearch -m avc -c cat
  

  ausearch claims that there are no matches, but there's a matching
  audit message if you look in audit.log:

  type=AVC msg=audit(1360193426.539:64): apparmor="DENIED"
  operation="open" parent=8253 profile="/usr/sbin/tcpdump"
  name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r"
  denied_mask="r" fsuid=1000 ouid=1000

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


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

[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Christian Ehrhardt ]

The seeding [1] of it is also quite clear on why it is still there.

"""
# This stack is no more very relevant, but was in the early days of internet
# dialin. This stack is a candidate for demotion, but OTOH received no
# bugs/CVEs over the last years and therefore can stay as-is for now.
# ppp itself is still recommended by network-manager and thereby has quite
# an install base.
"""

Removing is maybe too hard as Steve outlined, but what about at least
demoting to universe (to encourage it a bit less)?

The seed change to the section linked above would be trivial, but it
would need coordination with the Desktop variants as a dependency to
network-manager-pptp is in most of the meta packages.

reverse-depends  --release=noble  src:network-manager-pptp
Reverse-Recommends
==
* network-manager   (for network-manager-pptp)
* ubuntu-budgie-desktop [amd64 arm64 armhf ppc64el]
* ubuntu-budgie-desktop-minimal [amd64 arm64 armhf ppc64el]
* ubuntu-budgie-desktop-raspi [arm64 armhf]
* ubuntu-desktop [amd64 arm64 armhf ppc64el]
* ubuntu-desktop-minimal [amd64 arm64 armhf ppc64el]
* ubuntu-mate-core  (for network-manager-pptp-gnome)
* ubuntu-mate-desktop   (for network-manager-pptp-gnome)
* ubuntu-unity-desktop [amd64 arm64 armhf ppc64el]
* ubuntukylin-desktop   (for network-manager-pptp-gnome)
* vanilla-gnome-desktop [amd64 arm64 armhf ppc64el]
* xubuntu-desktop   (for network-manager-pptp-gnome)
* xubuntu-desktop   (for network-manager-pptp)

Reverse-Depends
===
* lomiri-indicator-network  (for network-manager-pptp)


It comes at a comfort loss though, since this is depended on by all those meta 
packages to work right away in a fresh install, which would be a behavior that 
will be lost.

Also if there is a CVE, then only people using ubuntu pro would get a
fix. Which is free for personal use, but those forced to use pptp are
likely people with non-personal use of outdated infrastructure. So we'd
make the world a bit less secure as likely not all would get the fixes
then.

Still I'd want to know from Steve and Seth which discussed so far - what
would you think about that as a compromise?

[1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/platform/tree/supported-misc-servers#n190

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  Incomplete

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  IPSec OpenVPN Strongswan are much better alternatives.

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


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

[Kernel-packages] [Bug 2046074] Re: The monitor screen appears black when connecting the PC through the sound bar to the monitor

[Noctis Bennington]

Thank you for reassigning @vanvugt.

Sorry, I reported this on 6.6.5 linux kernel. Yes, this happens too in
the Ubuntu kernel (6.5.x-generic).

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

Title:
  The monitor screen appears black when connecting the PC through the
  sound bar to the monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I connect the laptop to the sound bar hdmi and the sound bar to
  the monitor, it tries to connect and Ubuntu detects it, but nothing
  appears on the screen.

  My HDMI works as it should, tested directly when it's connected to the
  monitor. I have tried on a laptop other than my computer with Windows
  to test if it is something of the sound bar and it works perfectly
  without problems.

  Don't really know what package should be interfering here. Mesa?
  Mutter?

  
  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  OS: Ubuntu 23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  Uname: Linux 6.6.5-060605-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 10 17:39:27 2023
  InstallationDate: Installed on 2023-10-13 (58 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device

[Daniel van Vugt]

** Tags added: regression-update

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

Title:
  bluetooth device connected but not recognised as output device

Status in bluez package in Ubuntu:
  New

Bug description:
  bluetooth device connected but not recognised as output device

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 15:28:00 2023
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 81EK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2018
  dmi.bios.release: 1.28
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7QCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 530-14IKB
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB:
  dmi.product.family: YOGA 530-14IKB
  dmi.product.name: 81EK
  dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB
  dmi.product.version: Lenovo YOGA 530-14IKB
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 0C:54:15:91:FA:4F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:83770 acl:295 sco:0 events:4208 errors:0
TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0

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


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

[Kernel-packages] [Bug 2046074] Re: The monitor screen appears black when connecting the PC through the sound bar to the monitor

[Daniel van Vugt]

Wait, 6.6.5-060605-generic isn't an Ubuntu kernel - do you have the same
bug in the default Ubuntu kernel?

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

Title:
  The monitor screen appears black when connecting the PC through the
  sound bar to the monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I connect the laptop to the sound bar hdmi and the sound bar to
  the monitor, it tries to connect and Ubuntu detects it, but nothing
  appears on the screen.

  My HDMI works as it should, tested directly when it's connected to the
  monitor. I have tried on a laptop other than my computer with Windows
  to test if it is something of the sound bar and it works perfectly
  without problems.

  Don't really know what package should be interfering here. Mesa?
  Mutter?

  
  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  OS: Ubuntu 23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  Uname: Linux 6.6.5-060605-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 10 17:39:27 2023
  InstallationDate: Installed on 2023-10-13 (58 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2046074] Re: The monitor screen appears black when connecting the PC through the sound bar to the monitor

[Daniel van Vugt]

Sound and display coexisting on the same HDMI cable would be a kernel
issue so reassigning...

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

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

Title:
  The monitor screen appears black when connecting the PC through the
  sound bar to the monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I connect the laptop to the sound bar hdmi and the sound bar to
  the monitor, it tries to connect and Ubuntu detects it, but nothing
  appears on the screen.

  My HDMI works as it should, tested directly when it's connected to the
  monitor. I have tried on a laptop other than my computer with Windows
  to test if it is something of the sound bar and it works perfectly
  without problems.

  Don't really know what package should be interfering here. Mesa?
  Mutter?

  
  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  OS: Ubuntu 23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  Uname: Linux 6.6.5-060605-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 10 17:39:27 2023
  InstallationDate: Installed on 2023-10-13 (58 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2046074] [NEW] The monitor screen appears black when connecting the PC through the sound bar to the monitor

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I connect the laptop to the sound bar hdmi and the sound bar to the
monitor, it tries to connect and Ubuntu detects it, but nothing appears
on the screen.

My HDMI works as it should, tested directly when it's connected to the
monitor. I have tried on a laptop other than my computer with Windows to
test if it is something of the sound bar and it works perfectly without
problems.

Don't really know what package should be interfering here. Mesa? Mutter?


MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.

OS: Ubuntu 23.10

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: mutter (not installed)
Uname: Linux 6.6.5-060605-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 10 17:39:27 2023
InstallationDate: Installed on 2023-10-13 (58 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
ProcEnviron:
 LANG=es_ES.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug mantic wayland-session
-- 
The monitor screen appears black when connecting the PC through the sound bar 
to the monitor
https://bugs.launchpad.net/bugs/2046074
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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)

[Daniel van Vugt]

** No longer affects: mutter (Ubuntu)

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

Title:
  [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
  screen (no screen detected)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New

Bug description:
  When I go into "fullscreen" watching a video while browsing in Firefox
  or when playing a game through Steam (fullscreen mode), the screen
  goes black.

  The workaround I have discovered to get back is to enter the gdm from
  "Ctrl + alt + F1" and then return to the session you were in
  (normally, "Ctrl + alt + F2).

  Edit: It happens when I connect a second monitor and use it as the
  primary display while the laptop screen is disabled.

  MSI laptop.
  CPU: AMD Ryzen 7 Series 4000
  GPU: AMD Radeon RX 5600m
  RAM: 16GB
  NVM: 1TB.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  noctis 2095 F wireplumber
   /dev/snd/controlC0:  noctis 2095 F wireplumber
   /dev/snd/seq:noctis 2090 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:00:55 2023
  InstallationDate: Installed on 2023-10-13 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 amdgpudrmfb
   1 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2020
  dmi.bios.release: 1.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17EKAMS.101
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17EK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
  dmi.product.family: Al
  dmi.product.name: Alpha 17 A4DEK
  dmi.product.sku: 17EK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly

[Daniel van Vugt]

My previous comments one year ago were probably premature. And on top of
that I'm now using a different primary desktop (also Intel 12th gen, now
kernel 6.2) that periodically has a similar bug. My next plan is to try
replacing the USB-C cable with an expensive Apple Thunderbolt cable.


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

** Tags added: jammy

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  [i915] external monitor goes black for several seconds at a time,
  randomly

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  At times it is completely debilitating; at other times it does not happen for 
hours.
  The physical connections are clean and solid.

   I guess the attachments will show that I'm using Intel graphics
  hardware.  The monitor is a very popular Samsung one.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 16:56:04 2021
  DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2019-01-24 (847 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1642112] Re: Can’t connect to the second BT device successfully

[Daniel van Vugt]

Nicolas, this bug was reported over 7 years ago against an Ubuntu
version that will reach end of life in a few months. I suggest to keep
your issue alive that it should be reported as a new bug.

** Tags added: trusty

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

Title:
  Can’t connect to the second BT device successfully

Status in bluez package in Ubuntu:
  New

Bug description:
  OS: 14.04
  bluez version: 4.x

  After first bt device(eg. mouse) connected, try to connect second device(eg. 
keyboard),
  found it has no function when connected, and sometimes it fails to connect.

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


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

[Kernel-packages] [Bug 2046315] Re: oem-6.5: disable psr2 for some panels according to edid

[Timo Aaltonen]

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

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

Title:
  oem-6.5: disable psr2 for some panels according to edid

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  Triaged
Status in linux-oem-6.5 source package in Noble:
  Invalid

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

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

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

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

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

  [Test case]

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

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

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


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