[Kernel-packages] [Bug 2019543] Re: crypto / qat: unable to init GEN4 device
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019543
Title:
crypto / qat: unable to init GEN4 device
Status in linux package in Ubuntu:
Expired
Bug description:
[Target]
Jammy kernel.
[Impact]
The PCI device cannot be initialized.
This has been fixed in linux v5.18 with the below commits:
- a9dc0d966605 ("crypto: qat - add PFVF support to the GEN4 host driver")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a9dc0d966605
- 642a7d49c249 ("crypto: qat - fix access to PFVF interrupt registers for
GEN4")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=642a7d49c249
[Test Case]
Boot a machine with this device.
Before the patches, the following errors are logged:
> EAL: Probe PCI driver: qat (8086:4941) device: :00:08.0 (socket -1)
> qat_pf2vf_exch_msg(): ACK not received from remote
[Regression Potential]
The patches enable new code for this kind of device only.
It is living in linux for more than 1 years.
The potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019543/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028408] [NEW] Jammy update: v5.15.113 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.113 upstream stable release
from git://git.kernel.org/
drm/mipi-dsi: Set the fwnode for mipi_dsi_device
ARM: 9296/1: HP Jornada 7XX: fix kernel-doc warnings
net: mdio: mvusb: Fix an error handling path in mvusb_mdio_probe()
scsi: ufs: core: Fix I/O hang that occurs when BKOPS fails in W-LUN suspend
tick/broadcast: Make broadcast device replacement work correctly
linux/dim: Do nothing if no time delta between samples
net: stmmac: switch to use interrupt for hw crosstimestamping
net: stmmac: Initialize MAC_ONEUS_TIC_COUNTER register
net: Fix load-tearing on sk->sk_stamp in sock_recv_cmsgs().
netfilter: nf_tables: always release netdev hooks from notifier
netfilter: conntrack: fix possible bug_on with enable_hooks=1
netlink: annotate accesses to nlk->cb_running
net: annotate sk->sk_err write from do_recvmmsg()
net: deal with most data-races in sk_wait_event()
net: add vlan_get_protocol_and_depth() helper
tcp: add annotations around sk->sk_shutdown accesses
gve: Remove the code of clearing PBA bit
net: datagram: fix data-races in datagram_poll()
af_unix: Fix a data race of sk->sk_receive_queue->qlen.
af_unix: Fix data races around sk->sk_shutdown.
drm/i915/dp: prevent potential div-by-zero
fbdev: arcfb: Fix error handling in arcfb_probe()
ext4: remove an unused variable warning with CONFIG_QUOTA=n
ext4: reflect error codes from ext4_multi_mount_protect() to its callers
ext4: fix lockdep warning when enabling MMP
ext4: allow to find by goal if EXT4_MB_HINT_GOAL_ONLY is set
ext4: allow ext4_get_group_info() to fail
refscale: Move shutdown from wait_event() to wait_event_idle()
rcu: Protect rcu_print_task_exp_stall() ->exp_tasks access
fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()
drm/displayid: add displayid_get_header() and check bounds better
drm/amd/display: Use DC_LOG_DC in the trasform pixel function
regmap: cache: Return error in cache sync operations for REGCACHE_NONE
arm64: dts: qcom: msm8996: Add missing DWC3 quirks
media: cx23885: Fix a null-ptr-deref bug in buffer_prepare() and buffer_finish()
media: pci: tw68: Fix null-ptr-deref bug in buf prepare and finish
firmware: arm_sdei: Fix sleep from invalid context BUG
ACPI: EC: Fix oops when removing custom query handlers
remoteproc: stm32_rproc: Add mutex protection for workqueue
drm/tegra: Avoid potential 32-bit integer overflow
drm/msm/dp: Clean up handling of DP AUX interrupts
ACPICA: Avoid undefined behavior: applying zero offset to null pointer
ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in
acpi_db_display_objects
drm/amd: Fix an out of bounds error in BIOS parser
media: Prefer designated initializers over memset for subdev pad ops
wifi: ath: Silence memcpy run-time false positive warning
bpf: Annotate data races in bpf_local_storage
wifi: brcmfmac: cfg80211: Pass the PMK in binary instead of hex
ext2: Check block size validity during mount
scsi: lpfc: Prevent lpfc_debugfs_lockstat_write() buffer overflow
bnxt: avoid overflow in bnxt_get_nvram_directory()
net: pasemi: Fix return type of pasemi_mac_start_tx()
net: Catch invalid index in XPS mapping
scsi: target: iscsit: Free cmds before session free
lib: cpu_rmap: Avoid use after free on rmap->obj array entries
scsi: message: mptlan: Fix use after free bug in mptlan_remove() due to race
condition
gfs2: Fix inode height consistency check
scsi: ufs: ufs-pci: Add support for Intel Lunar Lake
ext4: set goal start correctly in ext4_mb_normalize_request
ext4: Fix best extent lstart adjustment logic in ext4_mb_new_inode_pa()
f2fs: fix to drop all dirty pages during umount() if cp_error is set
f2fs: fix to check readonly condition correctly
samples/bpf: Fix fout leak in hbm's run_bpf_prog
bpf: Add preempt_count_{sub,add} into btf id deny list
wifi: iwlwifi: pcie: fix possible NULL pointer dereference
wifi: iwlwifi: pcie: Fix integer overflow in iwl_write_to_user_buf
null_blk: Always check queue mode setting from configfs
wifi: iwlwifi: dvm: Fix memcpy: detected field-spanning write backtrace
wifi: ath11k: Fix SKB corruption in REO destination ring
nbd: fix incomplete validation of ioctl arg
ipvs: Update width of source for ip_vs_sync_conn_options
Bluetooth: btintel: Add LE States quirk support
Bluetooth: hci_bcm: Fall back to getting bdaddr from EFI if not set
Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
HID: logitech-hidpp: Don't use the USB serial for USB devices
HID: logitech-hidpp: Reconcile USB and Unifying serials
spi: spi-imx: fix MX51_ECSPI_* macros when cs > 3
[Kernel-packages] [Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB
Hello Ionut, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
I have updates! - I set /sys/devices/system/cpu/intel_pstate/max_perf_pct to 100 and confirmed that it restore the 4.7/4.8 peak turbo frequencies. - I ran `stress -c 1`, cpu package temps went up to ~84 degrees C. No changes on the grep, no changes on the powerprofilesctl degraded state. - I ran `stress -c 2`, cpu package temps went up to ~90 degrees C. This triggered the powerprofilesctl degraded state. The grep: /sys/devices/system/cpu/intel_pstate/hwp_dynamic_boost:0 /sys/devices/system/cpu/intel_pstate/max_perf_pct:70 /sys/devices/system/cpu/intel_pstate/min_perf_pct:10 /sys/devices/system/cpu/intel_pstate/no_turbo:1 /sys/devices/system/cpu/intel_pstate/status:active $ powerprofilesctl * performance: Driver: intel_pstate Degraded: yes (high-operating-temperature) balanced: Driver: intel_pstate power-saver: Driver: intel_pstate $ cpupower frequency-info analyzing CPU 6: driver: intel_pstate ... hardware limits: 400 MHz - 4.80 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 2.40 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware boost state support: Supported: yes Active: yes In case it is relevant, this has been with thermald running. Temperatures are back down around 45 degrees C, which is typical, but as stated in the original error report it will never recover on its own * * * I have now set those values back to their originals, e.g. /sys/devices/system/cpu/intel_pstate/max_perf_pct:100 /sys/devices/system/cpu/intel_pstate/no_turbo:0 I will also note that the 400MHz to 2.40GHz range indicated by cpupower reverts the full range when no_turbo is set to 0, and powerprofilesctl degraded state is also directly based off this value. (So I will stop reporting them!) From this I can at least write a script that sets these variables back to normal and regain normal functionality without rebooting! My next step will be to uninstall thermald entirely, reboot, and report back with whether I'm able trigger either bug. I'm confused about what I experienced before, the reboot is to clear thermal envelope lock from my script. -- 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/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: New Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see
[Kernel-packages] [Bug 2028400] [NEW] Apply 2023-07-20 Orin enablement patches from NVIDIA
Public bug reported: [Impact] Pull in a number of patches that NVIDIA use internally. These are intended to improve kernel support for Orin-based devices. This set of commits consists of 166 patches that were received on 2023-07-20. ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - Pull in a number of patches that NVIDIA use internally. These are intended to improve kernel support for Orin-based devices. + Pull in a number of patches that NVIDIA use internally. These are intended to improve kernel support for Orin-based devices. + + This set of commits consists of 166 patches that were received on + 2023-07-20. -- 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/2028400 Title: Apply 2023-07-20 Orin enablement patches from NVIDIA Status in linux-nvidia-tegra package in Ubuntu: New Bug description: [Impact] Pull in a number of patches that NVIDIA use internally. These are intended to improve kernel support for Orin-based devices. This set of commits consists of 166 patches that were received on 2023-07-20. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2028400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH
The issue persists using kernel 5.15.0-76, unfortunately, the console remains blank, no panic message is printed but the machine stays on (power light stays on) and is unresponsive. Holding down the power button is the only action possible. Could not find anything in the log files, looks like the machine totally locks up now rather than having a panic. On 2023-07-13 17:49, Kai-Heng Feng wrote: > Please install later kernel by issuing `sudo apt install linux-generic- > hwe-20.04` and reboot. > -- B. Bogart, PhD they/them www.ekran.org -- 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/2016388 Title: Kernel Panic on shutdown / reboot on NUC8I3BEH Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028190] Re: kernel panic when using conntrack tcp pedit
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Fix Committed
--
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/2028190
Title:
kernel panic when using conntrack tcp pedit
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
* Explain the bug(s)
when setting up conntrack offload with tcp pedit (test-ct-tcp-
pedit.sh), encounter kernel panic.
* brief explanation of fixes
In tc_setup_flow_action, need to properly assign action.
Which fixes previous commit ("UBUNTU: SAUCE: net/sched: Provide act to
offload action")
* Kernel log
[ 226.156222] Unable to handle kernel access to user memory outside uaccess
routines at
[ 226.177783] Mem abort info:
[ 226.183408] ESR = 0x9604
[ 226.190953] EC = 0x25: DABT (current EL), IL = 32 bits
[ 226.201641] SET = 0, FnV = 0
[ 226.207786] EA = 0, S1PTW = 0
[ 226.214095] FSC = 0x04: level 0 translation fault
[ 226.223906] Data abort info:
[ 226.229695] ISV = 0, ISS = 0x0004
[ 226.237410] CM = 0, WnR = 0
[ 226.243372] user pgtable: 4k pages, 48-bit VAs, pgdp=000123f25000
[ 226.256328] [0090] pgd=, p4d=
[ 226.269984] Internal error: Oops: 9604 [#1] SMP
[ 226.279779] Modules linked in: act_pedit act_ct nf_flow_table iptable_raw
xt_CT xt_tcpudp bpfilter xt_comment xt_mark
[ 226.279938] async_raid6_recov async_memcpy async_pq async_xor async_tx
xor xor_neon raid6_pq raid1 raid0 multipath
[ 226.544260] CPU: 2 PID: 4293 Comm: handler3 Tainted: G
[ 226.565581] Hardware name: https://www.mellanox.com BlueField
SoC/BlueField SoC, BIOS 4.2.0.12795 Jun 30 2023
[ 226.585497] pstate: a045 (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 226.599481] pc : tcf_action_update_stats+0x8/0xc4
[ 226.608933] lr : mlx5e_tc_act_stats_fill_stats+0xf8/0x19c [mlx5_core]
[ 226.622089] sp : 8e073130
[ 226.628735] x29: 8e073130 x28: 0008 x27:
0020
[ 226.643067] x26: ffe0 x25: 5913c62dfe71 x24:
5913c62dfe00
[ 226.657398] x23: x22: x21:
5913c62dfe70
[ 226.671730] x20: 5913c2fc3b00 x19: 5913f0058000 x18:
0014
[ 226.686059] x17: b96d1a87 x16: c6320acb93e0 x15:
[ 226.700390] x14: 0001 x13: x12:
0002
[ 226.714720] x11: 7f7f7f7f7f7f7f7f x10: x9 :
c631ce0b66ac
[ 226.729052] x8 : 8e073130 x7 : x6 :
000d
[ 226.743384] x5 : 0c62 x4 : 0001 x3 :
[ 226.757715] x2 : x1 : x0 :
[ 226.772047] Call trace:
[ 226.776947] tcf_action_update_stats+0x8/0xc4
[ 226.785695] mlx5e_tc_act_stats_fill_stats_flow+0x78/0xc0 [mlx5_core]
[ 226.798833] mlx5e_stats_flower+0x394/0x3c0 [mlx5_core]
[ 226.809502] mlx5e_rep_setup_tc_cls_flower+0x8c/0xa0 [mlx5_core]
[ 226.821732] mlx5e_rep_setup_tc_cb+0x74/0xb0 [mlx5_core]
[ 226.832549] tc_setup_cb_call+0xa4/0x160
[ 226.840426] fl_hw_update_stats+0x98/0x164 [cls_flower]
[ 226.850927] fl_dump.part.0+0x224/0x260 [cls_flower]
[ 226.860891] fl_dump+0x20/0x34 [cls_flower]
[ 226.869284] tcf_fill_node+0x164/0x244
[ 226.876803] tfilter_notify+0xc0/0x140
[ 226.884323] tc_new_tfilter+0x454/0x8bc
[ 226.892018] rtnetlink_rcv_msg+0x2e8/0x3cc
[ 226.900245] netlink_rcv_skb+0x64/0x130
[ 226.907942] rtnetlink_rcv+0x20/0x30
[ 226.915110] netlink_unicast+0x2ec/0x360
[ 226.922977] netlink_sendmsg+0x278/0x490
[ 226.930846] sock_sendmsg+0x5c/0x6c
[ 226.937845] sys_sendmsg+0x290/0x2d4
[ 226.945712] ___sys_sendmsg+0x84/0xd0
[ 226.953059] __sys_sendmsg+0x70/0xd0
[ 226.960229] __arm64_sys_sendmsg+0x2c/0x40
[ 226.968447] invoke_syscall+0x78/0x100
[ 226.975974] el0_svc_common.constprop.0+0x54/0x184
[ 226.985587] do_el0_svc+0x30/0xac
[ 226.992231] el0_svc+0x48/0x160
[ 226.998528] el0t_64_sync_handler+0xa4/0x130
[ 227.007094] el0t_64_sync+0x1a4/0x1a8
[ 227.01] Code: 9407cf7e d503201f aa1e03e9 d503201f (f9404805)
[ 227.026679] ---[ end trace 2aa44f8c6701f98e ]---
[ 236.273308] Kernel panic - not syncing: Oops: Fatal exception
[ 236.284885] SMP: stopping secondary CPUs
[ 236.292761] Kernel Offset: 0x463201de from 0x8800
[ 236.304996] PHYS_OFFSET: 0xa6ed4000
[ 236.313387] CPU features: 0x800804a1,2846
[ 236.322129] Memory Limit: none
[
[Kernel-packages] [Bug 2028197] Re: rshim console truncates dmesg output due to tmfifo issue
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- 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/2028197 Title: rshim console truncates dmesg output due to tmfifo issue Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] mlxbf_tmfifo driver does not always schedule work for VIRTIO CONSOLE nottification. The result is with rshim console, the dmesg output would be cut off or simply cat a big text file to stdout. [Fix] * Make sure TM_TX_LWM_IRQ bit is set when there is a notification of virtio console event. [Test Case] * Compare the output of dmesg from rshim console and ssh session. Make sure both are the same. * Issue is reproduced w/o fix and compare the same dmesg output from the same as above. [Regression Potential] The changes affect only virtio console event handling only and been tested fully. [Others] This issue is the same on focal and Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: New Bug description: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028309] Re: mlxbf-bootctl: Fix kernel panic due to buffer overflow
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- 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/2028309 Title: mlxbf-bootctl: Fix kernel panic due to buffer overflow Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Running the following LTP (linux-test-project) script, causes a kernel panic and a reboot of the DPU: ltp/testcases/bin/read_all -d /sys -q -r 10 The above test reads all directory and files under /sys. Reading the sysfs entry "large_icm" causes the kernel panic due to a garbage value returned via i2c read. That garbage value causes a buffer overflow in sprintf. [Fix] * Replace sprintf with snprintf. And also add missing lock and increase the buffer size to PAGE_SIZE. [Test Case] * Run from linux: ltp/testcases/bin/read_all -d /sys -q -r 10 [Regression Potential] no known regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028268] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r
Thanks Juerg! I had the same issue with "pfring/8.0.0.7334". Removing it solved the issue! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028268 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: upgrading OS ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2293 F pipewire parallels 2296 F wireplumber /dev/snd/pcmC0D0p: parallels 2293 F...m pipewire /dev/snd/seq:parallels 2293 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 14:41:04 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (377 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-07-20 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028096] Re: Blank screen when using GDM
*** This bug is a duplicate of bug 2026887 *** https://bugs.launchpad.net/bugs/2026887 I got the same problem unexpectedly on Kubuntu with X11. That suggests that the problem is beyond the desktop and window managers. The additional line in /etc/environment has temporarily fixed this for me. I have attached the journal logs with the pipe errors inside. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2028096/+attachment/5687817/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2028096 Title: Blank screen when using GDM Status in gdm: Unknown Status in linux-oem-5.17 package in Ubuntu: New Bug description: Refer to this issue that I created for the GDM developers: https://gitlab.gnome.org/GNOME/gdm/-/issues/860 They have indicated that they will not fix this bug. Description:Ubuntu 22.04.2 LTS Release:22.04 gnome-shell: Installed: 42.9-0ubuntu2 Candidate: 42.9-0ubuntu2 Version table: *** 42.9-0ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages I am expecting not to have pipe errors between my integrated graphics card and GDM and for the login screen to appear. I got a pixelated screen and then a blank, black screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.17.0-1034.35-oem 5.17.15 Uname: Linux 5.17.0-1034-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jul 18 18:12:57 2023 DisplayManager: sddm InstallationDate: Installed on 2023-06-14 (34 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu1 ShellJournal: -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2028096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028365] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
** Description changed: - Ubuntu 22.04.2 with kernel 6.2.0-25-generic @ 21/7/2023 + Ubuntu 22.04.2 with kernel HWE-EDGE 6.2.0-25-generic @ 21/7/2023 - After recent updates to kernel 6.2.0-25-generic my intel flickering has + After update to HWE-EDGE kernel 6.2.0-25-generic my intel flickering has returned with the same symptons as in previous bug(s) on ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 Ubuntu loads to desktop and after a few seconds the flickering starts to unusable glitches - - This bug dissapears when adding the kernel parameter: i915.enable_dc=0 intel_idle.max_cstate=2 + This bug dissapears when adding the kernel parameter: i915.enable_dc=0 + intel_idle.max_cstate=2 On Ubuntu 22.04 the bug was fixed since kernel 5.17.7-051707-generic #202205121146 (mainline) and kernel 5.19.0-28-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-25.25~22.04.2-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 14:21:38 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2028365 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.2 with kernel HWE-EDGE 6.2.0-25-generic @ 21/7/2023 After update to HWE-EDGE kernel 6.2.0-25-generic my intel flickering has returned with the same symptons as in previous bug(s) on ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 Ubuntu loads to desktop and after a few seconds the flickering starts to unusable glitches This bug dissapears when adding the kernel parameter: i915.enable_dc=0 intel_idle.max_cstate=2 On Ubuntu 22.04 the bug was fixed since kernel 5.17.7-051707-generic #202205121146 (mainline) and kernel 5.19.0-28-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-25.25~22.04.2-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 14:21:38 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2028365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028385] [NEW] LRM: support LRM-only install with kernel snaps and network boot
Public bug reported: When doing ephemeral network boot, for example with MAAS. And when creating kernel snaps. It can be desirable to install LRM kernel drivers, without installing any other userspace. For example: * In case of MAAS network boot, vmlinuz is booted over the network, modules are provided in the initrd, and copied into /lib/modules in the tpmfs. But the actual packages linux-image-ABI / linux-modules-ABI are not installed * On Hybrid & FDE systems - whilst linux-modules-ABI may be installed, linux-image-ABI are not installed. * In case of kernel snaps, they stage -uc signed kernel.efi images and do not use or care about having linux-image-ABI packages. All of the above scenarios are usable with LRM NVIDIA kernel modules, and at times even without any userspace dependencies, as those are provided externally. For example nvidia-assemble snap provides binutils. Adapt LRM to support using NVIDIA kernel drives without linux-image-ABI installed as a .deb, which currently is often needlessly pulled in. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - LRM: support kernel modules only install + LRM: support LRM-only install with kernel snaps and network boot -- 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/2028385 Title: LRM: support LRM-only install with kernel snaps and network boot Status in linux package in Ubuntu: New Bug description: When doing ephemeral network boot, for example with MAAS. And when creating kernel snaps. It can be desirable to install LRM kernel drivers, without installing any other userspace. For example: * In case of MAAS network boot, vmlinuz is booted over the network, modules are provided in the initrd, and copied into /lib/modules in the tpmfs. But the actual packages linux-image-ABI / linux-modules-ABI are not installed * On Hybrid & FDE systems - whilst linux-modules-ABI may be installed, linux-image-ABI are not installed. * In case of kernel snaps, they stage -uc signed kernel.efi images and do not use or care about having linux-image-ABI packages. All of the above scenarios are usable with LRM NVIDIA kernel modules, and at times even without any userspace dependencies, as those are provided externally. For example nvidia-assemble snap provides binutils. Adapt LRM to support using NVIDIA kernel drives without linux-image- ABI installed as a .deb, which currently is often needlessly pulled in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028382] [NEW] Pulse Audio hangs with kernel 5.15.0-76
Public bug reported: When trying to play videos using Firefox, playback will stop for periods and then eventually Firefox will no longer be able to connect to pulseaudio. Kernel 5.15.0-75 works fine and does not hang. lsb_release -rd Description:Linux Mint 20.3 Release:20.3 apt-cache policy linux-image-5.15.0-76-generic linux-image-5.15.0-76-generic: Installed: 5.15.0-76.83~20.04.1 Candidate: 5.15.0-76.83~20.04.1 Version table: *** 5.15.0-76.83~20.04.1 500 500 http://mirrors.ocf.berkeley.edu/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status hwinfo Motherboard: Micro-Star International B450 TOMAHAWK (MS-7C02) CPU: Model: 23.24.1 "AMD Ryzen 5 3400G with Radeon Vega Graphics" ** 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/2028382 Title: Pulse Audio hangs with kernel 5.15.0-76 Status in linux package in Ubuntu: New Bug description: When trying to play videos using Firefox, playback will stop for periods and then eventually Firefox will no longer be able to connect to pulseaudio. Kernel 5.15.0-75 works fine and does not hang. lsb_release -rd Description: Linux Mint 20.3 Release: 20.3 apt-cache policy linux-image-5.15.0-76-generic linux-image-5.15.0-76-generic: Installed: 5.15.0-76.83~20.04.1 Candidate: 5.15.0-76.83~20.04.1 Version table: *** 5.15.0-76.83~20.04.1 500 500 http://mirrors.ocf.berkeley.edu/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status hwinfo Motherboard: Micro-Star International B450 TOMAHAWK (MS-7C02) CPU: Model: 23.24.1 "AMD Ryzen 5 3400G with Radeon Vega Graphics" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules
I like this stamp file, but I'm not too sure who will create it and remove it and when. Note that separately, ubuntu-release-upgrader https://git.launchpad.net/ubuntu-release- upgrader/tree/DistUpgrade/README#n13 will set environment variables: The following environment variable will be *set* by the upgrader: RELEASE_UPGRADE_IN_PROGRESS: - set to "1" if a release-upgrade is running (and not a normal package/security upgrade) Can we also please add code to use the "no-autoinstall-errors" mode, whenever RELEASE_UPGRADE_IN_PROGRESS = 1 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: New Bug description: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028381] [NEW] broadcom linux drive bcm4352 not working
Public bug reported: broadcom linux drive bcm4352 does not work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firmware-b43-installer 1:019-7build2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 10:39:25 2023 InstallationDate: Installed on 2023-07-21 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: b43-fwcutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/2028381 Title: broadcom linux drive bcm4352 not working Status in b43-fwcutter package in Ubuntu: New Bug description: broadcom linux drive bcm4352 does not work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firmware-b43-installer 1:019-7build2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 10:39:25 2023 InstallationDate: Installed on 2023-07-21 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: b43-fwcutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/2028381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: New Status in nvidia-graphics-drivers-525 source package in Mantic: New Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules
Note the following line in the above log: * dkms: ignore autoinstall errors for dkms modules ** Description changed: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. - In this case, DKMS module build failures should be ignored so that so - that the kernel installation completes. + In this case, DKMS module build failures should be ignored so that the + kernel installation completes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: New Bug description: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules
With the above patch, a dist upgrade with a problematic DKMS module and /etc/dkms/no-autoinstall-errors present looks like: Setting up linux-headers-6.2.0-25-generic (6.2.0-25.25) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-25-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j1 KERNELRELEASE=6.2.0-25-generic -C /lib/modules/6.2.0-25-generic/build M=/var/lib/dkms/evdi/1.12.0+dfsg/build DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.12.0+dfsg not found Error! Bad return status for module build on kernel: 6.2.0-25-generic (x86_64) Consult /var/lib/dkms/evdi/1.12.0+dfsg/build/make.log for more information. dkms autoinstall on 6.2.0-25-generic/x86_64 failed for evdi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: ignore autoinstall errors for dkms modules * dkms: autoinstall for kernel 6.2.0-25-generic ...done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: New Bug description: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules
** Patch added: "dkms_3.0.11-1ubuntu9.debdiff" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+attachment/5687814/+files/dkms_3.0.11-1ubuntu9.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: New Bug description: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
Ok well this is interesting.
It has been over 24 hours (uptime 1 day 15:48hrs) and bug 2 still hasn't
triggered, "Degraded = no".
I probably need this computer today, so I ran `stress -c 1` to try to
force the high temperature power state after running the script to reset
the power values, but with lock set to False. This went onto the ideal
cpu core at 4.8ghz, package temperature spiked up to ~93 degrees C, and
eventually the power parameters dropped to this:
{'backup_rest': 281474976776192,
'locked': False,
'long_term_enabled': True,
'long_term_power': 0.125,
'long_term_time': 28.0,
'short_term_enabled': True,
'short_term_power': 250.0,
'short_term_time': 512.0}
Bug 2 still had not been triggered, cpu was throttled to 400Mhz, so I
reset the power values again this time with lock=True. When I ran
`stress -c 1` it was on the ideal core but now limited to 4.3ghz with a
cpu package temp of ~67.
I ran the grep and get this:
/sys/devices/system/cpu/intel_pstate/hwp_dynamic_boost:0
/sys/devices/system/cpu/intel_pstate/max_perf_pct:90
/sys/devices/system/cpu/intel_pstate/min_perf_pct:10
/sys/devices/system/cpu/intel_pstate/no_turbo:0
/sys/devices/system/cpu/intel_pstate/status:active
--
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/2026658
Title:
CPU frequency governor broken after upgrading from 22.10 to 23.04,
stuck at 400Mhz on Alder Lake
Status in linux package in Ubuntu:
New
Bug description:
I've tried to include as much detail as possible in this bug report, I
originally assembled it just after the release of ubuntu 23.04. There
has been no change since then.
I have had substantial performance problems since updating from ubuntu 22.10
to 23.04.
The computer in question is the 17 inch Razer Blade laptop from 2022 with an
intel i7-12800H.
Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing
has changed.)
This issue occurs regardless of whether the OpenRazer
(https://openrazer.github.io/) drivers etc are installed.
Description of problem:
I have discovered what may be two separate bugs involving low level power
management details on the cpu, they involve the cpu entering different types of
throttled states and never recovering. These issues appeared immediately after
upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with
plenty of thermal headroom, cpu temperatures cannot reach concerning values
except when using stress testing tools.
(I don't know how to propery untangle these two issues, so I'm posting
them as one. I apologize for the review complexity this causes, but I
think posting the information all in one spot is more constructive
here.)
High level testing notes:
- This issue occurs with use of both the intel_pstate driver and the cpufreq
driver. (I don't have the same level of detail for cpufreq, but the issue still
occurs.)
- I have additionally tested a handful of intel_pstate parameters (and
others) via grub kernel command line arguments to no effect. All testing
reported here was done with:
GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau"
GRUB_CMDLINE_LINUX=""
(loading nouveau caused problems for me on 22.10, I have not bothered
reinvestigating it on 23.04)
- There is a firmware update available from the manufacture when I boot into
Windows, I have not installed it (yet).
- - Update: I installed it. No change.
- Changing the cpu governor setting from "powersave" to "performance" using
`cpupower frequency-set -g performance` has no effect. (Note: this action is
separate from the intel_pstate's power-saver/balanced/performance setting
visible with the `powerprofilesctl` utility. It doesn't seem to be a governor
bug.
- - (There is a tertiary issue where I also see substantial (+50%)
performance degredation using the "performance" profile in a test suite I run
constantly for my job; that is clearly a problem but it is an unrelated bug
that has existed for quite some time.)
Summary and my own conclusions:
These are my takeaways, the ~raw data is in the followup section.
Bug 1)
The reported cpu power limits are progressively constrained over time. Once
this failure mode starts the performance never recovers.
- As this situation progresses the observed cpu speeds (I'm using htop)
list as 2800Mhz at idle, but the instant any load at all is placed on a cpu
core that core immediately drops to exactly 400Mhz.
- This situation occurs quite quickly in human terms, frequently within 20
minutes of normal usage after a boot, but it will also occur when the computer
is just sitting there unused for a handful of hours.
- This occurs when using the cpufreq gevernor (by including
"intel_pstate=disable" on the grub command line args.)
- At boot the default value for short_term_time looks wrong to me. This is
the
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
I have implemented a similar workaround to @fatordee: $ sudo smartctl -a /dev/nvme0 (...) Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.00W --0 0 0 00 0 1 + 2.60W --1 1 1 10 0 2 + 1.70W --2 2 2 20 0 3 - 0.0250W --3 3 3 3 50009000 4 - 0.0025W --4 4 4 4 5000 44000 (...) $ cat /etc/default/grub | grep latency GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=9000" I used Ex_Lat from the state right before the last one, as per [1]. It's a less aggressive workaround, as this one just disables the lowest power state, instead of them all. Seems to be working pretty well. [1] https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Controller_failure_due_to_broken_APST_support -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Released Status in Debian: New Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10
[Kernel-packages] [Bug 1981783]
Ubuntu 22.04 Jammy Jellyfish (x86-64) kernel 5.19.0-46-generic Started seeing this error 7/17/2023 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632255] ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] No Local Variables are initialized for Method [_OSC] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632265] Arg0: dc18fbccBuffer(16) 5D A8 3B B2 B7 C8 42 35 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632270] Arg1: 34c27800Integer 0001 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632272] Arg2: 0dc8a41aInteger 0002 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632273] Arg3: 653f1daaBuffer(8) 00 00 00 00 05 00 00 00 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632277] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632278] ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20220331/psparse-529) -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983180]
Ubuntu 22.04 Jammy Jellyfish (x86-64) kernel 5.19.0-46-generic Started seeing this error 7/17/2023 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632255] ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632263] No Local Variables are initialized for Method [_OSC] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632264] Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation) Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632265] Arg0: dc18fbccBuffer(16) 5D A8 3B B2 B7 C8 42 35 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632270] Arg1: 34c27800Integer 0001 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632272] Arg2: 0dc8a41aInteger 0002 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632273] Arg3: 653f1daaBuffer(8) 00 00 00 00 05 00 00 00 Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632277] Jul 17 15:45:50 scott-Precision-7670 kernel: [5.632278] ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20220331/psparse-529) -- 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/1983180 Title: ACPI Error _CPC not found Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: just recently (I guess since the last update) I get a few ACPI error messages during start up. Those are also visible with dmesg: ... [0.713907] ACPI: AC: AC Adapter [AC] (on-line) [0.713978] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [0.714011] ACPI: button: Sleep Button [SLPB] [0.714040] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [0.714061] ACPI: button: Lid Switch [LID] [0.714087] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [0.714105] ACPI: button: Power Button [PWRF] [0.714187] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714199] No Local Variables are initialized for Method [_CPC] [0.714201] No Arguments are initialized for method [_CPC] [0.714203] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714395] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714404] No Local Variables are initialized for Method [_CPC] [0.714405] No Arguments are initialized for method [_CPC] [0.714407] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714488] No Local Variables are initialized for Method [_CPC] [0.714490] No Arguments are initialized for method [_CPC] [0.714492] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714640] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714651] No Local Variables are initialized for Method [_CPC] [0.714653] No Arguments are initialized for method [_CPC] [0.714655] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714940] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714952] No Local Variables are initialized for Method [_CPC] [0.714953] No Arguments are initialized for method [_CPC] [0.714955] ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715106] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715118] No Local Variables are initialized for Method [_CPC] [0.715119] No Arguments are initialized for method [_CPC] [0.715121] ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715309] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715321] No Local Variables are initialized for Method [_CPC] [0.715322] No Arguments are initialized for method [_CPC] [0.715324] ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715611] ACPI BIOS Error (bug): Could not resolve symbol
[Kernel-packages] [Bug 2028374] [NEW] package linux-headers-generic 6.2.0.25.25 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: Update 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic 6.2.0.25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-46-generic. AplayDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: linuxlem 80906 F wireplumber /dev/snd/seq:linuxlem 80903 F pipewire CRDA: N/A Card0.Amixer.info: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'amixer' Card0.Amixer.values: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'amixer' CasperMD5CheckResult: pass Date: Fri Jul 21 15:06:11 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-07-01 (384 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20JES0Y400 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=6a88de4f-2d1c-4dd2-8eb6-c85c0d1a9dcc ro quiet splash snd_hda_intel.dmic_detect=0 vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-generic 6.2.0.25.25 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: Upgraded to lunar on 2023-07-21 (0 days ago) dmi.bios.date: 01/23/2019 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JES0Y400 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN1NET44W(1.31):bd01/23/2019:br1.31:efr1.16:svnLENOVO:pn20JES0Y400:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JES0Y400:rvrSDK0K17763WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20JE_BU_Think_FM_ThinkPadX1Yoga2nd: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JES0Y400 dmi.product.sku: LENOVO_MT_20JE_BU_Think_FM_ThinkPad X1 Yoga 2nd dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2028374 Title: package linux-headers-generic 6.2.0.25.25 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: New Bug description: Update 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic 6.2.0.25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-46-generic. AplayDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: linuxlem 80906 F wireplumber /dev/snd/seq:linuxlem 80903 F pipewire CRDA: N/A Card0.Amixer.info: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'amixer' Card0.Amixer.values: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'amixer' CasperMD5CheckResult: pass Date: Fri Jul 21 15:06:11 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-07-01 (384 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20JES0Y400 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=6a88de4f-2d1c-4dd2-8eb6-c85c0d1a9dcc ro quiet splash snd_hda_intel.dmic_detect=0 vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-generic 6.2.0.25.25 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: Upgraded to lunar on 2023-07-21 (0 days ago) dmi.bios.date: 01/23/2019 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JES0Y400
[Kernel-packages] [Bug 2028365] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2028365 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.2 with kernel 6.2.0-25-generic @ 21/7/2023 After recent updates to kernel 6.2.0-25-generic my intel flickering has returned with the same symptons as in previous bug(s) on ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 Ubuntu loads to desktop and after a few seconds the flickering starts to unusable glitches This bug dissapears when adding the kernel parameter: i915.enable_dc=0 intel_idle.max_cstate=2 On Ubuntu 22.04 the bug was fixed since kernel 5.17.7-051707-generic #202205121146 (mainline) and kernel 5.19.0-28-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-25.25~22.04.2-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 14:21:38 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2028365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
The bug has returned on kernel 6.2 series, i filed a new bug report here: https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-6.2/+bug/2028365 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028366] [NEW] Kernel header installation fails for incompatible DKMS modules
Public bug reported: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that so that the kernel installation completes. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Summary changed: - kernel header installation fails for incompatible DKMS modules + Kernel header installation fails for incompatible DKMS modules -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: New Bug description: If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that so that the kernel installation completes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028365] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
** Attachment added: "Dmesg with the kernel param fix" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2028365/+attachment/5687767/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2028365 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Ubuntu 22.04.2 with kernel 6.2.0-25-generic @ 21/7/2023 After recent updates to kernel 6.2.0-25-generic my intel flickering has returned with the same symptons as in previous bug(s) on ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 Ubuntu loads to desktop and after a few seconds the flickering starts to unusable glitches This bug dissapears when adding the kernel parameter: i915.enable_dc=0 intel_idle.max_cstate=2 On Ubuntu 22.04 the bug was fixed since kernel 5.17.7-051707-generic #202205121146 (mainline) and kernel 5.19.0-28-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-25.25~22.04.2-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 14:21:38 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2028365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028365] [NEW] [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Public bug reported: Ubuntu 22.04.2 with kernel 6.2.0-25-generic @ 21/7/2023 After recent updates to kernel 6.2.0-25-generic my intel flickering has returned with the same symptons as in previous bug(s) on ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 Ubuntu loads to desktop and after a few seconds the flickering starts to unusable glitches This bug dissapears when adding the kernel parameter: i915.enable_dc=0 intel_idle.max_cstate=2 On Ubuntu 22.04 the bug was fixed since kernel 5.17.7-051707-generic #202205121146 (mainline) and kernel 5.19.0-28-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-25.25~22.04.2-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 14:21:38 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2028365 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Ubuntu 22.04.2 with kernel 6.2.0-25-generic @ 21/7/2023 After recent updates to kernel 6.2.0-25-generic my intel flickering has returned with the same symptons as in previous bug(s) on ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 Ubuntu loads to desktop and after a few seconds the flickering starts to unusable glitches This bug dissapears when adding the kernel parameter: i915.enable_dc=0 intel_idle.max_cstate=2 On Ubuntu 22.04 the bug was fixed since kernel 5.17.7-051707-generic #202205121146 (mainline) and kernel 5.19.0-28-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-25.25~22.04.2-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 14:21:38 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2028365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003031] Re: [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only
This issue might be kernel related and not mutter related. I am running kubuntu 23.04 with kde plasma 5.27.4 with kwin under wayland and when plugging in to a usbc to HDMI adapter I received the kernel warning: "adding CRTC not allowed without modesets: requested 0x2, affected 0x3". Machine: Dell XPS 17 9720 (2022) CPU: intel core i9 12900HK GPU: RTX 3060 6GB + intel Xe graphics Nvidia driver: 535.54.03-0ubuntu1 (proprietary) OS: Kubuntu 23.04 (Lunar) Desktop environment: Plasma 5.27.4 Compositor: Wayland Window manager: Kwin kernel: 6.2.0-25-generic Attached is my dmesg output. ** Attachment added: "kern-drm-crash.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003031/+attachment/5687763/+files/kern-drm-crash.log -- 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/2003031 Title: [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only Status in GNOME Shell: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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
[Kernel-packages] [Bug 2028355] Re: erros upon trying to install linux-tools-generic
** Package changed: 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/2028355 Title: erros upon trying to install linux-tools-generic Status in linux package in Ubuntu: New Bug description: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: linux-tools-5.15.0-76 linux-tools-5.15.0-76-generic linux-tools-common The following NEW packages will be installed: linux-tools-5.15.0-76 linux-tools-5.15.0-76-generic linux-tools-common linux-tools-generic 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 8.218 kB of archives. After this operation, 28,2 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-common all 5.15.0-76.83 [276 kB] Get:2 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-5.15.0-76 amd64 5.15.0-76.83 [7.938 kB] Get:3 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-5.15.0-76-generic amd64 5.15.0-76.83 [1.792 B] Get:4 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-generic amd64 5.15.0.76.74 [2.346 B] Fetched 8.218 kB in 2s (4.557 kB/s) Selecting previously unselected package linux-tools-common. (Reading database ... 209100 files and directories currently installed.) Preparing to unpack .../linux-tools-common_5.15.0-76.83_all.deb ... Unpacking linux-tools-common (5.15.0-76.83) ... dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0-76.83_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-nvidia-6.2-tools-common 6.2.0-1003.3~22.04.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package linux-tools-5.15.0-76. Preparing to unpack .../linux-tools-5.15.0-76_5.15.0-76.83_amd64.deb ... Unpacking linux-tools-5.15.0-76 (5.15.0-76.83) ... Selecting previously unselected package linux-tools-5.15.0-76-generic. Preparing to unpack .../linux-tools-5.15.0-76-generic_5.15.0-76.83_amd64.deb ... Unpacking linux-tools-5.15.0-76-generic (5.15.0-76.83) ... Selecting previously unselected package linux-tools-generic. Preparing to unpack .../linux-tools-generic_5.15.0.76.74_amd64.deb ... Unpacking linux-tools-generic (5.15.0.76.74) ... Errors were encountered while processing: /var/cache/apt/archives/linux-tools-common_5.15.0-76.83_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) version.log Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-generic 5.15.0.76.74 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gustavo 866 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jul 21 05:25:41 2023 InstallationDate: Installed on 2023-07-20 (0 days ago) InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Positivo Informatica SA POS-EINM70CS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=82cb161d-9a79-4d63-b8f5-672dbf742716 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-46-generic N/A linux-backports-modules-5.19.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.14 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Desenvolvida por Positivo Informatica SA dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: POS-EINM70CS dmi.board.vendor: Positivo Informatica SA dmi.board.version: POSITIVO dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: POSITIVO dmi.chassis.version: POSITIVO dmi.modalias: dmi:bvnDesenvolvidaporPositivoInformaticaSA:bvr4.6.5:bd08/16/2013:br4.6:svnPositivoInformaticaSA:pnPOS-EINM70CS:pvr3816IPO_POS:rvnPositivoInformaticaSA:rnPOS-EINM70CS:rvrPOSITIVO:cvnPOSITIVO:ct3:cvrPOSITIVO:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: POS-EINM70CS dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3816IPO_POS dmi.sys.vendor: Positivo Informatica SA To manage notifications about this bug go to:
[Kernel-packages] [Bug 2016039] Re: mlxbf-tmfifo: fix potential race
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/2016039 Title: mlxbf-tmfifo: fix potential race Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021749] Re: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
In Progress
Status in lttng-modules package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in lttng-modules source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
In Progress
Status in lttng-modules source package in Kinetic:
Confirmed
Status in linux source package in Lunar:
In Progress
Status in lttng-modules source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
In Progress
Status in lttng-modules package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in lttng-modules source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
In Progress
Status in lttng-modules source package in Kinetic:
Confirmed
Status in linux source package in Lunar:
In Progress
Status in lttng-modules source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
** Changed in: lttng-modules (Ubuntu Kinetic)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
In Progress
Status in lttng-modules package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in lttng-modules source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
In Progress
Status in lttng-modules source package in Kinetic:
Confirmed
Status in linux source package in Lunar:
In Progress
Status in lttng-modules source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto)
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Kinetic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
In Progress
Status in lttng-modules package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in lttng-modules source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
In Progress
Status in lttng-modules source package in Kinetic:
Confirmed
Status in linux source package in Lunar:
In Progress
Status in lttng-modules source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified
# VERIFICATION JAMMY kexec-tools & kernel 5.15 1) On a jammy machine with 184G of memory, installed kexec-tools and kernel 5.15 from proposed and triggered a crash. Crashdump file is generated successfully. root@bigjelly:/var/crash# uname -rv 5.15.0-1043-azure #50-Ubuntu SMP Tue Jul 18 19:20:09 UTC 2023 root@bigjelly:/var/crash# dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.22-2ubuntu2.22.04.1 arm64tools to support fast kexec reboots root@bigjelly:/var/crash# cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" root@bigjelly:/var/crash# ls 202307201513/ dmesg.202307201513 dump.202307201513 root@bigjelly:/var/crash# 2) On a jammy machine with 4G of memory, installed kexec-tools and kernel 5.15 from proposed and triggered a crash. Crashdump file is generated successfully. root@smalljelly:/var/crash# uname -rv 5.15.0-1043-azure #50-Ubuntu SMP Tue Jul 18 19:20:09 UTC 2023 root@smalljelly:/var/crash# dpkg -l | grep kexec-tools ii kexec-tools 1:2.0.22-2ubuntu2.22.04.1 arm64tools to support fast kexec reboots root@smalljelly:/var/crash# cat /etc/default/grub.d/ 40-force-partuuid.cfg 50-cloudimg-settings.cfg init-select.cfg kdump-tools.cfg root@smalljelly:/var/crash# cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=320M" root@smalljelly:/var/crash# ls 202307210759/ dmesg.202307210759 dump.202307210759 root@smalljelly:/var/crash# ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Committed Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. 1) Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. 2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
[Kernel-packages] [Bug 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: Triaged Status in linux-hwe-5.19 package in Ubuntu: Won't Fix Status in linux-hwe-6.2 package in Ubuntu: New Status in linux source package in Lunar: In Progress Bug description: SRU Justification: [ Impact ] On systems that have the following combination of hardware 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ No output when connecting a display to the BMC's VGA port. [ Fix ] For AST2500+ MMIO should be enabled by default. [ Test Plan ] Test on targeted hardware to make sure BMC is displaying output. [ Where problems could occur ] Not aware of any potential problems, but any should be confined to ASPEED AST2500+ hardware. [ Other Info ] Patch is already in jammy/nvidia-5.19 and jammy/nvidia-6.2 and has been tested with affected BMC. [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6=4327a6137ed43a091d900b1ac833345d60f32228 [Action] Please apply the following two backports to the appropriate Ubuntu HWE kernels: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part
@mjrosato Many thx for this successful kernel verification! (I'll cross-reference this as fyi to the qemu bug, too.) -- 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/1853306 Title: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * Currently the PCI passthrough implementation for s390x is based on intercepting PCI I/O instructions, which leads to a reduced I/O performance compared to the execution of PCI instructions directly in LPAR. * Hence users may face I/O bottlenecks when using PCI devices in passthrough mode based on the current implementation. * For avoiding this and to improve performance, the interpretive execution of the PCI store and PCI load instructions get enabled. * A further improvement is achieved by enabling the Adapter-Event-Notification Interpretation (AENI). * Since LTS releases are the main focus for stable and long running KVM workloads, it is highly desired to get this backported to the jammy kernel (and because the next LTS is still some time away). [ Test Plan ] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only avaialble on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusuable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) Testing will include the following scenarios specifically for ISM devices: 1) Testing of SMC-D v1 fallback: Using 2 ISM devices on the same VCHID that share a PNETID, create 2 guests and pass one ISM device via vfio-pci device to each guest. Establish TCP connectivity between the 2 guests using the libvirt default network, and then use smc_run (https://manpages.ubuntu.com/manpages/jammy/man8/smc_run.8.html) to run an iperf workload between the 2 guests (will include both short workloads and longer-running workloads). Verify that SMC-D transfer was used between the guests instead of TCP via 'smcd stats' (https://manpages.ubuntu.com/manpages/jammy/man8/smcd.8.html) 2) Testing of SMC-D v2: Same as above, but using 2 ISM devices on the same VCHID that have no PNETID specified Testing will include the following scenarios specifically for RoCE devices: 1) Ping testing: Using 2 RoCE VFs that share a common network, create 2 guests and pass one RoCE device to each guest. Assign IP addresses within each guest to the associated TCP interface, perform a
[Kernel-packages] [Bug 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
I believe with dkms, you need a C compiler and related tools, so that the nvidia kernel module can be built on your machine during kernel / driver updates. So that probably means more packages have to be installed. It might also be a bit more error-prone? I'm not sure if it could affect secure boot in some way, I believe there is some mechanism to self-sign the modules after building them. I don't use secure boot. So it's not a huge issue. I do prefer using the pre-built kernel modules from linux-modules-nvidia-* though. Currently, I'm on 6.2.0-24 and nvidia-525 which seems to work without dkms and without issues. When a new linux-restricted-modules package like 6.2.0-27.28 is published, I'll try to update to nividia-535. -- 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/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.15/5.15.0.1041.46~20.04.30)
All autopkgtests for the newly accepted linux-meta-aws-5.15 (5.15.0.1041.46~20.04.30) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.22 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028205] Re: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure can be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. If this does resolve your bug please set its status to Invalid. Thanks in advance! ** Tags added: kern-7481 ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2028205 Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut Status in linux-firmware package in Ubuntu: Incomplete Bug description: Fresh install, first login. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hackan 1964 F wireplumber /dev/snd/seq:hackan 1952 F pipewire CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jul 19 23:10:46 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut InstallationDate: Installed on 2023-07-19 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IwConfig: lono wireless extensions. enp2s0f0 no wireless extensions. MachineType: Apple Inc. Macmini5,1 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 135.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvr135.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:skuSystemSKU#: dmi.product.family: Macmini dmi.product.name: Macmini5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2028205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028268] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r
uilding module: Cleaning build area... make -j2 KERNELRELEASE=6.2.0-25-generic -f Makefile.kmods KSRC=/lib/modules/6.2.0-25-generic/build KVER=6.2.0-25-generic...(bad exit status: 2) ERROR (dkms apport): binary package for parallels-tools: 1.8.2.23832 not found Error! Bad return status for module build on kernel: 6.2.0-25-generic (aarch64) Consult /var/lib/dkms/parallels-tools/1.8.2.23832/build/make.log for more information. dkms autoinstall on 6.2.0-25-generic/aarch64 failed for parallels-tools(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028268 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: upgrading OS ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2293 F pipewire parallels 2296 F wireplumber /dev/snd/pcmC0D0p: parallels 2293 F...m pipewire /dev/snd/seq:parallels 2293 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 14:41:04 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (377 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-07-20 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028268] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r
You have an unsupported DKMS module installed. Please remove it and retry the upgrade: $ dkms remove parallels-tools/1.8.2.23832 --all ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028268 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: upgrading OS ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17 Uname: Linux 5.19.0-46-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parallels 2293 F pipewire parallels 2296 F wireplumber /dev/snd/pcmC0D0p: parallels 2293 F...m pipewire /dev/snd/seq:parallels 2293 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 20 14:41:04 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-07 (377 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release arm64 (20220421) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=5a14ccf7-6bac-47b7-a3d6-6c10822fb10d ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-07-20 (0 days ago) acpidump: dmi.bios.date: Mon, 27 Mar 2023 17:35:19 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 1.8.2 (23832) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr1.8.2(23832):bdMon,27Mar2023173519:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023638] Re: Various backlight issues with the 6.0/6.1 kernel
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0/6.1 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025195] Re: HDMI output with More than one child device for port B in VBT error
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025195 Title: HDMI output with More than one child device for port B in VBT error Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 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 source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] From the bug report[1], skip the return workaround the issue, so I created the DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
