[Kernel-packages] [Bug 2049187] [NEW] Lunar update: 2024-01-12 upstream stable release

[Roxana Nicolescu]

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:

   2024-01-12 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Lunar)
   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/2049187

Title:
  Lunar update: 2024-01-12 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  New

Bug description:
  
  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:

 2024-01-12 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2049189] [NEW] Lunar update: upstream stable release 2024-01-12

[Roxana Nicolescu]

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:

   2024-01-12 upstream stable release
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Lunar)
 Importance: Medium
 Assignee: Roxana Nicolescu (roxanan)
 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 Lunar)
   Importance: Undecided
   Status: New

** Summary changed:

- Lunar update: 2024-01-12 upstream stable release
+ Lunar update: upstream stable release 2024-01-12

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

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

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

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

Title:
  Lunar update: upstream stable release 2024-01-12

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  In Progress

Bug description:
  
  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:

 2024-01-12 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2049189] Re: Lunar update: upstream stable release 2024-01-12

[Roxana Nicolescu]

** Description changed:

+ SRU Justification
  
- 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:
  
- 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:
+    upstream stable release 2024-01-12
+ Ported from the following upstream stable releases:
+ v6.1.58
+ v6.1.59, v6.5.8
+    from git://git.kernel.org/
  
-2024-01-12 upstream stable release
-from git://git.kernel.org/
+ Revert "NFS: More fixes for nfs_direct_write_reschedule_io()"
+ lib/test_meminit: fix off-by-one error in test_pages()
+ drm/i915: Don't set PIPE_CONTROL_FLUSH_L3 for aux inval
+ RDMA/cxgb4: Check skb value for failure to allocate
+ perf/arm-cmn: Fix the unhandled overflow status of counter 4 to 7
+ platform/x86: think-lmi: Fix reference leak
+ platform/x86: hp-wmi:: Mark driver struct with __refdata to prevent section 
mismatch warning
+ scsi: Do not rescan devices with a suspended queue
+ HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect
+ quota: Fix slow quotaoff
+ ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM
+ ata: libata-scsi: Disable scsi device manage_system_start_stop
+ net: prevent address rewrite in kernel_bind()
+ arm64: dts: qcom: sm8150: extend the size of the PDC resource
+ dt-bindings: interrupt-controller: renesas,rzg2l-irqc: Update description for 
'#interrupt-cells' property
+ irqchip: renesas-rzg2l: Fix logic to clear TINT interrupt source
+ KEYS: trusted: Remove redundant static calls usage
+ ALSA: usb-audio: Fix microphone sound on Opencomm2 Headset
+ ALSA: usb-audio: Fix microphone sound on Nexigo webcam.
+ ALSA: hda/realtek: Change model for Intel RVP board
+ ASoC: SOF: amd: fix for firmware reload failure after playback
+ ASoC: simple-card-utils: fixup simple_util_startup() error handling
+ ASoC: Intel: soc-acpi: Add entry for HDMI_In capture support in MTL match 
table
+ ASoC: Intel: sof_sdw: add support for SKU 0B14
+ ASoC: Intel: soc-acpi: Add entry for sof_es8336 in MTL match table.
+ ASoC: Use of_property_read_bool() for boolean properties
+ ASoC: fsl_sai: MCLK bind with TX/RX enable bit
+ ASoC: fsl_sai: Don't disable bitclock for i.MX8MP
+ ALSA: hda/realtek: Add quirk for HP Victus 16-d1xxx to enable mute LED
+ ALSA: hda/realtek: Add quirk for mute LEDs on HP ENVY x360 15-eu0xxx
+ ALSA: hda/realtek - ALC287 merge RTK codec with CS CS35L41 AMP
+ pinctrl: nuvoton: wpcm450: fix out of bounds write
+ drm/msm/dp: do not reinitialize phy unless retry during link training
+ drm/msm/dsi: skip the wait for video mode done if not applicable
+ drm/msm/dsi: fix irq_of_parse_and_map() error checking
+ drm/msm/dpu: change _dpu_plane_calc_bw() to use u64 to avoid overflow
+ drm/msm/dp: Add newlines to debug printks
+ phy: lynx-28g: cancel the CDR check work item on the remove path
+ phy: lynx-28g: lock PHY while performing CDR lock workaround
+ phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared 
registers
+ net: dsa: qca8k: fix potential MDIO bus conflict when accessing internal PHYs 
via management frames
+ can: isotp: isotp_sendmsg(): fix TX state detection and wait behavior
+ can: sun4i_can: Only show Kconfig if ARCH_SUNXI is set
+ arm64: dts: mediatek: mt8195: Set DSU PMU status to fail
+ ravb: Fix up dma_free_coherent() call in ravb_remove()
+ ravb: Fix use-after-free issue in ravb_tx_timeout_work()
+ ieee802154: ca8210: Fix a potential UAF in ca8210_probe
+ mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type
+ xen-netback: use default TX queue size for vifs
+ riscv, bpf: Factor out emit_call for kernel and bpf context
+ riscv, bpf: Sign-extend return values
+ drm/vmwgfx: fix typo of sizeof argument
+ bpf: Fix verifier log for async callback return values
+ net: refine debug info in skb_checksum_help()
+ net: macsec: indicate next pn update when offloading
+ net: phy: mscc: macsec: reject PN update requests
+ net/mlx5e: macsec: use update_pn flag instead of PN comparation
+ ixgbe: fix crash with empty VF macvlan list
+ net/mlx5e: Again mutually exclude RX-FCS and RX-port-timestamp
+ net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
+ pinctrl: renesas: rzn1: Enable missing PIN

[Kernel-packages] [Bug 2049024] Re: Focal update: v5.4.260 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => 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/2049024

Title:
  Focal update: v5.4.260 upstream stable release

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

Bug description:
  
  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.260 upstream stable release
 from git://git.kernel.org/

  mtd: rawnand: marvell: Ensure program page operations are successful
  selftests/ftrace: Add new test case which checks non unique symbol
  mcb: Return actual parsed size when reading chameleon table
  mcb-lpc: Reallocate memory region to avoid memory overlapping
  virtio_balloon: Fix endless deflation and inflation on arm64
  virtio-mmio: fix memory leak of vm_dev
  r8169: fix the KCSAN reported data-race in rtl_tx while reading 
TxDescArray[entry].opts1
  r8169: fix the KCSAN reported data race in rtl_rx while reading desc->opts1
  treewide: Spelling fix in comment
  igb: Fix potential memory leak in igb_add_ethtool_nfc_entry
  neighbour: fix various data-races
  igc: Fix ambiguity in the ethtool advertising
  net: ieee802154: adf7242: Fix some potential buffer overflow in 
adf7242_stats_show()
  r8152: Increase USB control msg timeout to 5000ms as per spec
  r8152: Run the unload routine if we have errors during probe
  r8152: Cancel hw_phy_work if we have an error in probe
  tcp: fix wrong RTO timeout when received SACK reneging
  gtp: uapi: fix GTPA_MAX
  gtp: fix fragmentation needed check with gso
  iio: exynos-adc: request second interupt only when touchscreen mode is used
  i2c: muxes: i2c-mux-pinctrl: Use of_get_i2c_adapter_by_node()
  i2c: muxes: i2c-mux-gpmux: Use of_get_i2c_adapter_by_node()
  i2c: muxes: i2c-demux-pinctrl: Use of_get_i2c_adapter_by_node()
  i2c: stm32f7: Fix PEC handling in case of SMBUS transfers
  i2c: aspeed: Fix i2c bus hang in slave read
  nvmem: imx: correct nregs for i.MX6ULL
  nvmem: imx: correct nregs for i.MX6SLL
  nvmem: imx: correct nregs for i.MX6UL
  perf/core: Fix potential NULL deref
  clk: Sanitize possible_parent_show to Handle Return Value of 
of_clk_get_parent_name
  i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR
  x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility
  drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper()
  arm64: fix a concurrency issue in emulation_proc_handler()
  smbdirect: missing rc checks while waiting for rdma events
  f2fs: fix to do sanity check on inode type during garbage collection
  nfsd: lock_rename() needs both directories to live on the same fs
  x86/mm: Simplify RESERVE_BRK()
  x86/mm: Fix RESERVE_BRK() for older binutils
  ext4: add two helper functions extent_logical_end() and pa_logical_end()
  ext4: avoid overlapping preallocations due to overflow
  ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow
  driver: platform: Add helper for safer setting of driver_override
  rpmsg: Constify local variable in field store macro
  rpmsg: Fix kfree() of static memory on setting driver_override
  rpmsg: Fix calling device_lock() on non-initialized device
  rpmsg: glink: Release driver_override
  rpmsg: Fix possible refcount leak in rpmsg_register_device_override()
  x86: Fix .brk attribute in linker script
  Input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table
  irqchip/stm32-exti: add missing DT IRQ flag translation
  dmaengine: ste_dma40: Fix PM disable depth imbalance in d40_probe
  Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport
  fbdev: atyfb: only use ioremap_uc() on i386 and ia64
  spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
  netfilter: nfnetlink_log: silence bogus compiler warning
  ASoC: rt5650: fix the wrong result of key button
  fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit()
  scsi: mpt3sas: Fix in error path
  platform/x86: asus-wmi: Change ASUS_WMI_BRN_DOWN code from 0x20 to 0x2e
  platform/mellanox: mlxbf-tmfifo: Fix a warning message
  net: chelsio: cxgb4: add an error code check in t4_load_phy_fw
  ata: ahci: fix enum constants for gcc-13
  remove the sx8 block driver
  UBUNTU: [Config] remove CONFIG_BLK_DEV_SX8
  Revert "ARM: dts: Move am33xx and am43xx mmc nodes to sdhci-omap driver"
  PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device
  usb: storage: set 1.50 as the lower bcdDevice for older "Super Top" 
compatibility
  tty: 8250: Remove U

[Kernel-packages] [Bug 2049069] Re: Focal update: v5.4.262 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => 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/2049069

Title:
  Focal update: v5.4.262 upstream stable release

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

Bug description:
  
  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.262 upstream stable release
 from git://git.kernel.org/

  locking/ww_mutex/test: Fix potential workqueue corruption
  perf/core: Bail out early if the request AUX area is out of bound
  clocksource/drivers/timer-imx-gpt: Fix potential memory leak
  clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware
  x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size
  wifi: mac80211_hwsim: fix clang-specific fortify warning
  wifi: mac80211: don't return unset power in ieee80211_get_tx_power()
  wifi: ath9k: fix clang-specific fortify warnings
  wifi: ath10k: fix clang-specific fortify warning
  net: annotate data-races around sk->sk_tx_queue_mapping
  net: annotate data-races around sk->sk_dst_pending_confirm
  wifi: ath10k: Don't touch the CE interrupt registers after power up
  Bluetooth: Fix double free in hci_conn_cleanup
  platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e
  drm/komeda: drop all currently held locks if deadlock happens
  drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7
  drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga
  drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL
  selftests/efivarfs: create-read: fix a resource leak
  crypto: pcrypt - Fix hungtask for PADATA_RESET
  RDMA/hfi1: Use FIELD_GET() to extract Link Width
  fs/jfs: Add check for negative db_l2nbperpage
  fs/jfs: Add validity check for db_maxag and db_agpref
  jfs: fix array-index-out-of-bounds in dbFindLeaf
  jfs: fix array-index-out-of-bounds in diAlloc
  ARM: 9320/1: fix stack depot IRQ stack filter
  ALSA: hda: Fix possible null-ptr-deref when assigning a stream
  PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields
  atm: iphase: Do PCI error checks on own line
  scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup()
  HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W
  tty: vcc: Add check for kstrdup() in vcc_probe()
  usb: gadget: f_ncm: Always set current gadget in ncm_bind()
  i2c: sun6i-p2wi: Prevent potential division by zero
  media: gspca: cpia1: shift-out-of-bounds in set_flicker
  media: vivid: avoid integer overflow
  gfs2: ignore negated quota changes
  media: cobalt: Use FIELD_GET() to extract Link Width
  drm/amd/display: Avoid NULL dereference of timing generator
  kgdb: Flush console before entering kgdb on panic
  ASoC: ti: omap-mcbsp: Fix runtime PM underflow warnings
  pwm: Fix double shift bug
  wifi: iwlwifi: Use FW rate for non-data frames
  NFSv4.1: fix SP4_MACH_CRED protection for pnfs IO
  ipvlan: add ipvlan_route_v6_outbound() helper
  tty: Fix uninit-value access in ppp_sync_receive()
  net: hns3: fix variable may not initialized problem in hns3_init_mac_addr()
  tipc: Fix kernel-infoleak due to uninitialized TLV value
  ppp: limit MRU to 64K
  xen/events: fix delayed eoi list handling
  ptp: annotate data-race around q->head and q->tail
  bonding: stop the device in bond_setup_by_slave()
  net: ethernet: cortina: Fix max RX frame define
  net: ethernet: cortina: Handle large frames
  net: ethernet: cortina: Fix MTU max setting
  netfilter: nf_conntrack_bridge: initialize err to 0
  net: stmmac: Rework stmmac_rx()
  net: stmmac: fix rx budget limit check
  net/mlx5_core: Clean driver version and name
  net/mlx5e: Check return value of snprintf writing to fw_version buffer for 
representors
  macvlan: Don't propagate promisc change to lower dev in passthru
  tools/power/turbostat: Fix a knl bug
  cifs: spnego: add ';' in HOST_KEY_LEN
  media: venus: hfi: add checks to perform sanity on queue pointers
  randstruct: Fix gcc-plugin performance mode to stay in group
  bpf: Fix precision tracking for BPF_ALU | BPF_TO_BE | BPF_END
  scsi: megaraid_sas: Increase register read retry rount from 3 to 30 for 
selected registers
  x86/cpu/hygon: Fix the CPU topology evaluation for real
  KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
  KVM: x86: Ignore MSR_AMD64_TW_CFG access
  audit: don't take task_lock() in audit_exe_compare() code path
  audit: do

[Kernel-packages] [Bug 2049049] Re: Focal update: v5.4.261 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => 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/2049049

Title:
  Focal update: v5.4.261 upstream stable release

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

Bug description:
  
  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.261 upstream stable release
 from git://git.kernel.org/

  vfs: fix readahead(2) on block devices
  genirq/matrix: Exclude managed interrupts in irq_matrix_allocated()
  i40e: fix potential memory leaks in i40e_remove()
  tcp: call tcp_try_undo_recovery when an RTOd TFO SYNACK is ACKed
  wifi: rtw88: debug: Fix the NULL vs IS_ERR() bug for debugfs_create_file()
  wifi: mt76: mt7603: rework/fix rx pse hang check
  tcp_metrics: add missing barriers on delete
  tcp_metrics: properly set tp->snd_ssthresh in tcp_init_metrics()
  tcp_metrics: do not create an entry from tcp_init_metrics()
  wifi: rtlwifi: fix EDCA limit set by BT coexistence
  can: dev: can_restart(): don't crash kernel if carrier is OK
  can: dev: can_restart(): fix race condition between controller restart and 
netif_carrier_on()
  thermal: core: prevent potential string overflow
  r8169: use tp_to_dev instead of open code
  r8169: fix rare issue with broken rx after link-down on RTL8125
  chtls: fix tp->rcv_tstamp initialization
  tcp: Remove one extra ktime_get_ns() from cookie_init_timestamp
  tcp: fix cookie_init_timestamp() overflows
  ACPI: sysfs: Fix create_pnp_modalias() and create_of_modalias()
  ipv6: avoid atomic fragment on GSO packets
  net: add DEV_STATS_READ() helper
  ipvlan: properly track tx_errors
  regmap: debugfs: Fix a erroneous check after snprintf()
  clk: qcom: clk-rcg2: Fix clock rate overflow for high parent frequencies
  clk: qcom: gcc-sm8150: use ARRAY_SIZE instead of specifying num_parents
  clk: qcom: gcc-sm8150: Fix gcc_sdcc2_apps_clk_src
  clk: imx: Select MXC_CLK for CLK_IMX8QXP
  clk: keystone: pll: fix a couple NULL vs IS_ERR() checks
  clk: npcm7xx: Fix incorrect kfree
  clk: mediatek: clk-mt6779: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt6797: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt7629-eth: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt7629: Add check for mtk_alloc_clk_data
  clk: mediatek: clk-mt2701: Add check for mtk_alloc_clk_data
  platform/x86: wmi: Fix probe failure when failing to register WMI devices
  platform/x86: wmi: remove unnecessary initializations
  platform/x86: wmi: Fix opening of char device
  hwmon: (coretemp) Fix potentially truncated sysfs attribute name
  drm/rockchip: vop: Fix reset of state in duplicate state crtc funcs
  drm/rockchip: vop: Fix call to crtc reset helper
  drm/radeon: possible buffer overflow
  drm/rockchip: cdn-dp: Fix some error handling paths in cdn_dp_probe()
  arm64: dts: qcom: sdm845-mtp: fix WiFi configuration
  ARM: dts: qcom: mdm9615: populate vsdcc fixed regulator
  soc: qcom: llcc cleanup to get rid of sdm845 specific driver file
  UBUNTU: [Config] remove CONFIG_QCOM_SDM845_LLCC
  soc: qcom: Rename llcc-slice to llcc-qcom
  UBUNTU: [Config] remove llcc-slice module
  soc: qcom: llcc: Handle a second device without data corruption
  firmware: ti_sci: Replace HTTP links with HTTPS ones
  firmware: ti_sci: Mark driver as non removable
  clk: scmi: Free scmi_clk allocated when the clocks with invalid info are 
skipped
  hwrng: geode - fix accessing registers
  libnvdimm/of_pmem: Use devm_kstrdup instead of kstrdup and check its return 
value
  sched/rt: Provide migrate_disable/enable() inlines
  nd_btt: Make BTT lanes preemptible
  crypto: caam/qi2 - fix Chacha20 + Poly1305 self test failure
  crypto: caam/jr - fix Chacha20 + Poly1305 self test failure
  HID: cp2112: Use irqchip template
  hid: cp2112: Fix duplicate workqueue initialization
  ARM: 9321/1: memset: cast the constant byte to unsigned char
  ext4: move 'ix' sanity check to corrent position
  scsi: ufs: core: Leave space for '\0' in utf8 desc string
  RDMA/hfi1: Workaround truncation compilation error
  sh: bios: Revive earlyprintk support
  ASoC: Intel: Skylake: Fix mem leak when parsing UUIDs fails
  ASoC: ams-delta.c: use component after check
  mfd: dln2: Fix double put in dln2_probe
  leds: pwm: simplify if condition
  leds: pwm: convert to atomic PWM API
  leds: pwm: Don't disable the PWM when the LED should be off
  ledtrig-cpu: Limit to 8 CPUs
  leds

[Kernel-packages] [Bug 2049202] Re: Mantic update: v6.5.9 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => 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/2049202

Title:
  Mantic update: v6.5.9 upstream stable release

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

Bug description:
  
  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:

 v6.5.9 upstream stable release
 from git://git.kernel.org/

  Bluetooth: hci_event: Ignore NULL link key
  Bluetooth: Reject connection with the device which has same BD_ADDR
  Bluetooth: Fix a refcnt underflow problem for hci_conn
  Bluetooth: vhci: Fix race when opening vhci device
  Bluetooth: hci_event: Fix coding style
  Bluetooth: avoid memcmp() out of bounds warning
  Bluetooth: hci_conn: Fix modifying handle while aborting
  ice: fix over-shifted variable
  ice: Fix safe mode when DDP is missing
  ice: reset first in crash dump kernels
  net/smc: return the right falback reason when prefix checks fail
  btrfs: fix stripe length calculation for non-zoned data chunk allocation
  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()
  regmap: fix NULL deref on lookup
  KVM: x86: Mask LVTPC when handling a PMI
  x86/fpu: Allow caller to constrain xfeatures when copying to uabi buffer
  KVM: x86/pmu: Truncate counter value to allowed width on write
  KVM: x86: Constrain guest-supported xfeatures only at KVM_GET_XSAVE{2}
  x86: KVM: SVM: add support for Invalid IPI Vector interception
  x86: KVM: SVM: refresh AVIC inhibition in svm_leave_nested()
  tcp: check mptcp-level constraints for backlog coalescing
  mptcp: more conservative check for zero probes
  selftests: mptcp: join: no RST when rm subflow/addr
  mm: slab: Do not create kmalloc caches smaller than arch_slab_minalign()
  fs/ntfs3: Fix OOB read in ntfs_init_from_boot
  fs/ntfs3: Fix possible null-pointer dereference in hdr_find_e()
  fs/ntfs3: fix panic about slab-out-of-bounds caused by ntfs_list_ea()
  fs/ntfs3: Fix shift-out-of-bounds in ntfs_fill_super
  fs/ntfs3: fix deadlock in mark_as_free_ex
  Revert "net: wwan: iosm: enable runtime pm support for 7560"
  netfilter: nft_payload: fix wrong mac header matching
  drm/i915: Retry gtt fault when out of fence registers
  drm/mediatek: Correctly free sg_table in gem prime vmap
  drm/nouveau/disp: fix DP capable DSM connectors
  drm/edid: add 8 bpc quirk to the BenQ GW2765
  ALSA: hda/realtek - Fixed ASUS platform headset Mic issue
  ALSA: hda/realtek: Add quirk for ASUS ROG GU603ZV
  ALSA: hda/relatek: Enable Mute LED on HP Laptop 15s-fq5xxx
  ASoC: codecs: wcd938x-sdw: fix use after free on driver unbind
  ASoC: codecs: wcd938x-sdw: fix runtime PM imbalance on probe errors
  ASoC: codecs: wcd938x: drop bogus bind error handling
  ASoC: codecs: wcd938x: fix unbind tear down order
  ASoC: codecs: wcd938x: fix resource leaks on bind errors
  ASoC: codecs: wcd938x: fix regulator leaks on probe errors
  ASoC: codecs: wcd938x: fix runtime PM imbalance on remove
  qed: fix LL2 RX buffer allocation
  xfrm: fix a data-race in xfrm_lookup_with_ifid()
  xfrm6: fix inet6_dev refcount underflow problem
  xfrm: fix a data-race in xfrm_gen_index()
  xfrm: interface: use DEV_STATS_INC()
  net: xfrm: skip policies marked as dead while reinserting policies
  fprobe: Fix to ensure the number of active retprobes is not zero
  wifi: cfg80211: use system_unbound_wq for wiphy work
  net: ipv4: fix return value check in esp_remove_trailer
  net: ipv6: fix return value check in esp_remove_trailer
  net: rfkill: gpio: prevent value glitch during probe
  tcp: fix excessive TLP and RACK timeouts from HZ rounding
  tcp: tsq: relax tcp_small_queue_check() when rtx queue contains a single skb
  tcp: Fix listen() warning with v4-mapped-v6 address.
  docs: fix info about representor identification
  tun: prevent negative ifindex
  gve: Do not fully free QPL pages on prefill errors
  ipv4: fib: annotate races around nh->nh_saddr_genid and nh->nh_saddr
  net: usb: smsc95xx: Fix an error code in smsc95xx_reset()
  octeon_ep: update BQL sent bytes before ringing doorbell
  i40e: prevent crash on probe if hw registers have invalid values
  net: dsa: bcm_sf2: Fix possible memory leak in bcm_sf2_mdio_register()
  bonding: Return pointer to data after pull on skb
  net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve
  neighbor: tracing: Move pin6 inside CONFIG_IPV6=y section
  selftests: openvswitch: Cat

[Kernel-packages] [Bug 2049084] Re: Focal update: v5.4.263 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => 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/2049084

Title:
  Focal update: v5.4.263 upstream stable release

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

Bug description:
  
  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.263 upstream stable release
 from git://git.kernel.org/

  driver core: Release all resources during unbind before updating device links
  RDMA/irdma: Prevent zero-length STAG registration
  PCI: keystone: Drop __init from ks_pcie_add_pcie_{ep,port}()
  afs: Make error on cell lookup failure consistent with OpenAFS
  drm/panel: simple: Fix Innolux G101ICE-L01 bus flags
  drm/panel: simple: Fix Innolux G101ICE-L01 timings
  ata: pata_isapnp: Add missing error check for devm_ioport_map()
  drm/rockchip: vop: Fix color for RGB888/BGR888 format on VOP full
  HID: core: store the unique system identifier in hid_device
  HID: fix HID device resource race between HID core and debugging support
  ipv4: Correct/silence an endian warning in __ip_do_redirect
  net: usb: ax88179_178a: fix failed operations during ax88179_reset
  arm/xen: fix xen_vcpu_info allocation alignment
  amd-xgbe: handle corner-case during sfp hotplug
  amd-xgbe: handle the corner-case during tx completion
  amd-xgbe: propagate the correct speed and duplex status
  net: axienet: Fix check for partial TX checksum
  afs: Return ENOENT if no cell DNS record can be found
  afs: Fix file locking on R/O volumes to operate in local mode
  nvmet: remove unnecessary ctrl parameter
  nvmet: nul-terminate the NQNs passed in the connect command
  MIPS: KVM: Fix a build warning about variable set but not used
  ext4: add a new helper to check if es must be kept
  ext4: factor out __es_alloc_extent() and __es_free_extent()
  ext4: use pre-allocated es in __es_insert_extent()
  ext4: use pre-allocated es in __es_remove_extent()
  ext4: using nofail preallocation in ext4_es_remove_extent()
  ext4: using nofail preallocation in ext4_es_insert_delayed_block()
  ext4: using nofail preallocation in ext4_es_insert_extent()
  ext4: fix slab-use-after-free in ext4_es_insert_extent()
  ext4: make sure allocate pending entry not fail
  arm64: cpufeature: Extract capped perfmon fields
  KVM: arm64: limit PMU version to PMUv3 for ARMv8.1
  ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA
  bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce()
  s390/dasd: protect device queue against concurrent access
  USB: serial: option: add Luat Air72*U series products
  hv_netvsc: Fix race of register_netdevice_notifier and VF register
  hv_netvsc: Mark VF as slave before exposing it to user-mode
  dm-delay: fix a race between delay_presuspend and delay_bio
  bcache: check return value from btree_node_alloc_replacement()
  bcache: prevent potential division by zero error
  USB: serial: option: add Fibocom L7xx modules
  USB: serial: option: fix FM101R-GL defines
  USB: serial: option: don't claim interface 4 for ZTE MF290
  USB: dwc2: write HCINT with INTMASK applied
  usb: dwc3: set the dma max_seg_size
  USB: dwc3: qcom: fix resource leaks on probe deferral
  USB: dwc3: qcom: fix wakeup after probe deferral
  io_uring: fix off-by one bvec index
  pinctrl: avoid reload of p state in list iteration
  firewire: core: fix possible memory leak in create_units()
  mmc: block: Do not lose cache flush during CQE error recovery
  ALSA: hda: Disable power-save on KONTRON SinglePC
  ALSA: hda/realtek: Headset Mic VREF to 100%
  ALSA: hda/realtek: Add supported ALC257 for ChromeOS
  dm-verity: align struct dm_verity_fec_io properly
  dm verity: don't perform FEC for failed readahead IO
  bcache: revert replacing IS_ERR_OR_NULL with IS_ERR
  powerpc: Don't clobber f0/vs0 during fp|altivec register save
  btrfs: fix off-by-one when checking chunk map includes logical address
  btrfs: send: ensure send_fd is writable
  btrfs: make error messages more clear when getting a chunk map
  Input: xpad - add HyperX Clutch Gladiate Support
  net: stmmac: xgmac: Disable FPE MMC interrupts
  ravb: Fix races between ravb_tx_timeout_work() and net related ops
  net: ravb: Use pm_runtime_resume_and_get()
  net: ravb: Start TX queues after HW initialization succeeded
  smb3: fix touch -h of symlink
  s390/mm: fix phys vs virt confusion in mark_kernel_pXd() functions family
  

[Kernel-packages] [Bug 2049350] Re: Jammy update: v5.15.137 upstream stable release

[Roxana Nicolescu]

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Portia Stephens (portias)

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

Title:
  Jammy update: v5.15.137 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  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:

     upstream stable patchset 2024-01-15
     from git://git.kernel.org/

  lib/Kconfig.debug: do not enable DEBUG_PREEMPT by default
  Documentation: sysctl: align cells in second content column
  xfs: don't expose internal symlink metadata buffers to the vfs
  Bluetooth: hci_event: Ignore NULL link key
  Bluetooth: Reject connection with the device which has same BD_ADDR
  Bluetooth: Fix a refcnt underflow problem for hci_conn
  Bluetooth: vhci: Fix race when opening vhci device
  Bluetooth: hci_event: Fix coding style
  Bluetooth: avoid memcmp() out of bounds warning
  ice: fix over-shifted variable
  ice: reset first in crash dump kernels
  nfc: nci: fix possible NULL pointer dereference in send_acknowledge()
  regmap: fix NULL deref on lookup
  KVM: x86: Mask LVTPC when handling a PMI
  tcp: check mptcp-level constraints for backlog coalescing
  fs/ntfs3: Fix possible null-pointer dereference in hdr_find_e()
  fs/ntfs3: fix panic about slab-out-of-bounds caused by ntfs_list_ea()
  fs/ntfs3: fix deadlock in mark_as_free_ex
  netfilter: nft_payload: fix wrong mac header matching
  drm/i915: Retry gtt fault when out of fence registers
  ASoC: codecs: wcd938x-sdw: fix use after free on driver unbind
  ASoC: codecs: wcd938x-sdw: fix runtime PM imbalance on probe errors
  ASoC: codecs: wcd938x: drop bogus bind error handling
  ASoC: codecs: wcd938x: fix unbind tear down order
  qed: fix LL2 RX buffer allocation
  xfrm: fix a data-race in xfrm_gen_index()
  xfrm: interface: use DEV_STATS_INC()
  net: ipv4: fix return value check in esp_remove_trailer
  net: ipv6: fix return value check in esp_remove_trailer
  net: rfkill: gpio: prevent value glitch during probe
  tcp: fix excessive TLP and RACK timeouts from HZ rounding
  tcp: tsq: relax tcp_small_queue_check() when rtx queue contains a single skb
  tun: prevent negative ifindex
  ipv4: fib: annotate races around nh->nh_saddr_genid and nh->nh_saddr
  net: usb: smsc95xx: Fix an error code in smsc95xx_reset()
  i40e: prevent crash on probe if hw registers have invalid values
  net: dsa: bcm_sf2: Fix possible memory leak in bcm_sf2_mdio_register()
  bonding: Return pointer to data after pull on skb
  net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve
  neighbor: tracing: Move pin6 inside CONFIG_IPV6=y section
  netfilter: nft_set_rbtree: .deactivate fails if element has expired
  netfilter: nf_tables: do not remove elements if set backend implements .abort
  netfilter: nf_tables: revert do not remove elements if set backend implements 
.abort
  net: pktgen: Fix interface flags printing
  selftests/mm: fix awk usage in charge_reserved_hugetlb.sh and 
hugetlb_reparenting_test.sh that may cause error
  serial: 8250: omap: Fix imprecise external abort for omap_8250_pm()
  serial: 8250_omap: Fix errors with no_console_suspend
  iio: Un-inline iio_buffer_enabled()
  iio: core: Hide read accesses to iio_dev->currentmode
  iio: core: introduce iio_device_{claim|release}_buffer_mode() APIs
  iio: cros_ec: fix an use-after-free in cros_ec_sensors_push_data()
  iio: adc: ad7192: Correct reference voltage
  perf: Add irq and exception return branch types
  perf/x86: Move branch classifier
  perf/x86/lbr: Filter vsyscall addresses
  drm/atomic-helper: relax unregistered connector check
  powerpc/32s: Remove capability to disable KUEP at boottime
  powerpc/32s: Do kuep_lock() and kuep_unlock() in assembly
  powerpc/47x: Fix 47x syscall return crash
  mctp: Allow local delivery to the null EID
  mctp: perform route lookups under a RCU read-side lock
  nfp: flower: avoid rmmod nfp crash issues
  ksmbd: not allow to open file if delelete on close bit is set
  ARM: dts: ti: omap: Fix noisy serial with overrun-throttle-ms for mapphone
  fs-writeback: do not requeue a clean inode having skipped pages
  btrfs: return -EUCLEAN for delayed tree ref with a ref count not

[Kernel-packages] [Bug 2049412] [NEW] Mantic update: v6.5.10 upstream stable release

[Roxana Nicolescu]

ewake during steering operations
iavf: in iavf_down, disable queues when removing the driver
scsi: sd: Introduce manage_shutdown device flag
blk-throttle: check for overflow in calculate_bytes_allowed
kasan: print the original fault addr when access invalid shadow
iio: afe: rescale: Accept only offset channels
iio: exynos-adc: request second interupt only when touchscreen mode is used
iio: adc: xilinx-xadc: Don't clobber preset voltage/temperature thresholds
iio: adc: xilinx-xadc: Correct temperature offset/scale for UltraScale
i2c: muxes: i2c-mux-pinctrl: Use of_get_i2c_adapter_by_node()
i2c: muxes: i2c-mux-gpmux: Use of_get_i2c_adapter_by_node()
i2c: muxes: i2c-demux-pinctrl: Use of_get_i2c_adapter_by_node()
i2c: stm32f7: Fix PEC handling in case of SMBUS transfers
i2c: aspeed: Fix i2c bus hang in slave read
tracing/kprobes: Fix symbol counting logic by looking at modules as well
tracing/kprobes: Fix the description of variable length arguments
misc: fastrpc: Reset metadata buffer to avoid incorrect free
misc: fastrpc: Free DMA handles for RPC calls with no arguments
misc: fastrpc: Clean buffers on remote invocation failures
misc: fastrpc: Unmap only if buffer is unmapped from DSP
nvmem: imx: correct nregs for i.MX6ULL
nvmem: imx: correct nregs for i.MX6SLL
nvmem: imx: correct nregs for i.MX6UL
x86/tsc: Defer marking TSC unstable to a worker
x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility
x86/cpu: Add model number for Intel Arrow Lake mobile processor
perf/core: Fix potential NULL deref
sparc32: fix a braino in fault handling in csum_and_copy_..._user()
clk: Sanitize possible_parent_show to Handle Return Value of 
of_clk_get_parent_name
clk: socfpga: gate: Account for the divider in determine_rate
clk: stm32: Fix a signedness issue in clk_stm32_composite_determine_rate()
platform/x86: Add s2idle quirk for more Lenovo laptops
mm/damon/sysfs: check DAMOS regions update progress from before_terminate()
accel/ivpu/37xx: Fix missing VPUIP interrupts
Linux 6.5.10
UBUNTU: Upstream stable to v6.5.10

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

** Affects: linux (Ubuntu Mantic)
 Importance: Medium
 Assignee: Roxana Nicolescu (roxanan)
 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 Mantic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Description changed:

+ SRU Justification
  
- 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:
  
- 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:
+    v6.5.10 upstream stable release
+    from git://git.kernel.org/
  
-v6.5.10 upstream stable release
-from git://git.kernel.org/
+ vdpa/mlx5: Fix firmware error on creation of 1k VQs
+ smb3: allow controlling length of time directory entries are cached with dir 
leases
+ smb3: allow controlling maximum number of cached directories
+ smb3: do not start laundromat thread when dir leases disabled
+ smb: client: do not start laundromat thread on nohandlecache
+ smb: client: make laundromat a delayed worker
+ smb: client: prevent new fids from being removed by laundromat
+ virtio_balloon: Fix endless deflation and inflation on arm64
+ virtio-mmio: fix memory leak of vm_dev
+ virtio-crypto: handle config changed by work queue
+ virtio_pci: fix the common cfg map size
+ vsock/virtio: initialize the_virtio_vsock before using VQs
+ vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE
+ arm64: dts: qcom: apq8096-db820c: fix missing clock populate
+ arm64: dts: qcom: msm8996-xiaomi: fix missing clock populate
+ arm64: dts: rockchip: use codec as clock master on px30-ringneck-haikou
+ arm64: dts: rockchip: set codec system-clock-fixed on px30-ringneck-haikou
+ arm64: dts: qcom: sa8775p: correct PM

[Kernel-packages] [Bug 2049417] [NEW] Jammy update: v5.15.138 upstream stable release

[Roxana Nicolescu]

h emulation exception
Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport
fbdev: atyfb: only use ioremap_uc() on i386 and ia64
fs/ntfs3: Add ckeck in ni_update_parent()
fs/ntfs3: Write immediately updated ntfs state
fs/ntfs3: Use kvmalloc instead of kmalloc(... __GFP_NOWARN)
fs/ntfs3: Fix possible NULL-ptr-deref in ni_readpage_cmpr()
fs/ntfs3: Fix NULL pointer dereference on error in attr_allocate_frame()
fs/ntfs3: Fix directory element type detection
fs/ntfs3: Avoid possible memory leak
spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
netfilter: nfnetlink_log: silence bogus compiler warning
ASoC: rt5650: fix the wrong result of key button
drm/ttm: Reorder sys manager cleanup step
fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit()
scsi: mpt3sas: Fix in error path
platform/mellanox: mlxbf-tmfifo: Fix a warning message
net: chelsio: cxgb4: add an error code check in t4_load_phy_fw
r8152: Check for unplug in rtl_phy_patch_request()
r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en()
powerpc/mm: Fix boot crash with FLATMEM
can: isotp: set max PDU size to 64 kByte
can: isotp: isotp_bind(): return -EINVAL on incorrect CAN ID formatting
can: isotp: check CAN address family in isotp_bind()
can: isotp: handle wait_event_interruptible() return values
can: isotp: add local echo tx processing and tx without FC
can: isotp: isotp_bind(): do not validate unused address information
can: isotp: isotp_sendmsg(): fix TX state detection and wait behavior
drm/amd: Move helper for dynamic speed switch check out of smu13
drm/amd: Disable ASPM for VI w/ all Intel systems
PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device
usb: storage: set 1.50 as the lower bcdDevice for older "Super Top" 
compatibility
usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm()
usb: raw-gadget: properly handle interrupted requests
tty: n_gsm: fix race condition in status line change on dead connections
tty: 8250: Remove UC-257 and UC-431
tty: 8250: Add support for additional Brainboxes UC cards
tty: 8250: Add support for Brainboxes UP cards
tty: 8250: Add support for Intashield IS-100
tty: 8250: Fix port count of PX-257
tty: 8250: Fix up PX-803/PX-857
tty: 8250: Add support for additional Brainboxes PX cards
tty: 8250: Add support for Intashield IX cards
tty: 8250: Add Brainboxes Oxford Semiconductor-based quirks
misc: pci_endpoint_test: Add deviceID for J721S2 PCIe EP device support
ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection
Linux 5.15.138
UBUNTU: Upstream stable to v5.15.138

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Roxana Nicolescu (roxanan)
 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 Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

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

** Description changed:

+ SRU Justification
  
- 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:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.138 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.138 upstream stable release
-from git://git.kernel.org/
+ ASoC: codecs: wcd938x: fix resource leaks on bind errors
+ ASoC: codecs: wcd938x: fix runtime PM imbalance on remove
+ pinctrl: qcom: lpass-lpi: fix concurrent register updates
+ tcp: remove dead code from tcp_sendmsg_locked()
+ tcp: cleanup tcp_remove_empty_skb() use
+ mptcp: more conservative check for zero probes
+ mcb: Return actual parsed size when reading chameleon table
+ mcb-lpc: Reallocate memory region to avoid memory overlapping
+ virtio_balloon: Fix endless deflation and inflation on arm64
+ virtio-mmio: fix memory leak of vm

[Kernel-packages] [Bug 2049432] [NEW] Jammy update: v5.15.139 upstream stable release

[Roxana Nicolescu]

ciate_ctty()
livepatch: Fix missing newline character in klp_resolve_symbols()
dmaengine: idxd: Register dsa_bus_type before registering idxd sub-drivers
usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency
usb: chipidea: Fix DMA overwrite for Tegra
usb: chipidea: Simplify Tegra DMA alignment code
dmaengine: ti: edma: handle irq_of_parse_and_map() errors
misc: st_core: Do not call kfree_skb() under spin_lock_irqsave()
tools: iio: iio_generic_buffer ensure alignment
USB: usbip: fix stub_dev hub disconnect
dmaengine: pxa_dma: Remove an erroneous BUG_ON() in pxad_free_desc()
f2fs: fix to initialize map.m_pblk in f2fs_precache_extents()
powerpc: Only define __parse_fpscr() when required
modpost: fix tee MODULE_DEVICE_TABLE built on big-endian host
powerpc/40x: Remove stale PTE_ATOMIC_UPDATES macro
powerpc/xive: Fix endian conversion size
powerpc/imc-pmu: Use the correct spinlock initializer.
powerpc/pseries: fix potential memory leak in init_cpu_associativity()
usb: host: xhci-plat: fix possible kernel oops while resuming
perf machine: Avoid out of bounds LBR memory read
perf hist: Add missing puts to hist__account_cycles
9p/net: fix possible memory leak in p9_check_errors()
i3c: Fix potential refcount leak in i3c_master_register_new_i3c_devs
cxl/mem: Fix shutdown order
rtc: pcf85363: fix wrong mask/val parameters in regmap_update_bits call
pcmcia: cs: fix possible hung task and memory leak pccardd()
pcmcia: ds: fix refcount leak in pcmcia_device_add()
pcmcia: ds: fix possible name leak in error path in pcmcia_device_add()
media: i2c: max9286: Fix some redundant of_node_put() calls
media: bttv: fix use after free error due to btv->timeout timer
media: s3c-camif: Avoid inappropriate kfree()
media: vidtv: psi: Add check for kstrdup
media: vidtv: mux: Add check and kfree for kstrdup
media: cedrus: Fix clock/reset sequence
media: dvb-usb-v2: af9035: fix missing unlock
regmap: prevent noinc writes from clobbering cache
pwm: sti: Reduce number of allocations and drop usage of chip_data
pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume
Input: synaptics-rmi4 - fix use after free in rmi_unregister_function()
llc: verify mac len before reading mac header
hsr: Prevent use after free in prp_create_tagged_frame()
tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING
bpf: Check map->usercnt after timer->timer is assigned
inet: shrink struct flowi_common
octeontx2-pf: Fix error codes
octeontx2-pf: Fix holes in error code
dccp: Call security_inet_conn_request() after setting IPv4 addresses.
dccp/tcp: Call security_inet_conn_request() after setting IPv6 addresses.
Fix termination state for idr_for_each_entry_ul()
net: stmmac: xgmac: Enable support for multiple Flexible PPS outputs
selftests: pmtu.sh: fix result checking
net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT
net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc
net/smc: put sk reference if close work was canceled
tg3: power down device only on SYSTEM_POWER_OFF
block: remove unneeded return value of bio_check_ro()
blk-core: use pr_warn_ratelimited() in bio_check_ro()
r8169: respect userspace disabling IFF_MULTICAST
i2c: iproc: handle invalid slave state
netfilter: xt_recent: fix (increase) ipv6 literal buffer length
netfilter: nft_redir: use `struct nf_nat_range2` throughout and deduplicate 
eval call-backs
netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses
drm/syncobj: fix DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE
ASoC: hdmi-codec: register hpd callback on component probe
spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies
fbdev: imsttfb: Fix error path of imsttfb_probe()
fbdev: imsttfb: fix a resource leak in probe
fbdev: fsl-diu-fb: mark wr_reg_wa() static
tracing/kprobes: Fix the order of argument descriptions
btrfs: use u64 for buffer sizes in the tree search ioctls
Linux 5.15.139
UBUNTU: Upstream stable to v5.15.139

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Roxana Nicolescu (roxanan)
 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 Jammy)
   Importance: Undecided
   Status: New

** Description changed:

+ SRU Justification
  
- 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:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in s

[Kernel-packages] [Bug 2049189] Re: Lunar update: upstream stable release 2024-01-12

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Lunar)
   Status: In Progress => Won't Fix

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

Title:
  Lunar update: upstream stable release 2024-01-12

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Won't Fix

Bug description:
  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:

     upstream stable release 2024-01-12
  Ported from the following upstream stable releases:
  v6.1.58
  v6.1.59, v6.5.8
     from git://git.kernel.org/

  Revert "NFS: More fixes for nfs_direct_write_reschedule_io()"
  lib/test_meminit: fix off-by-one error in test_pages()
  drm/i915: Don't set PIPE_CONTROL_FLUSH_L3 for aux inval
  RDMA/cxgb4: Check skb value for failure to allocate
  perf/arm-cmn: Fix the unhandled overflow status of counter 4 to 7
  platform/x86: think-lmi: Fix reference leak
  platform/x86: hp-wmi:: Mark driver struct with __refdata to prevent section 
mismatch warning
  scsi: Do not rescan devices with a suspended queue
  HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect
  quota: Fix slow quotaoff
  ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM
  ata: libata-scsi: Disable scsi device manage_system_start_stop
  net: prevent address rewrite in kernel_bind()
  arm64: dts: qcom: sm8150: extend the size of the PDC resource
  dt-bindings: interrupt-controller: renesas,rzg2l-irqc: Update description for 
'#interrupt-cells' property
  irqchip: renesas-rzg2l: Fix logic to clear TINT interrupt source
  KEYS: trusted: Remove redundant static calls usage
  ALSA: usb-audio: Fix microphone sound on Opencomm2 Headset
  ALSA: usb-audio: Fix microphone sound on Nexigo webcam.
  ALSA: hda/realtek: Change model for Intel RVP board
  ASoC: SOF: amd: fix for firmware reload failure after playback
  ASoC: simple-card-utils: fixup simple_util_startup() error handling
  ASoC: Intel: soc-acpi: Add entry for HDMI_In capture support in MTL match 
table
  ASoC: Intel: sof_sdw: add support for SKU 0B14
  ASoC: Intel: soc-acpi: Add entry for sof_es8336 in MTL match table.
  ASoC: Use of_property_read_bool() for boolean properties
  ASoC: fsl_sai: MCLK bind with TX/RX enable bit
  ASoC: fsl_sai: Don't disable bitclock for i.MX8MP
  ALSA: hda/realtek: Add quirk for HP Victus 16-d1xxx to enable mute LED
  ALSA: hda/realtek: Add quirk for mute LEDs on HP ENVY x360 15-eu0xxx
  ALSA: hda/realtek - ALC287 merge RTK codec with CS CS35L41 AMP
  pinctrl: nuvoton: wpcm450: fix out of bounds write
  drm/msm/dp: do not reinitialize phy unless retry during link training
  drm/msm/dsi: skip the wait for video mode done if not applicable
  drm/msm/dsi: fix irq_of_parse_and_map() error checking
  drm/msm/dpu: change _dpu_plane_calc_bw() to use u64 to avoid overflow
  drm/msm/dp: Add newlines to debug printks
  phy: lynx-28g: cancel the CDR check work item on the remove path
  phy: lynx-28g: lock PHY while performing CDR lock workaround
  phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared 
registers
  net: dsa: qca8k: fix potential MDIO bus conflict when accessing internal PHYs 
via management frames
  can: isotp: isotp_sendmsg(): fix TX state detection and wait behavior
  can: sun4i_can: Only show Kconfig if ARCH_SUNXI is set
  arm64: dts: mediatek: mt8195: Set DSU PMU status to fail
  ravb: Fix up dma_free_coherent() call in ravb_remove()
  ravb: Fix use-after-free issue in ravb_tx_timeout_work()
  ieee802154: ca8210: Fix a potential UAF in ca8210_probe
  mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type
  xen-netback: use default TX queue size for vifs
  riscv, bpf: Factor out emit_call for kernel and bpf context
  riscv, bpf: Sign-extend return values
  drm/vmwgfx: fix typo of sizeof argument
  bpf: Fix verifier log for async callback return values
  net: refine debug info in skb_checksum_help()
  net: macsec: indicate next pn update when offloading
  net: phy: mscc: macsec: reject PN update requests
  net/mlx5e: macsec: use update_pn flag instead of PN comparation
  ixgbe: fix crash with empty VF macvlan list
  net/mlx5e: Again mutually exclude RX-FCS and RX-port-timestamp
  net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()
  pinctrl: renesas: rzn1: Enable missing PINMUX
  nfc: nci: assert requested protocol is valid
  workqueue: Override implicit ordered attribute in 
workqueue_apply_unbound_cpumask()
  tcp: enforce receiv

[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

[Roxana Nicolescu]

This should be solved in the lastest jammy:hwe-6.5 version. It's gonna
be in -proposed these days.

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11

[Kernel-packages] [Bug 2049022] Re: virtualbox-dkms.0.crash VirtualBox DKMS module NOT working

[Roxana Nicolescu]

I just tried installing virtualbox dkms and it did build. Version
6.1.48-dfsg-1~ubuntu1.22.04.1.

Are you using a different version?
And some logs from virtualbox client will help.

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

Title:
  virtualbox-dkms.0.crash VirtualBox DKMS module NOT working

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

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  vcarceler@zvezda:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  vcarceler@zvezda:~$

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  vcarceler@zvezda:~$ apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Instalados: 6.5.0.14.14~22.04.7
Candidato:  6.5.0.14.14~22.04.7
Tabla de versión:
   *** 6.5.0.14.14~22.04.7 500
  500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  vcarceler@zvezda:~$

  3) What you expected to happen

  VirtualBox works

  4) What happened instead

  VirtualBox not working

  Building virtualbox module fails. It's not possible to run virtual
  machines with virtualbox.

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


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

[Kernel-packages] [Bug 2049750] Re: "kvm: enabling virtualization on CPUx failed" on "Ubuntu 22.04.03 with kernel 6.5.0-14-generic"

[Roxana Nicolescu]

Can you include some logs so we can properly investigate.
Follow 'Adding debug info to a bug report' from 
https://wiki.ubuntu.com/Kernel/Bugs

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

Title:
  "kvm: enabling virtualization on CPUx failed" on "Ubuntu 22.04.03 with
  kernel 6.5.0-14-generic"

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

Bug description:
  Hi, I am on Ubuntu 22.04.03 with kernel 6.5.0-14-generic.

  Running a VM by AndroidStudio, it does not start, and into the DMSG
  log I see a message like "kvm: enabling virtualization on CPUx failed"
  for each CPU.

  It works with kernel 6.2.

  Regards,
  Antonio Petricca

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


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

[Kernel-packages] [Bug 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

[Roxana Nicolescu]

Can you also attach the boot logs for both versions? Thanks

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

Title:
  Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630
  Coffee Lake

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

Bug description:
  lsb_release
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  Laptop: Rebadged Clevo
  Graphics: on-board Intel UHD 630 

  Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

  Problem:- LCD laptop screen not detected on kernel 6.5.0-14

  The laptop LCD screen is black but the external RGB monitor works
  fine. Using kernel 6.2.0-39, both the LCD and external monitor work.

  inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  This line using journalctl is in the boot log of kernel 6.2 but not in the 
boot log of 6.5(probably not relevant)
  Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

  Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
  against nvidia graphics but will try 1024x768 resolution.

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


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

[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64

[Roxana Nicolescu]

Lunar is EOL


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

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

Title:
  test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
  K-5.19 / J-OEM-6.1 / J-6.2 AMD64

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Won't Fix
Status in linux-oem-6.1 source package in Lunar:
  New
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.1 source package in Mantic:
  New
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.1 source package in Noble:
  Invalid

Bug description:
  Issue found on 5.19.0-9.9 Kinetic AMD64 systems

  Test log:
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: 
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs ... (default libs native) (default libs native rekey) (default 
libs COMPAT) FAIL
   
   ==
   FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
   self._test_aslr('libs', expected)
 File "./test-kernel-security.py", line 1727, in _test_aslr
   self._test_aslr_all(area, expected, "default %s" % area)
 File "./test-kernel-security.py", line 1720, in _test_aslr_all
   self._test_aslr_exec(area, expected, target, name)
 File "./test-kernel-security.py", line 1703, in _test_aslr_exec
   self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1203, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: default libs COMPAT:
   Got exit code 1, expected 0
   Command: './aslr32', 'libs', '--verbose'
   Output:
   Checking ASLR of libs:
   0xf7c81790
   0xf7c81790
   0xf7c81790
   FAIL: ASLR not functional (libs always at 0xf7c81790)
   
   
   --
   Ran 1 test in 0.144s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+subscriptions


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051584 is picking 6.6 
which includes the fix.
And it's going to be included for the next cycle for mantic and therefore 
hwe-6.5.

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  It is exactly this bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

My bad that's 6.6, not 6.9. I'll backport it asap so that will be in the
next cycle

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  It is exactly this bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

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

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

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

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

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  It is exactly this bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

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

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  It is exactly this bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

** Description changed:

- It is exactly this bug:
- https://gitlab.freedesktop.org/drm/intel/-/issues/8685
+ 
+ SRU Justification:
+ 
+ [Impact]
+ 
+ Multiple users have reported frozen displays when external HDMI device
+ is connected on systems with intel graphics chipsets.
+ 
+ [Fix]
+ 
+ * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
+ from 6.6.9
+ 
+ [Test Plan]
+ 
+ * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
+ It seems it affects mostly Alder Lake though, but at least it does not
+ cause any issues on other models.
+ * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685
+ 
+ [Where problems could occur]
+ * We could see issues on systems with Intel Graphics when HDMI devices
+ are connected during power state changes.
+ 
+ 
+ Old description:
+ It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685
  
  It was fixed with that kernel commit:
  
  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200
  
- drm/i915/dmc: Don't enable any pipe DMC events
- 
+ drm/i915/dmc: Don't enable any pipe DMC events
  
  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/
  
  which was picked for 6.6.9.
  
  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?
  
  Best
  Sönke
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  
  SRU Justification:

  [Impact]

  Multiple users have reported frozen displays when external HDMI device
  is connected on systems with intel graphics chipsets.

  [Fix]

  * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
  from 6.6.9

  [Test Plan]

  * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
  It seems it affects mostly Alder Lake though, but at least it does not
  cause any issues on other models.
  * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  [Where problems could occur]
  * We could see issues on systems with Intel Graphics when HDMI devices
  are connected during power state changes.

  
  Old description:
  It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device

[Roxana Nicolescu]

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

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

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

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

Title:
  linux-image-5.15.0-94-generic breaks partprobe on empty loopback
  device

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

Bug description:
  This is with the kernel from jammy-proposed (linux-
  image-5.15.0-94-generic 5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


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

[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device

[Roxana Nicolescu]

** Description changed:

- This is with the kernel from jammy-proposed (linux-
- image-5.15.0-94-generic 5.15.0-94.104).
+ SRU Justification:
+ 
+ [Impact]
+ 
+ * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
+ but now returns EINVAL, breaking partprobe due to commit
+ "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
+ introduced in mantic 6.5.0-17 and jammy 5.15.0-94.
+ 
+ [Fix]
+ 
+ * backport commit
+ "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"
+ 
+ [Test Plan]
+ 
+ * dd if=/dev/zero of=/tmp/foo bs=1M count=50
+ * partprobe $(losetup --find --show /tmp/foo)
+ Before the fix this fails.
+ After the fix it should work.
+ 
+ [Where problems could occur]
+ 
+ * We may see issues on disk partitions operations.
+ 
+ 
+ Old description:
+ This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).
  
  Do this:
  
  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"
  
  Notice this very odd error message:
  
  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33,
  34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51,
  52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop2 have
  been written, but we have been unable to inform the kernel of the
  change, probably because it/they are in use.  As a result, the old
  partition(s) will remain in use.  You should reboot now before making
  further changes.
  
  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.
  
  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)
  
  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
  
  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).
  
  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793
  
  This issue is being discussed on LKML here (with a patch likely to land
  soon): https://lkml.org/lkml/2024/1/15/147
  
  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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

Title:
  linux-image-5.15.0-94-generic breaks partprobe on empty loopback
  device

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

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed b

[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device

[Roxana Nicolescu]

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

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

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

Title:
  linux-image-5.15.0-94-generic breaks partprobe on empty loopback
  device

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

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


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

[Kernel-packages] [Bug 2049689] Re: partproke is broken on empty loopback device

[Roxana Nicolescu]

** Summary changed:

- linux-image-5.15.0-94-generic breaks partprobe on empty loopback device
+ partproke is broken on empty loopback device

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

Title:
  partproke is broken on empty loopback device

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

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


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

[Kernel-packages] [Bug 2049689] Re: partproke is broken on empty loopback device

[Roxana Nicolescu]

It is expected to be released in 2 weeks

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

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => 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/2049689

Title:
  partproke is broken on empty loopback device

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

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


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

[Kernel-packages] [Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec

[Roxana Nicolescu]

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

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

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

Title:
  Audio balancing setting doesn't work with the cirrus codec

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

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

  Currently this patch is in the linux-next, and will be in the
  mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble
  kernel, Noble kernel will have this patch automatically.

  [Impact]
  In the gnome audio setting, if we adjust balancing setting, it doesn't
  work at all on a Dell machine with cirrus codec, that is because with
  the current driver, the exported amixer controls can't be handled by
  pulseaudio.

  [Fix]
  Cherry-pick a mainline kernel patch, this could fix this issue.

  [Test]
  Booted with the patched kernel, move the bar to the left or right to
  adjust the balance, we could hear the sound from left channel or right
  channel accordingly.

  [Where problems could occur]
  This change will not create "Master Volume" amixer controls, probably
  will make the audio control malfunction, that is we couldn't control
  playback or capture volume correctly, but this regression possibility
  is very low, we already tested the patch on the machines with cirrus
  codec, they all worked well as before.

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


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

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

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

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

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  
  SRU Justification:

  [Impact]

  Multiple users have reported frozen displays when external HDMI device
  is connected on systems with intel graphics chipsets.

  [Fix]

  * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
  from 6.6.9

  [Test Plan]

  * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
  It seems it affects mostly Alder Lake though, but at least it does not
  cause any issues on other models.
  * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  [Where problems could occur]
  * We could see issues on systems with Intel Graphics when HDMI devices
  are connected during power state changes.

  
  Old description:
  It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel

[Roxana Nicolescu]

MAntic is fixed with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051584

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

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

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

Title:
  i915 regression introduced with 5.5 kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.15 source package in Focal:
  Triaged
Status in linux source package in Jammy:
  Fix Committed
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-hwe-5.15 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-5.15 source package in Noble:
  Invalid

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Original bug description:

  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the hardware should be still
  supported.

  Attaching lshw and lspci output.

To manage notifications 

[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => 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/2045233

Title:
  [SRU][22.04.04]: mpi3mr driver update

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Opinion
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [Impact]

  This update has been initiated to incorporate the mpi3mr driver from
  upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point
  releases).

  This has been requested by both Broadcom as the upstream and by one of
  the larger OEM partners who are going to be selling systems with these
  storage controllers to customers.  This series of patches includes bug
  fixes and support for current Broadcom controllers.

  [Fixes]
  Below are the commit IDs for the latest upstream version (v6.8).

  The 22.04 LTS point kernel already includes the latest mpi3mr driver
  version 8.0.0.69.0. Therefore, the listed commit IDs below correspond
  to the subsequent patches.

  The commit IDs listed below are in sequential order from bottom to
  top, indicating the order for applying the patches.

  linux-next
  d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0
  9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers 
part-3
  fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers 
part-2
  c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers 
part-1
  07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply 
descriptor
  f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and 
Unrecoverable State
  c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset
  e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset
  b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50
  1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor
  cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32
  c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116
  6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs

  Mainline at 6.6/6.7
  82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset
  9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0
  d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after 
controller reset
  e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation
  d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O
  6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28
  9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out

  [Testing]
  verify the mpi3mr driver is loaded
  verify the version string shows 8.5.1.0.0

  [Regression Risk]
  Low. These patches are contained to the mpi3mr driver code itself and are all 
already accepted upstream.  They cleanly pick into our 6.5 kernel tree.

  Broadcom has tested these and the only concern is the kernel warning
  below in Comment #7

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


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

[Kernel-packages] [Bug 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files

[Roxana Nicolescu]

Tested on multiple main kernels but also derivatives

** Tags removed: verification-needed-focal-linux 
verification-needed-jammy-linux-ibm-gt-fips 
verification-needed-jammy-linux-intel-iotg verification-needed-lunar-linux
** Tags added: verification-done-focal-linux 
verification-done-jammy-linux-ibm-gt-fips 
verification-done-jammy-linux-intel-iotg verification-done-lunar-linux

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

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

Title:
  [Debian] autoreconstruct - Do not generate chmod -x for deleted  files

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Debian source format 1.0 cannot remove files, create symlinks and change
  permission in the .diff.gz tarball. Therefore any changes in these 3
  categories cannot be represented without any tricks. To solve this,
  the `reconstruct` script is used every time we build the source package.
  The script is generated by `gen-auto-reconstruct` script during `cranky
  close`. It checks if there has been any changes in the 3 categories
  mentioned above between the upstream version (i.e v6.5) and the current one.
  The problem with the script is that in case a file A was removed since the
  upstream version was released, the `reconstruct` script will contains
  these commands in this exact order:
  rm -f A
  chmod -x A
  The second command will fail because file A does not exist anymore.
  This is solved by generating the `chmod +/-x` commands before `rm`.
  Which results in:
  chmod -x A
  rm -f A
  But because the reconstruct script is used during `clean` rule which is
  triggered pretty much during every cranky step which is run in the
  source repo, the first command will always file because file A is not
  present anymore in the tree. To solved this, any `chmod` change is added
  only if the file has not been deleted. Therefore if file A has been
  deleted, the `reconstruct` script will contain only this:
  rm -f A

  [Fix]
  Generate chmod commands first.
  And when generating chmod -x command, first check if the file has been 
deleted. If yes, no need for a chmod command.

  [Test Plan]
  It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and 
it reconstruct script looked correct.

  [Other Info]
  An example of this is #lp2038611 where `script/is_rust_module.sh` was 
removed, but we keep seeing
  "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory"
  because `rm -f` and `chmod -x` command were generated.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Roxana Nicolescu]

** Changed in: linux-meta-azure (Ubuntu Lunar)
   Status: New => Invalid

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

** Changed in: linux-meta-kvm (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-meta-kvm (Ubuntu Lunar)
   Status: New => Invalid

** Changed in: linux-kvm (Ubuntu Kinetic)
   Status: In Progress => Invalid

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  Invalid
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  Invalid
Status in linux-meta-kvm source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Roxana Nicolescu]

This bug VT is a mess.. Nevertheless.

Jammy:lowlatency-hwe-6.5
./amd64-config.flavour.lowlatency:3084:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
./amd64-config.flavour.lowlatency:3085:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y


** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-lowlatency-hwe-6.5

** Tags removed: verification-done-jammy-linux-lowlatency-hwe-6.5 
verification-needed-jammy-linux-hwe-6.5
** Tags added: verification-done-jammy-linux-hwe-6.5 
verification-needed-jammy-linux-lowlatency-hwe-6.5

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  Invalid
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  Invalid
Status in linux-meta-kvm source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Roxana Nicolescu]

Jammy:hwe-6.5
CONFIGS/amd64-config.flavour.generic:3079:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.generic:3080:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  Invalid
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  Invalid
Status in linux-meta-kvm source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Roxana Nicolescu]

jammy:nvidia-6.5
CONFIGS/amd64-config.flavour.nvidia:3079:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.nvidia:3080:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y


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

** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-lowlatency-hwe-6.5

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  Invalid
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  Invalid
Status in linux-meta-kvm source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Roxana Nicolescu]

mantic:linux-gcp
CONFIGS/amd64-config.flavour.gcp:3080:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.gcp:3081:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  Invalid
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  Invalid
Status in linux-meta-kvm source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Roxana Nicolescu]

mantic:linux-azure
CONFIGS/amd64-config.flavour.azure:2785:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.azure:2786:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y


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

** Tags removed: verification-needed-mantic-linux-gcp 
verification-needed-mantic-linux-laptop
** Tags added: verification-done-mantic-linux-gcp 
verification-done-mantic-linux-laptop

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  Invalid
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  Invalid
Status in linux-meta-kvm source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

[Kernel-packages] [Bug 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images

[Roxana Nicolescu]

mantic:linux-laptop
CONFIGS/arm64-config.flavour.laptop:3151:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/arm64-config.flavour.laptop:3152:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y

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

Title:
  linux-*: please enable dm-verity kconfigs to allow MoK/db verified
  root images

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-meta-azure package in Ubuntu:
  Invalid
Status in linux-meta-kvm package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  Fix Released
Status in linux-meta-azure source package in Jammy:
  Invalid
Status in linux-meta-kvm source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-kvm source package in Kinetic:
  Invalid
Status in linux-meta-azure source package in Kinetic:
  Invalid
Status in linux-meta-kvm source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-kvm source package in Lunar:
  Fix Released
Status in linux-meta-azure source package in Lunar:
  Invalid
Status in linux-meta-kvm source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-kvm source package in Mantic:
  Invalid
Status in linux-meta-azure source package in Mantic:
  Invalid
Status in linux-meta-kvm source package in Mantic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The kvm flavours currently do not enable dm-verity. This stops us from
  using integrity protected and verified images in VMs using this kernel
  flavour.

  [Fix]

  Please consider enabling the following kconfigs:

  CONFIG_DM_VERITY
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
  CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
  CONFIG_INTEGRITY_MACHINE_KEYRING
  CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring 
implementation is patched to skip the check enabled by this kconfig)

  (The latter two are needed to ensure that MoK keys can be used to
  verify dm-verity images too, via the machine keyring linked to the
  secondary keyring)

  These are already enabled in the 'main' kernel config, and in other
  distros.

  As a specific and explicit use case, in the systemd project we want to
  test functionality provided by systemd that needs these kconfigs on
  Ubuntu machines running the kvm flavour kernel.

  To verify whether this works, add a certificate to MOK, boot and check
  the content of the secondary keyring. The machine keyring should show
  up under it, and it should show the certificates loaded in MOK. E.g.:

  $ sudo keyctl show %:.secondary_trusted_keys
  Keyring
   159454604 ---lswrv  0 0  keyring: .secondary_trusted_keys
    88754641 ---lswrv  0 0   \_ keyring: .builtin_trusted_keys
   889010778 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   799434660 ---lswrv  0 0   |   \_ asymmetric: Debian Secure Boot 
Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f
   541326986 ---lswrv  0 0   \_ keyring: .machine
   188508854 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
   475039424 ---lswrv  0 0   \_ asymmetric: sb-bluca: Secure Boot 
Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479

  [Regression Potential]

  MOK keys may not be correctly read.

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


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

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

[Roxana Nicolescu]

Considering the lack of time and the no of VT needed, I won't boot the kernels 
and then check if the module is there.
I'll generate the configs options and then if WWAN is m.

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

mantic:linux-laptop
CONFIGS/arm64-config.flavour.laptop:4367:CONFIG_WWAN=m

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

mantic:linux-azure
CONFIGS/arm64-config.flavour.azure:4438:CONFIG_WWAN=m
CONFIGS/amd64-config.flavour.azure:3383:CONFIG_WWAN=m


** Tags removed: verification-needed-lunar-linux-riscv 
verification-needed-lunar-linux-starfive verification-needed-mantic-linux 
verification-needed-mantic-linux-azure verification-needed-mantic-linux-gcp 
verification-needed-mantic-linux-laptop
** Tags added: verification-done-lunar-linux-riscv 
verification-done-lunar-linux-starfive verification-done-mantic-linux 
verification-done-mantic-linux-azure verification-done-mantic-linux-gcp 
verification-done-mantic-linux-laptop

** Tags removed: verification-needed-lunar-linux-aws 
verification-needed-lunar-linux-kvm
** Tags added: verification-done-lunar-linux-aws 
verification-done-lunar-linux-kvm

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

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

mantic:linux
CONFIGS/riscv64-config.flavour.generic:3822:CONFIG_WWAN=m
CONFIGS/armhf-config.flavour.generic:4222:CONFIG_WWAN=y
CONFIGS/arm64-config.flavour.generic:4366:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.generic-64k:4363:CONFIG_WWAN=m
CONFIGS/ppc64el-config.flavour.generic:3863:CONFIG_WWAN=y
CONFIGS/amd64-config.flavour.generic:4216:CONFIG_WWAN=m


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

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

mantic:linux-gcp
CONFIGS/amd64-config.flavour.gcp:4213:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.gcp:4434:CONFIG_WWAN=m

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

jammy:linux-nvidia-6.5
CONFIGS/arm64-config.flavour.nvidia:4362:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.nvidia-64k:4359:CONFIG_WWAN=m
CONFIGS/amd64-config.flavour.nvidia:4211:CONFIG_WWAN=m


** Tags removed: verification-needed-jammy-linux-nvidia-tegra 
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-nvidia-tegra 
verification-done-jammy-linux-nvidia-tegra-igx

** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-lowlatency-hwe-6.5

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

jammy:lowlatency-hwe-6.5
CONFIGS/amd64-config.flavour.lowlatency:4216:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.lowlatency:4371:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.lowlatency-64k:4368:CONFIG_WWAN=m


** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.2
** Tags added: verification-done-jammy-linux-lowlatency-hwe-6.2

** Tags removed: verification-needed-jammy-linux-hwe-6.2 
verification-needed-jammy-linux-hwe-6.5
** Tags added: verification-done-jammy-linux-hwe-6.2 
verification-done-jammy-linux-hwe-6.5

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

jammy:hwe-6.5
ONFIGS/riscv64-config.flavour.generic:3819:CONFIG_WWAN=m
CONFIGS/armhf-config.flavour.generic:4222:CONFIG_WWAN=y
CONFIGS/arm64-config.flavour.generic:4366:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.generic-64k:4363:CONFIG_WWAN=m
CONFIGS/ppc64el-config.flavour.generic:3863:CONFIG_WWAN=y
CONFIGS/amd64-config.flavour.generic:4211:CONFIG_WWAN=m


jammy:linux-lowlatency
CONFIGS/amd64-config.flavour.lowlatency:4043:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.lowlatency:4125:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.lowlatency-64k:4125:CONFIG_WWAN=m

focal:gcp-5.15
CONFIGS/amd64-config.flavour.gcp:4038:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.gcp:4170:CONFIG_WWAN=m


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

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

** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15
** Tags added: verification-done-focal-linux-nvidia-tegra-5.15

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

jammy:linux-intel-iotg
CONFIGS/amd64-config.flavour.intel-iotg:4043:CONFIG_WWAN=m


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

** Tags removed: verification-needed-focal-linux-gcp-5.15
** Tags added: verification-done-focal-linux-gcp-5.15

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

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

jammy:linux-gkeop
CONFIGS/amd64-config.flavour.gkeop:4042:CONFIG_WWAN=m


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

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

jammy:linux-azure-fips

CONFIGS/arm64-config.flavour.azure-fips:3372:CONFIG_WWAN=m
CONFIGS/amd64-config.flavour.azure-fips:3226:CONFIG_WWAN=m

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

focal:linux-intel-iotg-5.15
CONFIGS/amd64-config.flavour.intel-iotg-5.15:4039:CONFIG_WWAN=m


** Tags removed: verification-needed-focal-linux-intel-iotg-5.15
** Tags added: verification-done-focal-linux-intel-iotg-5.15

** Tags removed: verification-needed-focal-linux-gcp-tcpx
** Tags added: verification-done-focal-linux-gcp-tcpx

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals

[Roxana Nicolescu]

jammy:hwe-6.5
CONFIGS/arm64-config.flavour.generic-64k:11066:CONFIG_IOMMU_IO_PGTABLE_ARMV7S=y
CONFIGS/arm64-config.flavour.generic:11071:CONFIG_IOMMU_IO_PGTABLE_ARMV7S=y

CONFIGS/arm64-config.flavour.generic:11096:CONFIG_MTK_IOMMU=m
CONFIGS/arm64-config.flavour.generic-64k:11091:CONFIG_MTK_IOMMU=m

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

Title:
  [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for
  multimedia and PCIE peripherals

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

Bug description:
  [SRU Justification]

  [Impact]
  IOMMU related peripherals cannot work.

  [Fix]
  CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. 
CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency.

  [Test Case]
  build test.
  this is the first step to enable the platform on generic kernel. to fully 
enable the platform, there are some modifications still needed, so only the 
build test is performed at this stage.

  [Where problems could occur]
  to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be 
built-in. the risk would be low because it's not used by default and it needs 
the driver to allocate by demand.

  [Other info]
  the purpose of this is to make ubuntu as an arm systemready ir distribution 
for mediatek platform.

  https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady-
  IR/Test-installation-of-Linux-distributions?lang=en

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


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

[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals

[Roxana Nicolescu]

mantic:linux
CONFIGS/arm64-config.flavour.generic:11096:CONFIG_MTK_IOMMU=m
CONFIGS/arm64-config.flavour.generic-64k:11091:CONFIG_MTK_IOMMU=m


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

** Tags removed: verification-needed-mantic-linux-azure 
verification-needed-mantic-linux-gcp verification-needed-mantic-linux-laptop
** Tags added: verification-done-mantic-linux-azure 
verification-done-mantic-linux-gcp verification-done-mantic-linux-laptop

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

Title:
  [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for
  multimedia and PCIE peripherals

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

Bug description:
  [SRU Justification]

  [Impact]
  IOMMU related peripherals cannot work.

  [Fix]
  CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. 
CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency.

  [Test Case]
  build test.
  this is the first step to enable the platform on generic kernel. to fully 
enable the platform, there are some modifications still needed, so only the 
build test is performed at this stage.

  [Where problems could occur]
  to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be 
built-in. the risk would be low because it's not used by default and it needs 
the driver to allocate by demand.

  [Other info]
  the purpose of this is to make ubuntu as an arm systemready ir distribution 
for mediatek platform.

  https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady-
  IR/Test-installation-of-Linux-distributions?lang=en

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


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

[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals

[Roxana Nicolescu]

Same for nvidia-6.5

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

Title:
  [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for
  multimedia and PCIE peripherals

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

Bug description:
  [SRU Justification]

  [Impact]
  IOMMU related peripherals cannot work.

  [Fix]
  CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. 
CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency.

  [Test Case]
  build test.
  this is the first step to enable the platform on generic kernel. to fully 
enable the platform, there are some modifications still needed, so only the 
build test is performed at this stage.

  [Where problems could occur]
  to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be 
built-in. the risk would be low because it's not used by default and it needs 
the driver to allocate by demand.

  [Other info]
  the purpose of this is to make ubuntu as an arm systemready ir distribution 
for mediatek platform.

  https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady-
  IR/Test-installation-of-Linux-distributions?lang=en

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


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

[Kernel-packages] [Bug 2036587] Re: [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals

[Roxana Nicolescu]

Same for lowlatency-hwe-6.5


** Tags removed: verification-needed-jammy-linux-hwe-6.5 
verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-hwe-6.5 
verification-done-jammy-linux-lowlatency-hwe-6.5

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

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

Title:
  [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for
  multimedia and PCIE peripherals

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

Bug description:
  [SRU Justification]

  [Impact]
  IOMMU related peripherals cannot work.

  [Fix]
  CONFIG_MTK_IOMMU should be enabled as "module" in generic kernel settings. 
CONFIG_IOMMU_IO_PGTABLE_ARMV7S is also enabled due to dependency.

  [Test Case]
  build test.
  this is the first step to enable the platform on generic kernel. to fully 
enable the platform, there are some modifications still needed, so only the 
build test is performed at this stage.

  [Where problems could occur]
  to enable MTK_IOMMU as a module, IOMMU_IO_PGTABLE_ARMV7S needs to be 
built-in. the risk would be low because it's not used by default and it needs 
the driver to allocate by demand.

  [Other info]
  the purpose of this is to make ubuntu as an arm systemready ir distribution 
for mediatek platform.

  https://developer.arm.com/documentation/DUI1101/2-0/Test-SystemReady-
  IR/Test-installation-of-Linux-distributions?lang=en

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


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

[Kernel-packages] [Bug 2038522] Re: disable shiftfs

[Roxana Nicolescu]

jammy:lowlatency-hwe-6.5
modprobe: FATAL: Module shiftfs not found in directory 
/lib/modules/6.5.0-14-lowlatency

jammy:hwe-6.5
modprobe: FATAL: Module shiftfs not found in directory 
/lib/modules/6.5.0-17-generic

** Tags removed: verification-needed-mantic-linux-azure 
verification-needed-mantic-linux-gcp verification-needed-mantic-linux-laptop
** Tags added: verification-done-mantic-linux-azure 
verification-done-mantic-linux-gcp verification-done-mantic-linux-laptop

** Tags removed: verification-needed-jammy-linux-hwe-6.5 
verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-hwe-6.5 
verification-done-jammy-linux-lowlatency-hwe-6.5

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

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

Title:
  disable shiftfs

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

Bug description:
  [Impact]

  Now that all the filesystems that we officially support have the
  idmapped mounts capability we can get rid of shiftfs.

  The benefit of this change is that we don't have to maintain an out-
  of-tree filesystem anymore and we can completely rely on upstream
  features.

  [Test case]

  lxd was the main user of shiftfs to compensate the lack of idmapped
  mounts capability of certain filesystems, such as zfs / ceph, but now
  in mantic also these two filesystem received the support for idmapped
  mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see
  LP: #2032959).

  The lxd team provided a positive feedback, testing the latest 6.5
  Mantic kernel across all the supported filesystems with shiftfs
  disabled.

  [Fix]

  Disable shiftfs in the kernel config and enable unsafe idmapped mounts
  by default (default=on).

  [Regression potential]

  The support for idmapped mounts for the ceph filesystem is not applied
  upstream yet, so we may experience regressions in systems that are
  using this filesystem. Moreover disabling shiftfs may trigger failures
  in our testing (testing shiftfs capabilities will obviously fail) or
  break any other user-space application that is relying on shiftfs
  (however to our knowledge lxd was the only "official" user or shiftfs;
  for this reason we may also see potential regressions in lxd).

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


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

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

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux 
verification-needed-jammy-linux-ibm-gt-fips 
verification-needed-jammy-linux-intel-iotg verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux 
verification-done-jammy-linux-ibm-gt-fips 
verification-done-jammy-linux-intel-iotg verification-done-mantic-linux

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

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

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

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

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

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

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

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

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

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

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

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


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

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

[Roxana Nicolescu]

** Tags removed: verification-needed-lunar-linux-starfive 
verification-needed-mantic-linux-azure verification-needed-mantic-linux-gcp 
verification-needed-mantic-linux-lowlatency
** Tags added: verification-done-lunar-linux-starfive 
verification-done-mantic-linux-azure verification-done-mantic-linux-gcp 
verification-done-mantic-linux-lowlatency

** Tags removed: verification-needed-lunar-linux-aws 
verification-needed-lunar-linux-azure verification-needed-lunar-linux-kvm 
verification-needed-lunar-linux-riscv verification-needed-mantic-linux-laptop
** Tags added: verification-done-lunar-linux-aws 
verification-done-lunar-linux-azure verification-done-lunar-linux-kvm 
verification-done-lunar-linux-riscv verification-done-mantic-linux-laptop

** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.2 
verification-needed-jammy-linux-lowlatency-hwe-6.5 
verification-needed-jammy-linux-nvidia-6.5 
verification-needed-jammy-linux-nvidia-tegra 
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-lowlatency-hwe-6.2 
verification-done-jammy-linux-lowlatency-hwe-6.5 
verification-done-jammy-linux-nvidia-6.5 
verification-done-jammy-linux-nvidia-tegra 
verification-done-jammy-linux-nvidia-tegra-igx

** Tags removed: verification-needed-jammy-linux-gkeop 
verification-needed-jammy-linux-hwe-6.2 verification-needed-jammy-linux-hwe-6.5 
verification-needed-jammy-linux-intel-iotg 
verification-needed-jammy-linux-lowlatency
** Tags added: verification-done-jammy-linux-gkeop 
verification-done-jammy-linux-hwe-6.2 verification-done-jammy-linux-hwe-6.5 
verification-done-jammy-linux-intel-iotg 
verification-done-jammy-linux-lowlatency

** Tags removed: verification-needed-focal-linux-intel-iotg-5.15 
verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-azure-fips 
verification-needed-jammy-linux-bluefield 
verification-needed-jammy-linux-gcp-6.2
** Tags added: verification-done-focal-linux-intel-iotg-5.15 
verification-done-focal-linux-nvidia-tegra-5.15 
verification-done-jammy-linux-azure-fips 
verification-done-jammy-linux-bluefield verification-done-jammy-linux-gcp-6.2

** Tags removed: verification-needed-focal-linux-gcp-5.15 
verification-needed-focal-linux-gcp-tcpx
** Tags added: verification-done-focal-linux-gcp-5.15 
verification-done-focal-linux-gcp-tcpx

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

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

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


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

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

[Roxana Nicolescu]

Marking all these derivatives as verified since the main ones are verified. 
I need to check why these were triggered in the first place.

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

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

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


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

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

[Roxana Nicolescu]

Also tested on hwe-6.5 and lowlatency-hwe-6.5.
Installing linux-tools-common will install hwdata

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

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

  [Fix]

  Make hwdata a dependency of linux-tools-common.

  [Regression Potential]

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

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


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

[Kernel-packages] [Bug 2044512] Re: Build failure if run in a console

[Roxana Nicolescu]

Looks alright to me 
...
# Compress kernel modules, on mantic+
find debian/linux-buildinfo-6.5.0-20-generic -name '*.ko' -print0 | xargs -0 
-n1 -P 4 -r zstd -19 --quiet --rm
dh_fixperms -plinux-buildinfo-6.5.0-20-generic -X/boot/
...

https://launchpadlibrarian.net/712537644/buildlog_ubuntu-mantic-
amd64.linux_6.5.0-20.20_BUILDING.txt.gz

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

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

Title:
  Build failure if run in a console

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [Impact]

  Build fails if run in a console:

  $ debian/rules binary
  ...
  # Compress kernel modules
  find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 
-P 8 zstd -19 --quiet --rm
  stdout is a console, aborting
  make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123

  [Test Case]

  See above.

  [Where Problems Could Occur]

  Build failures.

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


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

[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

[Roxana Nicolescu]

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

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

Title:
  Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

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

Bug description:
  [Impact]
  Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops

  [Fix]
  Need to backport 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492
 to support dual speaker configuration on Dell Oasis series

  [Test Case]
  1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA.
  2. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Add CS35L41 support on specific Dell laptops. Risk of regression is low.

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


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

[Kernel-packages] [Bug 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Roxana Nicolescu]

Dan Clash, apologize for the late reply. Next time feel free to test it since 
you know the details better than anyone. Just use the latest version in 
proposed.
But providing the test info was really useful as I managed to test it without 
spending time on it, so thanks for that :)

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

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

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

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is to change the refcnt member of struct audit_names
  from int to atomic_t.

  kernel BUG at fs/namei.c:262!
  Call Trace:
  ...
   ? putname+0x68/0x70
   audit_reset_context.part.0.constprop.0+0xe1/0x300
   __audit_uring_exit+0xda/0x1c0
   io_issue_sqe+0x1f3/0x450
   ? lock_timer_base+0x3b/0xd0
   io_wq_submit_work+0x8d/0x2b0
   ? __try_to_del_timer_sync+0x67/0xa0
   io_worker_handle_work+0x17c/0x2b0
   io_wqe_worker+0x10a/0x350

  Cc: sta...@vger.kernel.org
  Link: 
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
  Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support 
to io_uring")
  Signed-off-by: Dan Clash 
  Link: 
https://lore.kernel.org/r/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
  Reviewed-by: Jens Axboe 
  Signed-off-by: Christian Brauner 

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


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

[Kernel-packages] [Bug 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Roxana Nicolescu]

Ran ./io_uring_open_close_audit_hang --directory /tmp/deleteme --count 1 on 
6.5.0-17-generic
and it finished

** Tags removed: verification-needed-lunar-linux 
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

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

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is to change the refcnt member of struct audit_names
  from int to atomic_t.

  kernel BUG at fs/namei.c:262!
  Call Trace:
  ...
   ? putname+0x68/0x70
   audit_reset_context.part.0.constprop.0+0xe1/0x300
   __audit_uring_exit+0xda/0x1c0
   io_issue_sqe+0x1f3/0x450
   ? lock_timer_base+0x3b/0xd0
   io_wq_submit_work+0x8d/0x2b0
   ? __try_to_del_timer_sync+0x67/0xa0
   io_worker_handle_work+0x17c/0x2b0
   io_wqe_worker+0x10a/0x350

  Cc: sta...@vger.kernel.org
  Link: 
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
  Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support 
to io_uring")
  Signed-off-by: Dan Clash 
  Link: 
https://lore.kernel.org/r/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
  Reviewed-by: Jens Axboe 
  Signed-off-by: Christian Brauner 

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


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

[Kernel-packages] [Bug 2043730] Re: Update io_uring to 6.6

[Roxana Nicolescu]

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

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

Title:
  Update io_uring to 6.6

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

Bug description:
  [Impact]
  io_uring is a fast-developed subsystem in the Linux kernel. In order to keep 
up with the latest changes such that applying further fixes are possible, it 
should be updated to a more recent version.

  [Test case]
  Given the general update, there are no specific test cases.

  [Potential regression]
  io_uring users only would be affected given most changes are restricted to it.

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


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

[Kernel-packages] [Bug 2041613] Re: correct cephfs pull request for uidmap support

[Roxana Nicolescu]

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

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

Title:
  correct cephfs pull request for uidmap support

Status in linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]

   * During mantic dev cycle, we pulled all of cephfs testing patches, rather 
than uidmapshift patches alone
   * We also pulled in debug patches that generate a lot of dmesg and delays in 
the cephfs module

  [ Test Plan ]

   * run ceph fs and experience less dmesg at info level

  [ Where problems could occur ]

   * Hopefully the reverts were done correctly, and none of the messages
  reference non-existing things, in all the code paths.

  [ Other Info ]

   * Story time how we got here:

  The following pull requests

  BugLink: https://bugs.launchpad.net/bugs/2038522
  BugLink: https://bugs.launchpad.net/bugs/2032959

  generated the following commit list 1:

  eddf9ed788 UBUNTU: [Config] disable shiftfs
  72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default
  80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts
  9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op
  ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op
  1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op
  b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr
  8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op
  e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op
  f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir
  5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter
  19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in 
create_request_message()
  6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request
  8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put
  55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32
  54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct 
ceph_mds_request_args_ext an union
  f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug 
logs
  b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support
  a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/
  cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client()
  42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers
  9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support
  8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client 
caps still outstanding
  a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting
  17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio 
with a non-NULL ->private
  834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're 
waiting too long for them
  498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128
  3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h
  d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new 
fscrypt helper
  8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for 
fscrypt
  288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish 
when unmounting
  435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting
  862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot 
naming limitations
  904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked 
directories
  a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names
  e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes
  9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads
  e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and 
writepages
  0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write
  a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write
  edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for encrypted 
inodes
  efed7d1764 UBUNTU: SAUCE: ceph: add truncate size handling support for fscrypt
  5d65284a6a UBUNTU: SAUCE: ceph: add object version support for sync read
  d76cff7c37 UBUNTU: SAUCE: libceph: allow ceph_osdc_new_request to accept a 
multi-op read
  53d1c3958e UBUNTU: SAUCE: libceph: add CEPH_OSD_OP_ASSERT_VER support
  7ecbaa5849 UBUNTU: SAUCE: ceph: add infrastructure for file encryption and 
decryption
  4142d15305 UBUNTU: SAUCE: ceph: handle fscrypt fields in cap messages from MDS
  53507ac6a8 UBUNTU: SAUCE: ceph: size handling in MClientRequest, cap updates 
and inode traces
  b9936d13f4 UBUNTU: SAUCE: ceph: mark directory as non-complete after lo

[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0

[Roxana Nicolescu]

** Tags removed: verification-needed-lunar-linux 
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

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

  [Impact]

  NVME module left unready, therefore not recognized by the installation 
process, and/or after installation with following error messages:
  ```
  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0
  ```

  [Fix]

  Proposed fix in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5&id=6cc834ba62998c65c42d0c63499bdd35067151ec
  "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well
  as stable kernels v6.1.55 and v6.5.5.

  [Test Case]

  Apply to kernel and boot with the nvme module installed. Now the device 
should be probed with success.
  ```
  kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0
  kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI 
INT A
  kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff
  kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds
  kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer.
  kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues
  kernel: [2.136735]  nvme0n1: p1 p2 p3
  ```

  [Where problems could occur]

  This patch tries to set an appropriate CRTO (Controller Ready
  Timeouts) that may be reported incorrectly by some devices. There
  should be little (a bit longer CRTO) to no effect on devices
  performing normally before hands.

  [Other Info]

  While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1
  will be nominated.

  == original bug report ==

  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

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


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

[Kernel-packages] [Bug 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card

[Roxana Nicolescu]

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

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

Title:
  System hang after unplug/plug DP monitor with AMD W7500 card

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System hangs and no external output after unplug/plug DP monitor. (AMD Radeon 
Pro W7500)
  Observed a bunch of [Hardware Error] messages and finally amdgpu crashed.

  [Fix]
  AMD provides a patch to fix the issue
  https://www.spinics.net/lists/amd-gfx/msg99737.html

  which is included in v6.7-rc1
  7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code

  [Testcase]
  1. Connect the DUT to an external DP monitor via one of the ports on the AMD 
graphics card
  2. Boot into Ubuntu
  3. Unplug the DP cable from the DUT
  4. Wait for 30 seconds
  5. Replug in the DP cable
  6. Make sure the system doesn't hang and the external DP monitor works

  [Where probles could occur]
  The patch make sure MACO is supported only if BACO is supported. It creates a 
stricter rule for MACO to avoid MACO is enabled with BACO supports. It should 
be safe to apply stricter rules to enable features.

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


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

[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11

[Roxana Nicolescu]

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

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

Title:
  Add SoF topology support on Intel RaptorLake DELL SKU 0C11

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

Bug description:
  SRU Jusitification for firmware-sof

  [Impact]
  To support audio functions on RPL Dell SKU 0C11, it requires the topology 
file from sof-tplg-v2.2.7

  [Fix]
  Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from 
https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  [Test Case]
  Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the 
audio function.
  1. Install the firmware-sof on platform(RPL) Dell SKU 0C11
  2. Make sure the audio output/input devices are not dummy in audio settings.

  [Where problems could occur]
  New firmware is only for the RPL platforms which requires the specific 
topology file.

  [Misc]
  https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  

  [Impact]
  Audio play/capture are not functional on specific Dell machines of Intel RPL 
platforms

  [Fix]
  Backport the fix from Intel in https://github.com/thesofproject/linux

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy` shown on the Audio output/input option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

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


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

[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Roxana Nicolescu]

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

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

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


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

[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux 
verification-needed-jammy-linux-ibm-gt-fips 
verification-needed-jammy-linux-intel-iotg verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux 
verification-done-jammy-linux-ibm-gt-fips 
verification-done-jammy-linux-intel-iotg verification-done-mantic-linux

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

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

Title:
  Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System can't enter suspend on AHCI mode,
  the CPU FAN and System FAN is running, PSU LED is on.
  When fail to enter suspend, remove ODD, the system can successfully enter 
suspend again.

  [Fix]
  Enable LPM on Alder Lake-P AHCI.

  [Test Cases]
  1. enabled AHCI on target machine.
  2. boot with kernel applied fix.
  3. suspend then check slp_s0_residency_usec&package_cstate_show
  ~~~
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  4951200
  Package C2 : 63571033
  Package C3 : 6212
  Package C6 : 5633477
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 5255561
  u@ubuntu:~$ sudo rtcwake -m mem -s 10
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  12965280
  Package C2 : 75052691
  Package C3 : 46989
  Package C6 : 8108332
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 13628111
  ~~~

  [where the issue could happen]
  Medium, Intel promise there's no issue of ADL AHCI and
  they will take responsibility after regression.
  Intel also take LPM as POR so they will fix any issues.

  [Misc]
  Because the board_ahci_mobile is still not modified to board_ahci_low_power 
on Jammy,
  provide a single patch for Jammy.

  For generic J/M, passed the all arch compilations on cbd,
  Jammy,
  ~~~
  $ git push j_cbd
  Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ
  remote: * 0/1 workers busy, 0 builds queued
  remote: 2023-11-17 19:50:25  kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK
  remote: 2023-11-17 20:18:29  kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK
  remote: 2023-11-17 20:01:41  kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK
  remote: 2023-11-17 20:31:51  kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK
  remote: 2023-11-17 20:37:25  kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK
  remote: 

  To cbd.kernel:jammy.git
   * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next
  ~~~

  Lunar,
  $ git push l_cbd
  Enumerating objects: 9, done.
  Counting objects: 100% (9/9), done.
  Delta compression using up to 8 threads
  Compressing objects: 100% (5/5), done.
  Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done.
  Total 5 (delta 4), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-915de03d6ecf-V1nm
  remote: * 9/9 workers busy, 0 builds queued
  remote: 2023-11-20 16:00:11  kobako-lunar-915de03d6ecf-V1nm/amd64/BUILD-OK
  remote: 2023-11-20 15:59:57  kobako-lunar-915de03d6ecf-V1nm/arm64/BUILD-OK
  remote: 2023-11-20 15:55:14  kobako-lunar-915de03d6ecf-V1nm/armhf/BUILD-OK
  remote: 2023-11-20 15:55:26  kobako-lunar-915de03d6ecf-V1nm/ppc64el/BUILD-OK
  remote: 2023-11-20 15:47:17  kobako-lunar-915de03d6ecf-V1nm/s390x/BUILD-OK
  remote: 

[Kernel-packages] [Bug 2036600] Re: Azure: Fix Azure vendor ID

[Roxana Nicolescu]

** Tags removed: verification-needed-lunar-linux 
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  Azure: Fix Azure vendor ID

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The linux-azure 6.2 kernel doesn't report a correct GUEST_ID

  There is a mistake in the commit
  (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
  azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
  :

  Before the commit, the good guest_id is 0x81860210.

  With the commit, the generated guest_id is incorrect:
  0x00860210, i.e. the 0x81 from bit 56~63 are dropped.

  See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
  * Bit(s)
  * 63 - Indicates if the OS is Open Source or not; 1 is Open Source

  * 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
  I'll post a patch to LKML to fix this typo.

  * 55:48 - Distro specific identification
  * 47:16 - Linux kernel version number
  * 15:0 - Distro specific identification

  See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
  windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)

  As a result, the host thinks that the VM is not an open-source OS, and
  it's not Linux. Consequently, the "VM Availability" fron Azure portal
  is 0 (unhealthy): some users rely on the info to manage their VMs,
  e.g. if the VM is erroneously reported "unhealthy", the VM may be
  killed and re-created, and the new VM is still "unhealthy", and the VM
  may be killed and re-created again...

  Please consider integrating the below fix ASAP. This affects regular
  VMs, and I think this affects CVMs as well.

  The fix should be:

  diff --git a/include/asm-generic/hyperv-tlfs.h 
b/include/asm-generic/hyperv-tlfs.h
  @@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
  *
  */

  -#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
  +#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  VMs could be misclassified.

  [Other Info]

  SF: #00368936

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


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

[Kernel-packages] [Bug 2046184] Re: [arm64] Increase max CPU count to 512

[Roxana Nicolescu]

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

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

Title:
  [arm64] Increase max CPU count to 512

Status in linux-oracle package in Ubuntu:
  In Progress
Status in linux-oracle source package in Jammy:
  Fix Released
Status in linux-oracle source package in Mantic:
  Fix Released
Status in linux-oracle source package in Noble:
  In Progress

Bug description:
  [Impact]

  * Request to accommodate new shape with 320 CPUs, greater than current
  max value of 256.

  [Fix]

  * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch.

  [Test Case]

  * Compile tested
  * Boot tested

  [Where things could go wrong]

  * Low chance of regression. Simple config change.

  [Other Info]

  * Change proposed in Debian unstable 
(https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1),
 but was denied due to additional kernel size. This shouldn't affect Ubuntu 
kernel so much as it's compressed.
  * SF #00375112

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


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

[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux 
verification-needed-jammy-linux-intel-iotg verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux 
verification-done-jammy-linux-intel-iotg verification-done-mantic-linux

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

Title:
  linux tools packages for derived kernels refuse to install
  simultaneously due to libcpupower name collision

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

Bug description:
  [ Impact ]

   * Multiple kernel flavours are conflicting with each on .deb / file
  level via their tools packages

   * Resolve the conflicting private libcpupower.so by statically
  linking it into the only C binary that uses said library in the linux-
  tools

  [ Test Plan ]

   * co-install tools packages from multiple kernel flavours of the same
  major version and abi, it should be successful

  [ Where problems could occur ]

   * If one tries really hard to find the private location of
  libcpupower.so and dlopen it by ever changing abi name, that will not
  be possible, until the separate bug report is fixed to introduce the
  public stable libcpupower.so.1 which so far ubuntu has never yet
  provided.

  [ Other Info ]
   
   * original bug report

  Taking linux-kvm and linux-gcp for example:

  $ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103384 2023-07-25 20:00 
./usr/lib/libcpupower.so.6.2.0-1011
  $ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103392 2023-08-16 15:08 
./usr/lib/libcpupower.so.6.2.0-1011

  linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
  a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
  utilities, and yet files of the same full path cannot be installed
  from two distinct debian packages, which follows we won't be able to
  install two linux-tools packages of two different derived kernels on
  the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
  Uname: Linux 6.5.0-9004-generic x86_64
  NonfreeKernelModules: zfs wl
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicamo 6331 F wireplumber
   /dev/snd/controlC0:  vicamo 6331 F wireplumber
   /dev/snd/seq:vicamo 6315 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Sep 14 23:31:16 2023
  InstallationDate: Installed on 2022-04-10 (522 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic 
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-generic N/A
   linux-backports-modules-6.5.0-9004-generic  N/A
   linux-firmware  20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.60.3.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

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

[Roxana Nicolescu]

** Tags removed: verification-needed-lunar-linux-azure 
verification-needed-lunar-linux-gcp verification-needed-lunar-linux-kvm 
verification-needed-lunar-linux-riscv verification-needed-lunar-linux-starfive
** Tags added: verification-done-lunar-linux-azure 
verification-done-lunar-linux-gcp verification-done-lunar-linux-kvm 
verification-done-lunar-linux-riscv verification-done-lunar-linux-starfive

** Tags removed: verification-needed-jammy-linux-nvidia-tegra 
verification-needed-jammy-linux-nvidia-tegra-igx 
verification-needed-jammy-linux-oracle verification-needed-lunar-linux-aws
** Tags added: verification-done-jammy-linux-nvidia-tegra 
verification-done-jammy-linux-nvidia-tegra-igx 
verification-done-jammy-linux-oracle verification-done-lunar-linux-aws

** Tags removed: verification-needed-jammy-linux-hwe-6.2 
verification-needed-jammy-linux-intel-iotg 
verification-needed-jammy-linux-lowlatency 
verification-needed-jammy-linux-lowlatency-hwe-6.2
** Tags added: verification-done-jammy-linux-hwe-6.2 
verification-done-jammy-linux-intel-iotg 
verification-done-jammy-linux-lowlatency 
verification-done-jammy-linux-lowlatency-hwe-6.2

** Tags removed: verification-needed-jammy-linux-azure-fips 
verification-needed-jammy-linux-bluefield 
verification-needed-jammy-linux-gcp-6.2 verification-needed-jammy-linux-gkeop
** Tags added: verification-done-jammy-linux-azure-fips 
verification-done-jammy-linux-bluefield verification-done-jammy-linux-gcp-6.2 
verification-done-jammy-linux-gkeop

** Tags removed: verification-needed-focal-linux-iot 
verification-needed-focal-linux-kvm 
verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-focal-linux-oracle
** Tags added: verification-done-focal-linux-iot 
verification-done-focal-linux-kvm 
verification-done-focal-linux-nvidia-tegra-5.15 
verification-done-focal-linux-oracle

** Tags removed: verification-needed-focal-linux-gcp-5.15 
verification-needed-focal-linux-gcp-tcpx verification-needed-focal-linux-gkeop 
verification-needed-focal-linux-intel-iotg-5.15
** Tags added: verification-done-focal-linux-gcp-5.15 
verification-done-focal-linux-gcp-tcpx verification-done-focal-linux-gkeop 
verification-done-focal-linux-intel-iotg-5.15

** Tags removed: verification-needed-bionic-linux-raspi-5.4
** Tags added: verification-done-bionic-linux-raspi-5.4

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

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

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

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

  [Fix]
  Use logarithmic encoding for the bMaxPacketSize0 value.

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-90-generic 5.15.0-90.100
  ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
  Uname: Linux 5.15.0-90-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-90-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command 

[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision

[Roxana Nicolescu]

Tested on jammy on an older version 5.15.67:
installed linux-tools-gcp
And then linux-tools-kvm
Unpacking linux-kvm-tools-5.15.0-1049 (5.15.0-1049.54) ...
dpkg: error processing archive 
/var/cache/apt/archives/linux-kvm-tools-5.15.0-1049_5.15.0-1049
.54_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/libcpupower.so.5.15.0-1049', which is also in 
package linux-gcp
-tools-5.15.0-1049 5.15.0-1049.57
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/linux-kvm-tools-5.15.0-1049_5.15.0-1049.54_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


New version: 5.15.92
Installation worked


Same for mantic.


** Tags removed: verification-needed-jammy-linux-ibm-gt-fips
** Tags added: verification-done-jammy-linux-ibm-gt-fips

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

Title:
  linux tools packages for derived kernels refuse to install
  simultaneously due to libcpupower name collision

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

Bug description:
  [ Impact ]

   * Multiple kernel flavours are conflicting with each on .deb / file
  level via their tools packages

   * Resolve the conflicting private libcpupower.so by statically
  linking it into the only C binary that uses said library in the linux-
  tools

  [ Test Plan ]

   * co-install tools packages from multiple kernel flavours of the same
  major version and abi, it should be successful

  [ Where problems could occur ]

   * If one tries really hard to find the private location of
  libcpupower.so and dlopen it by ever changing abi name, that will not
  be possible, until the separate bug report is fixed to introduce the
  public stable libcpupower.so.1 which so far ubuntu has never yet
  provided.

  [ Other Info ]
   
   * original bug report

  Taking linux-kvm and linux-gcp for example:

  $ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103384 2023-07-25 20:00 
./usr/lib/libcpupower.so.6.2.0-1011
  $ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103392 2023-08-16 15:08 
./usr/lib/libcpupower.so.6.2.0-1011

  linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
  a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
  utilities, and yet files of the same full path cannot be installed
  from two distinct debian packages, which follows we won't be able to
  install two linux-tools packages of two different derived kernels on
  the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
  Uname: Linux 6.5.0-9004-generic x86_64
  NonfreeKernelModules: zfs wl
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicamo 6331 F wireplumber
   /dev/snd/controlC0:  vicamo 6331 F wireplumber
   /dev/snd/seq:vicamo 6315 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Sep 14 23:31:16 2023
  InstallationDate: Installed on 2022-04-10 (522 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic 
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-generic N/A
   linux-backports-modules-6.5.0-9004-generic  N/A
   linux-firmware  20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.60.3.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System S

[Kernel-packages] [Bug 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9

[Roxana Nicolescu]

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

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

Title:
  Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook
  Fury 16 G9

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  
  [Impact]
  Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume 
from suspend. The audio play and capture functions are not working after resume 
from S3.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/.

  [Test Case]
  1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA .
  2. Perform system suspend/resume at least 3 times.
  3. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA. The impact is restricted.

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


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

[Kernel-packages] [Bug 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore

[Roxana Nicolescu]

** Tags added: verification-done-mantic-linux

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

Title:
  [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
  anymore

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  ---Problem Description---
  Regression: uvdevice at /dev/uv not compiled into kernel
   
  Machine Type = IBM z15, IBM z16
   
  Contact Information = steffen.ei...@ibm.com 
   
  ---uname output---
  Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x 
s390x s390x GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   
  ---Additional Hardware Info---
  Secure Execution feature code enabled (optional)

   
  ---Steps to Reproduce---
   # working/ old behavior
  on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution 
available)

  > cat /dev/uv
  /dev/uv
  > cat /boot/config-$(uname -r) | grep UV_UAPI
  CONFIG_S390_UV_UAPI=y

  that's the expected state for Ubuntu.

  # current/ non expected behavior

  since Ubuntu 23.04 the following happens:
  stock kernel non-modified, latest available

  > cat /dev/uv
  cat: /dev/uv: No such file or directory

  COMMENT:
  this still can happen if the machine has no Secure Execution feature available
  However, the following should not be the case under any circumstances:

  > cat /boot/config-$(uname -r) | grep UV_UAPI
  # CONFIG_S390_UV_UAPI is not set

  
  Somehow that configuration got lost between 22.X and 23.X.
  Maybe, because IIRC that features got back-ported to 22.X

  
  # Proposed Solution:

  change the kernel config to

  CONFIG_S390_UV_UAPI=y(same as 22.X backport)  
 
  or
  CONFIG_S390_UV_UAPI=m(same as upstream)  

  and provide a new kernel binary
   
  Stack trace output:
   n/a
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  Oops output:
   n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+subscriptions


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

[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Roxana Nicolescu]

Retriggered systemd adt tests for all architectures supported for 
bionic:linux-meta-hwe-5.15, version 
5.15.0-69.76~20.04.1 and test now passes. Logs for reference:

https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20230328_034339_ab6b2@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/s/systemd/20230327_202607_75cd6@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230327_184926_47043@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20230327_200017_63527@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20230327_180205_cbc1f@/log.gz

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

** Tags added: sru-20230227 sru-20230320

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

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [SRU Impact]

  Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, 
test_protect_syscall
  sysctl is called with the expectation the error result is EFAULT and not 
ENOSYS.
  This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, 
oem, gke, oracle).

  [Fix]
  Assertion checks if either EFAULT or ENOSYS is returned. This way it will 
work for focal-5.4 kernels and focal-5.15 kernels.

  [Test to reproduce the issue]
  1. Create a vm and install one of the focal-5.15 kernels (i.e 
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
  2. Run the autotests for upstream and/or root-unittests:
  autopkgtest --test-name=upstream systemd -- qemu 

  [Test to verify the fix]
  1. Same as above
  2. Apply the fix in your local repo and run the tests using your local repo
  autopkgtest --test-name=upstream  -- qemu 

  [Where problems could occur]
  This is not gonna affect end users since it is a change in the test only.
  It may impact autotests, but it's a very low probability.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)

  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion
  failure.

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


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

[Kernel-packages] [Bug 2009436] Re: dkms modules are not built anymore for linux-kvm

[Roxana Nicolescu]

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

** Changed in: autopkgtest (Ubuntu Kinetic)
   Status: New => Invalid

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

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

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

Title:
  dkms modules are not built anymore for linux-kvm

Status in autopkgtest package in Ubuntu:
  Invalid
Status in dkms package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in autopkgtest source package in Jammy:
  Invalid
Status in dkms source package in Jammy:
  New
Status in linux-kvm source package in Jammy:
  Invalid
Status in autopkgtest source package in Kinetic:
  Invalid
Status in dkms source package in Kinetic:
  New
Status in linux-kvm source package in Kinetic:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Some dkms modules are not built anymore when a retry is triggred from adt 
matrix page.
  It was noticed because these modules previously failed during build (because 
a config options is disabled) but now they pass (artificial pass).

  Affected modules:
  1. digimend-dkms
  2. oss4
  3. rtl8812au
  4. rtl8812ce

  Looking at digimend-dkms for jammy:linux-kvm, first time the test was correct 
(it failed) was when the new kernel was just pushed to proposed and adt testing 
was triggered. When a manual retry was done, it passed because build was 
ignored.
  Looking at the artifacts (attached for both cases), ADT_TEST_TRIGGERS differs:
  1. when build is triggered, ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26 
linux-kvm/5.15.0-1030.35 linux-signed-kvm/5.15.0-1030.35
  logs 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230213_171044_032fa@/log.gz

  2. when build is not triggered, 
ADT_TEST_TRIGGERS=linux-meta-kvm/5.15.0.1030.26
  logs:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/d/digimend-dkms/20230301_110606_17e6d@/log.gz

  
  Last log line present in both cases is:
  "I: Testing binary package $pkg".

  Looking at dkms: debian/scripts/dkms-autopkgtest

  After that line and the line where build is triggered the following code:
  dkms_pkg=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_NAME" 
2>/dev/null)
  dkms_ver=$(bash -c ". $dkms_conf > /dev/null; echo \$PACKAGE_VERSION" 
2>/dev/null)

  for k in /lib/modules/*/build
  do
  test -d "$k" || continue
  kver="${k%/build}"
  kver="${kver#/lib/modules/}"

  # If any linux-meta is in triggers, only test abistems that
  # match triggers otherwise continue. This helps integration
  # with adt-matrix which specifically requests test results
  # against each individual linux-meta and tracks unique results
  # per kernel abi.
  abistem=$(echo $kver | sed 's/-[a-z]*$//')
## abistem is 5.15.0-130
  case "${ADT_TEST_TRIGGERS-}" in
  *linux-meta*)
  case "$ADT_TEST_TRIGGERS" in
  *"$abistem"*)
  ;;
  *)
  continue
  ;;
  esac
  esac

  echo "I: Trying to build $dkms_pkg/$dkms_ver for $kver"

  What happens here is that it never gets passed the switch case and
  build is not triggered when ADT_TEST_TRIGGERS consists of linux-meta
  only, because abistem=-, but meta
  version=.. Notice the dot instead of the
  dash.

  This justifies why the module is built when ADT_TEST_TRIGGERS=linux-
  meta-kvm/5.15.0.1030.26 linux-kvm/5.15.0-1030.35 linux-signed-
  kvm/5.15.0-1030.35, but not when ADT_TEST_TRIGGERS=linux-meta-
  kvm/5.15.0.1030.26

  [Fix]
  Add an extra check for meta_version in that switch case statement.

  [Testcase]
  1. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. before fix
  I:   linux-headers-virtual
  I: Testing binary package digimend-dkms
  autopkgtest [11:14:45]: test dkms-autopkgtest: ---]
  autopkgtest [11:14:46]: test dkms-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -
  dkms-autopkgtest PASS
  autopkgtest [11:14:47]:  summary
  dkms-autopkgtest PASS
  qemu-system-x86_64: terminating on signal 15 from pid 15111 (/usr/bin/python3)
  2. Tested locally with ADT_TEST_TRIGGERS=linux-meta.. with the fix
  I: Testing binary package digimend-dkms
  I: Trying to build digimend/10 for 5.15.0-1029-kvm
  Creating symlink /var/lib/dkms/digimend/10/source -> /usr/src/digimend-10

  Kernel preparation unnecessary for this kernel. Skipping...

  Building module:
  cleaning build area...
  make -j1 KERNELRELEASE=5.15.0-1029-kvm KVERSION=5.15.0-1029-kvm...(bad exit 
status: 2)
  ERROR (dkms apport): kernel package linux-headers-5.15.0-1029-kvm 

[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules

[Roxana Nicolescu]

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  Incompatible jbd2 format between kernel and lttng-modules

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in lttng-modules package in Ubuntu:
  Fix Committed
Status in lttng-modules source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Incomplete
Status in lttng-modules source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Incomplete
Status in lttng-modules source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Incomplete
Status in lttng-modules source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Incomplete
Status in lttng-modules source package in Lunar:
  Fix Committed

Bug description:
  [SRU Justification]

  Impact:
  Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 
6.1.3.
  This is incompatible with the current changes in the lttng-module for 
bionic-5.4 backports, focal, jammy, and kinetic.

  Focal and bionic updates are needed for the current sru kernel release 
(2023.01.30). Both adt and rt fail during compilation of the module.
  Jammy and kinetic updates are not needed for this cycle because patches from 
upstream stable are not applied yet but it will be needed for the next 
release(s).

  Correct changes are already in lttng-modules:master and in 2.13.8-1
  version.

  Fix(es):
  1. focal and bionic: Picking 4 patches from upstream lttng-modules which 
handle the changed interface as well as add the required code to enable that 
change for other versions as well:
  LTTNG_KERNEL_RANGE(5,4,229, 5,5,0)
  LTTNG_KERNEL_RANGE(5,10,163, 5,11,0)
  LTTNG_KERNEL_RANGE(5,15,87, 5,16,0)
  LTTNG_KERNEL_RANGE(6,0,18, 6,1,0)
  LTTNG_KERNEL_RANGE(6,1,4, 6,2,0)

  2. Jammy and kinetic: backport 2.13.8-1

  Tescase(s) for focal:
  1. lttng-smoke-test fail to compile with the error from below.
  2. adt lttng-module fail to compile with same error

  Regression potential:
  We may notice new failures in ubuntu_lttng_smoke_test once this will compile 
and run. But it was tested locally and results were good, so probablity is very 
very low.

  760 21:14:39 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87,
761 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177,
762 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29:
763 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6:
 error: conflicting types for ‘trace_jbd2_run_stats’
764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto);
765 21:14:39 DEBUG| [stdout] | ^~
766 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
767 21:14:39 DEBUG| [stdout] 43 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
768 21:14:39 DEBUG| [stdout] | ^~~
769 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, 
name, \
771 21:14:39 DEBUG| [stdout] | ^~
772 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
773 21:14:39 DEBUG| [stdout] 104 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
774 21:14:39 DEBUG| [stdout] | ^~
775 21:14:39 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
776 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18:
777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: 
previous definition of ‘trace_jbd2_run_stats’ was here
778 21:14:39 DEBUG| [stdout] 243 | static inline void 
trace_##name(proto) \
779 21:14:39 DEBUG| [stdout] | ^~
780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: 
in expansion of macro ‘__DECLARE_TRACE’
781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), 
PARAMS(args), \
782 21:14:39 DEBUG| [stdout] | ^~~
783 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint

[Kernel-packages] [Bug 2015372] [NEW] Add support for intel EMR cpu

[Roxana Nicolescu]

Public bug reported:

TODO current status in lunar and mainline.

The following commits had to be backported to Jammy:

Usually backporting new features to existing kernels it's not a common practice.
But these backports were easy to pick. Some of the commits were already applied.
More information about backporting these commits is addressed inline.

1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
Already applied to jammy. Picked up in v5.15.80 upstream stable release
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122

2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
Had to adjust the path to uncore-frequency.c
In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

3. PMU Update to Support New EMR CPU model Number: 
3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
Small adjustment needed because saphire, raptor changes were not there.
3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 
upstream
https://bugs.launchpad.net/bugs/2012665
3.4 69ced4160969025821f2999ff92163ed26568f1c already applied in 5.15.91
https://bugs.launchpad.net/bugs/2011467


4. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
Manually solved small conflict due to missing 80275ca9e525c
where a fixed DRAM domain energy unit is introduced
 
5. linux kernel: add EMR support to the intel_idle driver: 
74528edfbc664f9d2c927c4e5a44f1285598ed0f
clean cherry-pick

6. intel-speed-select tool support for EMR: 
61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
clean cherry-pick

7. Turbostat support on EMR: 93cac4150727dae0ee89f501dd75413b88eedec0
clean cherry-pick

8. intel-RAPL drivers to support new EMR CPU model number: 
7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
clean cherry-pick

9. Provide accel-config for EMR : TODO userspace
   - this is user-space code, not kernel code (accel-config seems the
 package that we already have in lunar, sync'ed from Debian, not
 sure if we need to provide additional changes applied or if we
 need to backport the whole user-space package to jammy)

10. Enable in-field Array BIST for EMR
code is still in the process of being reviewed, we shouldn't apply/backport 
this for now

11. CXL 1.1 Compatibility ECN
Very big patch -- won't port it to jammy

12. Split Lock detection change for EMR: 
d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8
TODO linux-next only

13. Add Emerald Rapids CPU model number ID for EDAC driver support: 
e4b2bc6616e21
clean cherry-pick

Testing:
Kernel was built on cbd. roxanan-jammy-63b23a4757ba-H6S4
TODO qemu

Regression potential
Very very low, these are new features, nothing to regress here.

** Affects: linux (Ubuntu)
 Importance: Medium
     Assignee: Roxana Nicolescu (roxanan)
 Status: In Progress

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Status: New

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

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

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

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  New

Bug description:
  TODO current status in lunar and mainline.

  The following commits had to be backported to Jammy:

  Usually backporting new features to existing kernels it's not a common 
practice.
  But these backports were easy to pick. Some of the commits were already 
applied.
  More information about backporting these commits is addressed inline.

  1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
  Already applied to jammy. Picked up in v5.15.80 upstream stable release
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122

  2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

  3. PMU Update to Support New EMR CPU model Number: 
  3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
  3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
  Small adjustment needed because saphire, raptor changes were not there.
  3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 
upstream
  https://bugs.launchpad.net/bugs/2012665
  3.4 69ced416096

[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

[Roxana Nicolescu]

** Description changed:

  TODO current status in lunar and mainline.
  
  The following commits had to be backported to Jammy:
  
  Usually backporting new features to existing kernels it's not a common 
practice.
  But these backports were easy to pick. Some of the commits were already 
applied.
  More information about backporting these commits is addressed inline.
  
  1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
  Already applied to jammy. Picked up in v5.15.80 upstream stable release
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122
  
  2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir
  
- 3. PMU Update to Support New EMR CPU model Number: 
+ 3. PMU Update to Support New EMR CPU model Number:
  3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
  3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
  Small adjustment needed because saphire, raptor changes were not there.
+ TODO check the actual commit
  3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 
upstream
  https://bugs.launchpad.net/bugs/2012665
  3.4 69ced4160969025821f2999ff92163ed26568f1c already applied in 5.15.91
  https://bugs.launchpad.net/bugs/2011467
  
- 
  4. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
  Manually solved small conflict due to missing 80275ca9e525c
  where a fixed DRAM domain energy unit is introduced
-  
+ 
  5. linux kernel: add EMR support to the intel_idle driver: 
74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick
  
  6. intel-speed-select tool support for EMR: 
61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick
  
  7. Turbostat support on EMR: 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick
  
  8. intel-RAPL drivers to support new EMR CPU model number: 
7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick
  
  9. Provide accel-config for EMR : TODO userspace
-- this is user-space code, not kernel code (accel-config seems the
-  package that we already have in lunar, sync'ed from Debian, not
-  sure if we need to provide additional changes applied or if we
-  need to backport the whole user-space package to jammy)
+    - this is user-space code, not kernel code (accel-config seems the
+  package that we already have in lunar, sync'ed from Debian, not
+  sure if we need to provide additional changes applied or if we
+  need to backport the whole user-space package to jammy)
  
  10. Enable in-field Array BIST for EMR
  code is still in the process of being reviewed, we shouldn't apply/backport 
this for now
  
  11. CXL 1.1 Compatibility ECN
  Very big patch -- won't port it to jammy
  
- 12. Split Lock detection change for EMR: 
d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8
- TODO linux-next only
+ 12. Split Lock detection change for EMR:
+ d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 linux-next
+ Had to apply the following:
+ - 727209376f499 x86/split_lock: Add sysctl to control the misery mode
+ - b041b525dab95 x86/split_lock: Make life miserable for split lockers
+ - 054ed6349c1bd Documentation/x86: Update split lock documentation
+ And manually solved a conflict due to missing:
+ - d3287fb0d3c8a x86/microcode/intel: Expose collect_cpu_info_early() for IFS
+ - 3f2adf00f52b5 x86/cpu: Use MSR_IA32_MISC_ENABLE constants
+ - ef79970d7ccdc x86/split-lock: Remove unused TIF_SLD bit
+ 
+ which are just small improvements and not critical.
+ 
+ Build results: roxanan-jammy-124924e9131a-lLt8
  
  13. Add Emerald Rapids CPU model number ID for EDAC driver support: 
e4b2bc6616e21
  clean cherry-pick
  
  Testing:
- Kernel was built on cbd. roxanan-jammy-63b23a4757ba-H6S4
- TODO qemu
+ Kernel was built on cbd.
  
  Regression potential
  Very very low, these are new features, nothing to regress here.

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

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  New

Bug description:
  TODO current status in lunar and mainline.

  The following commits had to be backported to Jammy:

  Usually backporting new features to existing kernels it's not a common 
practice.
  But these backports were easy to pick. Some of the commits were already 
applied.
  More information about backporting these commits is addressed inline.

  1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
  Already applied to jammy. Picked up in v5.15.80 upstream stable release
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122

  2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
  

[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

[Roxana Nicolescu]

** Description changed:

  TODO current status in lunar and mainline.
  
  The following commits had to be backported to Jammy:
  
  Usually backporting new features to existing kernels it's not a common 
practice.
  But these backports were easy to pick. Some of the commits were already 
applied.
  More information about backporting these commits is addressed inline.
  
  1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
  Already applied to jammy. Picked up in v5.15.80 upstream stable release
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122
  
  2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir
  
  3. PMU Update to Support New EMR CPU model Number:
  3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
  3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
  Small adjustment needed because saphire, raptor changes were not there.
  TODO check the actual commit
  3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 
upstream
  https://bugs.launchpad.net/bugs/2012665
  3.4 69ced4160969025821f2999ff92163ed26568f1c already applied in 5.15.91
  https://bugs.launchpad.net/bugs/2011467
  
  4. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
  Manually solved small conflict due to missing 80275ca9e525c
  where a fixed DRAM domain energy unit is introduced
  
  5. linux kernel: add EMR support to the intel_idle driver: 
74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick
  
  6. intel-speed-select tool support for EMR: 
61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick
  
  7. Turbostat support on EMR: 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick
  
  8. intel-RAPL drivers to support new EMR CPU model number: 
7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick
  
  9. Provide accel-config for EMR : TODO userspace
     - this is user-space code, not kernel code (accel-config seems the
   package that we already have in lunar, sync'ed from Debian, not
   sure if we need to provide additional changes applied or if we
   need to backport the whole user-space package to jammy)
  
  10. Enable in-field Array BIST for EMR
  code is still in the process of being reviewed, we shouldn't apply/backport 
this for now
  
  11. CXL 1.1 Compatibility ECN
  Very big patch -- won't port it to jammy
  
  12. Split Lock detection change for EMR:
  d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 linux-next
  Had to apply the following:
  - 727209376f499 x86/split_lock: Add sysctl to control the misery mode
  - b041b525dab95 x86/split_lock: Make life miserable for split lockers
  - 054ed6349c1bd Documentation/x86: Update split lock documentation
  And manually solved a conflict due to missing:
  - d3287fb0d3c8a x86/microcode/intel: Expose collect_cpu_info_early() for IFS
  - 3f2adf00f52b5 x86/cpu: Use MSR_IA32_MISC_ENABLE constants
  - ef79970d7ccdc x86/split-lock: Remove unused TIF_SLD bit
  
  which are just small improvements and not critical.
  
- Build results: roxanan-jammy-124924e9131a-lLt8
- 
  13. Add Emerald Rapids CPU model number ID for EDAC driver support: 
e4b2bc6616e21
  clean cherry-pick
  
  Testing:
- Kernel was built on cbd.
+ Kernel was built on cbd. roxanan-jammy-cd5956c49599-A3Ur
  
  Regression potential
  Very very low, these are new features, nothing to regress here.

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

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  New

Bug description:
  TODO current status in lunar and mainline.

  The following commits had to be backported to Jammy:

  Usually backporting new features to existing kernels it's not a common 
practice.
  But these backports were easy to pick. Some of the commits were already 
applied.
  More information about backporting these commits is addressed inline.

  1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
  Already applied to jammy. Picked up in v5.15.80 upstream stable release
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122

  2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

  3. PMU Update to Support New EMR CPU model Number:
  3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
  3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
  Small adjustment needed because saphire, raptor changes were not the

[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

[Roxana Nicolescu]

** Description changed:

- TODO current status in lunar and mainline.
+ SRU Justification
  
- The following commits had to be backported to Jammy:
+ [Impact]
+ Usually backporting new features to existing kernels it's not a common 
practice.
+ But these commits were easy to pick. Some of the commits were already applied.
+ More information about backporting these commits is addressed inline.
  
- Usually backporting new features to existing kernels it's not a common 
practice.
- But these backports were easy to pick. Some of the commits were already 
applied.
- More information about backporting these commits is addressed inline.
+ [Commits]
  
  1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
  Already applied to jammy. Picked up in v5.15.80 upstream stable release
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122
  
  2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir
  
  3. PMU Update to Support New EMR CPU model Number:
  3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
  3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
  Small adjustment needed because saphire, raptor changes were not there.
- TODO check the actual commit
+ done in 528c9f1daf20d "perf/x86/cstate: Add SAPPHIRERAPIDS_X CPU support"
+ 
  3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 
upstream
  https://bugs.launchpad.net/bugs/2012665
  3.4 69ced4160969025821f2999ff92163ed26568f1c already applied in 5.15.91
  https://bugs.launchpad.net/bugs/2011467
  
  4. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
  Manually solved small conflict due to missing 80275ca9e525c
  where a fixed DRAM domain energy unit is introduced
+ TODO not sure if this one is correct.
  
  5. linux kernel: add EMR support to the intel_idle driver: 
74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick
  
  6. intel-speed-select tool support for EMR: 
61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick
  
  7. Turbostat support on EMR: 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick
  
  8. intel-RAPL drivers to support new EMR CPU model number: 
7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick
  
  9. Provide accel-config for EMR : TODO userspace
     - this is user-space code, not kernel code (accel-config seems the
   package that we already have in lunar, sync'ed from Debian, not
   sure if we need to provide additional changes applied or if we
   need to backport the whole user-space package to jammy)
  
  10. Enable in-field Array BIST for EMR
  code is still in the process of being reviewed, we shouldn't apply/backport 
this for now
  
  11. CXL 1.1 Compatibility ECN
  Very big patch -- won't port it to jammy
  
  12. Split Lock detection change for EMR:
  d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 linux-next
  Had to apply the following:
  - 727209376f499 x86/split_lock: Add sysctl to control the misery mode
  - b041b525dab95 x86/split_lock: Make life miserable for split lockers
  - 054ed6349c1bd Documentation/x86: Update split lock documentation
  And manually solved a conflict due to missing:
  - d3287fb0d3c8a x86/microcode/intel: Expose collect_cpu_info_early() for IFS
  - 3f2adf00f52b5 x86/cpu: Use MSR_IA32_MISC_ENABLE constants
  - ef79970d7ccdc x86/split-lock: Remove unused TIF_SLD bit
  
  which are just small improvements and not critical.
+ TODO more explanation here
  
  13. Add Emerald Rapids CPU model number ID for EDAC driver support: 
e4b2bc6616e21
  clean cherry-pick
  
  Testing:
  Kernel was built on cbd. roxanan-jammy-cd5956c49599-A3Ur
  
  Regression potential
  Very very low, these are new features, nothing to regress here.

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

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  New

Bug description:
  SRU Justification

  [Impact]
  Usually backporting new features to existing kernels it's not a common 
practice.
  But these commits were easy to pick. Some of the commits were already applied.
  More information about backporting these commits is addressed inline.

  [Commits]

  1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
  Already applied to jammy. Picked up in v5.15.80 upstream stable release
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122

  2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

  3. PMU Update to Support N

[Kernel-packages] [Bug 2015498] [NEW] Debian autoreconstruct Fix restoration of execute permissions

[Roxana Nicolescu]

Public bug reported:

SRU justification

[Impact]

Debian source package diffs cannot represent that a file should
be executable.
gen-auto-reconstruct detects when a commit adds a script that is supposed to be 
invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

But, if a file removes its execute permission, this will change it back.
This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
removed the execute permission for a header file but then our scripts brought 
it back.

[Fix]
Andy proposed the following fix
https://dpaste.com/6SJ8YR3BM
Basically it checks if the permission was added or removed and uses either +x 
or -x.

[Test plan]
Easily tested with jammy-kvm, latest release where a rebase picked this commit
"treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
When debian packages are prepared, you'll notice the file has changed its 
permission back to 755. 
With the fix, it should be the same.

[Regression potential]
Low, it is a small fix. Scripts will still have execute permission.

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Lunar)
   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/2015498

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  New

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755. 
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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


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

[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions

[Roxana Nicolescu]

** Description changed:

  SRU justification
  
  [Impact]
  
  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.
  
  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.
  
  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.
  
  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
- When debian packages are prepared, you'll notice the file has changed its 
permission back to 755. 
+ When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.
  
  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  New

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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


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

[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

[Roxana Nicolescu]

** Description changed:

  SRU Justification
  
  [Impact]
+ 
+ Intel has introduced support for their new Emerald Rapids CPU.
+ This support is a nice feature to have in Jammy because it is an LTS release 
and enabling extra hardware adds to its usability.
+ 
  Usually backporting new features to existing kernels it's not a common 
practice.
- But these commits were easy to pick. Some of the commits were already applied.
- More information about backporting these commits is addressed inline.
+ But these commits were easy to backport. Most of them were clean cherry 
picks. Some of them were already picked up from upstream stable releases,
+ and some required manual intervention because Jammy did not have some commits 
applied but the actual changes were very minimal.
+  
+ More information about each commit is addressed inline.
  
  [Commits]
  
- 1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
- Already applied to jammy. Picked up in v5.15.80 upstream stable release
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122
- 
- 2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
+ 1. 9c252ecf3036:
+ "platform/x86: intel-uncore-freq: add Emerald Rapids support"
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir
  
- 3. PMU Update to Support New EMR CPU model Number:
- 3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
- 3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
- Small adjustment needed because saphire, raptor changes were not there.
- done in 528c9f1daf20d "perf/x86/cstate: Add SAPPHIRERAPIDS_X CPU support"
+ 2. 5a8a05f165fb18d37526062419774d9088c2a9b9
+ TODO explain 
  
- 3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 
upstream
- https://bugs.launchpad.net/bugs/2012665
- 3.4 69ced4160969025821f2999ff92163ed26568f1c already applied in 5.15.91
- https://bugs.launchpad.net/bugs/2011467
+ 3. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
+ Manually solved small conflicts due to missing
+ - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL 
domain"
+ - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N"
+ - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake"
+ - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake"
  
- 4. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
- Manually solved small conflict due to missing 80275ca9e525c
- where a fixed DRAM domain energy unit is introduced
- TODO not sure if this one is correct.
- 
- 5. linux kernel: add EMR support to the intel_idle driver: 
74528edfbc664f9d2c927c4e5a44f1285598ed0f
+ 4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick
  
- 6. intel-speed-select tool support for EMR: 
61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
+ 5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick
  
- 7. Turbostat support on EMR: 93cac4150727dae0ee89f501dd75413b88eedec0
+ 6. 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick
  
- 8. intel-RAPL drivers to support new EMR CPU model number: 
7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
+ 7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick
  
- 9. Provide accel-config for EMR : TODO userspace
-    - this is user-space code, not kernel code (accel-config seems the
-  package that we already have in lunar, sync'ed from Debian, not
-  sure if we need to provide additional changes applied or if we
-  need to backport the whole user-space package to jammy)
- 
- 10. Enable in-field Array BIST for EMR
- code is still in the process of being reviewed, we shouldn't apply/backport 
this for now
- 
- 11. CXL 1.1 Compatibility ECN
- Very big patch -- won't port it to jammy
- 
- 12. Split Lock detection change for EMR:
- d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 linux-next
- Had to apply the following:
- - 727209376f499 x86/split_lock: Add sysctl to control the misery mode
- - b041b525dab95 x86/split_lock: Make life miserable for split lockers
- - 054ed6349c1bd Documentation/x86: Update split lock documentation
- And manually solved a conflict due to missing:
- - d3287fb0d3c8a x86/microcode/intel: Expose collect_cpu_info_early() for IFS
- - 3f2adf00f52b5 x86/cpu: Use MSR_IA32_MISC_ENABLE constants
- - ef79970d7ccdc x86/split-lock: Remove unused TIF_SLD bit
- 
- which are just small improvements and not critical.
- TODO more explanation here
- 
- 13. Add Emerald Rapids CPU model number ID for EDAC driver support: 
e4b2bc6616e21
+ 8. e4b2bc6616e21
  clean cherry-pick
  
- Testing:
- Kernel was built on cbd. roxanan-jammy-cd5956c49599-A3Ur
  
- Regression potential
- Very very low, these are new features, nothing to regress here.
+ [Testing]
+ Kernel was built on cbd and boot tested on a VM.
+ TODO ask for help from intel.
+ 
+ [Regression pot

[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

[Roxana Nicolescu]

** Description changed:

  SRU Justification
  
  [Impact]
  
  Intel has introduced support for their new Emerald Rapids CPU.
  This support is a nice feature to have in Jammy because it is an LTS release 
and enabling extra hardware adds to its usability.
  
  Usually backporting new features to existing kernels it's not a common 
practice.
  But these commits were easy to backport. Most of them were clean cherry 
picks. Some of them were already picked up from upstream stable releases,
  and some required manual intervention because Jammy did not have some commits 
applied but the actual changes were very minimal.
-  
+ 
  More information about each commit is addressed inline.
  
  [Commits]
  
  1. 9c252ecf3036:
  "platform/x86: intel-uncore-freq: add Emerald Rapids support"
- Had to adjust the path to uncore-frequency.c
+ Adjusted the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir
  
  2. 5a8a05f165fb18d37526062419774d9088c2a9b9
- TODO explain 
+ "perf/x86/intel/cstate: Add Emerald Rapids"
+ Small context adjustment in intel_cstates_match array
+ because of missing SPR, RPL and MDL cpu models introduced in
+ 528c9f1daf20d
  
- 3. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
- Manually solved small conflicts due to missing
+ 3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0
+ "perf/x86/rapl: Add support for Intel Emerald Rapids"
+ 
+ Context adjustment due to missing 
  - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL 
domain"
  - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N"
  - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake"
  - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake"
  
  4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick
  
  5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick
  
  6. 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick
  
  7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick
  
  8. e4b2bc6616e21
  clean cherry-pick
  
- 
  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.
  
  [Regression potential]
- Very low, these are minimal new features, which actually reuse a lot of the 
existing cpu structures/functions. 
- 
+ Very low, these are minimal new features, which actually reuse a lot of the 
existing cpu structures/functions.
  
  
  
  The following changes since commit
- 4f9b8d032dc91e32d562bb8253097dc9af920269
+ 8feeaa9039a290b978e7855ab82955cd9348fc13
  
  "platform/x86: intel-uncore-freq: add Emerald Rapids support"
  
  are available in the Git repository at:
  
-   git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy
- 2015372
+   git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy
+ lp2015372
  
  for you to fetch changes up to commit
- 8491ea154755d2c8ce59e7e4b9091baa3baef2c5
+ 7d88565e6777082265b373733fd93eb3e0914e12
  
  "EDAC/i10nm: Add Intel Emerald Rapids server support"

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

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  New

Bug description:
  SRU Justification

  [Impact]

  Intel has introduced support for their new Emerald Rapids CPU.
  This support is a nice feature to have in Jammy because it is an LTS release 
and enabling extra hardware adds to its usability.

  Usually backporting new features to existing kernels it's not a common 
practice.
  But these commits were easy to backport. Most of them were clean cherry 
picks. Some of them were already picked up from upstream stable releases,
  and some required manual intervention because Jammy did not have some commits 
applied but the actual changes were very minimal.

  More information about each commit is addressed inline.

  [Commits]

  1. 9c252ecf3036:
  "platform/x86: intel-uncore-freq: add Emerald Rapids support"
  Adjusted the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

  2. 5a8a05f165fb18d37526062419774d9088c2a9b9
  "perf/x86/intel/cstate: Add Emerald Rapids"
  Small context adjustment in intel_cstates_match array
  because of missing SPR, RPL and MDL cpu models introduced in
  528c9f1daf20d

  3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0
  "perf/x86/rapl: Add support for Intel Emerald Rapids"

  Context adjustment due to missing 
  - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL 
domain"
  - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N"
  - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake"
  - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake"

[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

[Roxana Nicolescu]

Builds are pushed in this repo 
https://code.launchpad.net/~roxanan/+git/kernel-build/+ref/lp2015372
Given the lack of resources to properly test this new CPU support, extra help 
is needed.

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

Title:
  Add support for intel EMR cpu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  New

Bug description:
  SRU Justification

  [Impact]

  Intel has introduced support for their new Emerald Rapids CPU.
  This support is a nice feature to have in Jammy because it is an LTS release 
and enabling extra hardware adds to its usability.

  Usually backporting new features to existing kernels it's not a common 
practice.
  But these commits were easy to backport. Most of them were clean cherry 
picks. Some of them were already picked up from upstream stable releases,
  and some required manual intervention because Jammy did not have some commits 
applied but the actual changes were very minimal.

  More information about each commit is addressed inline.

  [Commits]

  1. 9c252ecf3036:
  "platform/x86: intel-uncore-freq: add Emerald Rapids support"
  Adjusted the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir

  2. 5a8a05f165fb18d37526062419774d9088c2a9b9
  "perf/x86/intel/cstate: Add Emerald Rapids"
  Small context adjustment in intel_cstates_match array
  because of missing SPR, RPL and MDL cpu models introduced in
  528c9f1daf20d

  3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0
  "perf/x86/rapl: Add support for Intel Emerald Rapids"

  Context adjustment due to missing 
  - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL 
domain"
  - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N"
  - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake"
  - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake"

  4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick

  5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick

  6. 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick

  7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick

  8. e4b2bc6616e21
  clean cherry-pick

  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.

  [Regression potential]
  Very low, these are minimal new features, which actually reuse a lot of the 
existing cpu structures/functions.

  

  The following changes since commit
  8feeaa9039a290b978e7855ab82955cd9348fc13

  "platform/x86: intel-uncore-freq: add Emerald Rapids support"

  are available in the Git repository at:

    git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy
  lp2015372

  for you to fetch changes up to commit
  7d88565e6777082265b373733fd93eb3e0914e12

  "EDAC/i10nm: Add Intel Emerald Rapids server support"

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


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

[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR

[Roxana Nicolescu]

Waiting on intel response if these 2 commits
- b041b525dab95
- 727209376f499
are needed to support this as well.

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

Title:
  Add split lock detection for EMR

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  SRU Justification

  [Impact]

  #2009315 adds support for their new Emerald Rapids CPU to Jammy.

  Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next
  introduces support for Split lock detection.

  
  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.

  [Regression potential]
  TODO assess this

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


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

[Kernel-packages] [Bug 2015855] [NEW] Add split lock detection for EMR

[Roxana Nicolescu]

Public bug reported:

SRU Justification

[Impact]

#2009315 adds support for their new Emerald Rapids CPU to Jammy.

Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next
introduces support for Split lock detection.


[Testing]
Kernel was built on cbd and boot tested on a VM.
TODO ask for help from intel.

[Regression potential]
TODO assess this

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Roxana Nicolescu (roxanan)
 Status: Incomplete

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

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

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

Title:
  Add split lock detection for EMR

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  SRU Justification

  [Impact]

  #2009315 adds support for their new Emerald Rapids CPU to Jammy.

  Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next
  introduces support for Split lock detection.

  
  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.

  [Regression potential]
  TODO assess this

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


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

[Kernel-packages] [Bug 2004132] Re: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision

[Roxana Nicolescu]

bionic:linux-snapdragon was not released last cycle, hence it asks for 
verification again. 
Given that the main kernel was verified, I will mark this as verified as well. 

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  btrfs/154: rename fails with EOVERFLOW when calculating item size
  during item key collision

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released

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

  [Impact]

  xfstests btrfs/154 fails on both Bionic and Focal, leading to a kernel
  oops and the btrfs volume being forced readonly.

  In btrfs, item key collision is allowed for some item types, namely
  dir item and inode references. When inserting items into the btree,
  there are two objects, the btrfs_item and the item data. These objects
  must fit within the btree nodesize.

  When a hash collision occurs, and we call btrfs_search_slot() to place
  the objects in the tree, when btrfs_search_slot() reaches the leaf
  node, a check is performed to see if we need to split the leaf. The
  check is incorrect, returning that we need to split the leaf, since it
  thinks that both btrfs_item and the item data need to be inserted,
  when in reality, the item can be merged with the existing one and no
  new btrfs_item will be inserted.

  split_leaf() will return EOVERFLOW from following code:

    if (extend && data_size + btrfs_item_size_nr(l, slot) +
    sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(fs_info))
    return -EOVERFLOW;

  In the rename case, btrfs_check_dir_item_collision() is called early
  stages of treewalking, and correctly calculates the needed size,
  taking into account that a hash collision has occurred.

    data_size = sizeof(*di) + name_len;
    if (data_size + btrfs_item_size_nr(leaf, slot) +
    sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(root->fs_info))

  The two sizes reported from btrfs_check_dir_item_collision() and
  btrfs_search_slot() are different, and rename fails due to
  split_leaf() returning -EOVERFLOW, leading to transaction abort and
  forcing the volume readonly.

  Kernel oops:

  BTRFS: Transaction aborted (error -75)
  WARNING: CPU: 0 PID: 2921 at 
/build/linux-fTmV3T/linux-4.15.0/fs/btrfs/inode.c:10217 
btrfs_rename+0xcf1/0xdf0 [btrfs]
  CPU: 0 PID: 2921 Comm: python3 Not tainted 4.15.0-202-generic #213-Ubuntu
  RIP: 0010:btrfs_rename+0xcf1/0xdf0 [btrfs]
  RSP: 0018:9e6f4183fd20 EFLAGS: 00010282
  RAX:  RBX: 91a493f27b98 RCX: 0006
  RDX: 0007 RSI: 0096 RDI: 91a4bfc1b4d0
  RBP: 9e6f4183fdc0 R08: 02b4 R09: 0004
  R10:  R11: 0001 R12: 0236
  R13: 91a493f56518 R14: 91a4b6b57b40 R15: 91a493f27b98
  FS:  7f6041081740() GS:91a4bfc0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f6040fe84c8 CR3: 00015c8ca005 CR4: 00760ef0
  PKRU: 5554
  Call Trace:
   btrfs_rename2+0x1d/0x30 [btrfs]
   vfs_rename+0x46e/0x960
   SyS_rename+0x362/0x3c0
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x41/0xa6
  Code: 0f ba a8 d0 cd 00 00 02 72 2b 41 83 f8 fb 0f 84 d9 00 00 00 44 89 c6 48 
c7 c7 68 43 4b c0 44 89 55 80 44 89 45 98 e8 8f 5c a6 d0 <0f> 0b 44 8b 45 98 44 
8b 55 80 44 89 55 80 44 89 c1 44 89 45 98
  ---[ end trace 9c6b87a19f4436f3 ]---
  BTRFS: error (device vdd) in btrfs_rename:10217: errno=-75 unknown
  BTRFS info (device vdd): forced readonly

  [Testcase]

  Start a fresh Bionic or Focal VM.

  Attach two scratch disks, I used standard virtio disks with 3gb of
  storage each. These disks are /dev/vdc and /dev/vdd.

  Compile xfstests:

  $ sudo apt-get install acl attr automake bc dbench dump e2fsprogs fio gawk \
  gcc git indent libacl1-dev libaio-dev libcap-dev libgdbm-dev libtool \
  libtool-bin  libuuid1 lvm2 make psmisc python3 quota sed \
  uuid-dev uuid-runtime xfsprogs linux-headers-$(uname -r) sqlite3 make
  $ sudo apt-get install  f2fs-tools ocfs2-tools udftools xfsdump \
  xfslibs-dev
  $ git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
  $ cd xfstests-dev
  $ make
  $ sudo su
  # mkdir /test
  # mkdir /scratch
  # mkfs.btrfs -f /dev/vdc
  # cat << EOF >> ./local.config
  export TEST_DEV=/dev/vdc
  export TEST_DIR=/test
  export SCRATCH_DEV=/dev/vdd
  export SCRATCH_MNT=/scratch
  EOF

  # ./check btrfs/154

  btrfs/154   _check_dmesg: something found in dmesg (see 
/home/ubuntu/xfstests-dev/results//btrfs/154.dmesg)
  - output mismatch (see /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad)
  -

[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR

[Roxana Nicolescu]

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

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

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

Title:
  Add split lock detection for EMR

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

Bug description:
  SRU Justification

  [Impact]

  #2009315 adds support for their new Emerald Rapids CPU to Jammy.

  Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next
  introduces support for Split lock detection.

  
  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.

  [Regression potential]
  TODO assess this

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


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

[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR

[Roxana Nicolescu]

Got feedback from intel that the extra commits are not necessary.

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

Title:
  Add split lock detection for EMR

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

Bug description:
  SRU Justification

  [Impact]

  #2009315 adds support for their new Emerald Rapids CPU to Jammy.

  Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next
  introduces support for Split lock detection.

  
  [Testing]
  Kernel was built on cbd and boot tested on a VM.
  TODO ask for help from intel.

  [Regression potential]
  TODO assess this

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


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

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

[Roxana Nicolescu]

Judging from previous comments this change was verified.
Verification is requested again because the initial change was pushed in the 
last cycle and non aws derivatives that were not respun introduced this change 
in this cycle.
Since this is blocking the release of a lot of kernels for cycle 20230320, I 
will tag verification-done. 

** Tags removed: verification-needed-bionic verification-needed-focal 
verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-bionic verification-done-focal 
verification-done-jammy verification-done-kinetic

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

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Fix Released

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgad

[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR

[Roxana Nicolescu]

** Description changed:

  SRU Justification
+ [Impact]
+ Intel has introduced support for their new Emerald Rapids CPU. 
+ It was backported to Jammy in #lp2015372
+  
+ The remaining feature needed to fully support EMR is the split lock detection 
mechanism.
+ So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is 
supported or not, but this is not architectural, meaning that this should be 
trusted only if it’s confirmed that a specific CPU model implements it. This 
lead to a mapping between a CPU model and whether it supports split lock 
detection by default (no need to check IA32_CORE_CAPABILITIES) or they may 
support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be 
checked.
  
- [Impact]
+ With more and more CPU models, this becomes hard to maintain. Moreover, the 
December 2022 edition of the Intel Instruction Set Extensions manual defined 
that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and 
retrospectively always has been) architectural. Documentation also mentions 
+ “All processors that enumerate support for MSR_IA32_CORE_CAPS and set 
MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.”
  
- #2009315 adds support for their new Emerald Rapids CPU to Jammy.
+ Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8:
+ “ x86/split_lock: Enumerate architectural split lock disable bit” from 
linux-next removes the need of adding a new CPU model in that mapping.
  
- Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next
- introduces support for Split lock detection.
- 
- 
+ This is needed to support split lock detection for the new EMR CPU and future 
models that don’t suffer architectural changes.
+  
  [Testing]
- Kernel was built on cbd and boot tested on a VM.
- TODO ask for help from intel.
+  Kernel was built on cbd and boot tested on a VM.
+ Intel was asked to install and test the new kernel from this ppa 
https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855
  
  [Regression potential]
- TODO assess this
+  Very low, it is a small refactor and in essence, it does the exact same 
thing for existing cpu models:
+ 1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes 
the mechanism is supported.
+ 2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES 
without the extra step of checking the map if the CPU supports this (which was 
always true)

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

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

Title:
  Add split lock detection for EMR

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Confirmed

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU. 
  It was backported to Jammy in #lp2015372
   
  The remaining feature needed to fully support EMR is the split lock detection 
mechanism.
  So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is 
supported or not, but this is not architectural, meaning that this should be 
trusted only if it’s confirmed that a specific CPU model implements it. This 
lead to a mapping between a CPU model and whether it supports split lock 
detection by default (no need to check IA32_CORE_CAPABILITIES) or they may 
support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be 
checked.

  With more and more CPU models, this becomes hard to maintain. Moreover, the 
December 2022 edition of the Intel Instruction Set Extensions manual defined 
that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and 
retrospectively always has been) architectural. Documentation also mentions 
  “All processors that enumerate support for MSR_IA32_CORE_CAPS and set 
MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.”

  Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8:
  “ x86/split_lock: Enumerate architectural split lock disable bit” from 
linux-next removes the need of adding a new CPU model in that mapping.

  This is needed to support split lock detection for the new EMR CPU and future 
models that don’t suffer architectural changes.
   
  [Testing]
   Kernel was built on cbd and boot tested on a VM.
  Intel was asked to install and test the new kernel from this ppa 
https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855

  [Regression potential]
   Very low, it is a small refactor and in essence, it does the exact same 
thing for existing cpu models:
  1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes 
the mechanism is supported.
  2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES 
without the extra step of checking the map if the CPU supports this (which was 
always true)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s

[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR

[Roxana Nicolescu]

** Attachment added: 
"architecture-instruction-set-extensions-programming-reference.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015855/+attachment/5663634/+files/architecture-instruction-set-extensions-programming-reference.pdf

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

Title:
  Add split lock detection for EMR

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Confirmed

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU. 
  It was backported to Jammy in #lp2015372
   
  The remaining feature needed to fully support EMR is the split lock detection 
mechanism.
  So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is 
supported or not, but this is not architectural, meaning that this should be 
trusted only if it’s confirmed that a specific CPU model implements it. This 
lead to a mapping between a CPU model and whether it supports split lock 
detection by default (no need to check IA32_CORE_CAPABILITIES) or they may 
support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be 
checked.

  With more and more CPU models, this becomes hard to maintain. Moreover, the 
December 2022 edition of the Intel Instruction Set Extensions manual defined 
that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and 
retrospectively always has been) architectural. Documentation also mentions 
  “All processors that enumerate support for MSR_IA32_CORE_CAPS and set 
MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.”

  Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8:
  “ x86/split_lock: Enumerate architectural split lock disable bit” from 
linux-next removes the need of adding a new CPU model in that mapping.

  This is needed to support split lock detection for the new EMR CPU and future 
models that don’t suffer architectural changes.
   
  [Testing]
   Kernel was built on cbd and boot tested on a VM.
  Intel was asked to install and test the new kernel from this ppa 
https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855

  [Regression potential]
   Very low, it is a small refactor and in essence, it does the exact same 
thing for existing cpu models:
  1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes 
the mechanism is supported.
  2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES 
without the extra step of checking the map if the CPU supports this (which was 
always true)

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


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

[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR

[Roxana Nicolescu]

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu)
     Assignee: Roxana Nicolescu (roxanan) => (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/2015855

Title:
  Add split lock detection for EMR

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

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU. 
  It was backported to Jammy in #lp2015372
   
  The remaining feature needed to fully support EMR is the split lock detection 
mechanism.
  So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is 
supported or not, but this is not architectural, meaning that this should be 
trusted only if it’s confirmed that a specific CPU model implements it. This 
lead to a mapping between a CPU model and whether it supports split lock 
detection by default (no need to check IA32_CORE_CAPABILITIES) or they may 
support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be 
checked.

  With more and more CPU models, this becomes hard to maintain. Moreover, the 
December 2022 edition of the Intel Instruction Set Extensions manual defined 
that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and 
retrospectively always has been) architectural. Documentation also mentions 
  “All processors that enumerate support for MSR_IA32_CORE_CAPS and set 
MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.”

  Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8:
  “ x86/split_lock: Enumerate architectural split lock disable bit” from 
linux-next removes the need of adding a new CPU model in that mapping.

  This is needed to support split lock detection for the new EMR CPU and future 
models that don’t suffer architectural changes.
   
  [Testing]
   Kernel was built on cbd and boot tested on a VM.
  Intel was asked to install and test the new kernel from this ppa 
https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855

  [Regression potential]
   Very low, it is a small refactor and in essence, it does the exact same 
thing for existing cpu models:
  1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes 
the mechanism is supported.
  2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES 
without the extra step of checking the map if the CPU supports this (which was 
always true)

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


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