date:20240118

All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1055.51) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

digimend-dkms/10-4 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2049733] [NEW] Dynamically determine acpi_handle_list size

2024-01-18 Thread Ivan Hu

Public bug reported:

[Impact]
ACPI handle list will be dynamic allocated without default fixed size.

[Fix]
Currently the ACPI_MAX_HANDLES is defined fix to 10, and it is not enough for 
some platforms that called ACPI _PSL method to get passive cooling device 
objects. then will get the error message "Invalid passive threshold", this 
patch change the fixed size with the dynamic handle list size which fixes the 
handle reference error.

[Test Case]
check the dmesg to see if there is the error message "Invalid passive threshold"

[Where problems could occur]
Only change the fixed size with the dynamic handle list size. Risk of 
regression is low.

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

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

Title:
  Dynamically determine acpi_handle_list size

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  ACPI handle list will be dynamic allocated without default fixed size.

  [Fix]
  Currently the ACPI_MAX_HANDLES is defined fix to 10, and it is not enough for 
some platforms that called ACPI _PSL method to get passive cooling device 
objects. then will get the error message "Invalid passive threshold", this 
patch change the fixed size with the dynamic handle list size which fixes the 
handle reference error.

  [Test Case]
  check the dmesg to see if there is the error message "Invalid passive 
threshold"

  [Where problems could occur]
  Only change the fixed size with the dynamic handle list size. Risk of 
regression is low.

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


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

[Kernel-packages] [Bug 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

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

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

Title:
  Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  To support HP stella's latest machine, we need to backport some new PCIIDs 
and corresponding drivers to our OEM kernel, the requirement is here:
  
https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508

  This pull-request is to unitfy and add some audio controller's ID, but
  to do so, need to apply some depending patches otherwise it will have
  conflict to introduce the new ID and new driver to OEM kernel.

  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL

  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

  [Fix]
  This add the audio driver for machines with Intel Arrowlake.

  [Test case]
  Boot the patched kernel on a Arrowlake machine, the audio function could 
work. Boot the patches kernel on non-Arrowlake machines, the audio function 
could work as well as before.

  [Where problems could occur]
  Could lose some pciids and make the auido driver not work on those machines, 
and could not play sound or record sound. But this possibility is very low, I 
checked each patch carefully and I verify the patcheset on some lenovo an dell 
machines.

  From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based 
on it, added new PCIID and audio support for arrowlake-s, need to backport them 
to oem-6.5, this is a preparation for supporting HP latest laptops:
  unified PCIIDs:
  PCI_DEVICE_ID_INTEL_HDA_ADL_N
  PCI_DEVICE_ID_INTEL_HDA_RPL_P_0
  PCI_DEVICE_ID_INTEL_HDA_ADL_P
  PCI_DEVICE_ID_INTEL_HDA_RPL_S
  PCI_DEVICE_ID_INTEL_HDA_MTL

  new added PCIID:
  PCI_DEVICE_ID_INTEL_HDA_ARL_S

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


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

[Kernel-packages] [Bug 2049634] Re: SMB 1 broken in kernel 6.5.0.14.14~22.04.7

2024-01-18 Thread R. Diez

I have kept one corrupt text file (which I cannot post here), and I ran
this command on it:

grep  --perl-regexp  --text  --byte-offset  '\x00{3900}'  my-corrupt-
text-file

The file has 2 blocks of binary zeros which should not be there. Their
offsets are random, but both blocks are exactly 3900 bytes long. I had
expected some power of 2 like 1024.

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

Title:
  SMB 1 broken in kernel 6.5.0.14.14~22.04.7

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

Bug description:
  Hi all:

  I upgraded my Ubuntu yesterday and automatically got the newer Linux
  Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was
  running kernel version 6.2 .

  I still have a legacy system on the network using SMB protocol version
  1.0.

  With the new kernel version, copying files does not work reliably
  anymore. Some random byte blocks in the destination files are
  overwritten with binary zeros. It happens quite often.

  This is not the first time the Linux guys temporarily break SMB protocol 
version 1.0, see for example this bug report of mine:
  https://bugs.launchpad.net/ubuntu/+bug/2033732

  I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it 
lists just 2 versions:
6.5.0.14.14~22.04.7 (jammy-updates)
5.15.0.25.27 (jammy)
  Is there a way to go back to the latest 6.2 kernel version?

  How do I prevent Ubuntu from upgrading to 6.5 next time around? I have 
searched the Internet, but I haven't
  found yet a usable answer. I don't want to go back all the way to Kernel 5.15 
if I can avoid it.

  Thanks in advance,
rdiez

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


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

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

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

Title:
  Mantic update: v6.5.10 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.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 PMIC GPIO label in gpio-ranges
  arm64: dts: rockchip: Add i2s0-2ch-bus-bclk-off pins to RK3399
  arm64: dts: rockchip: Fix i2s0 pin conflict on ROCK Pi 4 boards
  i40e: sync next_to_clean and next_to_process for programming status desc
  mm: fix vm_brk_flags() to not bail out while holding lock
  hugetlbfs: clear resv_map pointer if mmap fails
  mm/page_alloc: correct start page when guard page debug is enabled
  mm/migrate: fix do_pages_move for compat pointers
  selftests/mm: include mman header to access MREMAP_DONTUNMAP identifier
  mm/mempolicy: fix set_mempolicy_home_node() previous VMA pointer
  hugetlbfs: extend hugetlb_vma_lock to private VMAs
  maple_tree: add GFP_KERNEL to allocations in mas_expected_entries()
  nfsd: lock_rename() needs both directories to live on the same fs
  vdpa_sim_blk: Fix the potential leak of mgmt_dev
  vdpa/mlx5: Fix double release of debugfs entry
  ARM: OMAP1: ams-delta: Fix MODEM initialization failure
  ARM: dts: rockchip: Fix i2c0 register address for RK3128
  ARM: dts: rockchip: Add missing arm timer interrupt for RK3128
  ARM: dts: rockchip: Add missing quirk for RK3128's dma engine
  ARM: dts: rockchip: Fix timer clocks for RK3128
  accel/ivpu: Don't enter d0i3 during FLR
  drm/i915/pmu: Check if pmu is closed before stopping event
  drm/amd: Disable ASPM for VI w/ all Intel systems
  drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper()
  btrfs: remove v0 extent handling
  btrfs: fix unwritten extent buffer after snapshotting a new subvolume
  ARM: OMAP: timer32K: fix all kernel-doc warnings
  firmware/imx-dsp: Fix use_after_free in imx_dsp_setup_channels()
  clk: ti: Fix missing omap4 mcbsp functional clock and aliases
  clk: ti: Fix missing omap5 mcbsp functional clock and aliases
  r8169: fix the KCSAN reported data-race in rtl_tx() while reading tp->cur_tx
  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
  iavf: initialize waitqueues before starting watchdog_task
  i40e: Fix I40E_FLAG_VF_VLAN_PRUNING value
  treewide: Spelling fix in comment
  igb: Fix potential memory leak in igb_add_ethtool_nfc_entry
  net: do not leave an empty skb in write queue
  neighbour: fix various data-races
  igc: Fix ambiguity in the ethtool advertising
  net: ethernet: adi: adin1110: Fix uninitialized variable
  net: ieee802154: adf7242: Fix some potential buffer overflow in 
adf7242_stats_show()
  net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg
  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
  r8152: Release firmware if we have an error in probe
  tcp: fix wrong RTO timeout when received SACK reneging
  wifi: cfg80211: pass correct pointer to rdev_inform_bss()
  wifi: cfg80211: fix assoc resp

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  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:

     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 equals to 1
  btrfs: initialize start_slot in btrfs_log_prealloc_extents
  i2c: mux: Avoid potential false error message in i2c_mux_add_adapter
  overlayfs: set ctime when setting mtime and atime
  gpio: timberdale: Fix

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

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

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

Title:
  Jammy update: v5.15.138 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  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.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_dev
  vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE
  mm/page_alloc: correct start page when guard page debug is enabled
  mm/migrate: fix do_pages_move for compat pointers
  nfsd: lock_rename() needs both directories to live on the same fs
  drm/i915/pmu: Check if pmu is closed before stopping event
  vsock/virtio: factor our the code to initialize and delete VQs
  vsock/virtio: add support for device suspend/resume
  vsock/virtio: initialize the_virtio_vsock before using VQs
  drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper()
  firmware/imx-dsp: Fix use_after_free in imx_dsp_setup_channels()
  r8169: fix the KCSAN reported data-race in rtl_tx() while reading tp->cur_tx
  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
  i40e: Fix I40E_FLAG_VF_VLAN_PRUNING value
  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()
  net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg
  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
  r8152: Release firmware 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
  i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR
  kasan: print the original fault addr when access invalid shadow
  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 the description of variable length arguments
  misc: fastrpc: Clean buffers on remote invocation failures
  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
  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
  iio: afe: rescale: reorder includes
  iio: afe: rescale: expose scale processing function
  iio: afe: rescale: add offset support
  iio: afe: rescale: Accept only offset channels
  gve: Fix GFP flags when allocing pages
  x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility
  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: fix BUG in ext4_mb_new_inode_pa() due to overflow
  ext4: avoid overlapping preallocations due to overflow
  objtool/x86: add missing embedded_insn check
  driver: platform: Add helper for safer setting of driver_override
  rpmsg: Constify local variable in field store macro
  rpmsg: Fix kfree() of static memory

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

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

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

Title:
  Jammy update: v5.15.139 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  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.15.139 upstream stable release
     from git://git.kernel.org/

  iov_iter, x86: Be consistent about the __user tag on copy_mc_to_user()
  sched/uclamp: Ignore (util == 0) optimization in feec() when p_util_max = 0
  sched: Fix stop_one_cpu_nowait() vs hotplug
  vfs: fix readahead(2) on block devices
  writeback, cgroup: switch inodes with dirty timestamps to release dying cgwbs
  x86/srso: Fix SBPB enablement for (possible) future fixed HW
  futex: Don't include process MM in futex key on no-MMU
  x86: Share definition of __is_canonical_address()
  x86/sev-es: Allow copy_from_kernel_nofault() in earlier boot
  x86/boot: Fix incorrect startup_gdt_descr.size
  pstore/platform: Add check for kstrdup
  genirq/matrix: Exclude managed interrupts in irq_matrix_allocated()
  i40e: fix potential memory leaks in i40e_remove()
  selftests/bpf: Test tail call counting with bpf2bpf and data on stack
  selftests/bpf: Correct map_fd to data_fd in tailcalls
  udp: add missing WRITE_ONCE() around up->encap_rcv
  tcp: call tcp_try_undo_recovery when an RTOd TFO SYNACK is ACKed
  gve: Use size_add() in call to struct_size()
  mlxsw: Use size_mul() in call to struct_size()
  tipc: Use size_add() in calls to struct_size()
  net: spider_net: Use size_add() in call to struct_size()
  wifi: rtw88: debug: Fix the NULL vs IS_ERR() bug for debugfs_create_file()
  wifi: mt76: mt7603: rework/fix rx pse hang check
  mt76: dma: use kzalloc instead of devm_kzalloc for txwi
  mt76: add support for overriding the device used for DMA mapping
  mt76: pass original queue id from __mt76_tx_queue_skb to the driver
  wifi: mt76: mt7603: improve stuck beacon handling
  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()
  can: dev: can_put_echo_skb(): don't crash kernel if can_priv::echo_skb is 
accessed out of bounds
  PM / devfreq: rockchip-dfi: Make pmu regmap mandatory
  netfilter: nf_tables: Drop pointless memset when dumping rules
  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: fix cookie_init_timestamp() overflows
  iwlwifi: pcie: adjust to Bz completion descriptor
  wifi: iwlwifi: call napi_synchronize() before freeing rx/tx queues
  wifi: iwlwifi: pcie: synchronize IRQs before NAPI
  wifi: iwlwifi: empty overflow queue during flush
  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()
  spi: tegra: Fix missing IRQ check in tegra_slink_probe()
  clk: qcom: clk-rcg2: Fix clock rate overflow for high parent frequencies
  clk: qcom: mmcc-msm8998: Don't check halt bit on some branch clks
  clk: qcom: mmcc-msm8998: Fix the SMMU GDSC
  clk: qcom: gcc-sm8150: Fix gcc_sdcc2_apps_clk_src
  clk: imx: Select MXC_CLK for CLK_IMX8QXP
  clk: imx: imx8mq: correct error handling path
  clk: imx: imx8qxp: Fix elcdif_pll clock
  clk: renesas: rzg2l: Simplify multiplication/shift logic
  clk: renesas: rzg2l: Use FIELD_GET() for PLL register fields
  clk: renesas: rzg2l: Fix computation formula
  spi: nxp-fspi: use the correct ioremap function
  clk: keystone: pll: fix a couple NULL vs IS_ERR() checks
  clk: ti: Add ti_dt_clk_name() helper to use clock-output-names
  clk: ti: Update pll and clockdomain clocks to use ti_dt_clk_name()
  clk: ti: Update component clocks to use ti_dt_clk_name()
  clk: ti: change ti_clk_register[_omap_hw]() API
  clk: ti: fix double free in of_ti_divider_clk_setup()
  clk: npcm7xx: Fix incorrect kfree
  clk: mediatek: clk-mt6765: Add check for mtk_alloc_clk_data
  clk: medi

[Kernel-packages] [Bug 2049634] Re: SMB 1 broken in kernel 6.5.0.14.14~22.04.7

2024-01-18 Thread Matthew Ruffell

Exactly 3900 bytes long? That sure is strange. Do you think I would be
able to reproduce if I set up a smb1.0 mount, make a bunch of text files
with random content, take their sha256 checksums, copy to the smb1.0
share, then re-compute the sha256 checksums to see if they match?

I would probably be able to bisect kernel commits if it reproduced most
of the time.

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

** No longer affects: linux-hwe-6.5 (Ubuntu)

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

Title:
  SMB 1 broken in kernel 6.5.0.14.14~22.04.7

Status in linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  New

Bug description:
  Hi all:

  I upgraded my Ubuntu yesterday and automatically got the newer Linux
  Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was
  running kernel version 6.2 .

  I still have a legacy system on the network using SMB protocol version
  1.0.

  With the new kernel version, copying files does not work reliably
  anymore. Some random byte blocks in the destination files are
  overwritten with binary zeros. It happens quite often.

  This is not the first time the Linux guys temporarily break SMB protocol 
version 1.0, see for example this bug report of mine:
  https://bugs.launchpad.net/ubuntu/+bug/2033732

  I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it 
lists just 2 versions:
6.5.0.14.14~22.04.7 (jammy-updates)
5.15.0.25.27 (jammy)
  Is there a way to go back to the latest 6.2 kernel version?

  How do I prevent Ubuntu from upgrading to 6.5 next time around? I have 
searched the Internet, but I haven't
  found yet a usable answer. I don't want to go back all the way to Kernel 5.15 
if I can avoid it.

  Thanks in advance,
rdiez

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


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

[Kernel-packages] [Bug 2049733] Re: Dynamically determine acpi_handle_list size

2024-01-18 Thread Ivan Hu

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Ivan Hu (ivan.hu)

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

Title:
  Dynamically determine acpi_handle_list size

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  New

Bug description:
  [Impact]
  ACPI handle list will be dynamic allocated without default fixed size.

  [Fix]
  Currently the ACPI_MAX_HANDLES is defined fix to 10, and it is not enough for 
some platforms that called ACPI _PSL method to get passive cooling device 
objects. then will get the error message "Invalid passive threshold", this 
patch change the fixed size with the dynamic handle list size which fixes the 
handle reference error.

  [Test Case]
  check the dmesg to see if there is the error message "Invalid passive 
threshold"

  [Where problems could occur]
  Only change the fixed size with the dynamic handle list size. Risk of 
regression is low.

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


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

[Kernel-packages] [Bug 2049634] Re: SMB 1 broken in kernel 6.5.0.14.14~22.04.7

2024-01-18 Thread R. Diez

I haven't tested much, but this corruption was obvious very quickly. I
just copied a few megabytes of files and got several corruptions. Most
files were compressed, and the easiest file to look at was a text file,
and the binary zeros were quickly visible in the text editor. I think
you will not have any trouble reproducing this issue.

I didn't need to do checksums, just copy with "cp" and immediately
compare with "cmp" or "meld". There was no need to reconnect, purge any
caches or anything fancy.

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

Title:
  SMB 1 broken in kernel 6.5.0.14.14~22.04.7

Status in linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  New

Bug description:
  Hi all:

  I upgraded my Ubuntu yesterday and automatically got the newer Linux
  Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was
  running kernel version 6.2 .

  I still have a legacy system on the network using SMB protocol version
  1.0.

  With the new kernel version, copying files does not work reliably
  anymore. Some random byte blocks in the destination files are
  overwritten with binary zeros. It happens quite often.

  This is not the first time the Linux guys temporarily break SMB protocol 
version 1.0, see for example this bug report of mine:
  https://bugs.launchpad.net/ubuntu/+bug/2033732

  I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it 
lists just 2 versions:
6.5.0.14.14~22.04.7 (jammy-updates)
5.15.0.25.27 (jammy)
  Is there a way to go back to the latest 6.2 kernel version?

  How do I prevent Ubuntu from upgrading to 6.5 next time around? I have 
searched the Internet, but I haven't
  found yet a usable answer. I don't want to go back all the way to Kernel 5.15 
if I can avoid it.

  Thanks in advance,
rdiez

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/6.5.0.17.17.14)

All autopkgtests for the newly accepted linux-meta-lowlatency (6.5.0.17.17.14) 
for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

linux-lowlatency/6.5.0-17.17.1 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#linux-meta-lowlatency

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

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


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

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

You have been subscribed to a public bug:

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

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

-- 
"kvm: enabling virtualization on CPUx failed" on "Ubuntu 22.04.03 with kernel 
6.5.0-14-generic"
https://bugs.launchpad.net/bugs/2049750
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.5 in Ubuntu.

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

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

2024-01-18 Thread Paul White

** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)

** Tags added: jammy

-- 
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 2046504] Re: Fix AMDGPU display on lower resolution modes

2024-01-18 Thread AaronMa

It's merged by Bug #2044174 by stable updates.

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

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

Title:
  Fix AMDGPU display on lower resolution modes

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  AMD GPU display is blank when set lower resolution than native mode on eDP.

  [Fix]
  On eDP the invalid modes are set, call mode set for valid modes instead.

  [Test]
  Tested on hardware, all the modes shown in gnome menu can be set OK.

  [Where problems could occur]
  It may break AMD display.

  This issue is not reproduced on v6.2- kernel versions, so SRU for
  oem-6.5 only.

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


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

[Kernel-packages] [Bug 2047389] Re: Fix AMDGPU crash on 6.5 kernel

2024-01-18 Thread AaronMa

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

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

Title:
  Fix AMDGPU crash on 6.5 kernel

Status in HWE Next:
  In Progress
Status in linux 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.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  AMD GPU crash with a message: " cp queue preemption timeout".

  [Fix]
  Disable MCBP(mid command buffer preemption) by default as old Mesa
  hangs with it.

  [Test]
  Tested on hardware, play web video for more than 1 hour OK.

  [Where problems could occur]
  It may break AMD GPU.

  This issue is only reproduced on v6.5+ kernel versions and fixes in
  v6.6, so SRU for oem-6.5, mantic.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-ibm/5.15.0.1046.42)

All autopkgtests for the newly accepted linux-meta-ibm (5.15.0.1046.42) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

wireguard/unknown (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-ibm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2047518] Re: Fix BCM57416 lost after resume

2024-01-18 Thread AaronMa

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

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

Title:
  Fix BCM57416 lost after resume

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
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.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  BCM57416 is lost after resume.
  Error log:
  [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 
0x125d error 0x4
  [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 
failed. rc:ffe4 err:4
  [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure 
rc: fffb
  [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb

  [Fix]
  Clear the reservations in driver after reset the ethernet card.

  [Test]
  Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works 
fine.

  [Where problems could occur]
  It may break broadcom bnxt driver.

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


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

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

2024-01-18 Thread Tony Duan

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

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

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

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

Bug description:
  Bug description:

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

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

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

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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-01-18 Thread Daniel van Vugt

Actually, not that scary. I think I can implement a complete solution as
a single kernel patch. Just extend fbcon's deferred takeover feature to
wait until a certain timeout has passed. And if "splash" is present then
you can assume that should be a default of 10 seconds to wait for
Plymouth's 8 second device timeout.


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

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

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  In Progress

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync

2024-01-18 Thread alex

Hi. I have the same problem on radi5x2 arrays assembled in stripe
The total volume of the array is 97 TB and free 16 GB
Do users who have a bug also have little free space?
I couldn’t reproduce this condition on a test bench under a synthetic load.
Ubuntu 22.04.3 LTS
kernel 5.15.0.-72-generic

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]  submit_bio_noacct+0x112/0x4f0
  [921588.559075]  submit_bio+0x51/0x1a

[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

Is this going to happen for noble? It should just be kernel config
changes at this point.

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

Title:
  Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer

Status in gdm:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Won't Fix
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in linux package in Fedora:
  Fix Released

Bug description:
  [ Impact ]

  The fbdev subsystem has been deprecated for a long time. We should
  drop it in favour of using simpledrm with fbdev emulation layer.

  This requires Kernel config changes:

  FB_EFI=n
  FB_VESA=n

  fbcon will still require FB to be available, but will use the fbdev
  emulation layer

  [ Test Plan ]

  * Ensure that systems currently relying on fbdev (and therefore only
  allowing Xorg logins) such as some virtual machine types, boot with
  working Wayland support.

  [ Where Problems could occur ]

  * When this stack is enabled, it changes boot timing such that some drivers 
may take a longer time to boot and GDM may hang in a black screen (bug 2039757).
  * Race conditions could be exposed to DE environments
  * Software that expects to find DRM device at /dev/dri/card0 may have a 
problem.
  * Some older versions of NVIDIA driver might not work properly.

  [ Other Info ]

  * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1123.116)

All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1123.116) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
systemd/245.4-4ubuntu3.22 (arm64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.15.0.1050.46)

All autopkgtests for the newly accepted linux-meta-kvm (5.15.0.1050.46) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/9858-0ubuntu3.4 (amd64)
digimend-dkms/10-4 (amd64)
oss4/4.2-build2010-5ubuntu9.1 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.2 (amd64)
rtl8821ce/5.5.2.1-0ubuntu11~0.22.04.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-kvm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2049758] [NEW] DP connection swap to break eDP behavior on AMD 7735U

2024-01-18 Thread Anson Tsao

Public bug reported:

Some OEM platforms swap DP connections on the Rembrandt-R, which causes
improper eDP behavior. AMD experimented with reproducing at CRB level to
come out with a solution

- Fn key failed to control brightness
- eDP remains black screen during S0i3 cycle

Patch:
https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749

DMCUB FW:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8

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

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

Title:
  DP connection swap to break eDP behavior on AMD 7735U

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

Bug description:
  Some OEM platforms swap DP connections on the Rembrandt-R, which
  causes improper eDP behavior. AMD experimented with reproducing at CRB
  level to come out with a solution

  - Fn key failed to control brightness
  - eDP remains black screen during S0i3 cycle

  Patch:
  
https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749

  DMCUB FW:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8

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


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

[Kernel-packages] [Bug 2049303] Re: MT7921 - IPv6 no longer working (Not receiving Multicast)

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

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

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

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

Title:
  MT7921 - IPv6 no longer working (Not receiving Multicast)

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

Bug description:
  After updating to kernel linux-image-6.5.0-14-generic, IPv6 stopped working 
with the MT7921 wifi card.
  No errors are logged, but when using tcpdump / wireshark to capture traffic, 
I can see the MT7921 card no longer appears to receive IPv6 Multicast (thus it 
never receives the Router Advertisements, etc.).

  Booting back to the previous kernel image (linux-
  image-6.2.0-39-generic) resolves the issue and IPv6 Multicast works
  fine and IPv6 connectivity works fine again.

  The system is configured to use the 22.04 HWE kernel to better support
  the AMD Advantage Platform hardware (ASUS ROG Strix G513QY).

  Steps to reproduce:
  1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and 
connect it to a Dual-stack network leveraging Router Advertisements for IPv6.

  2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the 
following:
  - IPv6 stateless autoconfiguration works and a public/global address is 
assigned.
  - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.

  3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the 
following:
  - IPv6 only configures link-local address (fe80::) and no public/global 
address.
  - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.

  
  fludizz@pauwel:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Network card in question:
  05:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express 
Wireless Network Adapter
Subsystem: AzureWave Device 4680
Flags: bus master, fast devsel, latency 0, IRQ 83, IOMMU group 14
Memory at fc3030 (64-bit, prefetchable) [size=1M]
Memory at fc3040 (64-bit, prefetchable) [size=16K]
Memory at fc30404000 (64-bit, prefetchable) [size=4K]
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 

Capabilities: [108] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [200] Advanced Error Reporting
Kernel driver in use: mt7921e
Kernel modules: mt7921e

  
  fludizz@pauwel:~$ apt-cache policy linux-image-6.5.0-14-generic
  linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14~22.04.1
Candidate: 6.5.0-14.14~22.04.1
Version table:
   *** 6.5.0-14.14~22.04.1 500
  500 http://nl.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

  Note: The WiFi device is using the same firmware version on both
  kernels.

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


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

[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms

2024-01-18 Thread Andreas Hasenack

> because of lp:2047492, I can't verify it on mantic.

If this can't be verified in mantic, then please don't flip the mantic
verification tags :)


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

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

Title:
  Update soundwire topology files for Intel RPL platforms

Status in firmware-sof package in Ubuntu:
  Fix Released
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Mantic:
  Fix Committed

Bug description:
  [Impact]
  Old RPL soundwire topology files are found to be muted when doing audio 
capture on left channel.

  [Fix]

  The commit from https://github.com/thesofproject/sof-bin/ is required.
  * 
https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d
 (Update v2.2.8 topology files for Intel RPL platforms)

  [Test Case]

  Test audio functions on Dell MayaBay RTL platforms.

  [Where problems could occur]
  Most topology files for Intel RPL are updated. Need more confirmation on 
Intel RPL platforms.

  [Other info]

  Lunar is skipped, as it'll be EOL soon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+subscriptions


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

[Kernel-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable

2024-01-18 Thread theofficialgman

Found a rouge service (not from the ubuntu distro but instead my custom
nvidia tegra BSP) that had the `/usr/lib/bluetooth/bluetoothd` path in
it.

Closing as removing or altering that service fixes it.

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

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

Title:
  bluez bluetoothd unable to locate executable

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Release: Ubuntu Noble Dev Branch

  the location of bluetoothd was just changed to
  /usr/libexec/bluetooth/bluetoothd

  this causes bluetooth to fail to start since something is still
  looking for the old location

  Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth 
service...
  ░░ Subject: A start job for unit bluetooth.service has begun execution
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ A start job for unit bluetooth.service has begun execution.
  ░░
  ░░ The job identifier is 2843.
  Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 ConfigurationDire>
  Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate 
executable /usr/lib/bluetooth/bluetoothd: No such file or directory
  ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed.
  ░░
  ░░ The error number returned by this process is ERRNO.
  Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step 
EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory

  the system service ExecStart location was correctly updated so not
  sure what still has the old location

  cat /lib/systemd/system/bluetooth.service
  [Unit]
  Description=Bluetooth service
  Documentation=man:bluetoothd(8)
  ConditionPathIsDirectory=/sys/class/bluetooth

  [Service]
  Type=dbus
  BusName=org.bluez
  ExecStart=/usr/libexec/bluetooth/bluetoothd

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


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

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

This bug was fixed in the package ivsc-driver -
0~git202212210258.94ecb88b-0ubuntu0.23.10.3

---
ivsc-driver (0~git202212210258.94ecb88b-0ubuntu0.23.10.3) mantic; urgency=low

  [ You-Sheng Yang ]
  * Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
- ljca: try to find acpi device from hub device
- mei-vsc: port mei api change in v6.2
- mfd: ljca: Fix try_match_acpi_hid return value checking
- misc: spi-vsc: Fix cvfd_ids array with terminator

 -- You-Sheng Yang   Wed, 23 Aug 2023
00:11:46 +0800

** Changed in: ivsc-driver (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

** Changed in: ipu6-drivers (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Released
Status in ivsc-driver source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic

[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform

This bug was fixed in the package ipu6-drivers -
0~git202310180730.3f813580-0ubuntu0.23.10.1

---
ipu6-drivers (0~git202310180730.3f813580-0ubuntu0.23.10.1) mantic; urgency=low

  [ You-Sheng Yang ]
  * New upstream release
- Support mipi camera on Intel Meteor Lake platform (LP: #2031412)
- debian: refresh patches, drop upstreamed ones
  * d/patches/0007: add CONFIG_VIDEO_V4L2_I2C to BUILD_EXCLUSIVE_CONFIG
(LP: #2012407)
  * debian: add modaliases (LP: #2021740)

 -- You-Sheng Yang   Fri, 01 Sep 2023
17:51:53 +0800

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

Title:
  Support mipi camera on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in ivsc-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in ivsc-driver source package in Jammy:
  Won't Fix
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Mantic:
  Fix Released
Status in ivsc-driver source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in ivsc-driver source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  == ipu6-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform.

  [Fix]

  Based on upstream tag
  https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019,
  and an additional patch to enable/fix compilation of additional sensor
  modules.

  [Test Case]

  This is verified on MTL Lattice and VSC platforms, as well as previous
  generations e.g. TGL and ADL.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  This is a new platform. We've been verifying its functions and features, and
  are still polishing it.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == ivsc-driver ==

  [Impact]

  Missing Intel MIPI firmware for Meteor Lake platform. Need both
  firmware and driver change to probe the hardware correctly.

  [Fix]

  4 commits from the latest trunk branch on upstream repository
  https://github.com/intel/ivsc-driver.

  [Test Case]

  With all other changes in position, Intel VSC driver modules are to be
  loaded as a soft dependency of some selected camera sensor modules.
  LJCA modules should be loaded automatically on MTL platforms as well.

  To actually verify the camera framework:
  ```
  # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
  # reboot into the 6.5.0-14.14 kernel
  $ sudo apt install intel-ipu6-dkms intel-vsc-dkms
  $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
  $ sudo apt install gstreamer1.0-icamera v4l2-relayd
  ```
  In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, 
and their dependencies, are fetched from the oem-solutions-group PPA. 
Everything else must come from the mantic archive.

  And then browse https://webcamtests.com/ for testing.

  [Where problems could occur]

  While it changes how LJCA modules match from ACPI ID, it's also tested
  and verified on previous generations using IVSC, e.g. TGL, ADL.

  [Other Info]

  While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and
  linux/mantic and on, and yet the lastest stable driver was verified after 
Mantic was released, it's being proposed to Noble instead.

  == linux/linux-oem-6.5 ==

  [Impact]

[Kernel-packages] [Bug 2048077] Re: Migrate oem-6.1 to oem-6.5

** Changed in: linux-meta-oem-6.5 (Ubuntu Jammy)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: linux-restricted-modules-oem-6.5 (Ubuntu Jammy)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Migrate oem-6.1 to oem-6.5

Status in linux-meta-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-restricted-modules-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-meta-oem-6.5 source package in Jammy:
  New
Status in linux-restricted-modules-oem-6.5 source package in Jammy:
  New

Bug description:
  [Impact]
  Migrate oem-6.1 to oem-6.5, because some platforms need it instead of hwe-6.5.

  
  [Test case]
  Update a machine with oem-6.1 metapackages to the proposed ones, and verify 
that all packages (including nvidia etc) migrate properly.

  [Where things could go wrong]
  In theory we might miss a package to transition, but at this point this is 
unlikely.

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


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

[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)

2024-01-18 Thread Craig G

Thanks for the update.  I've just installed the suggested 17 series of
kernel packages on a test machine.  It will probably take a day or so to
confirm the issue is gone, but as long as that patch is in there, I'm
pretty confident it will address the issue I was seeing.  I'll update
again if I still see the issue, otherwise, thanks again for your help!

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

Title:
  Memory leak in 23.10 kernel (6.5.0-10)

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

Bug description:
  There appears to be a memory 'leak' in the kernel of the latest Ubuntu release
  (Mantic Minotaur, kernel version 6.5.0-10).  I put 'leak' in quotes because 
this
  memory appears to be allocated but never used.  The kernel's memory 
over-commit
  mechanism seems to prevent this leak from manifesting in OOM killer triggers 
or
  other failures.

  The primary symptom is a steady increase in the value reported as 
'Committed_AS'
  in '/proc/meminfo'.  The other memory stats reported there remain reasonable,
  though.

  I've observed this problem on a fairly diverse set of machines (both VMs and
  physical machines) with a variety of workloads.  Busier machines seem to have 
a
  faster leak rate.  I've tried to narrow down the issue by rebooting into 
single
  user mode, killing all userspace processes (except the systemd processes) and
  removing as many kernel models as possible.  The problem continues in that
  state.  I didn't see any obvious culprits in /proc/slabinfo nor
  /proc/vmallocinfo.

  So far, the only way I've been able to remediate this issue is to reboot back
  into the Lunar Lobster kernel (6.2.0-35).  I think this fact alone rules out 
any
  triggers that may be part of the 23.10 userspace environment.

  I've attached the generic debug info requested by this component's bug 
template
  from an example machine. Please let me know if there is any more information I
  can provide.  It seems to be pretty trivial to reproduce though, and I'm
  guessing it has not been reported yet because the leak doesn't actually 
manifest
  in an out-of-memory situation.  At least, I haven't observed that yet.  The
  worst case I've observed was 150 GB of memory committed on a machine with 16 
GB
  of physical RAM after about 24 hours.  Moving back to the previous kernel
  version, the committed memory statistic holds fairly steady around 7 GB on 
that
  machine and workload.

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


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

[Kernel-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop

2024-01-18 Thread saber716rus

we found a solution for my problem together with Marian Postevca. He made a 
patch, and there is also an alsa regression. A temporary solution is described 
here.
https://github.com/codepayne/linux-sound-huawei/issues/26#issuecomment-1837502247

** Bug watch added: github.com/codepayne/linux-sound-huawei/issues #28
   https://github.com/codepayne/linux-sound-huawei/issues/28

** Changed in: linux
   Importance: High => Unknown

** Changed in: linux
   Status: Confirmed => Unknown

** Changed in: linux
 Remote watch: Linux Kernel Bug Tracker #215119 => 
github.com/codepayne/linux-sound-huawei/issues #28

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

Title:
  dummy sound on huawei mate d15 laptop

Status in Linux:
  Unknown
Status in alsa-driver package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I tried different options, but I couldn't raise the sound.
  saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release
  NAME="Green Linux"
  VERSION="21.2 (Victoria)"
  ID=linuxmint
  ID_LIKE="ubuntu debian"
  PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)"
  VERSION_ID="21"
  HOME_URL="https://greenlinux.ru/";
  SUPPORT_URL="https://forum.linuxmint.su/";
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/";
  PRIVACY_POLICY_URL="https://greenlinux.ru/";
  VERSION_CODENAME=victoria
  UBUNTU_CODENAME=jammy
  saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 
   0 [Generic]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xd03c irq 80
   1 [acp]: acp - acp
HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2
  saber716rus@saber716rus-BOM-WXX9 ~>

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


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

[Kernel-packages] [Bug 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Mantic)
   Status: New => Won't Fix

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

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

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

Title:
  DP connection swap to break eDP behavior on AMD 7735U

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Won't Fix
Status in linux-firmware source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  Some OEM platforms swap DP connections on the Rembrandt-R, which
  causes improper eDP behavior. AMD experimented with reproducing at CRB
  level to come out with a solution

  - Fn key failed to control brightness
  - eDP remains black screen during S0i3 cycle

  Patch:
  
https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749

  DMCUB FW:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8

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


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

[Kernel-packages] [Bug 2049697] Re: [i915] GPU not being detected when I try to run any game

2024-01-18 Thread Justin Klassen

** Attachment added: "glfxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2049697/+attachment/5740491/+files/glfxinfo.txt

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

Title:
  [i915] GPU not being detected when I try to run any game

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

Bug description:
  I ran ran apport-bug xorg and it took me here. Trying to figure out an
  issue where any time I open a game, it crashes and gives the error
  message "GPU not detected". From everything I've tried it seems like
  the computer has no problem detecting the GPU and it seems to be
  working fine, but games are still not working. Any help is
  appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 18:34:19 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:0122]
  InstallationDate: Installed on 2023-10-25 (84 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Apple Inc. iMac14,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 146.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031B6874CF7F642A
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,1
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-031B6874CF7F642A
  dmi.modalias: 
dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#:
  dmi.product.family: iMac
  dmi.product.name: iMac14,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U

** Description changed:

- Some OEM platforms swap DP connections on the Rembrandt-R, which causes
- improper eDP behavior. AMD experimented with reproducing at CRB level to
- come out with a solution
+ [Impact]
+ Some OEM platforms swap DP connections on the Rembrandt-R, which causes 
improper eDP behavior.  The following issues will occur in these designs:
  
  - Fn key failed to control brightness
  - eDP remains black screen during S0i3 cycle
+ 
+ AMD has fixed these issues, but it requires both a kernel patch and an
+ updated DMCUB microcode.
+ 
+ [Test Plan]
+ Validate brightness control works.
+ Validate that PSR works.
+ Validate that eDP works after suspend/resume.
+ Validate that external display works.
+ 
+ Run above test plan on Rembrandt or Rembrandt-R system with swapped DP
+ as well as one without swapped DP.
+ 
+ [Where problems can occur]
+ The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R 
systems.  Issues would occur specifically on these designs, which is why they 
should be tested.
+ 
+ [Other Info]
  
  Patch:
  
https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749
  
  DMCUB FW:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8

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

Title:
  DP connection swap to break eDP behavior on AMD 7735U

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Won't Fix
Status in linux-firmware source package in Mantic:
  New
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Some OEM platforms swap DP connections on the Rembrandt-R, which causes 
improper eDP behavior.  The following issues will occur in these designs:

  - Fn key failed to control brightness
  - eDP remains black screen during S0i3 cycle

  AMD has fixed these issues, but it requires both a kernel patch and an
  updated DMCUB microcode.

  [Test Plan]
  Validate brightness control works.
  Validate that PSR works.
  Validate that eDP works after suspend/resume.
  Validate that external display works.

  Run above test plan on Rembrandt or Rembrandt-R system with swapped DP
  as well as one without swapped DP.

  [Where problems can occur]
  The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R 
systems.  Issues would occur specifically on these designs, which is why they 
should be tested.

  [Other Info]

  Patch:
  
https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749

  DMCUB FW:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8

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


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

[Kernel-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop

2024-01-18 Thread Bug Watch Updater

** Changed in: linux
   Status: Unknown => New

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

Title:
  dummy sound on huawei mate d15 laptop

Status in Linux:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I tried different options, but I couldn't raise the sound.
  saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release
  NAME="Green Linux"
  VERSION="21.2 (Victoria)"
  ID=linuxmint
  ID_LIKE="ubuntu debian"
  PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)"
  VERSION_ID="21"
  HOME_URL="https://greenlinux.ru/";
  SUPPORT_URL="https://forum.linuxmint.su/";
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/";
  PRIVACY_POLICY_URL="https://greenlinux.ru/";
  VERSION_CODENAME=victoria
  UBUNTU_CODENAME=jammy
  saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 
   0 [Generic]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xd03c irq 80
   1 [acp]: acp - acp
HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2
  saber716rus@saber716rus-BOM-WXX9 ~>

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


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

[Kernel-packages] [Bug 2045573] Re: AMDGPU: cp queue preemption timeout

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

noble has 6.7 now, so this is essentially fixed.

Kuba, if you need this for mantic, open a task and submit it for
inclusion, thanks.

** Changed in: linux (Ubuntu)
   Status: New => 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/2045573

Title:
  AMDGPU: cp queue preemption timeout

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic

  Under load, GPU crashed resulting in a weird behavior. Screen froze,
  blinked a few times and the laptop suspended. After wakeup a normal
  login screen showed up but after logging in, it crashed to black
  screen with a message: " cp queue preemption timeout". Eventually I
  was able to log in to a clean session.

  Log attached

  X-HWE-Bug: Bug #2047389

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


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

[Kernel-packages] [Bug 2045573] Re: AMDGPU: cp queue preemption timeout

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

hah, should probably refresh old tabs before posting on them

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

Title:
  AMDGPU: cp queue preemption timeout

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic

  Under load, GPU crashed resulting in a weird behavior. Screen froze,
  blinked a few times and the laptop suspended. After wakeup a normal
  login screen showed up but after logging in, it crashed to black
  screen with a message: " cp queue preemption timeout". Eventually I
  was able to log in to a clean session.

  Log attached

  X-HWE-Bug: Bug #2047389

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


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

[Kernel-packages] [Bug 2047389] Re: Fix AMDGPU crash on 6.5 kernel

** Changed in: linux (Ubuntu Noble)
   Status: Invalid => Fix Released

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

Title:
  Fix AMDGPU crash on 6.5 kernel

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  AMD GPU crash with a message: " cp queue preemption timeout".

  [Fix]
  Disable MCBP(mid command buffer preemption) by default as old Mesa
  hangs with it.

  [Test]
  Tested on hardware, play web video for more than 1 hour OK.

  [Where problems could occur]
  It may break AMD GPU.

  This issue is only reproduced on v6.5+ kernel versions and fixes in
  v6.6, so SRU for oem-6.5, mantic.

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


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

[Kernel-packages] [Bug 2036737] Re: Enable dynamic boost control in ccp kernel driver

** Changed in: linux (Ubuntu)
   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/2036737

Title:
  Enable dynamic boost control in ccp kernel driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Triaged

Bug description:
  [Impact]

  We need to backport dynamic boost control into OEM-6.5 kernel. This
  request is to backport the ccp changes.

  Here are the commits necessary to backport to OEM-6.5 kernel from
  kernel 6.6:

  b58276372182 crypto: ccp - Rename macro for security attributes
  2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
  e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
  b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
  c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost 
control
  d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost 
control
  e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters

  Here are the commits necessary to backport to OEM-6.5 kernel from
  kernel 6.7:

  53f7f779f45c crypto: ccp - Get a free page to use while fetching
  initial nonce

  [Test case]

  WIP

  [Regression potential]

  WIP

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


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

[Kernel-packages] [Bug 2039167] Re: I get this message "array-index-out-of-bounds" every time I turn on my laptop since I upgraded from 23.04. to 23.10. (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwm

2024-01-18 Thread Bruno Maderni

Happens to me as well on 22.04.3 with 6.5.0-14-generic.

6.2 works fine.

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

Title:
  I get this message "array-index-out-of-bounds"  every time I turn on
  my laptop since I upgraded from 23.04. to 23.10.
  (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
  index 1 is out of range for type 'UCHAR [1]'

  My firmware version is X515DAP.311.
  OS type 64-bit.
  GNOME version 45.0.
  Kernel version Linux 6.5.0-9-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zoran  2329 F wireplumber
   /dev/snd/controlC0:  zoran  2329 F wireplumber
   /dev/snd/seq:zoran  2316 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 13:42:16 2023
  InstallationDate: Installed on 2023-09-21 (21 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X515DAP.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515DAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515DAP_M515DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 2049787] [NEW] igb module crashing server

Public bug reported:

Description:Ubuntu 20.04.6 LTS
Release:20.04

linux-image-generic:
  Installed: 5.4.0.169.167
  Candidate: 5.4.0.169.167

A server has started to crash with logs that suggest the igb module is the 
reason.  Investigating the logs of the server showed the issue started with 
kernel
linux-image-5.4.0-166-generic

Because of the timing and the log messages this patch is suspected as the cause
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=Ubuntu-5.4.0-166.183&id=64285e660b7ab4614b44b19d062944be1c1971de

The crashes are inconsistent.  They appear to be triggered by a hardware
error which is unexpected.  The logs show the hardware error has been
happening for a while but only results in a crash with newer kernels.

The hardware is a quad-port NIC
Ethernet controller: Intel Corporation I350 Gigabit Network Connection



Up through kernel 
5.4.0-165-generic
the kernel logs include the following error and does *not* result in a crash

Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Multiple 
Uncorrected (Non-Fatal) error received: :04:00.3
Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Device 
recovery successful
Nov 01 07:13:41 ksq-a-mon-p13 kernel: igb :04:00.2 enp4s0f2: igb: enp4s0f2 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Nov 01 07:13:41 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837221.513:31): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.2/net/enp4s0f2/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
 fsuid=0 ouid=0
Nov 01 07:13:42 ksq-a-mon-p13 kernel: igb :04:00.3 enp4s0f3: igb: enp4s0f3 
NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Nov 01 07:13:42 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837222.301:32): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.3/net/enp4s0f3/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
 fsuid=0 ouid=0



Starting with kernel
5.4.0-166-generic
the kernel logs include the following and the server crashes

Dec 27 09:26:55 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Uncorrected 
(Non-Fatal) error received: :04:00.3
Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.0: Non-correctable 
non-fatal error reported.
Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.1: Non-correctable 
non-fatal error reported.
Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.2: Non-correctable 
non-fatal error reported.
Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: Non-correctable 
non-fatal error reported.
Dec 27 09:26:55 ksq-a-mon-p13 kernel: [ cut here ]
Dec 27 09:26:55 ksq-a-mon-p13 kernel: kernel BUG at 
include/linux/netdevice.h:525!
Dec 27 09:26:55 ksq-a-mon-p13 kernel: invalid opcode:  [#1] SMP PTI
Dec 27 09:26:55 ksq-a-mon-p13 kernel: CPU: 4 PID: 131 Comm: irq/26-aerdrv Not 
tainted 5.4.0-169-generic #187-Ubuntu
Dec 27 09:26:55 ksq-a-mon-p13 kernel: Hardware name: Supermicro 
SYS-5018A-FTN4/A1SRi, BIOS 2.1 01/18/2018
Dec 27 09:26:55 ksq-a-mon-p13 kernel: RIP: 0010:igb_up+0x51/0x160 [igb]
Dec 27 09:26:55 ksq-a-mon-p13 kernel: Code: d2 eb 16 f0 80 60 60 fe f0 80 60 60 
f7 48 83 c2 01 39 93 14 02 00 00 76 13 48 8b 84 d3 08 0f 00 00 48 8b 48 60 83 
e1 01 75 d9 <0f> 0b f6 83 11 02 00 00 20 0f 85 c0 00 00 00 48 8b bb 08 0f 00 00
Dec 27 09:26:55 ksq-a-mon-p13 kernel: RSP: 0018:ab48c02d7ce8 EFLAGS: 
00010246
Dec 27 09:26:55 ksq-a-mon-p13 kernel: RAX: 9489f40be000 RBX: 
9489e9d7c8c0 RCX: 
Dec 27 09:26:55 ksq-a-mon-p13 kernel: RDX:  RSI: 
0008 RDI: 9489e94b0b00
Dec 27 09:26:55 ksq-a-mon-p13 kernel: RBP: ab48c02d7cf8 R08: 
03d1 R09: ab48c08f5000
Dec 27 09:26:55 ksq-a-mon-p13 kernel: R10: 0168 R11: 
9489f7b2eba0 R12: 9489e9d7c000
Dec 27 09:26:55 ksq-a-mon-p13 kernel: R13: 9489e9d7c8c0 R14: 
9489f5e1d000 R15: 9489f5e81000
Dec 27 09:26:55 ksq-a-mon-p13 kernel: FS:  () 
GS:9489f7b0() knlGS:
Dec 27 09:26:55 ksq-a-mon-p13 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
D

[Kernel-packages] [Bug 2049787] Re: igb module crashing server

** Attachment added: "crashdump dmesg file"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049787/+attachment/5740528/+files/dmesg.202401130941

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

Title:
  igb module crashing server

Status in linux package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.6 LTS
  Release:20.04

  linux-image-generic:
Installed: 5.4.0.169.167
Candidate: 5.4.0.169.167

  A server has started to crash with logs that suggest the igb module is the 
reason.  Investigating the logs of the server showed the issue started with 
kernel
  linux-image-5.4.0-166-generic

  Because of the timing and the log messages this patch is suspected as the 
cause
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=Ubuntu-5.4.0-166.183&id=64285e660b7ab4614b44b19d062944be1c1971de

  The crashes are inconsistent.  They appear to be triggered by a
  hardware error which is unexpected.  The logs show the hardware error
  has been happening for a while but only results in a crash with newer
  kernels.

  The hardware is a quad-port NIC
  Ethernet controller: Intel Corporation I350 Gigabit Network Connection

  
  
  Up through kernel 
  5.4.0-165-generic
  the kernel logs include the following error and does *not* result in a crash

  Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Multiple 
Uncorrected (Non-Fatal) error received: :04:00.3
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Device 
recovery successful
  Nov 01 07:13:41 ksq-a-mon-p13 kernel: igb :04:00.2 enp4s0f2: igb: 
enp4s0f2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Nov 01 07:13:41 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837221.513:31): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.2/net/enp4s0f2/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
   fsuid=0 ouid=0
  Nov 01 07:13:42 ksq-a-mon-p13 kernel: igb :04:00.3 enp4s0f3: igb: 
enp4s0f3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Nov 01 07:13:42 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837222.301:32): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.3/net/enp4s0f3/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
   fsuid=0 ouid=0

  
  
  Starting with kernel
  5.4.0-166-generic
  the kernel logs include the following and the server crashes

  Dec 27 09:26:55 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Uncorrected 
(Non-Fatal) error received: :04:00.3
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.0: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.1: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.2: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: [ cut here ]
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: kernel BUG at 
include/linux/netdevice.h:525!
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: invalid opcode:  [#1] SMP PTI
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: CPU: 4 PID: 131 Comm: irq/26-aerdrv Not 
tainted 5.4.0-169-generic #187-Ubuntu
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: Hardware name: Supermicro 
SYS-5018A-FTN4/A1SRi, BIOS 2.1 01/18/2018
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RIP: 0010:igb_up+0x51/0x160 [igb]
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: Code: d2 eb 16 f0 80 60 60 fe f0 80 60 
60 f7 48 83 c2 01 39 93 14 02 00 00 76 13 48 8b 84 d3 08 0f 00 00 48 8b 48 60 
83 e1 01 75 d9 <0f> 0b f6 83 11 02 00 00 20 0f 85 c0 00 00 00 48 8b bb 08 0f 00 
00
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RSP: 0018:ab48c02d7ce8 EFLAGS: 
00010246
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RAX: 9489f40be000 RBX: 
9489e9d7c8c0 RCX: 
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RDX:  RSI: 
0008 RDI: 9489e94b0b00
  Dec 27 09:26:

[Kernel-packages] [Bug 2049787] Re: igb module crashing server

** Attachment added: "crashdump dump file"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049787/+attachment/5740529/+files/dump.202401130941

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

Title:
  igb module crashing server

Status in linux package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.6 LTS
  Release:20.04

  linux-image-generic:
Installed: 5.4.0.169.167
Candidate: 5.4.0.169.167

  A server has started to crash with logs that suggest the igb module is the 
reason.  Investigating the logs of the server showed the issue started with 
kernel
  linux-image-5.4.0-166-generic

  Because of the timing and the log messages this patch is suspected as the 
cause
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=Ubuntu-5.4.0-166.183&id=64285e660b7ab4614b44b19d062944be1c1971de

  The crashes are inconsistent.  They appear to be triggered by a
  hardware error which is unexpected.  The logs show the hardware error
  has been happening for a while but only results in a crash with newer
  kernels.

  The hardware is a quad-port NIC
  Ethernet controller: Intel Corporation I350 Gigabit Network Connection

  
  
  Up through kernel 
  5.4.0-165-generic
  the kernel logs include the following error and does *not* result in a crash

  Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Multiple 
Uncorrected (Non-Fatal) error received: :04:00.3
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Device 
recovery successful
  Nov 01 07:13:41 ksq-a-mon-p13 kernel: igb :04:00.2 enp4s0f2: igb: 
enp4s0f2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Nov 01 07:13:41 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837221.513:31): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.2/net/enp4s0f2/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
   fsuid=0 ouid=0
  Nov 01 07:13:42 ksq-a-mon-p13 kernel: igb :04:00.3 enp4s0f3: igb: 
enp4s0f3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Nov 01 07:13:42 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837222.301:32): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.3/net/enp4s0f3/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
   fsuid=0 ouid=0

  
  
  Starting with kernel
  5.4.0-166-generic
  the kernel logs include the following and the server crashes

  Dec 27 09:26:55 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Uncorrected 
(Non-Fatal) error received: :04:00.3
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.0: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.1: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.2: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: [ cut here ]
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: kernel BUG at 
include/linux/netdevice.h:525!
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: invalid opcode:  [#1] SMP PTI
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: CPU: 4 PID: 131 Comm: irq/26-aerdrv Not 
tainted 5.4.0-169-generic #187-Ubuntu
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: Hardware name: Supermicro 
SYS-5018A-FTN4/A1SRi, BIOS 2.1 01/18/2018
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RIP: 0010:igb_up+0x51/0x160 [igb]
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: Code: d2 eb 16 f0 80 60 60 fe f0 80 60 
60 f7 48 83 c2 01 39 93 14 02 00 00 76 13 48 8b 84 d3 08 0f 00 00 48 8b 48 60 
83 e1 01 75 d9 <0f> 0b f6 83 11 02 00 00 20 0f 85 c0 00 00 00 48 8b bb 08 0f 00 
00
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RSP: 0018:ab48c02d7ce8 EFLAGS: 
00010246
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RAX: 9489f40be000 RBX: 
9489e9d7c8c0 RCX: 
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RDX:  RSI: 
0008 RDI: 9489e94b0b00
  Dec 27 09:26:55

[Kernel-packages] [Bug 2049787] Re: igb module crashing server

** Attachment added: "crashdump crash file"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049787/+attachment/5740530/+files/linux-image-5.4.0-169-generic-202401130941.crash

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

Title:
  igb module crashing server

Status in linux package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04.6 LTS
  Release:20.04

  linux-image-generic:
Installed: 5.4.0.169.167
Candidate: 5.4.0.169.167

  A server has started to crash with logs that suggest the igb module is the 
reason.  Investigating the logs of the server showed the issue started with 
kernel
  linux-image-5.4.0-166-generic

  Because of the timing and the log messages this patch is suspected as the 
cause
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=Ubuntu-5.4.0-166.183&id=64285e660b7ab4614b44b19d062944be1c1971de

  The crashes are inconsistent.  They appear to be triggered by a
  hardware error which is unexpected.  The logs show the hardware error
  has been happening for a while but only results in a crash with newer
  kernels.

  The hardware is a quad-port NIC
  Ethernet controller: Intel Corporation I350 Gigabit Network Connection

  
  
  Up through kernel 
  5.4.0-165-generic
  the kernel logs include the following error and does *not* result in a crash

  Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Multiple 
Uncorrected (Non-Fatal) error received: :04:00.3
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
  Nov 01 07:13:38 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Device 
recovery successful
  Nov 01 07:13:41 ksq-a-mon-p13 kernel: igb :04:00.2 enp4s0f2: igb: 
enp4s0f2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Nov 01 07:13:41 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837221.513:31): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.2/net/enp4s0f2/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
   fsuid=0 ouid=0
  Nov 01 07:13:42 ksq-a-mon-p13 kernel: igb :04:00.3 enp4s0f3: igb: 
enp4s0f3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Nov 01 07:13:42 ksq-a-mon-p13 kernel: audit: type=1400 
audit(1698837222.301:32): apparmor="ALLOWED" operation="open" 
profile="/usr/sbin/sssd" 
name="/sys/devices/pci:00/:00:03.0/:04:00.3/net/enp4s0f3/type" 
pid=514 comm="sssd" requested_mask="r" denied_mask="r"
   fsuid=0 ouid=0

  
  
  Starting with kernel
  5.4.0-166-generic
  the kernel logs include the following and the server crashes

  Dec 27 09:26:55 ksq-a-mon-p13 kernel: pcieport :00:03.0: AER: Uncorrected 
(Non-Fatal) error received: :04:00.3
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER: PCIe Bus Error: 
severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:   device 
[8086:1521] error status/mask=4000/
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: AER:[14] CmpltTO
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.0: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.1: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.2: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: igb :04:00.3: Non-correctable 
non-fatal error reported.
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: [ cut here ]
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: kernel BUG at 
include/linux/netdevice.h:525!
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: invalid opcode:  [#1] SMP PTI
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: CPU: 4 PID: 131 Comm: irq/26-aerdrv Not 
tainted 5.4.0-169-generic #187-Ubuntu
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: Hardware name: Supermicro 
SYS-5018A-FTN4/A1SRi, BIOS 2.1 01/18/2018
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RIP: 0010:igb_up+0x51/0x160 [igb]
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: Code: d2 eb 16 f0 80 60 60 fe f0 80 60 
60 f7 48 83 c2 01 39 93 14 02 00 00 76 13 48 8b 84 d3 08 0f 00 00 48 8b 48 60 
83 e1 01 75 d9 <0f> 0b f6 83 11 02 00 00 20 0f 85 c0 00 00 00 48 8b bb 08 0f 00 
00
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RSP: 0018:ab48c02d7ce8 EFLAGS: 
00010246
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RAX: 9489f40be000 RBX: 
9489e9d7c8c0 RCX: 
  Dec 27 09:26:55 ksq-a-mon-p13 kernel: RDX:  RSI: 
0008 RDI: ff

[Kernel-packages] [Bug 2049768] [NEW] my computer doesnt start

You have been subscribed to a public bug:

This shows up on the black screen:

UBSAN:
 array-index-out-of-bounds in 
/build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 
: 28 index 15 is out of range for type 'u8 [1]

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


** Tags: bot-comment
-- 
my computer doesnt start
https://bugs.launchpad.net/bugs/2049768
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2049768] Re: my computer doesnt start

2024-01-18 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

( this bug report can be turned into QUESTION which is geared at
support; but as a bug report too little detail currently exists given
apport tools were not used in filing )

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 2049768

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  my computer doesnt start

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This shows up on the black screen:

  UBSAN:
   array-index-out-of-bounds in 
/build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 
: 28 index 15 is out of range for type 'u8 [1]

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


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

[Kernel-packages] [Bug 2049697] Re: [i915] GPU not being detected when I try to run any game

2024-01-18 Thread Daniel van Vugt

Thanks. It looks like the GPU driver is working correctly there. Next
please try:

  sudo apt install glmark2
  glmark2

Does it render smoothly and display correct driver information in the
Terminal?


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

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

Title:
  [i915] GPU not being detected when I try to run any game

Status in Ubuntu:
  Incomplete

Bug description:
  I ran ran apport-bug xorg and it took me here. Trying to figure out an
  issue where any time I open a game, it crashes and gives the error
  message "GPU not detected". From everything I've tried it seems like
  the computer has no problem detecting the GPU and it seems to be
  working fine, but games are still not working. Any help is
  appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 18:34:19 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.2.0-35-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:0d22] (rev 08) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Device [106b:0122]
  InstallationDate: Installed on 2023-10-25 (84 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Apple Inc. iMac14,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=773b635d-a617-4aa4-8333-273b3ed7b502 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 146.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-031B6874CF7F642A
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,1
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-031B6874CF7F642A
  dmi.modalias: 
dmi:bvnAppleInc.:bvr146.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pniMac14,1:pvr1.0:rvnAppleInc.:rnMac-031B6874CF7F642A:rvriMac14,1:cvnAppleInc.:ct13:cvrMac-031B6874CF7F642A:skuSystemSKU#:
  dmi.product.family: iMac
  dmi.product.name: iMac14,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2049327] Re: `alsactl init` unable to initialze audio device on G700

2024-01-18 Thread ethan.hsieh

** Tags added: oem-priority originate-from-2047345

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

Title:
`alsactl init` unable to initialze audio device on G700

Status in alsa-ucm-conf package in Ubuntu:
Fix Released

Bug description:
[Impact]
This bug cause "alsactl init" command unable to initialize mt8390-evk
correctly and print these error message:

```
ceqa@ubuntu:/home/ceqa$ alsactl init
alsa-lib main.c:761:(execute_sequence) unable to execute cset
'name='DP_OUT_MUX' Disconnect'
alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence
Found hardware: "mt8390-evk" "" "" "" ""
Hardware is initialized using a generic method
```

Thus, the audio devices on MediaTek G700 do not work.

This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'.

[ Test Plan ]
Reproduce:
1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device
2. Run `alsactl init` on MediaTek G700 device
3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX'
Disconnect'" and audio devices do not work.

Verify:
By applying this patch, alsactl does not print this error message and audio
devices work.

[Where problems could occur]
This patch fix the typo in ucm files, and it affects the device init process
on Mediatek Genio boards.

[ Other Info ]
There is a typo in
'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'.

The name of the flag that controls the audio output of the DP port is
not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'.

MediaTek fix this issue in the PR in upstream:

https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079

mt8390-evk (G700) Pull Request: (Still under review)
https://github.com/alsa-project/alsa-ucm-conf/pull/321

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327/+subscriptions

--
Mailing list: https://launchpad.net/~kernel-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

2024-01-18 Thread Martin Pitt

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

** Also affects: linux-signed (Ubuntu Jammy)
   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/2049689

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

Status in linux package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-signed source package in Jammy:
  New

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 2039720] Re: Intel IDPF support

2024-01-18 Thread John Cabaj

** No longer affects: linux-gcp (Ubuntu Focal)

** No longer affects: linux-gcp (Ubuntu Lunar)

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

Title:
  Intel IDPF support

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  New
Status in linux-gcp source package in Mantic:
  New

Bug description:
  [Impact]

  * Request from Google to include new Intel IDPF driver support

  [Fix]

  * Cherry pick commits from net-next,
  b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96

  [Test Case]

  * Compile tested
  * Boot tested
  * To be tested by Google

  [Where things could go wrong]

  * Low chance of regression, new driver is isolated and will be tested
  by Google

  [Other Info]

  * SF #00368902

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


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

[Kernel-packages] [Bug 2039720] Re: Intel IDPF support

2024-01-18 Thread John Cabaj

** Description changed:

  [Impact]
  
  * Request from Google to include new Intel IDPF driver support
  
  [Fix]
  
- * Cherry pick commits from net-next,
- b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96
+ * Mantic - 24 clean cherry-picks, 1 backport from upstream
+ * Jammy - 11 clean cherry-picks, 7 backports from upstream
  
  [Test Case]
  
  * Compile tested
  * Boot tested
- * To be tested by Google
+ * Tested internally and by Google using neper 
(https://github.com/google/neper)
+ * Networking is functional and throughput is as expected
  
  [Where things could go wrong]
  
- * Low chance of regression, new driver is isolated and will be tested by
- Google
+ * Low chance of regression, changes have been upstream since 6.6 kernel
+ * Bulk of changes in IDPF driver
+ * Other changes to network drivers largely adding #include directives
  
  [Other Info]
  
  * SF #00368902

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

Title:
  Intel IDPF support

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  New
Status in linux-gcp source package in Mantic:
  New

Bug description:
  [Impact]

  * Request from Google to include new Intel IDPF driver support

  [Fix]

  * Mantic - 24 clean cherry-picks, 1 backport from upstream
  * Jammy - 11 clean cherry-picks, 7 backports from upstream

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested internally and by Google using neper 
(https://github.com/google/neper)
  * Networking is functional and throughput is as expected

  [Where things could go wrong]

  * Low chance of regression, changes have been upstream since 6.6 kernel
  * Bulk of changes in IDPF driver
  * Other changes to network drivers largely adding #include directives

  [Other Info]

  * SF #00368902

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


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

[Kernel-packages] [Bug 2049352] Re: Package BlueZ 5.72 for Noble

This bug was fixed in the package bluez - 5.72-0ubuntu1

---
bluez (5.72-0ubuntu1) noble; urgency=medium

  * New upstream release 5.72 (LP: #2049352):
- Fix issue with BAP and handling stream IO linking.
- Fix issue with BAP and setup of multiple streams per endpoint.
- Fix issue with AVDTP and potential incorrect transaction label.
- Fix issue with A2DP and handling crash on suspend.
- Fix issue with GATT database and an invalid pointer.
- Add support for AICS service.
  * Add bluetoothctl.1 man page to bluez package.

 -- Daniel van Vugt   Tue, 16 Jan 2024
15:15:23 +0800

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

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

Title:
  Package BlueZ 5.72 for Noble

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  ver 5.72:
  Fix issue with BAP and handling stream IO linking.
  Fix issue with BAP and setup of multiple streams per endpoint.
  Fix issue with AVDTP and potential incorrect transaction label.
  Fix issue with A2DP and handling crash on suspend.
  Fix issue with GATT database and an invalid pointer.
  Add support for AICS service.

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72

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


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

[Kernel-packages] [Bug 2039720] Re: Intel IDPF support

2024-01-18 Thread John Cabaj

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

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

** Changed in: linux-gcp (Ubuntu Jammy)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

** Changed in: linux-gcp (Ubuntu Mantic)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

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

Title:
  Intel IDPF support

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  In Progress
Status in linux-gcp source package in Mantic:
  In Progress

Bug description:
  [Impact]

  * Request from Google to include new Intel IDPF driver support

  [Fix]

  * Mantic - 24 clean cherry-picks, 1 backport from upstream
  * Jammy - 11 clean cherry-picks, 7 backports from upstream

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested internally and by Google using neper 
(https://github.com/google/neper)
  * Networking is functional and throughput is as expected

  [Where things could go wrong]

  * Low chance of regression, changes have been upstream since 6.6 kernel
  * Bulk of changes in IDPF driver
  * Other changes to network drivers largely adding #include directives

  [Other Info]

  * SF #00368902

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


-- 
Mailing list: https://launchpad.net/~kernel-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

2024-01-18 Thread Martin Pitt

** Tags added: jammy regression-release

** Tags removed: regression-release
** Tags added: regression-update

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed 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:
  New
Status in linux-signed package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-signed source package in Jammy:
  New

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 2049838] [NEW] Mute/mic LEDs no function on HP ZBook

2024-01-18 Thread Leo Lin

Public bug reported:

[Impact]
The mute LEDS are not work properly on some newer HP ZBooks.

[Fix]
It needs the specific quirk for the hardware layout. Add it accordingly. 

[Test]
Install the patched kernel and click the mute button. Confirm that the LED on 
the mute key turns on an off according to mute status.

[Where problems could occur]
This quirk only works if design of the board w.r.t. the same subsystem ID is 
unchanged. Otherwise the quirk will not work (the mute LEDs won't function 
normally).

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

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

Title:
  Mute/mic LEDs no function on HP ZBook

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  The mute LEDS are not work properly on some newer HP ZBooks.

  [Fix]
  It needs the specific quirk for the hardware layout. Add it accordingly. 

  [Test]
  Install the patched kernel and click the mute button. Confirm that the LED on 
the mute key turns on an off according to mute status.

  [Where problems could occur]
  This quirk only works if design of the board w.r.t. the same subsystem ID is 
unchanged. Otherwise the quirk will not work (the mute LEDs won't function 
normally).

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


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

[Kernel-packages] [Bug 2049838] Re: Mute/mic LEDs no function on HP ZBook

2024-01-18 Thread Leo Lin

** Tags added: oem-priority originate-from-2046342 stella

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

Title:
  Mute/mic LEDs no function on HP ZBook

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  [Impact]
  The mute LEDS are not work properly on some newer HP ZBooks.

  [Fix]
  It needs the specific quirk for the hardware layout. Add it accordingly. 

  [Test]
  Install the patched kernel and click the mute button. Confirm that the LED on 
the mute key turns on an off according to mute status.

  [Where problems could occur]
  This quirk only works if design of the board w.r.t. the same subsystem ID is 
unchanged. Otherwise the quirk will not work (the mute LEDs won't function 
normally).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2049838/+subscriptions


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

[Kernel-packages] [Bug 2049838] Re: Mute/mic LEDs no function on HP ZBook

2024-01-18 Thread Andy Chi

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

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

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

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

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

** Changed in: linux-oem-6.5 (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Leo Lin (0xff07)

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

Title:
  Mute/mic LEDs no function on HP ZBook

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  [Impact]
  The mute LEDS are not work properly on some newer HP ZBooks.

  [Fix]
  It needs the specific quirk for the hardware layout. Add it accordingly. 

  [Test]
  Install the patched kernel and click the mute button. Confirm that the LED on 
the mute key turns on an off according to mute status.

  [Where problems could occur]
  This quirk only works if design of the board w.r.t. the same subsystem ID is 
unchanged. Otherwise the quirk will not work (the mute LEDs won't function 
normally).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2049838/+subscriptions


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

[Kernel-packages] [Bug 2049733] Re: Dynamically determine acpi_handle_list size

2024-01-18 Thread Ivan Hu

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

Title:
  Dynamically determine acpi_handle_list size

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

Bug description:
  [Impact]
  ACPI handle list will be dynamic allocated without default fixed size.

  [Fix]
  Currently the ACPI_MAX_HANDLES is defined fix to 10, and it is not enough for 
some platforms that called ACPI _PSL method to get passive cooling device 
objects. then will get the error message "Invalid passive threshold", this 
patch change the fixed size with the dynamic handle list size which fixes the 
handle reference error.

  [Test Case]
  check the dmesg to see if there is the error message "Invalid passive 
threshold"

  [Where problems could occur]
  Only change the fixed size with the dynamic handle list size. Risk of 
regression is low.

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


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

[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops