[Kernel-packages] [Bug 2064560] [NEW] kernel panic with linux-intel-iotg 5.15.0.1056.56
Public bug reported: During the SRU testing for linux-intel-iotg 5.15.0.1056.56, Intel ADL-PS went into kernel panic. There are no journal logs existed. Please check screenshot attached. https://certification.canonical.com/hardware/202212-30962/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "intel-iotg.jpg" https://bugs.launchpad.net/bugs/2064560/+attachment/5773888/+files/intel-iotg.jpg -- 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/2064560 Title: kernel panic with linux-intel-iotg 5.15.0.1056.56 Status in linux package in Ubuntu: New Bug description: During the SRU testing for linux-intel-iotg 5.15.0.1056.56, Intel ADL- PS went into kernel panic. There are no journal logs existed. Please check screenshot attached. https://certification.canonical.com/hardware/202212-30962/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064560/+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 2064561] [NEW] Focal update: v5.4.273 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.4.273 upstream stable release
from git://git.kernel.org/
io_uring/unix: drop usage of io_uring socket
io_uring: drop any code related to SCM_RIGHTS
selftests: tls: use exact comparison in recv_partial
ASoC: rt5645: Make LattePanda board DMI match more precise
x86/xen: Add some null pointer checking to smp.c
MIPS: Clear Cause.BD in instruction_pointer_set
HID: multitouch: Add required quirk for Synaptics 0xcddc device
RDMA/mlx5: Relax DEVX access upon modify commands
net/iucv: fix the allocation size of iucv_path_table array
parisc/ftrace: add missing CONFIG_DYNAMIC_FTRACE check
block: sed-opal: handle empty atoms when parsing response
dm-verity, dm-crypt: align "struct bvec_iter" correctly
btrfs: fix data race at btrfs_use_block_rsv() when accessing block reserve
scsi: mpt3sas: Prevent sending diag_reset when the controller is ready
Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security
firewire: core: use long bus reset on gap count error
ASoC: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet
Input: gpio_keys_polled - suppress deferred probe error for gpio
ASoC: wm8962: Enable oscillator if selecting WM8962_FLL_OSC
ASoC: wm8962: Enable both SPKOUTR_ENA and SPKOUTL_ENA in mono mode
ASoC: wm8962: Fix up incorrect error message in wm8962_set_fll
do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak
fs/select: rework stack allocation hack for clang
aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
timekeeping: Fix cross-timestamp interpolation on counter wrap
timekeeping: Fix cross-timestamp interpolation corner case decision
timekeeping: Fix cross-timestamp interpolation for non-x86
wifi: ath10k: fix NULL pointer dereference in
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()
b43: dma: Fix use true/false for bool type variable
wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled
wifi: b43: Stop/wake correct queue in PIO Tx path when QoS is disabled
b43: main: Fix use true/false for bool type
wifi: b43: Stop correct queue in DMA worker when QoS is disabled
wifi: b43: Disable QoS for bcm4331
wifi: wilc1000: fix declarations ordering
wifi: wilc1000: fix RCU usage in connect path
wifi: mwifiex: debugfs: Drop unnecessary error check for debugfs_create_dir()
sock_diag: annotate data-races around sock_diag_handlers[family]
af_unix: Annotate data-race of gc_in_progress in wait_for_unix_gc().
net: blackhole_dev: fix build warning for ethh set but not used
wifi: libertas: fix some memleaks in lbs_allocate_cmd_buffer()
arm64: dts: mediatek: mt7622: add missing "device_type" to memory nodes
bpf: Add typecast to bpf helpers to help BTF generation
bpf: Factor out bpf_spin_lock into helpers.
bpf: Mark bpf_spin_{lock,unlock}() helpers with notrace correctly
arm64: dts: qcom: db820c: Move non-soc entries out of /soc
arm64: dts: qcom: msm8996: Use node references in db820c
arm64: dts: qcom: msm8996: Move regulator consumers to db820c
arm64: dts: qcom: msm8996: Pad addresses
ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()
bus: tegra-aconnect: Update dependency to ARCH_TEGRA
UBUNTU: [Config]: Update tegra configs
iommu/amd: Mark interrupt as managed
wifi: brcmsmac: avoid function pointer casts
net: ena: Remove ena_select_queue
ARM: dts: arm: realview: Fix development chip ROM compatible value
ARM: dts: imx6dl-yapp4: Move phy reset into switch node
ARM: dts: imx6dl-yapp4: Fix typo in the QCA switch register address
ARM: dts: imx6dl-yapp4: Move the internal switch PHYs under the switch node
ACPI: scan: Fix device check notification handling
x86, relocs: Ignore relocations in .notes section
SUNRPC: fix some memleaks in gssx_dec_option_array
mmc: wmt-sdmmc: remove an incorrect release_mem_region() call in the .remove
function
igb: move PEROUT and EXTTS isr logic to separate functions
igb: Fix missing time sync events
Bluetooth: Remove superfluous call to hci_conn_check_pending()
Bluetooth: hci_core: Fix possible buffer overflow
sr9800: Add check for usbnet_get_endpoints
bpf: Fix hashtab overflow check on 32-bit arches
bpf: Fix stackmap overflow check on 32-bit arches
ipv6: fib6_rules: flush route cache when rule is changed
net: ip_tunnel: make sure to pull inner header in ip_tunnel_rcv()
net: hns3: fix port duplex configure error in IMP reset
tcp: fix incorrect parameter validation in the do_tcp_getsockopt() function
l2tp: fix incorrect parameter validation in the pppol2tp_getsockopt() function
udp: fix incorrect parameter validation in the udp_lib_getsockopt()
[Kernel-packages] [Bug 1929048] Re: Speed up resume time on HP laptops
Paul, As the commit message described, the resume overhead was reduced for around 2 seconds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1929048 Title: Speed up resume time on HP laptops Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Some HP laptops can take very long time to resume from sleep. [Fix] Avoid evaluating _INI on resume. It's only needed to run once at boot. [Test] Suspend and resume the system. With the patch applied, the system resumes in a blink. [Where problems could occur] Maybe there are some platforms require the old behavior, so hp-accel can break after system resume. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929048/+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 2064555] [NEW] Focal update: v5.4.272 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.4.272 upstream stable release
from git://git.kernel.org/
lan78xx: Fix white space and style issues
lan78xx: Add missing return code checks
lan78xx: Fix partial packet errors on suspend/resume
lan78xx: Fix race conditions in suspend/resume handling
net: lan78xx: fix runtime PM count underflow on link stop
ixgbe: {dis, en}able irqs in ixgbe_txrx_ring_{dis, en}able
geneve: make sure to pull inner header in geneve_rx()
net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink()
net/ipv6: avoid possible UAF in ip6_route_mpath_notify()
net/rds: fix WARNING in rds_conn_connect_if_down
netfilter: nft_ct: fix l3num expectations with inet pseudo family
netfilter: nf_conntrack_h323: Add protection for bmp length out of range
netrom: Fix a data-race around sysctl_netrom_default_path_quality
netrom: Fix a data-race around sysctl_netrom_obsolescence_count_initialiser
netrom: Fix data-races around sysctl_netrom_network_ttl_initialiser
netrom: Fix a data-race around sysctl_netrom_transport_timeout
netrom: Fix a data-race around sysctl_netrom_transport_maximum_tries
netrom: Fix a data-race around sysctl_netrom_transport_acknowledge_delay
netrom: Fix a data-race around sysctl_netrom_transport_busy_delay
netrom: Fix a data-race around sysctl_netrom_transport_requested_window_size
netrom: Fix a data-race around sysctl_netrom_transport_no_activity_timeout
netrom: Fix a data-race around sysctl_netrom_routing_control
netrom: Fix a data-race around sysctl_netrom_link_fails_count
netrom: Fix data-races around sysctl_net_busy_read
selftests: mm: fix map_hugetlb failure on 64K page size systems
um: allow not setting extra rpaths in the linux binary
serial: max310x: Use devm_clk_get_optional() to get the input clock
serial: max310x: Try to get crystal clock rate from property
serial: max310x: fail probe if clock crystal is unstable
serial: max310x: Make use of device properties
serial: max310x: use regmap methods for SPI batch operations
serial: max310x: use a separate regmap for each port
serial: max310x: prevent infinite while() loop in port startup
Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU
hv_netvsc: Make netvsc/VF binding check both MAC and serial number
hv_netvsc: use netif_is_bond_master() instead of open code
hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed
y2038: rusage: use __kernel_old_timeval
getrusage: add the "signal_struct *sig" local variable
getrusage: move thread_group_cputime_adjusted() outside of lock_task_sighand()
getrusage: use __for_each_thread()
getrusage: use sig->stats_lock rather than lock_task_sighand()
serial: max310x: Unprepare and disable clock in error path
regmap: allow to define reg_update_bits for no bus configuration
regmap: Add bulk read/write callbacks into regmap_config
serial: max310x: make accessing revision id interface-agnostic
serial: max310x: implement I2C support
serial: max310x: fix IO data corruption in batched operations
arm64: dts: qcom: add PDC interrupt controller for SDM845
arm64: dts: qcom: sdm845: fix USB DP/DM HS PHY interrupts
Linux 5.4.272
UBUNTU: Upstream stable to v5.4.272
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Portia Stephens (portias)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Portia Stephens (portias)
** Description changed:
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.4.272 upstream stable release
from git://git.kernel.org/
-
+ lan78xx: Fix white space and style issues
+ lan78xx:
[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
** Changed in: linux (Ubuntu) Status: In Progress => 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/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic Status in linux package in Ubuntu: Triaged Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 2064549] [NEW] pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
Public bug reported:
The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.
This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:
- SCR_SEC_REN + SCR_SEC_WEN both set
or
- SCR_SEC_REN + SCR_SEC_WEN both set and
SCR_SEC_G1R + SCR_SEC_G1W both set
Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2064549
Title:
pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin
permission before access.")
Status in linux-nvidia package in Ubuntu:
New
Bug description:
The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.
This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:
- SCR_SEC_REN + SCR_SEC_WEN both set
or
- SCR_SEC_REN + SCR_SEC_WEN both set and
SCR_SEC_G1R + SCR_SEC_G1W both set
Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2064549/+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 2055241] Re: Update on-chip oscillator clock nodes for Kria
@Sagar - thanks, I've updated the tags. In the future, "If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx- zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] * Changes are pulled from Xilinx' 6.6 tree https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+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 2058321] Re: Unsupported platform 'ZynqMP KV260 revB
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: Invalid Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2055241] Re: Update on-chip oscillator clock nodes for Kria
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] * Changes are pulled from Xilinx' 6.6 tree https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+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 2058707] Re: Backport AXI 1-wire host driver
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1995465 Title: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security. Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] Enable all configs checked in ubuntu_qrt_kernel_security. [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/1995465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 2055237] Re: Backport ps uart RS485 driver
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055237 Title: Backport ps uart RS485 driver Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Incomplete Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * Backports support for rs485 to the uartps driver from the tty staging tree [ Test Plan ] * Testing is needed to ensure this doesn't break the serial console on current platforms. QA will develop a new automated test to be integrated into cert testing * Testing of the RS485 port will be integrated into the cert testing for the KD240 [ Where problems could occur ] * The patches have not landed in mainline and are being pulled from the maintainers tree. There is a risk they will be rejected from mainline. [ Other info ] * The following 3 patches are required from the tty-dev tree. All other patches were pulled in to support the backport. 1. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=32152467ffac3b79eae7313959c310946b0e6072 2. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=74231ab6cc2d02303ddf1fabd878756c52f788a5 3. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=fccc9d9233f918ee50cf2955ae7134a7f3418351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055237/+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 2064483] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773809/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773806/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773802/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773804/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773803/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773800/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773798/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773797/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773808/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773807/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773794/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773793/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773805/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] Re: Ubuntu 24.04 doesn't respect vm.swappiness
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: Ubuntu Noble Importance: Undecided Status: New ** No longer affects: ubuntu ** No longer affects: Ubuntu Noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773801/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773799/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773796/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773795/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin- guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:archerallstars F pipewire /dev/snd/controlC0: archerallstars 4448 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-27 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Acer Swift SF514-52T NonfreeKernelModules: zfs Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 11/26/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Carlsberg_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-52T dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064483/+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 2064483] Re: Ubuntu 24.04 doesn't respect vm.swappiness
apport information ** Tags added: apport-collected noble wayland-session ** Description changed: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like mine, see kernel docs: https://docs.kernel.org/admin-guide/sysctl/vm.html#swappiness This is my main workstation (laptop). I used to run openSUSE Tumbleweed on it (~2 years). The experience with `vm.swappiness` is totally different. --- Here's my zRAM script: ``` #!/bin/bash mem_total_kb=$(grep MemTotal /proc/meminfo | grep -E --only-matching '[[:digit:]]+') mem_total=$((mem_total_kb * 1536)) modprobe zram echo zstd > /sys/block/zram0/comp_algorithm; echo $mem_total > /sys/block/zram0/disksize mkswap /dev/zram0 swapon -p 100 /dev/zram0 ``` Here's the content of my /etc/sysctl.conf ``` vm.swappiness=180 vm.page-cluster=0 vm.watermark_scaling_factor=125 vm.watermark_boost_factor=0 ``` I make a fresh install, not upgrading from the previous release. I also upload the screen recording of this issue on my personal Proton drive here: https://drive.proton.me/urls/5KTCS1DF58#qZTscuv5XE0M - I mount ~/ramtest in the RAM, then copy the system's usr folder to - ~/ramtest. Since most contents in usr are compressible, it should be - perfect to show this issue. + I mount ~/ramtest in the RAM, then copy the system's usr folder to ~/ramtest. Since most contents in usr are compressible, it should be perfect to show this issue. + --- + ProblemType: Bug + ApportVersion: 2.28.1-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/seq:archerallstars F pipewire + /dev/snd/controlC0: archerallstars 4448 F wireplumber + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 24.04 + InstallationDate: Installed on 2024-04-27 (5 days ago) + InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) + MachineType: Acer Swift SF514-52T + NonfreeKernelModules: zfs + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_o799y4@/vmlinuz-6.8.0-31-generic root=ZFS=rpool/ROOT/ubuntu_o799y4 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-6.8.0-31-generic N/A + linux-backports-modules-6.8.0-31-generic N/A + linux-firmware20240318.git3b128b60-0ubuntu2 + Tags: noble wayland-session + Uname: Linux 6.8.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users + _MarkForUpload: True + dmi.bios.date: 11/26/2018 + dmi.bios.release: 1.11 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V1.11 + dmi.board.name: Carlsberg_KL + dmi.board.vendor: KBL + dmi.board.version: V1.11 + dmi.chassis.type: 10 + dmi.chassis.vendor: Acer + dmi.chassis.version: V1.11 + dmi.ec.firmware.release: 1.5 + dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/26/2018:br1.11:efr1.5:svnAcer:pnSwiftSF514-52T:pvrV1.11:rvnKBL:rnCarlsberg_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:sku: + dmi.product.family: Swift 5 + dmi.product.name: Swift SF514-52T + dmi.product.sku: + dmi.product.version: V1.11 + dmi.sys.vendor: Acer + modified.conffile..etc.default.apport: + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 + mtime.conffile..etc.default.apport: 2024-04-27T05:52:33.862578 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2064483/+attachment/5773792/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064483 Title: Ubuntu 24.04 doesn't respect vm.swappiness Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: My sysctl vm.swappiness returns vm.swappiness = 180. Swap kicked in when RAM is filled around 95%. I’m using zRAM as the swap. When this happened, my laptop is barely usable, as the system would have to do both the swap and compression at the same time. If `vm.swappiness = 180` worked as intended, the issue wouldn't have happened, as the swap would kick in early, which is good for zRAM system like
[Kernel-packages] [Bug 2064291] Re: Ubuntu 24.04 crashed multiple times
** Attachment added: "apport.log.1.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+attachment/5773787/+files/apport.log.1.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064291 Title: Ubuntu 24.04 crashed multiple times Status in linux package in Ubuntu: New Bug description: Ubuntu 24.04 crashed multiple times due to unstable kernel. Crashed 8 times attempting to file this bug report. Recently installed the new updates for 24.04. Steps to reproduce: Open "Show Apps"-Crash, Open Firefox -Crash, Open Terminal -Crash, Setting idle does not crash. Installed synaptic -Crashed 2 times. Check for broken packages - None, no missing dependencies. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:b3 1256 F pipewire /dev/snd/controlC0: b3 1260 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 09:07:32 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=381f85c9-ec76-4686-aaa1-aa5e3673ec82 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+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 2064291] Re: Ubuntu 24.04 crashed multiple times
** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+attachment/5773786/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064291 Title: Ubuntu 24.04 crashed multiple times Status in linux package in Ubuntu: New Bug description: Ubuntu 24.04 crashed multiple times due to unstable kernel. Crashed 8 times attempting to file this bug report. Recently installed the new updates for 24.04. Steps to reproduce: Open "Show Apps"-Crash, Open Firefox -Crash, Open Terminal -Crash, Setting idle does not crash. Installed synaptic -Crashed 2 times. Check for broken packages - None, no missing dependencies. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:b3 1256 F pipewire /dev/snd/controlC0: b3 1260 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 09:07:32 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=381f85c9-ec76-4686-aaa1-aa5e3673ec82 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+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 2064291] Re: Ubuntu 24.04 crashed multiple times
** Attachment added: "kern.log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+attachment/5773785/+files/kern.log.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064291 Title: Ubuntu 24.04 crashed multiple times Status in linux package in Ubuntu: New Bug description: Ubuntu 24.04 crashed multiple times due to unstable kernel. Crashed 8 times attempting to file this bug report. Recently installed the new updates for 24.04. Steps to reproduce: Open "Show Apps"-Crash, Open Firefox -Crash, Open Terminal -Crash, Setting idle does not crash. Installed synaptic -Crashed 2 times. Check for broken packages - None, no missing dependencies. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:b3 1256 F pipewire /dev/snd/controlC0: b3 1260 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 09:07:32 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=381f85c9-ec76-4686-aaa1-aa5e3673ec82 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
The fix for me is to edit the kernel options before booting and removing splash and quiet. Boots after that. https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share_medium=web3x_name=web3xcss_term=1_content=share_button https://askubuntu.com/questions/477821/how-can-i-permanently-remove-the- boot-option-quiet-splash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064530] Re: Include support for .NET 8 for Ubuntu on Power
** Package changed: linux (Ubuntu) => dotnet8 (Ubuntu) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: dotnet8 (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064530 Title: Include support for .NET 8 for Ubuntu on Power Status in The Ubuntu-power-systems project: New Status in dotnet8 package in Ubuntu: New Bug description: == Comment: #0 - JAMIE L. DOLAN - 2024-05-01 12:19:47 == This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04 - This has already been added for s390x - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+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 2059316] Re: backport arm64 THP improvements from 6.9
** Also affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-nvidia (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059316 Title: backport arm64 THP improvements from 6.9 Status in linux package in Ubuntu: In Progress Status in linux-nvidia package in Ubuntu: New Status in linux source package in Noble: New Status in linux-nvidia source package in Noble: New Bug description: Initial support for multi-size THP landed upstream in v6.8. In the 6.9 merge window, 2 other series have landed that show significant performance improvements on arm64 mm/memory: optimize fork() with PTE-mapped THP https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.html Transparent Contiguous PTEs for User Mappings: https://lwn.net/Articles/962330/ On an Ampere AltraMax system w/ 4K page size, kernel builds in a tmpfs are reduced from 6m30s to 5m17s, a ~19% improvement. It has been reported that this can have a *10x* improvement for certain GPU workloads on ARM: https://lwn.net/Articles/954094/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+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 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker (LP: #2063265) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - [Packaging] Remove renamed out-of-tree sound drivers from blacklist [ Ubuntu: 5.15.0-1025.25 ] * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Wed, 24 Apr 2024 08:55:41 -0500 -- 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/2056486 Title: apply nvidia-tegra patches 2024 Mar 1-7 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+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 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25 --- linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Tue, 23 Apr 2024 15:45:58 -0500 ** Changed in: linux-nvidia-tegra (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- 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/2055468 Title: apply nvidia-tegra patches 2024 Feb 6-29 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+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 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker (LP: #2063265) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - [Packaging] Remove renamed out-of-tree sound drivers from blacklist [ Ubuntu: 5.15.0-1025.25 ] * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Wed, 24 Apr 2024 08:55:41 -0500 -- 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/2055468 Title: apply nvidia-tegra patches 2024 Feb 6-29 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+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 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25 --- linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Tue, 23 Apr 2024 15:45:58 -0500 ** Changed in: linux-nvidia-tegra (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- 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/2056486 Title: apply nvidia-tegra patches 2024 Mar 1-7 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+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 2056594] Re: apply nvidia-tegra patches 2024 Mar 8
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker (LP: #2063265) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - [Packaging] Remove renamed out-of-tree sound drivers from blacklist [ Ubuntu: 5.15.0-1025.25 ] * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Wed, 24 Apr 2024 08:55:41 -0500 -- 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/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+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 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25 --- linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Tue, 23 Apr 2024 15:45:58 -0500 ** Changed in: linux-nvidia-tegra (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- 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/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+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 2056594] Re: apply nvidia-tegra patches 2024 Mar 8
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25 --- linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Tue, 23 Apr 2024 15:45:58 -0500 ** Changed in: linux-nvidia-tegra (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- 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/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+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 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker (LP: #2063265) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - [Packaging] Remove renamed out-of-tree sound drivers from blacklist [ Ubuntu: 5.15.0-1025.25 ] * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Wed, 24 Apr 2024 08:55:41 -0500 -- 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/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+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 2058706] Re: Tegra234 SD card corruption after rebooting some number of times
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker (LP: #2063265) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - [Packaging] Remove renamed out-of-tree sound drivers from blacklist [ Ubuntu: 5.15.0-1025.25 ] * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Wed, 24 Apr 2024 08:55:41 -0500 ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Released -- 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/2058706 Title: Tegra234 SD card corruption after rebooting some number of times Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: The SD card is being observed to get corrupted after some number of reboots, e.g. often in the neighborhood of 10-50 iterations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058706/+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 2059958] Re: Include networking drivers used on Tegra platforms in initrd.img
This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed - 5.15.0-1012.12 --- linux-nvidia-tegra-igx-modules-signed (5.15.0-1012.12) jammy; urgency=medium * Master version: 5.15.0-1012.12 -- Jacob Martin Wed, 24 Apr 2024 10:31:47 -0500 ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059958 Title: Include networking drivers used on Tegra platforms in initrd.img Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Bug description: A race occurs between the probing of network devices and systemd- networkd detecting network devices to enable. This can be avoided by loading networking drivers earlier in the boot process, which we accomplish by including them in the initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2059958/+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 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx
This bug was fixed in the package linux-meta-nvidia-tegra-igx - 5.15.0.1012.12 --- linux-meta-nvidia-tegra-igx (5.15.0.1012.12) jammy; urgency=medium * Bump ABI 5.15.0-1012 * Add initial r36.3 out-of-tree module meta packages (LP: #2060071) - [Packaging] Add conflicts against r36.x branch metas -- Jacob Martin Wed, 24 Apr 2024 10:30:22 -0500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059968 Title: Produce kernel snaps for linux-nvidia-tegra-igx Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Status in linux-signed-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: We plan on producing Ubuntu Core images with the linux-nvidia-tegra- igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx
This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed - 5.15.0-1012.12 --- linux-nvidia-tegra-igx-modules-signed (5.15.0-1012.12) jammy; urgency=medium * Master version: 5.15.0-1012.12 -- Jacob Martin Wed, 24 Apr 2024 10:31:47 -0500 ** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059968 Title: Produce kernel snaps for linux-nvidia-tegra-igx Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Status in linux-signed-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: We plan on producing Ubuntu Core images with the linux-nvidia-tegra- igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2060071] Re: Add initial r36.3 out-of-tree module meta packages
This bug was fixed in the package linux-meta-nvidia-tegra-igx - 5.15.0.1012.12 --- linux-meta-nvidia-tegra-igx (5.15.0.1012.12) jammy; urgency=medium * Bump ABI 5.15.0-1012 * Add initial r36.3 out-of-tree module meta packages (LP: #2060071) - [Packaging] Add conflicts against r36.x branch metas -- Jacob Martin Wed, 24 Apr 2024 10:30:22 -0500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2060071 Title: Add initial r36.3 out-of-tree module meta packages Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Bug description: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2060071/+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 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx
This bug was fixed in the package linux-signed-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-signed-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * Main version: 5.15.0-1012.12 * Packaging resync (LP: #1786013) - [Packaging] debian/tracking-bug -- resync from main package -- Jacob Martin Wed, 24 Apr 2024 10:30:12 -0500 ** Changed in: linux-signed-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059968 Title: Produce kernel snaps for linux-nvidia-tegra-igx Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Status in linux-signed-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: We plan on producing Ubuntu Core images with the linux-nvidia-tegra- igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2060071] Re: Add initial r36.3 out-of-tree module meta packages
This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed - 5.15.0-1012.12 --- linux-nvidia-tegra-igx-modules-signed (5.15.0-1012.12) jammy; urgency=medium * Master version: 5.15.0-1012.12 -- Jacob Martin Wed, 24 Apr 2024 10:31:47 -0500 ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2060071 Title: Add initial r36.3 out-of-tree module meta packages Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Bug description: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2060071/+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 2060337] Re: apply NVIDIA patches Mar 22 - April 5, 2024
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker (LP: #2063265) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - [Packaging] Remove renamed out-of-tree sound drivers from blacklist [ Ubuntu: 5.15.0-1025.25 ] * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Wed, 24 Apr 2024 08:55:41 -0500 -- 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/2060337 Title: apply NVIDIA patches Mar 22 - April 5, 2024 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: NVIDIA patches Mar 22 - April 5, 2024. NVIDIA tracking details soc/tegra: fuse: Remove security_mode fuse from keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228 soc/tegra: fuse: Update Tegra234 nvmem keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227 arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255 arm64: defconfig: Enable DMATEST https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125 PCI: tegra194: Fix probe path for Endpoint mode https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622 arm64: configs: enable hidraw https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2060337/+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 2060337] Re: apply NVIDIA patches Mar 22 - April 5, 2024
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25 --- linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Tue, 23 Apr 2024 15:45:58 -0500 ** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Released -- 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/2060337 Title: apply NVIDIA patches Mar 22 - April 5, 2024 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: NVIDIA patches Mar 22 - April 5, 2024. NVIDIA tracking details soc/tegra: fuse: Remove security_mode fuse from keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228 soc/tegra: fuse: Update Tegra234 nvmem keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227 arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255 arm64: defconfig: Enable DMATEST https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125 PCI: tegra194: Fix probe path for Endpoint mode https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622 arm64: configs: enable hidraw https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2060337/+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 2061900] Re: apply NVIDIA patches April 6-16, 2024
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1012.12 --- linux-nvidia-tegra-igx (5.15.0-1012.12) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1012.12 -proposed tracker (LP: #2063265) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - [Packaging] Remove renamed out-of-tree sound drivers from blacklist [ Ubuntu: 5.15.0-1025.25 ] * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Wed, 24 Apr 2024 08:55:41 -0500 -- 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/2061900 Title: apply NVIDIA patches April 6-16, 2024 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply NVIDIA patches April 6-16, 2024: NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016 NVIDIA: SAUCE: enable handling of macronix block protection https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006 PCI: dwc: Restore MSI Receiver mask during resume https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2061900/+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 2061900] Re: apply NVIDIA patches April 6-16, 2024
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1025.25 --- linux-nvidia-tegra (5.15.0-1025.25) jammy; urgency=medium * jammy/linux-nvidia-tegra: 5.15.0-1025.25 -proposed tracker (LP: #2063258) * apply NVIDIA patches April 6-16, 2024 (LP: #2061900) - NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 - NVIDIA: SAUCE: enable handling of macronix block protection - PCI: dwc: Restore MSI Receiver mask during resume * apply NVIDIA patches Mar 22 - April 5, 2024 (LP: #2060337) - NVIDIA: SAUCE: arm64: configs: enable hidraw - NVIDIA: SAUCE: PCI: tegra194: Fix probe path for Endpoint mode - NVIDIA: SAUCE: arm64: defconfig: Enable DMATEST - NVIDIA: SAUCE: arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module - NVIDIA: SAUCE: soc/tegra: fuse: Update Tegra234 nvmem keepout list - NVIDIA: SAUCE: soc/tegra: fuse: Remove security_mode fuse from keepout list - [Config] Enable DMATEST -- Jacob Martin Tue, 23 Apr 2024 15:45:58 -0500 ** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Released -- 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/2061900 Title: apply NVIDIA patches April 6-16, 2024 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: Apply NVIDIA patches April 6-16, 2024: NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016 NVIDIA: SAUCE: enable handling of macronix block protection https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006 PCI: dwc: Restore MSI Receiver mask during resume https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2061900/+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 2064530] Re: Include support for .NET 8 for Ubuntu on Power
Was this filed against the correct package? https://launchpad.net/ubuntu/+source/dotnet8 looks more appropriate. It's a pity this request wasn't made two months ago, 24.04's Feature Freeze date was February 29 https://discourse.ubuntu.com/t/noble-numbat- release-schedule/35649 -- it might have been trivial then, I don't know what the path is for this now, but it won't be as quick and easy. I suggest working on a debdiff for the dotnet8 package to get it to build and pass the test suites etc. Thanks -- 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/2064530 Title: Include support for .NET 8 for Ubuntu on Power Status in linux package in Ubuntu: New Bug description: == Comment: #0 - JAMIE L. DOLAN - 2024-05-01 12:19:47 == This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04 - This has already been added for s390x - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064530/+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 2064530] [NEW] Include support for .NET 8 for Ubuntu on Power
Public bug reported: == Comment: #0 - JAMIE L. DOLAN - 2024-05-01 12:19:47 == This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04 - This has already been added for s390x - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-206154 severity-medium targetmilestone-inin2404 ** Tags added: architecture-ppc64le bugnameltc-206154 severity-medium targetmilestone-inin2404 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** 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/2064530 Title: Include support for .NET 8 for Ubuntu on Power Status in linux package in Ubuntu: New Bug description: == Comment: #0 - JAMIE L. DOLAN - 2024-05-01 12:19:47 == This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04 - This has already been added for s390x - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064530/+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 2058052] Re: Enable Intel IDPF support on ARM64
** Description changed: [Impact] * Request from Google to enable Intel IDPF driver support on ARM64 [Fix] - * Mantic - - * Jammy - + UBUNTU: [Config] gcp: Add ARM64 support for IDPF driver + [Test Case] * Compile tested * Boot tested + * Google performed some basic validation of the IDPF driver on arm64 [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00381197 ** Also affects: linux-gke (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Noble) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gke (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-gke (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Noble) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2058052 Title: Enable Intel IDPF support on ARM64 Status in linux-gcp package in Ubuntu: In Progress Status in linux-gke package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: In Progress Status in linux-gke source package in Jammy: In Progress Status in linux-gcp source package in Mantic: In Progress Status in linux-gcp source package in Noble: In Progress Status in linux-gke source package in Noble: In Progress Bug description: [Impact] * Request from Google to enable Intel IDPF driver support on ARM64 [Fix] UBUNTU: [Config] gcp: Add ARM64 support for IDPF driver [Test Case] * Compile tested * Boot tested * Google performed some basic validation of the IDPF driver on arm64 [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00381197 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2058052/+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 2064529] [NEW] amdgpu crash
Public bug reported: graphics crashes, requires reboot this has happened a few times recently - typically during periods of activity but not always. See the journal log from the last boot below: Apr 30 21:07:15 arc kernel: snd_hda_intel :1f:00.1: Unable to change power state from D3hot to D0, device inaccessible Apr 30 21:07:16 arc kernel: snd_hda_intel :1f:00.1: CORB reset timeout#2, CORBRP = 65535 Apr 30 21:07:25 arc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout, signaled seq=155368, emitted seq=155370 Apr 30 21:07:25 arc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process spotify pid 11047 thread spotify:cs0 pid 11105 Apr 30 21:07:25 arc kernel: amdgpu :1f:00.0: amdgpu: GPU reset begin! Apr 30 21:07:33 arc kernel: amdgpu :1f:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6 Apr 30 21:07:34 arc kernel: amdgpu: [powerplay] Failed message: 0x24, input parameter: 0x0, error code: 0x Apr 30 21:07:34 arc kernel: amdgpu: [powerplay] Failed message: 0x9, input parameter: 0xf4, error code: 0x Apr 30 21:07:34 arc kernel: amdgpu: [powerplay] Failed message: 0xa, input parameter: 0x103000, error code: 0x Apr 30 21:07:34 arc kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0x Apr 30 21:07:34 arc kernel: amdgpu: [powerplay] Failed message: 0x42, input parameter: 0x1, error code: 0x Apr 30 21:07:34 arc kernel: amdgpu: [powerplay] Failed message: 0x24, input parameter: 0x0, error code: 0x Apr 30 21:07:54 arc kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting Apr 30 21:07:54 arc kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E18E (len 824, WS 0, PS 0) @ 0xE30E Apr 30 21:07:54 arc kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E048 (len 326, WS 0, PS 0) @ 0xE138 Apr 30 21:07:54 arc kernel: amdgpu :1f:00.0: [drm] *ERROR* dce110_link_encoder_disable_output: Failed to execute VBIOS command table! Apr 30 21:08:14 arc kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting Apr 30 21:08:14 arc kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing C30A (len 62, WS 0, PS 0) @ 0xC326 Apr 30 21:08:34 arc kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting Apr 30 21:08:34 arc kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing B802 (len 1359, WS 12, PS 8) @ 0xBB17 Apr 30 21:08:34 arc kernel: amdgpu :1f:00.0: [drm] REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:936 Apr 30 21:08:54 arc kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting Apr 30 21:08:54 arc kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E18E (len 824, WS 0, PS 0) @ 0xE30E Apr 30 21:08:54 arc kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing E048 (len 326, WS 0, PS 0) @ 0xE138 Apr 30 21:08:54 arc kernel: amdgpu :1f:00.0: [drm] *ERROR* dce110_link_encoder_disable_output: Failed to execute VBIOS command table! Apr 30 21:09:14 arc kernel: [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 20secs aborting Apr 30 21:09:14 arc kernel: [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing C30A (len 62, WS 0, PS 0) @ 0xC326 Apr 30 21:09:14 arc kernel: amdgpu :1f:00.0: [drm] REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:936 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 1 11:09:48 2024 InstallationDate: Installed on 2021-10-20 (924 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-01-30 (92 days ago) dmi.bios.date: 06/28/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS (MS-7B79) dmi.board.vendor: Micro-Star
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
This bug was fixed in the package ipu6-drivers - 0~git202404110253.97c94720-0ubuntu1 --- ipu6-drivers (0~git202404110253.97c94720-0ubuntu1) noble; urgency=medium [ You-Sheng Yang ] * New upstream Release_20240409 release (LP: #2061747) - drop upstreamed "backport: replace strlcpy with strscpy" patch - debian: refresh patches - UBUNTU: SAUCE: firmware: fallback to old firmware path - UBUNTU: SAUCE: don't fail probing at hwcfg checks -- You-Sheng Yang Thu, 11 Apr 2024 18:38:46 +0800 ** Changed in: ipu6-drivers (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem-6.8 package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: Fix Committed Status in linux-meta source package in Noble: Fix Committed Status in linux-meta-oem-6.8 source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 == linux-meta, linux-meta-unstable, linux-meta-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The main fixes are in kernel & dkms packages. This adds ivsc-modules to Provides list of linux-image-generic as other built-in linux-modules-foo packages do. [Test Case] The generated meta package linux-image-generic should then provides "ivsc-modules". [Where problems could occur] Meta package changes only. No real effect but in package dependency. [Other Info] While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will only be nominated for Unstable/Noble/OEM-6.8. == ipu6-drivers, linux, linux-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064530] [NEW] Include support for .NET 8 for Ubuntu on Power
You have been subscribed to a public bug: == Comment: #0 - JAMIE L. DOLAN - 2024-05-01 12:19:47 == This is a bug to track adding the feature of .NET 8 to Ubuntu 24.04 - This has already been added for s390x - Customer survey showed strong interest in .NET on Linux on Power, having .NET on Ubuntu on Power will help in adoption of .NET on Power ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-206154 severity-medium targetmilestone-inin2404 -- Include support for .NET 8 for Ubuntu on Power https://bugs.launchpad.net/bugs/2064530 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064514] Re: Azure: Update CIFS to 5.15-backport-1-24-24
https://lists.ubuntu.com/archives/kernel-team/2024-May/150689.html -- 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/2064514 Title: Azure: Update CIFS to 5.15-backport-1-24-24 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Test Plan: Microsoft tested. Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2064514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I think it would be quite helpful if any of you could file separate bug reports of testing a fresh 24.04 install of any flavour and could gather the full kernel log from when the system booted to black screen, with AMD graphics. That's because this can have many different causes, and we do not know the root causes for what you're describing are identical at this point. While obviously what you report is correct and a real issue for each of you, developers need to identify root causes across ideally multiple installations of the same type and in the same or similar environment. However, from a developers' perspective, all we have so far is a few reports of "under some (possibly different) circumstances, an unsupported upgrade to 24.04 resulted into the system booting to a black screen, with some (different models of) AMD graphics. Having seperate reports including logs which *may* (should) point to the root cause would certainly help understanding whether these are isolated corner cases with similar symptoms but different root causes, or whether there really is a generic issue affecting some or many amdgpu driven devices with the 24.04 LTS GA kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064370] Re: Blank screen after boot in raspberry pi 4
** Package changed: software-properties (Ubuntu) => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 Status in linux-raspi package in Ubuntu: New Bug description: I just flashed noble arm64+raspi image and booted it in my raspberry pi 4, and after initial rainbow screen kernel boots with 4 raspberries on the top and boot text appears as normal. But then, before it finishes booting, the screen goes blank. Image is ubuntu-24.04-preinstalled-server-arm64+raspi.img.xz downloaded at Apr/30. ubuntu@ubuntu:~$ uname -a Linux ubuntu 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 02:29:55 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux I know the system booted because I can access it over the network and I even plugged a usb-serial adapter in the uart GPIOs and from there I can see the boot does progress to completion and offers me a prompt where I can use the system normally. But the HDMI screen stays blank. The funny thing is that I have been trying daily builds for quite some time now and they used to work well, this is the first one that does this (the official release). After testing some config options I found that if I change "dtoverlay=vc4-kms-v3d" for "dtoverlay=vc4-fkms-v3d" in config.txt then it boots ok and the screen stays on (note the change from kms to fkms). I also tried appending ",cma-128" to that line (it is present on other lines -- like for pi3 and pi0 -- but not on this one), it does not help. I don't think the issue is with my monitor since it works well for a long time. Also I checked EDIDs, they are detected when using fkms but they are blank when using kms: With KMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty. With fKMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00 01 1a 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24 .. (supressed) I do not use a graphical environment on this unit so I don't know the consequences of this change (to me it just fixes the issue, but I guess it was there for a reason). Let me know if you need any other information from the environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+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 2061324] Re: Error when re-building package from source
Hello Hector, or anyone else affected,
Accepted intel-gpu-tools into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/intel-gpu-
tools/1.26-2ubuntu0.1 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.
** Changed in: intel-gpu-tools (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Status in intel-gpu-tools source package in Jammy:
Fix Committed
Bug description:
[ Impact ]
Impossible to build the package from source on Ubuntu 22.04, users will get
this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The problem comes from the bad call to meson function underscorify in
lib/meson.build
This problem has been fixed upstream:
963917a3565466832a3b2fc22e9285d34a0bf944
lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.
The proposed fix for Ubuntu consists of backporting this patch.
[ Test Plan ]
Build the package from source on Ubuntu 22.04
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
[ Where problems could occur ]
The problem occurs only at build process
[ Other Info ]
This issue only happens at build and has been fixed upstream.
It is safe to have it in SRU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+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 1949314] Please test proposed package
Hello Leonardo, or anyone else affected, Accepted intel-gpu-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.26-2ubuntu0.1 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: Fix Committed Status in intel-gpu-tools source package in Mantic: Fix Committed Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully NOTES: For Noble, all the 4 patches will be backported For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Hello Leonardo, or anyone else affected, Accepted intel-gpu-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.27.1-1ubuntu0.1 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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. ** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: Fix Committed Status in intel-gpu-tools source package in Mantic: Fix Committed Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully NOTES: For Noble, all the 4 patches will be backported For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2064370] [NEW] Blank screen after boot in raspberry pi 4
You have been subscribed to a public bug: I just flashed noble arm64+raspi image and booted it in my raspberry pi 4, and after initial rainbow screen kernel boots with 4 raspberries on the top and boot text appears as normal. But then, before it finishes booting, the screen goes blank. Image is ubuntu-24.04-preinstalled-server-arm64+raspi.img.xz downloaded at Apr/30. ubuntu@ubuntu:~$ uname -a Linux ubuntu 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 02:29:55 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux I know the system booted because I can access it over the network and I even plugged a usb-serial adapter in the uart GPIOs and from there I can see the boot does progress to completion and offers me a prompt where I can use the system normally. But the HDMI screen stays blank. The funny thing is that I have been trying daily builds for quite some time now and they used to work well, this is the first one that does this (the official release). After testing some config options I found that if I change "dtoverlay=vc4-kms-v3d" for "dtoverlay=vc4-fkms-v3d" in config.txt then it boots ok and the screen stays on (note the change from kms to fkms). I also tried appending ",cma-128" to that line (it is present on other lines -- like for pi3 and pi0 -- but not on this one), it does not help. I don't think the issue is with my monitor since it works well for a long time. Also I checked EDIDs, they are detected when using fkms but they are blank when using kms: With KMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty. With fKMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00 01 1a 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24 .. (supressed) I do not use a graphical environment on this unit so I don't know the consequences of this change (to me it just fixes the issue, but I guess it was there for a reason). Let me know if you need any other information from the environment. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- Blank screen after boot in raspberry pi 4 https://bugs.launchpad.net/bugs/2064370 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064514] Re: Azure: Update CIFS to 5.15-backport-1-24-24
** Description changed: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. + git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 - git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 + Test Plan: + + Microsoft tested. Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 -- 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/2064514 Title: Azure: Update CIFS to 5.15-backport-1-24-24 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Test Plan: Microsoft tested. Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2064514/+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 2064514] [NEW] Azure: Update CIFS to 5.15-backport-1-24-24
Public bug reported: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2064514 Title: Azure: Update CIFS to 5.15-backport-1-24-24 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2064514/+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 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
Test result with the patch set applied (ubuntu_fan_smoke_test): 11:48:05 INFO | Writing results to /home/ubuntu/autotest/client/results/default 11:48:05 INFO | START timestamp=1714564085localtime=May 01 11:48:05 11:48:05 INFO | START ubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timeout=1200timestamp=1714564085 localtime=May 01 11:48:05 11:48:07 INFO | GOODubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timestamp=1714564087localtime=May 01 11:48:07 completed successfully 11:48:07 INFO | END GOODubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timestamp=1714564087localtime=May 01 11:48:07 11:48:07 INFO | START ubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimeout=1800timestamp=1714564087 localtime=May 01 11:48:07 11:51:46 INFO | Testing Fan Networking (pre-0.13.0 API) 11:51:46 INFO | docker pull --platform linux/amd64 ubuntu: PASSED 11:51:46 INFO | enable disable fan test: PASSED 11:51:46 INFO | fanctl show test: PASSED 11:51:46 INFO | fanctl check bridge config test: PASSED 11:51:46 INFO | fanatic docker test(--dns=192.168.122.1): PASSED 11:51:47 INFO | GOODubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1714564307localtime=May 01 11:51:47 completed successfully 11:51:47 INFO | END GOODubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1714564307localtime=May 01 11:51:47 11:51:47 INFO | END GOODtimestamp=1714564307 localtime=May 01 11:51:47 11:51:47 INFO | Report successfully generated at /home/ubuntu/autotest/client/results/default/job_report.html -- 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/2064508 Title: re-enable Ubuntu FAN in the Noble kernel Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Impact] In LP: #2063298, we have opted to deprecate Ubuntu FAN support because of the maintenance overhead and the possibility of regressions / conflicts with the new networking eBPF APIs in kernels >= 6.8. However, we cannot disable this feature in HWE/backport kernels, so it seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper co-existence with the updated vxlan policy requirements in newer 6.8 kernels. The re-introduction of Ubuntu FAN should be considered as a temporary measure, aimed at facilitating a smooth transition during its deprecation without disrupting existing users (specifically Juju), and enabling the backporting of 6.8 kernels to older releases. The main plan is still to deprecate Ubuntu FAN in newer releases. [Test case] Rely on the specific Ubuntu FAN regression test to validate the proper kernel support of this feature: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/tree/ubuntu_fan_smoke_test?h=autotest3 [Fix] Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to satisfy the strict length validation check. [Regression potential] We may experience regressions with eBPF vxlan capabilities and potentially specific use cases of the Ubuntu FAN technology (Juju installations). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+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 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
Patch set to re-enable Ubuntu FAN in the 6.8 Noble kernel: https://lists.ubuntu.com/archives/kernel-team/2024-May/150684.html -- 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/2064508 Title: re-enable Ubuntu FAN in the Noble kernel Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Impact] In LP: #2063298, we have opted to deprecate Ubuntu FAN support because of the maintenance overhead and the possibility of regressions / conflicts with the new networking eBPF APIs in kernels >= 6.8. However, we cannot disable this feature in HWE/backport kernels, so it seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper co-existence with the updated vxlan policy requirements in newer 6.8 kernels. The re-introduction of Ubuntu FAN should be considered as a temporary measure, aimed at facilitating a smooth transition during its deprecation without disrupting existing users (specifically Juju), and enabling the backporting of 6.8 kernels to older releases. The main plan is still to deprecate Ubuntu FAN in newer releases. [Test case] Rely on the specific Ubuntu FAN regression test to validate the proper kernel support of this feature: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/tree/ubuntu_fan_smoke_test?h=autotest3 [Fix] Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to satisfy the strict length validation check. [Regression potential] We may experience regressions with eBPF vxlan capabilities and potentially specific use cases of the Ubuntu FAN technology (Juju installations). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+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 2064508] [NEW] re-enable Ubuntu FAN in the Noble kernel
Public bug reported: [Impact] In LP: #2063298, we have opted to deprecate Ubuntu FAN support because of the maintenance overhead and the possibility of regressions / conflicts with the new networking eBPF APIs in kernels >= 6.8. However, we cannot disable this feature in HWE/backport kernels, so it seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper co-existence with the updated vxlan policy requirements in newer 6.8 kernels. The re-introduction of Ubuntu FAN should be considered as a temporary measure, aimed at facilitating a smooth transition during its deprecation without disrupting existing users (specifically Juju), and enabling the backporting of 6.8 kernels to older releases. The main plan is still to deprecate Ubuntu FAN in newer releases. [Test case] Rely on the specific Ubuntu FAN regression test to validate the proper kernel support of this feature: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/tree/ubuntu_fan_smoke_test?h=autotest3 [Fix] Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to satisfy the strict length validation check. [Regression potential] We may experience regressions with eBPF vxlan capabilities and potentially specific use cases of the Ubuntu FAN technology (Juju installations). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Impact] In LP: #2063298, we have opted to deprecate Ubuntu FAN support because of the maintenance overhead and the possibility of regressions / conflicts with the new networking eBPF APIs in kernels >= 6.8. However, we cannot disable this feature in HWE/backport kernels, so it seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper co-existence with the updated vxlan policy requirements in newer 6.8 kernels. The re-introduction of Ubuntu FAN should be considered as a temporary measure, aimed at facilitating a smooth transition during its deprecation without disrupting existing users (specifically Juju), and enabling the backporting of 6.8 kernels to older releases. The main plan is still to deprecate Ubuntu FAN in newer releases. [Test case] Rely on the specific Ubuntu FAN regression test to validate the proper kernel support of this feature: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/tree/ubuntu_fan_smoke_test?h=autotest3 [Fix] Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to satisfy the strict length validation check. [Regression potential] We may experience regressions with eBPF vxlan capabilities and potentially specific use cases of the Ubuntu FAN technology (Juju installations). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+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 2063893] Re: after last OS uptate system will not boot normaly.
Sounds exactly the same as I am haveing. On Sat, Apr 27, 2024 at 11:45 AM Sni <2063...@bugs.launchpad.net> wrote: > Hello, I have the same or similar problem, after a dist-upgrade and > subsequent reboot, my server ran into a kernel panic (sync init). I have > the problem with the linux-6.5.0-34-generic kernel, the > linux-6.5.0-28-generic and all previous ones work fine. > > Since the kernel does not seem to mount the root volume, there are no > logs. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2063893 > > Title: > after last OS uptate system will not boot normaly. > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot > into Linux 6.5.0-28 generic if forced. I have never had an issue > before with OS updates. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063893/+subscriptions > > -- 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/2063893 Title: after last OS uptate system will not boot normaly. Status in linux package in Ubuntu: Confirmed Bug description: will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot into Linux 6.5.0-28 generic if forced. I have never had an issue before with OS updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063893/+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 2064500] [NEW] Rebooting the system fails during boot process, only a cold boot from power-off works
Public bug reported: The system fails to reboot, during the kernel boot process it hangs with the following red error Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 120.832745] Btrfs loaded, zoned=yes, Scanning for Btrfs filesystems About 2 minutes later, kernel panic. The system will boot normally if powered off fully first. I have compiled kernel 6.8.8 using the same config and that solves the problem, however the Ubuntu -generic kernel does not work as described. Thank you ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D9p', '/dev/snd/hwC0D0', '/dev/snd/controlC0', '/dev/snd/by-path'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 1 11:11:43 2024 InstallationDate: Installed on 2022-09-11 (598 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: To Be Filled By O.E.M. B550M Pro4 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=bdf784c5-eacf-49de-9db6-9966caa375bf ro nomodeset RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-15 (16 days ago) acpidump: dmi.bios.date: 01/18/2024 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P3.40 dmi.board.name: B550M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP3.40:bd01/18/2024:br5.17:svnToBeFilledByO.E.M.:pnB550MPro4:pvrToBeFilledByO.E.M.:rvnASRock:rnB550MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: B550M Pro4 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064500 Title: Rebooting the system fails during boot process, only a cold boot from power-off works Status in linux package in Ubuntu: New Bug description: The system fails to reboot, during the kernel boot process it hangs with the following red error Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 120.832745] Btrfs loaded, zoned=yes, Scanning for Btrfs filesystems About 2 minutes later, kernel panic. The system will boot normally if powered off fully first. I have compiled kernel 6.8.8 using the same config and that solves the problem, however the Ubuntu -generic kernel does not work as described. Thank you ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such
[Kernel-packages] [Bug 2064266] Re: linux-virtual: recommends linux-tools and ubuntu-kernel-accessories
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2064266
Title:
linux-virtual: recommends linux-tools and ubuntu-kernel-accessories
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
Fix Committed
Bug description:
[Impact]
The linux-virtual meta is missing a recommends line (already present
in every other noble/ubuntu kernel):
...
Recommends: linux-tools-${kernel-abi-version}-generic,
ubuntu-kernel-accessories
...
[Fix]
Apply the attached fix.
[How to test]
Install linux-virtual with '--install-recommends' and it should pull
in:
-linux-tools-${kernel-abi-version}-generic
-ubuntu-kernel-accessories
[Regression potential]
Low: it's recommend line and it's already present in every other
Ubuntu Noble kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064266/+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 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064275 Title: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument] Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock. After logging in using wayland, both monitors goes blank and then enters power saving mode. If I replug the dock then the monitors wake up but with display settings reset. When using x-server, both screen work as normal after login remembering my screen placement etc. Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode. Ubuntu 24.04 with latest updtes installed. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-26 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 46.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 RelatedPackageVersions: mutter-common 46.0-1ubuntu9 Tags: noble Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-26 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 46.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 RelatedPackageVersions: mutter-common 46.0-1ubuntu9 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064275/+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 2064189] Re: Screen flickers after installing Ubuntu 24.04
Hi @lotuspsychje, As per your comment on #2, I have updated the kernel parameter: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" Also ran "sudo update-grub" after that. Hope this will fix it. Will observe for the next 2-3 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/2064189 Title: Screen flickers after installing Ubuntu 24.04 Status in linux package in Ubuntu: Confirmed Bug description: I've been struggling with some random screen flickering after a fresh install of Ubuntu 24.04. My laptop is running the Mesa Intel(R) HD Graphics 620 (KBL GT2F) integrated graphics. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:melk 2393 F pipewire /dev/snd/controlC0: melk 2401 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 22:22:53 2024 InstallationDate: Installed on 2024-04-29 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Dell Inc. Inspiron 3584 ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=2e0a4d2b-a47f-4fff-8c17-c90f6816b03e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 05RCHV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd09/12/2023:br1.24:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr:sku08D1: dmi.product.family: Inspiron dmi.product.name: Inspiron 3584 dmi.product.sku: 08D1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063228] Re: screen sometimes blinking
I'm not sure you even need to undo the changes in /etc/default/grub and etc/environment if the bug is still happening. But sure... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: screen sometimes blinking Status in linux package in Ubuntu: Incomplete Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
Seems I was mistaken. This happens on 6.8 as well. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+attachment/5773507/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:42:52 2024 InstallationDate: Installed on 2022-06-28 (653 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
