date:20221024

This bug is awaiting verification that the linux-bluefield/5.4.0-1050.56
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

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

Title:
  i2c-mlxbf.c: Sync up driver with upstreaming

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

Bug description:
  SRU Justification:

  [Impact]

  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4)
  and Jammy (5.15) and cherry-pick all changes from linux-next master.

  IMPORTANT NOTE: The new linux i2c support for BF3 also REQUIRES
  upgrading the UEFI firmware version. For BF1 and BF2 however, this
  driver should be backward compatible with older UEFI versions.

  [Fix]

  * There is a total of 17 commits: 8 reverts, 8 cherry-picks from
  linux-next and one internal "UBUNTU: SAUCE:" to ad the driver version.
  Following is the list of commits cherry-picked.

  * i2c: mlxbf: incorrect base address passed during io write
  From 


  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
  From 


  * i2c: mlxbf: remove IRQF_ONESHOT
  From 


  * i2c: mlxbf: Fix frequency calculation
  From 


  * i2c: mlxbf: support lock mechanism
  From 


  * i2c: mlxbf: add multi slave functionality
  From 


  * i2c: mlxbf: support BlueField-3 SoC
  From 


  * i2c: mlxbf: remove device tree support
  From 


  * Also add the i2c driver version to keep track of the changes
  internally.

  [Test Case]

  * Check that the i2c driver loads without errors on BF1 and BF2 (dmesg, and 
check i2c1 sysfs is created)
  * Check that the i2c module can be removed and reloaded without errors.
  * Check that IPMB services work successfully on systems with BMC. This is the 
best way to test the i2c driver. Run ipmitool command from the BF: ipmitool mc 
info
  * Run ipmitool from the BMC as well: ipmitool -I ipmb mc info
  * This driver should be backward compatible
  * Make sure this driver is backward compatible with older UEFI version (only 
applicable for BF1 and BF2)
  * Make sure this driver works for BF1, BF2 and BF3 with the latest UEFI 
version.

  [Regression Potential]

  * The i2c driver could fail to load because the UEFI firmware hasn't been 
upgraded
  * The i2c driver would fail to load due to a bug
  * IPMB code which utilises the i2c driver fails to work (ipmitool commands)

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


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

[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

This bug is awaiting verification that the linux/5.4.0-132.148 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following ip parameters

  $ sudo ip a a 192.168.1.7/24 dev enp7s0
  $ sudo ip link set up dev enp7s0
  $ sudo ip link set mtu 9000

[Kernel-packages] [Bug 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='

This bug is awaiting verification that the linux/5.4.0-132.148 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

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

Title:
  cgroup: all controllers mounted when using 'cgroup_no_v1='

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

Bug description:
  [Impact]

  When mounting a cgroup hierarchy with disabled controller in cgroup v1,
  all available controllers will be attached.
  For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then
  mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all
  enabled controllers will be attached except cpu.

  This exists since linux v5.1 and fixed in linux v5.11 with this commit:
  61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param()

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637

  [Test Case]

  root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic 
--initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat 
/proc/cmdline) cgroup_no_v1=net_prio,net_cls"
  root@dut-vm:~# systemctl kexec
  root@dut-vm:~# mount | grep cgroup
  tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
  cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma)

  
  => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio.
  Note that several reboots may be needed to reproduce the problem (it fails 
only when systemd tries to mount 'net_cls,net_prio' first, but the order is 
random).

  [Regression Potential]

  The patch is located in cgroup1_parse_param(), the potential
  regressions are low.

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


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

[Kernel-packages] [Bug 1994061] Re: Kinetic update: v5.19.8 upstream stable release

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

Title:
  Kinetic update: v5.19.8 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.8 upstream stable release
     from git://git.kernel.org/

  drm/msm/dp: make eDP panel as the first connected connector
  drm/msm/dsi: fix the inconsistent indenting
  drm/msm/dpu: populate wb or intf before reset_intf_cfg
  drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4
  drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
  drm/msm/dsi: Fix number of regulators for SDM660
  platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
  platform/x86: x86-android-tablets: Fix broken touchscreen on Chuwi Hi8 with 
Windows BIOS
  xsk: Fix corrupted packets for XDP_SHARED_UMEM
  drm/msm/gpu: Drop qos request if devm_devfreq_add_device() fails
  peci: aspeed: fix error check return value of platform_get_irq()
  iio: adc: mcp3911: make use of the sign bit
  skmsg: Fix wrong last sg check in sk_msg_recvmsg()
  bpf: Restrict bpf_sys_bpf to CAP_PERFMON
  ip_tunnel: Respect tunnel key's "flow_flags" in IP tunnels
  bpf, cgroup: Fix kernel BUG in purge_effective_progs
  drm/i915/gvt: Fix Comet Lake
  ieee802154/adf7242: defer destroy_workqueue call
  bpf: Fix a data-race around bpf_jit_limit.
  drm/i915/ttm: fix CCS handling
  drm/i915/display: avoid warnings when registering dual panel backlight
  ALSA: hda: intel-nhlt: Correct the handling of fmt_config flexible array
  wifi: cfg80211: debugfs: fix return type in ht40allow_map_read()
  xhci: Fix null pointer dereference in remove if xHC has only one roothub
  Revert "xhci: turn off port power in shutdown"
  bpf: Allow helpers to accept pointers with a fixed size
  bpf: Tidy up verifier check_func_arg()
  bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO
  Bluetooth: hci_event: Fix vendor (unknown) opcode status handling
  Bluetooth: hci_sync: Fix suspend performance regression
  Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt
  Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn
  net: sparx5: fix handling uneven length packets in manual extraction
  net: smsc911x: Stop and start PHY during suspend and resume
  openvswitch: fix memory leak at failed datapath creation
  nfp: flower: fix ingress police using matchall filter
  net: dsa: xrs700x: Use irqsave variant for u64 stats update
  net: sched: tbf: don't call qdisc_put() while holding tree lock
  net/sched: fix netdevice reference leaks in attach_default_qdiscs()
  net: phy: micrel: Make the GPIO to be non-exclusive
  net: lan966x: improve error handle in lan966x_fdma_rx_get_frame()
  ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler
  cachefiles: fix error return code in cachefiles_ondemand_copen()
  cachefiles: make on-demand request distribution fairer
  mlxbf_gige: compute MDIO period based on i1clk
  kcm: fix strp_init() order and cleanup
  sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb
  tcp: annotate data-race around challenge_timestamp
  Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb"
  net/smc: Remove redundant refcount increase
  soundwire: qcom: fix device status array range
  mm/slab_common: Deleting kobject in kmem_cache_destroy() without holding 
slab_mutex/cpu_hotplug_lock
  platform/mellanox: mlxreg-lc: Fix coverity warning
  platform/mellanox: mlxreg-lc: Fix locking issue
  serial: fsl_lpuart: RS485 RTS polariy is inverse
  tty: serial: atmel: Preserve previous USART mode if RS485 disabled
  staging: rtl8712: fix use after free bugs
  staging: r8188eu: Add Rosewill USB-N150 Nano to device tables
  staging: r8188eu: add firmware dependency
  Revert "powerpc: Remove unused FW_FEATURE_NATIVE references"
  powerpc: align syscall table for ppc32
  powerpc/rtas: Fix RTAS MSR[HV] handling for Cell
  vt: Clear selection before changing the font
  musb: fix USB_MUSB_TUSB6010 dependency
  tty: serial: lpuart: disable flow control while waiting for the transmit 
engine to complete
  Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
  iio: light: cm3605: Fix an error handling path in cm3605_probe()
  iio: ad7292: Prevent regulator double disable
  iio: adc: mcp3911: correct

[Kernel-packages] [Bug 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

This bug is awaiting verification that the linux/5.4.0-132.148 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

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

Title:
  fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu

  This is a new test case from bug 1988809

  Test failed with:
   Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh 
TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
     INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: fib_nexthop_nongw.sh
   # Object "nexthop" is unknown, try "ip help".
   # Error: either "to" is duplicate, or "nhid" is a garbage.
   # TEST: nexthop: get route with nexthop without gw[FAIL]
   # TEST: nexthop: ping through nexthop without gw  [FAIL]
   not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1

  --

  [Impact]

  When running kselftests on Bionic with a 5.4 kernel, it would
  fail because of no nexthop capability.

  [Fix]

  We query the ip command help to know whether it is implemented
  or not, and we skip or execute the test accordingly

  [Test Plan]

  Running the test script directly in Bionic will throw a Skip,
  while running it in Focal will throw the test result.

  [Where problems could ocurr]

  The regression potential for this is low.

  [Other Info]

  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990800/+subscriptions


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

[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

This bug is awaiting verification that the linux/5.4.0-132.148 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

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

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

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

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


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

[Kernel-packages] [Bug 1994068] Re: Kinetic update: v5.19.9 upstream stable release

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

Title:
  Kinetic update: v5.19.9 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.9 upstream stable release
     from git://git.kernel.org/

  efi: libstub: Disable struct randomization
  efi: capsule-loader: Fix use-after-free in efi_capsule_write
  wifi: mt76: mt7921e: fix crash in chip reset fail
  wifi: iwlegacy: 4965: corrected fix for potential off-by-one overflow in 
il4965_rs_fill_link_cmd()
  fs: only do a memory barrier for the first set_buffer_uptodate()
  soc: fsl: select FSL_GUTS driver for DPIO
  Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()"
  scsi: qla2xxx: Disable ATIO interrupt coalesce for quad port ISP27XX
  scsi: core: Allow the ALUA transitioning state enough time
  scsi: megaraid_sas: Fix double kfree()
  drm/gem: Fix GEM handle release errors
  drm/amdgpu: Move psp_xgmi_terminate call from amdgpu_xgmi_remove_device to 
psp_hw_fini
  drm/amdgpu: fix hive reference leak when adding xgmi device
  drm/amdgpu: Check num_gfx_rings for gfx v9_0 rb setup.
  drm/amdgpu: Remove the additional kfd pre reset call for sriov
  drm/radeon: add a force flush to delay work when radeon
  scsi: ufs: core: Reduce the power mode change timeout
  Revert "parisc: Show error if wrong 32/64-bit compiler is being used"
  parisc: ccio-dma: Handle kmalloc failure in ccio_init_resources()
  parisc: Add runtime check to prevent PA2.0 kernels on PA1.x machines
  UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_2457168
  arm64: errata: add detection for AMEVCNTR01 incrementing incorrectly
  netfilter: conntrack: work around exceeded receive window
  thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR
  cpufreq: check only freq_table in __resolve_freq()
  net/core/skbuff: Check the return value of skb_copy_bits()
  md: Flush workqueue md_rdev_misc_wq in md_alloc()
  fbdev: omapfb: Fix tests for platform_get_irq() failure
  fbdev: fbcon: Destroy mutex on freeing struct fb_info
  fbdev: chipsfb: Add missing pci_disable_device() in chipsfb_pci_init()
  x86/sev: Mark snp_abort() noreturn
  drm/amdgpu: add sdma instance check for gfx11 CGCG
  drm/amdgpu: mmVM_L2_CNTL3 register not initialized correctly
  ALSA: pcm: oss: Fix race at SNDCTL_DSP_SYNC
  ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc()
  ALSA: hda: Once again fix regression of page allocations with IOMMU
  ALSA: aloop: Fix random zeros in capture data when using jiffies timer
  ALSA: usb-audio: Clear fixed clock rate at closing EP
  ALSA: usb-audio: Fix an out-of-bounds bug in __snd_usb_parse_audio_interface()
  tracefs: Only clobber mode/uid/gid on remount if asked
  tracing: hold caller_addr to hardirq_{enable,disable}_ip
  tracing: Fix to check event_mutex is held while accessing trigger list
  btrfs: zoned: set pseudo max append zone limit in zone emulation mode
  btrfs: zoned: fix API misuse of zone finish waiting
  vfio/type1: Unpin zero pages
  kprobes: Prohibit probes in gate area
  perf: RISC-V: fix access beyond allocated array
  debugfs: add debugfs_lookup_and_remove()
  sched/debug: fix dentry leak in update_sched_domain_debugfs
  drm/amd/display: fix memory leak when using debugfs_lookup()
  driver core: fix driver_set_override() issue with empty strings
  nvmet: fix a use-after-free
  drm/i915/bios: Copy the whole MIPI sequence block
  drm/i915/slpc: Let's fix the PCODE min freq table setup for SLPC
  scsi: mpt3sas: Fix use-after-free warning
  scsi: lpfc: Add missing destroy_workqueue() in error path
  cgroup: Elide write-locking threadgroup_rwsem when updating csses on an empty 
subtree
  cgroup: Fix threadgroup_rwsem <-> cpus_read_lock() deadlock
  cifs: remove useless parameter 'is_fsctl' from SMB2_ioctl()
  smb3: missing inode locks in zero range
  spi: bitbang: Fix lsb-first Rx
  ASoC: cs42l42: Only report button state if there was a button interrupt
  Revert "soc: imx: imx8m-blk-ctrl: set power device name"
  arm64: dts: imx8mm-verdin: update CAN clock to 40MHz
  arm64: dts: imx8mm-verdin: use level interrupt for mcp251xfd
  ASoC: qcom: sm8250: add missing module owner
  regmap: spi: Reserve space for register address/padding
  arm64: dts:

[Kernel-packages] [Bug 1994070] Re: Kinetic update: v5.19.11 upstream stable release

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

Title:
  Kinetic update: v5.19.11 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.11 upstream stable release
     from git://git.kernel.org/

  of: fdt: fix off-by-one error in unflatten_dt_nodes()
  pinctrl: qcom: sc8180x: Fix gpio_wakeirq_map
  pinctrl: qcom: sc8180x: Fix wrong pin numbers
  pinctrl: rockchip: Enhance support for IRQ_TYPE_EDGE_BOTH
  pinctrl: sunxi: Fix name for A100 R_PIO
  SUNRPC: Fix call completion races with call_decode()
  NFSv4: Turn off open-by-filehandle and NFS re-export for NFSv4.0
  gpio: mpc8xxx: Fix support for IRQ_TYPE_LEVEL_LOW flow_type in mpc85xx
  NFSv4.2: Update mode bits after ALLOCATE and DEALLOCATE
  Revert "SUNRPC: Remove unreachable error condition"
  drm/panel-edp: Fix delays for Innolux N116BCA-EA1
  drm/meson: Correct OSD1 global alpha value
  drm/meson: Fix OSD1 RGB to YCbCr coefficient
  drm/rockchip: vop2: Fix eDP/HDMI sync polarities
  drm/i915/vdsc: Set VDSC PIC_HEIGHT before using for DP DSC
  drm/i915/guc: Don't update engine busyness stats too frequently
  drm/i915/guc: Cancel GuC engine busyness worker synchronously
  block: blk_queue_enter() / __bio_queue_enter() must return -EAGAIN for nowait
  parisc: ccio-dma: Add missing iounmap in error path in ccio_probe()
  of/device: Fix up of_dma_configure_id() stub
  io_uring/msg_ring: check file type before putting
  cifs: revalidate mapping when doing direct writes
  cifs: don't send down the destination address to sendmsg for a SOCK_STREAM
  cifs: always initialize struct msghdr smb_msg completely
  blk-lib: fix blkdev_issue_secure_erase
  parisc: Allow CONFIG_64BIT with ARCH=parisc
  tools/include/uapi: Fix  for parisc and xtensa
  drm/i915/gt: Fix perf limit reasons bit positions
  drm/i915: Set correct domains values at _i915_vma_move_to_active
  drm/amdgpu: make sure to init common IP before gmc
  drm/amdgpu: Don't enable LTR if not supported
  drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
  drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
  net: Find dst with sk's xfrm policy not ctl_sk
  dt-bindings: apple,aic: Fix required item "apple,fiq-index" in affinity 
description
  cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()
  ALSA: hda/sigmatel: Keep power up while beep is enabled
  ALSA: hda/sigmatel: Fix unused variable warning for beep power change
  Linux 5.19.11
  UBUNTU: Upstream stable to v5.19.11

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


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

[Kernel-packages] [Bug 1994069] Re: Kinetic update: v5.19.10 upstream stable release

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

Title:
  Kinetic update: v5.19.10 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.10 upstream stable release
     from git://git.kernel.org/

  iommu/vt-d: Fix kdump kernels boot failure with scalable mode
  net/mlx5: Introduce ifc bits for using software vhca id
  net/mlx5: Use software VHCA id when it's supported
  RDMA/mlx5: Rely on RoCE fw cap instead of devlink when setting profile
  RDMA/mlx5: Add a umr recovery flow
  RDMA/mlx5: Fix UMR cleanup on error flow of driver init
  ACPI: resource: skip IRQ override on AMD Zen platforms
  Input: goodix - add support for GT1158
  platform/surface: aggregator_registry: Add support for Surface Laptop Go 2
  drm/msm/rd: Fix FIFO-full deadlock
  peci: cpu: Fix use-after-free in adev_release()
  kvm: x86: mmu: Always flush TLBs when enabling dirty logging
  dt-bindings: iio: gyroscope: bosch,bmg160: correct number of pins
  HID: ishtp-hid-clientHID: ishtp-hid-client: Fix comment typo
  hid: intel-ish-hid: ishtp: Fix ishtp client sending disordered message
  Bluetooth: MGMT: Fix Get Device Flags
  tg3: Disable tg3 device on system reboot to avoid triggering AER
  r8152: add PID for the Lenovo OneLink+ Dock
  gpio: mockup: remove gpio debugfs when remove device
  ieee802154: cc2520: add rc code in cc2520_tx()
  Input: iforce - add support for Boeder Force Feedback Wheel
  drm/amdgpu: disable FRU access on special SIENNA CICHLID card
  drm/amd/pm: use vbios carried pptable for all SMU13.0.7 SKUs
  nvme-pci: add NVME_QUIRK_BOGUS_NID for Lexar NM610
  nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()
  drm/amd/amdgpu: skip ucode loading if ucode_size == 0
  net: dsa: hellcreek: Print warning only once
  perf/arm_pmu_platform: fix tests for platform_get_irq() failure
  platform/x86: acer-wmi: Acer Aspire One AOD270/Packard Bell Dot keymap fixes
  usb: storage: Add ASUS <0x0b05:0x1932> to IGNORE_UAS
  platform/x86: asus-wmi: Increase FAN_CURVE_BUF_LEN to 32
  LoongArch: Fix section mismatch due to acpi_os_ioremap()
  LoongArch: Fix arch_remove_memory() undefined build error
  gpio: 104-dio-48e: Make irq_chip immutable
  gpio: 104-idio-16: Make irq_chip immutable
  RDMA/irdma: Use s/g array in post send only when its valid
  Input: goodix - add compatible string for GT1158
  Linux 5.19.10
  UBUNTU: Upstream stable to v5.19.10

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


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

[Kernel-packages] [Bug 1994074] Re: Kinetic update: v5.19.12 upstream stable release

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

Title:
  Kinetic update: v5.19.12 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.12 upstream stable release
     from git://git.kernel.org/

  smb3: Move the flush out of smb2_copychunk_range() into its callers
  smb3: fix temporary data corruption in collapse range
  smb3: fix temporary data corruption in insert range
  usb: add quirks for Lenovo OneLink+ Dock
  usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
  smb3: use filemap_write_and_wait_range instead of filemap_write_and_wait
  Revert "usb: add quirks for Lenovo OneLink+ Dock"
  Revert "usb: gadget: udc-xilinx: replace memcpy with memcpy_toio"
  xfrm: fix XFRMA_LASTUSED comment
  block: remove QUEUE_FLAG_DEAD
  block: stop setting the nomerges flags in blk_cleanup_queue
  block: simplify disk shutdown
  scsi: core: Fix a use-after-free
  drivers/base: Fix unsigned comparison to -1 in CPUMAP_FILE_MAX_BYTES
  USB: core: Fix RST error in hub.c
  USB: serial: option: add Quectel BG95 0x0203 composition
  USB: serial: option: add Quectel RM520N
  ALSA: core: Fix double-free at snd_card_new()
  ALSA: hda/tegra: set depop delay for tegra
  ALSA: hda: Fix hang at HD-audio codec unbinding due to refcount saturation
  ALSA: hda: Fix Nvidia dp infoframe
  ALSA: hda: add Intel 5 Series / 3400 PCI DID
  ALSA: hda/realtek: Add quirk for Huawei WRT-WX9
  ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5570 laptop
  ALSA: hda/realtek: Re-arrange quirk table entries
  ALSA: hda/realtek: Add pincfg for ASUS G513 HP jack
  ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack
  ALSA: hda/realtek: Add quirk for ASUS GA503R laptop
  ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5530 laptop
  ALSA: hda/realtek: Add a quirk for HP OMEN 16 (8902) mute LED
  iommu/vt-d: Check correct capability for sagaw determination
  exfat: fix overflow for large capacity partition
  btrfs: fix hang during unmount when stopping block group reclaim worker
  btrfs: fix hang during unmount when stopping a space reclaim worker
  btrfs: zoned: wait for extent buffer IOs before finishing a zone
  libperf evlist: Fix polling of system-wide events
  media: flexcop-usb: fix endpoint type check
  usb: dwc3: core: leave default DMA if the controller does not support 64-bit 
DMA
  thunderbolt: Add support for Intel Maple Ridge single port controller
  efi: x86: Wipe setup_data on pure EFI boot
  efi: libstub: check Shim mode using MokSBStateRT
  wifi: mt76: fix reading current per-tid starting sequence number for 
aggregation
  gpio: mockup: fix NULL pointer dereference when removing debugfs
  gpio: mockup: Fix potential resource leakage when register a chip
  gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
  riscv: fix a nasty sigreturn bug...
  riscv: fix RISCV_ISA_SVPBMT kconfig dependency warning
  drm/i915/gem: Flush contexts on driver release
  drm/i915/gem: Really move i915_gem_context.link under ref protection
  xen/xenbus: fix xenbus_setup_ring()
  kasan: call kasan_malloc() from __kmalloc_*track_caller()
  can: flexcan: flexcan_mailbox_read() fix return value for drop = true
  net: mana: Add rmb after checking owner bits
  mm/slub: fix to return errno if kmalloc() fails
  mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.
  KVM: x86: Reinstate kvm_vcpu_arch.guest_supported_xcr0
  KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES
  KVM: x86: Inject #UD on emulated XSETBV if XSAVES isn't enabled
  perf/arm-cmn: Add more bits to child node address offset field
  arm64: topology: fix possible overflow in amu_fie_setup()
  vmlinux.lds.h: CFI: Reduce alignment of jump-table to function alignment
  batman-adv: Fix hang up with small MTU hard-interface
  firmware: arm_scmi: Harden accesses to the reset domains
  firmware: arm_scmi: Fix the asynchronous reset requests
  arm64: dts: rockchip: Lower sd speed on quartz64-b
  arm64: dts: rockchip: Pull up wlan wake# on Gru-Bob
  arm64: dts: rockchip: Fix typo in lisense text for PX30.Core
  drm/mediatek: dsi: Add atomic {destroy,duplicate}_state, reset callbacks
  arm64: dts: imx8mm: Reverse CPLD_Dn GPIO label mapping on MX8Menlo
  arm64:

[Kernel-packages] [Bug 1994076] Re: Kinetic update: v5.19.14 upstream stable release

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

Title:
  Kinetic update: v5.19.14 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.14 upstream stable release
     from git://git.kernel.org/

  riscv: make t-head erratas depend on MMU
  tools/perf: Fix out of bound access to cpu mask array
  perf record: Fix cpu mask bit setting for mixed mmaps
  counter: 104-quad-8: Utilize iomap interface
  counter: 104-quad-8: Implement and utilize register structures
  counter: 104-quad-8: Fix skipped IRQ lines during events configuration
  uas: add no-uas quirk for Hiksemi usb_disk
  usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
  uas: ignore UAS for Thinkplus chips
  usb: typec: ucsi: Remove incorrect warning
  thunderbolt: Explicitly reset plug events delay back to USB4 spec value
  net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
  Input: snvs_pwrkey - fix SNVS_HPVIDR1 register address
  can: c_can: don't cache TX messages for C_CAN cores
  clk: ingenic-tcu: Properly enable registers before accessing timers
  wifi: mac80211: ensure vif queues are operational after start
  x86/sgx: Do not fail on incomplete sanitization on premature stop of ksgxd
  frontswap: don't call ->init if no ops are registered
  ARM: dts: integrator: Tag PCI host with device_type
  ntfs: fix BUG_ON in ntfs_lookup_inode_by_name()
  x86/uaccess: avoid check_object_size() in copy_from_user_nmi()
  mm/damon/dbgfs: fix memory leak when using debugfs_lookup()
  net: mt7531: only do PLL once after the reset
  Revert "firmware: arm_scmi: Add clock management to the SCMI power domain"
  powerpc/64s/radix: don't need to broadcast IPI for radix pmd collapse flush
  drm/i915/gt: Restrict forced preemption to the active context
  drm/amdgpu: Add amdgpu suspend-resume code path under SRIOV
  vduse: prevent uninitialized memory accesses
  libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205
  mm: fix BUG splat with kvmalloc + GFP_ATOMIC
  mptcp: factor out __mptcp_close() without socket lock
  mptcp: fix unreleased socket in accept queue
  mmc: moxart: fix 4-bit bus width and remove 8-bit bus width
  mmc: hsq: Fix data stomping during mmc recovery
  mm: gup: fix the fast GUP race against THP collapse
  mm/page_alloc: fix race condition between build_all_zonelists and page 
allocation
  mm: prevent page_frag_alloc() from corrupting the memory
  mm/page_isolation: fix isolate_single_pageblock() isolation behavior
  mm: fix dereferencing possible ERR_PTR
  mm/migrate_device.c: flush TLB while holding PTL
  mm/migrate_device.c: add missing flush_cache_page()
  mm/migrate_device.c: copy pte dirty bit to page
  mm: fix madivse_pageout mishandling on non-LRU page
  mm: bring back update_mmu_cache() to finish_fault()
  mm/hugetlb: correct demote page offset logic
  mm,hwpoison: check mm when killing accessing process
  media: dvb_vb2: fix possible out of bound access
  media: rkvdec: Disable H.264 error detection
  media: mediatek: vcodec: Drop platform_get_resource(IORESOURCE_IRQ)
  media: v4l2-compat-ioctl32.c: zero buffer passed to 
v4l2_compat_get_array_args()
  ARM: dts: am33xx: Fix MMCHS0 dma properties
  reset: imx7: Fix the iMX8MP PCIe PHY PERST support
  ARM: dts: am5748: keep usb4_tm disabled
  soc: sunxi: sram: Actually claim SRAM regions
  soc: sunxi: sram: Prevent the driver from being unbound
  soc: sunxi: sram: Fix probe function ordering issues
  soc: sunxi: sram: Fix debugfs info for A64 SRAM C
  ASoC: imx-card: Fix refcount issue with of_node_put
  clk: microchip: mpfs: fix clk_cfg array bounds violation
  clk: microchip: mpfs: make the rtc's ahb clock critical
  arm64: dts: qcom: sm8350: fix UFS PHY serdes size
  ASoC: tas2770: Reinit regcache on reset
  drm/bridge: lt8912b: add vsync hsync
  drm/bridge: lt8912b: set hdmi or dvi mode
  drm/bridge: lt8912b: fix corrupted image output
  net: macb: Fix ZynqMP SGMII non-wakeup source resume failure
  Revert "drm: bridge: analogix/dp: add panel prepare/unprepare in 
suspend/resume time"
  Input: melfas_mip4 - fix return value check in mip4_probe()
  gpio: mvebu: Fix check for pwm support on non-A8K platforms
  perf parse-events: Break out tracepoint and printing
  perf print-events: Fix "perf list" can not

[Kernel-packages] [Bug 1994075] Re: Kinetic update: v5.19.13 upstream stable release

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

Title:
  Kinetic update: v5.19.13 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.13 upstream stable release
     from git://git.kernel.org/

  Note: v5.19.13 consisted only of reverts to patches that were not
  applied to Ubuntu kinetic, hence this patch set is "empty".

  Linux 5.19.13
  UBUNTU: Upstream stable to v5.19.13

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


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

[Kernel-packages] [Bug 1994078] Re: Kinetic update: v5.19.15 upstream stable release

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

Title:
  Kinetic update: v5.19.15 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  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.19.15 upstream stable release
     from git://git.kernel.org/

  sparc: Unbreak the build
  Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
  UBUNTU: [Config] updateconfigs for CC_HAS_AUTO_VAR_INIT_ZERO_ENABLER
  hardening: Remove Clang's enable flag for -ftrivial-auto-var-init=zero
  docs: update mediator information in CoC docs
  xsk: Inherit need_wakeup flag for shared sockets
  firmware: arm_scmi: Improve checks in the info_get operations
  firmware: arm_scmi: Harden accesses to the sensor domains
  firmware: arm_scmi: Add SCMI PM driver remove routine
  arm64: dts: rockchip: fix upper usb port on BPI-R2-Pro
  dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
  dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
  dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API 
failure
  wifi: iwlwifi: don't spam logs with NSS>2 messages
  ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
  drm/amdgpu/mes: zero the sdma_hqd_mask of 2nd SDMA engine for SDMA 6.0.1
  scsi: qedf: Fix a UAF bug in __qedf_probe()
  net/ieee802154: fix uninit value bug in dgram_sendmsg
  net: marvell: prestera: add support for for Aldrin2
  ALSA: hda/hdmi: Fix the converter reuse for the silent stream
  um: Cleanup syscall_handler_t cast in syscalls_32.h
  um: Cleanup compiler warning in arch/x86/um/tls_32.c
  gpio: ftgpio010: Make irqchip immutable
  arch: um: Mark the stack non-executable to fix a binutils warning
  net: atlantic: fix potential memory leak in aq_ndev_close()
  KVM: s390: Pass initialized arg even if unused
  drm/amd/display: Fix double cursor on non-video RGB MPO
  drm/amd/display: Assume an LTTPR is always present on fixed_vs links
  drm/amd/display: update gamut remap if plane has changed
  drm/amd/display: skip audio setup when audio stream is enabled
  drm/amd/display: Fix DP MST timeslot issue when fallback happened
  drm/amd/display: increase dcn315 pstate change latency
  perf/x86/intel: Fix unchecked MSR access error for Alder Lake N
  don't use __kernel_write() on kmap_local_page()
  i2c: davinci: fix PM disable depth imbalance in davinci_i2c_probe
  usb: mon: make mmapped memory read only
  USB: serial: ftdi_sio: fix 300 bps rate for SIO
  gpiolib: acpi: Add support to ignore programming an interrupt
  gpiolib: acpi: Add a quirk for Asus UM325UAZ
  mmc: core: Replace with already defined values for readability
  mmc: core: Terminate infinite loop in SD-UHS voltage switch
  rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
  bpf: Gate dynptr API behind CAP_BPF
  net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear
  bpf: Fix resetting logic for unreferenced kptrs
  Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
  Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5"
  Linux 5.19.15
  UBUNTU: Upstream stable to v5.19.15

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


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

[Kernel-packages] [Bug 1994079] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1994079

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

Title:
  fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to
  generate SIGXFSZ signal

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a corner case on 32 bit systems when using large file offsets,
  fallocate and setrlimit.

  Setting the RLIMIT_FSIZE with setrlimit to 0x and then
  fallocating 1 or more bytes at the offset of 0x should make
  the fallocate fail with EFBIG and generate a SIGXFSZ signal. On 64 bit
  platforms this works, on 32 bit platforms such as i386 Ubuntu bionic
  with 4.15 kernels it fails to generate EFBIG errors and SIGXFSZ.

  Attached is a test program to illustrate the problem. It sets the file
  size limit and allocates 1024 bytes at the boundary file size limit
  for 3 offsets:

  On 64 bit systems we get the expected results:
  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294967295 (0x), fallocate returned: -1

  On 32 bit systems the code fails on the 0x offset:

  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  offset: 4294967295 (0x), fallocate returned: 0

  Attached is the reproducer.

  I found this while developing a file limit boundary test case in
  stress-ng and discovered it breaks on all 32 bit kernels (armhf, i386,
  etc), even with recent 5.15 kernels.

  This could be seen as a security issue; the sysadmin can set the file
  size limit and yet a 32 bit system can use a corner case like this to
  fallocate a much larger file by using the 0x offset and a huge
  fallocate size.

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


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

[Kernel-packages] [Bug 1994079] [NEW] fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to generate SIGXFSZ signal

2022-10-24 Thread Colin Ian King

Public bug reported:

This is a corner case on 32 bit systems when using large file offsets,
fallocate and setrlimit.

Setting the RLIMIT_FSIZE with setrlimit to 0x and then
fallocating 1 or more bytes at the offset of 0x should make the
fallocate fail with EFBIG and generate a SIGXFSZ signal. On 64 bit
platforms this works, on 32 bit platforms such as i386 Ubuntu bionic
with 4.15 kernels it fails to generate EFBIG errors and SIGXFSZ.

Attached is a test program to illustrate the problem. It sets the file
size limit and allocates 1024 bytes at the boundary file size limit for
3 offsets:

On 64 bit systems we get the expected results:
got signal SIGXFSZ
offset: 65536 (0x1), fallocate returned: -1
got signal SIGXFSZ
offset: 4294966271 (0xfbff), fallocate returned: -1
got signal SIGXFSZ
offset: 4294967295 (0x), fallocate returned: -1

On 32 bit systems the code fails on the 0x offset:

got signal SIGXFSZ
offset: 65536 (0x1), fallocate returned: -1
got signal SIGXFSZ
offset: 4294966271 (0xfbff), fallocate returned: -1
offset: 4294967295 (0x), fallocate returned: 0

Attached is the reproducer.

I found this while developing a file limit boundary test case in stress-
ng and discovered it breaks on all 32 bit kernels (armhf, i386, etc),
even with recent 5.15 kernels.

This could be seen as a security issue; the sysadmin can set the file
size limit and yet a 32 bit system can use a corner case like this to
fallocate a much larger file by using the 0x offset and a huge
fallocate size.

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

** Attachment added: "fallocate/file size limit reproducer C source"
   
https://bugs.launchpad.net/bugs/1994079/+attachment/5626526/+files/fallocate.c

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

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

Title:
  fallocate on 32 bit boundary on 32 bit systems with setrlimit fails to
  generate SIGXFSZ signal

Status in linux package in Ubuntu:
  New

Bug description:
  This is a corner case on 32 bit systems when using large file offsets,
  fallocate and setrlimit.

  Setting the RLIMIT_FSIZE with setrlimit to 0x and then
  fallocating 1 or more bytes at the offset of 0x should make
  the fallocate fail with EFBIG and generate a SIGXFSZ signal. On 64 bit
  platforms this works, on 32 bit platforms such as i386 Ubuntu bionic
  with 4.15 kernels it fails to generate EFBIG errors and SIGXFSZ.

  Attached is a test program to illustrate the problem. It sets the file
  size limit and allocates 1024 bytes at the boundary file size limit
  for 3 offsets:

  On 64 bit systems we get the expected results:
  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294967295 (0x), fallocate returned: -1

  On 32 bit systems the code fails on the 0x offset:

  got signal SIGXFSZ
  offset: 65536 (0x1), fallocate returned: -1
  got signal SIGXFSZ
  offset: 4294966271 (0xfbff), fallocate returned: -1
  offset: 4294967295 (0x), fallocate returned: 0

  Attached is the reproducer.

  I found this while developing a file limit boundary test case in
  stress-ng and discovered it breaks on all 32 bit kernels (armhf, i386,
  etc), even with recent 5.15 kernels.

  This could be seen as a security issue; the sysadmin can set the file
  size limit and yet a 32 bit system can use a corner case like this to
  fallocate a much larger file by using the 0x offset and a huge
  fallocate size.

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


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

[Kernel-packages] [Bug 1994078] [NEW] Kinetic update: v5.19.15 upstream stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.15 upstream stable release
   from git://git.kernel.org/

sparc: Unbreak the build
Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
UBUNTU: [Config] updateconfigs for CC_HAS_AUTO_VAR_INIT_ZERO_ENABLER
hardening: Remove Clang's enable flag for -ftrivial-auto-var-init=zero
docs: update mediator information in CoC docs
xsk: Inherit need_wakeup flag for shared sockets
firmware: arm_scmi: Improve checks in the info_get operations
firmware: arm_scmi: Harden accesses to the sensor domains
firmware: arm_scmi: Add SCMI PM driver remove routine
arm64: dts: rockchip: fix upper usb port on BPI-R2-Pro
dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API 
failure
wifi: iwlwifi: don't spam logs with NSS>2 messages
ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
drm/amdgpu/mes: zero the sdma_hqd_mask of 2nd SDMA engine for SDMA 6.0.1
scsi: qedf: Fix a UAF bug in __qedf_probe()
net/ieee802154: fix uninit value bug in dgram_sendmsg
net: marvell: prestera: add support for for Aldrin2
ALSA: hda/hdmi: Fix the converter reuse for the silent stream
um: Cleanup syscall_handler_t cast in syscalls_32.h
um: Cleanup compiler warning in arch/x86/um/tls_32.c
gpio: ftgpio010: Make irqchip immutable
arch: um: Mark the stack non-executable to fix a binutils warning
net: atlantic: fix potential memory leak in aq_ndev_close()
KVM: s390: Pass initialized arg even if unused
drm/amd/display: Fix double cursor on non-video RGB MPO
drm/amd/display: Assume an LTTPR is always present on fixed_vs links
drm/amd/display: update gamut remap if plane has changed
drm/amd/display: skip audio setup when audio stream is enabled
drm/amd/display: Fix DP MST timeslot issue when fallback happened
drm/amd/display: increase dcn315 pstate change latency
perf/x86/intel: Fix unchecked MSR access error for Alder Lake N
don't use __kernel_write() on kmap_local_page()
i2c: davinci: fix PM disable depth imbalance in davinci_i2c_probe
usb: mon: make mmapped memory read only
USB: serial: ftdi_sio: fix 300 bps rate for SIO
gpiolib: acpi: Add support to ignore programming an interrupt
gpiolib: acpi: Add a quirk for Asus UM325UAZ
mmc: core: Replace with already defined values for readability
mmc: core: Terminate infinite loop in SD-UHS voltage switch
rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
bpf: Gate dynptr API behind CAP_BPF
net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear
bpf: Fix resetting logic for unreferenced kptrs
Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5"
Linux 5.19.15
UBUNTU: Upstream stable to v5.19.15

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Kinetic)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.19.15 upstream stable release
+    from git://git.kernel.org/
  
-v5.19.15 upstream stable release
-from git://git.kernel.org/
+ sparc: Unbreak the build
+ Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
+

[Kernel-packages] [Bug 1994076] [NEW] Kinetic update: v5.19.14 upstream stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.14 upstream stable release
   from git://git.kernel.org/

riscv: make t-head erratas depend on MMU
tools/perf: Fix out of bound access to cpu mask array
perf record: Fix cpu mask bit setting for mixed mmaps
counter: 104-quad-8: Utilize iomap interface
counter: 104-quad-8: Implement and utilize register structures
counter: 104-quad-8: Fix skipped IRQ lines during events configuration
uas: add no-uas quirk for Hiksemi usb_disk
usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
uas: ignore UAS for Thinkplus chips
usb: typec: ucsi: Remove incorrect warning
thunderbolt: Explicitly reset plug events delay back to USB4 spec value
net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
Input: snvs_pwrkey - fix SNVS_HPVIDR1 register address
can: c_can: don't cache TX messages for C_CAN cores
clk: ingenic-tcu: Properly enable registers before accessing timers
wifi: mac80211: ensure vif queues are operational after start
x86/sgx: Do not fail on incomplete sanitization on premature stop of ksgxd
frontswap: don't call ->init if no ops are registered
ARM: dts: integrator: Tag PCI host with device_type
ntfs: fix BUG_ON in ntfs_lookup_inode_by_name()
x86/uaccess: avoid check_object_size() in copy_from_user_nmi()
mm/damon/dbgfs: fix memory leak when using debugfs_lookup()
net: mt7531: only do PLL once after the reset
Revert "firmware: arm_scmi: Add clock management to the SCMI power domain"
powerpc/64s/radix: don't need to broadcast IPI for radix pmd collapse flush
drm/i915/gt: Restrict forced preemption to the active context
drm/amdgpu: Add amdgpu suspend-resume code path under SRIOV
vduse: prevent uninitialized memory accesses
libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205
mm: fix BUG splat with kvmalloc + GFP_ATOMIC
mptcp: factor out __mptcp_close() without socket lock
mptcp: fix unreleased socket in accept queue
mmc: moxart: fix 4-bit bus width and remove 8-bit bus width
mmc: hsq: Fix data stomping during mmc recovery
mm: gup: fix the fast GUP race against THP collapse
mm/page_alloc: fix race condition between build_all_zonelists and page 
allocation
mm: prevent page_frag_alloc() from corrupting the memory
mm/page_isolation: fix isolate_single_pageblock() isolation behavior
mm: fix dereferencing possible ERR_PTR
mm/migrate_device.c: flush TLB while holding PTL
mm/migrate_device.c: add missing flush_cache_page()
mm/migrate_device.c: copy pte dirty bit to page
mm: fix madivse_pageout mishandling on non-LRU page
mm: bring back update_mmu_cache() to finish_fault()
mm/hugetlb: correct demote page offset logic
mm,hwpoison: check mm when killing accessing process
media: dvb_vb2: fix possible out of bound access
media: rkvdec: Disable H.264 error detection
media: mediatek: vcodec: Drop platform_get_resource(IORESOURCE_IRQ)
media: v4l2-compat-ioctl32.c: zero buffer passed to v4l2_compat_get_array_args()
ARM: dts: am33xx: Fix MMCHS0 dma properties
reset: imx7: Fix the iMX8MP PCIe PHY PERST support
ARM: dts: am5748: keep usb4_tm disabled
soc: sunxi: sram: Actually claim SRAM regions
soc: sunxi: sram: Prevent the driver from being unbound
soc: sunxi: sram: Fix probe function ordering issues
soc: sunxi: sram: Fix debugfs info for A64 SRAM C
ASoC: imx-card: Fix refcount issue with of_node_put
clk: microchip: mpfs: fix clk_cfg array bounds violation
clk: microchip: mpfs: make the rtc's ahb clock critical
arm64: dts: qcom: sm8350: fix UFS PHY serdes size
ASoC: tas2770: Reinit regcache on reset
drm/bridge: lt8912b: add vsync hsync
drm/bridge: lt8912b: set hdmi or dvi mode
drm/bridge: lt8912b: fix corrupted image output
net: macb: Fix ZynqMP SGMII non-wakeup source resume failure
Revert "drm: bridge: analogix/dp: add panel prepare/unprepare in suspend/resume 
time"
Input: melfas_mip4 - fix return value check in mip4_probe()
gpio: mvebu: Fix check for pwm support on non-A8K platforms
perf parse-events: Break out tracepoint and printing
perf print-events: Fix "perf list" can not display the PMU prefix for some 
hybrid cache events
perf parse-events: Remove "not supported" hybrid cache events
usbnet: Fix memory leak in usbnet_disconnect()
net: sched: act_ct: fix possible refcount leak in tcf_ct_init()
cxgb4: fix missing unlock on ETHOFLD desc collect fail path
net/mlxbf_gige: Fix an IS_ERR() vs NULL bug in mlxbf_gige_mdio_probe
nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices
wifi: cfg80211: fix MCS divisor value
wifi: mac80211: fix regression with non-QoS drivers
wifi: mac80211: fix memory corruption in minstrel_ht_update_rates()

[Kernel-packages] [Bug 1994074] [NEW] Kinetic update: v5.19.12 upstream stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.12 upstream stable release
   from git://git.kernel.org/

smb3: Move the flush out of smb2_copychunk_range() into its callers
smb3: fix temporary data corruption in collapse range
smb3: fix temporary data corruption in insert range
usb: add quirks for Lenovo OneLink+ Dock
usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
smb3: use filemap_write_and_wait_range instead of filemap_write_and_wait
Revert "usb: add quirks for Lenovo OneLink+ Dock"
Revert "usb: gadget: udc-xilinx: replace memcpy with memcpy_toio"
xfrm: fix XFRMA_LASTUSED comment
block: remove QUEUE_FLAG_DEAD
block: stop setting the nomerges flags in blk_cleanup_queue
block: simplify disk shutdown
scsi: core: Fix a use-after-free
drivers/base: Fix unsigned comparison to -1 in CPUMAP_FILE_MAX_BYTES
USB: core: Fix RST error in hub.c
USB: serial: option: add Quectel BG95 0x0203 composition
USB: serial: option: add Quectel RM520N
ALSA: core: Fix double-free at snd_card_new()
ALSA: hda/tegra: set depop delay for tegra
ALSA: hda: Fix hang at HD-audio codec unbinding due to refcount saturation
ALSA: hda: Fix Nvidia dp infoframe
ALSA: hda: add Intel 5 Series / 3400 PCI DID
ALSA: hda/realtek: Add quirk for Huawei WRT-WX9
ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5570 laptop
ALSA: hda/realtek: Re-arrange quirk table entries
ALSA: hda/realtek: Add pincfg for ASUS G513 HP jack
ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack
ALSA: hda/realtek: Add quirk for ASUS GA503R laptop
ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5530 laptop
ALSA: hda/realtek: Add a quirk for HP OMEN 16 (8902) mute LED
iommu/vt-d: Check correct capability for sagaw determination
exfat: fix overflow for large capacity partition
btrfs: fix hang during unmount when stopping block group reclaim worker
btrfs: fix hang during unmount when stopping a space reclaim worker
btrfs: zoned: wait for extent buffer IOs before finishing a zone
libperf evlist: Fix polling of system-wide events
media: flexcop-usb: fix endpoint type check
usb: dwc3: core: leave default DMA if the controller does not support 64-bit DMA
thunderbolt: Add support for Intel Maple Ridge single port controller
efi: x86: Wipe setup_data on pure EFI boot
efi: libstub: check Shim mode using MokSBStateRT
wifi: mt76: fix reading current per-tid starting sequence number for aggregation
gpio: mockup: fix NULL pointer dereference when removing debugfs
gpio: mockup: Fix potential resource leakage when register a chip
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
riscv: fix a nasty sigreturn bug...
riscv: fix RISCV_ISA_SVPBMT kconfig dependency warning
drm/i915/gem: Flush contexts on driver release
drm/i915/gem: Really move i915_gem_context.link under ref protection
xen/xenbus: fix xenbus_setup_ring()
kasan: call kasan_malloc() from __kmalloc_*track_caller()
can: flexcan: flexcan_mailbox_read() fix return value for drop = true
net: mana: Add rmb after checking owner bits
mm/slub: fix to return errno if kmalloc() fails
mm: slub: fix flush_cpu_slab()/__free_slab() invocations in task context.
KVM: x86: Reinstate kvm_vcpu_arch.guest_supported_xcr0
KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES
KVM: x86: Inject #UD on emulated XSETBV if XSAVES isn't enabled
perf/arm-cmn: Add more bits to child node address offset field
arm64: topology: fix possible overflow in amu_fie_setup()
vmlinux.lds.h: CFI: Reduce alignment of jump-table to function alignment
batman-adv: Fix hang up with small MTU hard-interface
firmware: arm_scmi: Harden accesses to the reset domains
firmware: arm_scmi: Fix the asynchronous reset requests
arm64: dts: rockchip: Lower sd speed on quartz64-b
arm64: dts: rockchip: Pull up wlan wake# on Gru-Bob
arm64: dts: rockchip: Fix typo in lisense text for PX30.Core
drm/mediatek: dsi: Add atomic {destroy,duplicate}_state, reset callbacks
arm64: dts: imx8mm: Reverse CPLD_Dn GPIO label mapping on MX8Menlo
arm64: dts: rockchip: Set RK3399-Gru PCLK_EDP to 24 MHz
arm64: dts: imx8mn: remove GPU power domain reset
arm64: dts: imx8ulp: add #reset-cells for pcc
dmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()
arm64: dts: rockchip: fix property for usb2 phy supply on rock-3a
arm64: dts: rockchip: fix property for usb2 phy supply on rk3568-evb1-v10
arm64: dts: rockchip: Remove 'enable-active-low' from rk3399-puma
arm64: dts: rockchip: Remove 'enable-active-low' from rk3566-quartz64-a
arm64: dts: imx8mm-verdin: extend pmic voltages
netfilter: nf_conntrack_sip:

[Kernel-packages] [Bug 1994075] [NEW] Kinetic update: v5.19.13 upstream stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.13 upstream stable release
   from git://git.kernel.org/

Note: v5.19.13 consisted only of reverts to patches that were not
applied to Ubuntu kinetic, hence this patch set is "empty".

Linux 5.19.13
UBUNTU: Upstream stable to v5.19.13

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Kinetic)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Changed in: linux (Ubuntu Kinetic)
   Status: Confirmed => In Progress

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.19.13 upstream stable release
+    from git://git.kernel.org/
  
-v5.19.13 upstream stable release
-from git://git.kernel.org/
+ Note: v5.19.13 consisted only of reverts to patches that were not
+ applied to Ubuntu kinetic, hence this patch set is "empty".
+ 
+ Linux 5.19.13
+ UBUNTU: Upstream stable to v5.19.13

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

Title:
  Kinetic update: v5.19.13 upstream stable release

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.19.13 upstream stable release
     from git://git.kernel.org/

  Note: v5.19.13 consisted only of reverts to patches that were not
  applied to Ubuntu kinetic, hence this patch set is "empty".

  Linux 5.19.13
  UBUNTU: Upstream stable to v5.19.13

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


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

[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

2022-10-24 Thread Dan Meyers

Still no crashes/freezes after almost day of usage, so I think we're
good in that respect.

I also resolved the distortion issue I was having by adding the
"i915.enable_psr=0" kernel option. I was detecting some slight lag w/
the mouse periodically and found that as a potential solution -- it
seems to fix both the lag AND the distortion!

Anyhow, at the moment my system feels much like the sturdy/stable system
I had with 22.04. Thanks again for the 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/1993818

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant kernel: [  281.052899]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Oct 21 20:41:38 tyrant kernel: [  281.052902]  ? __x64_sys_kcmp+0x1f/0x30
  Oct 21 20:41:38 tyrant kernel: [  281.052905]  ? do_syscall_64+0x67/0x90
  Oct 21 20:41:38

[Kernel-packages] [Bug 1993352] Re: unable to boot kernel 5.15.0.50

2022-10-24 Thread warxnox

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

Updated to Kinetic Kudu and Linux 5.19.0-23-generic, did not resolved
the issue


** Tags added: kinetic kudu

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

Title:
  unable to boot kernel 5.15.0.50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel
  5.15.0.50

  Normal boot on 5.15.0.50 : stuck at boot with the following message : 
  INFO: task gpu-manager:749 blocked for more than XXX seconds

  I deactivated the silent splash screen on Grub to get more details
  about what's wrong :

  "a start job is running for Detect the available GPU..."

  Recovery mode on 5.15.0.50: I can boot but after login only integrated
  monitor is working

  Normal boot on 5.15.0.43: No issue

  Configuration:  Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated
  Intel GPU

  Nvidia drivers: 515

  What I'v done so far :

  -Deactivated gpu-manager in grub: no effect
  -Uninstall intel-microcode or downgraded intel-microcode : no effect
  -Tried various nvidia drivers: no effect
  -Tried other external monitors: no effect
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gwendal1853 F pulseaudio
   /dev/snd/controlC2:  gwendal1853 F pulseaudio
   /dev/snd/controlC1:  gwendal1853 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-10-12 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Alienware Alienware 15 R3
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/vgubuntu-root ro
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  Tags:  jammy
  Uname: Linux 5.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2020
  dmi.bios.release: 1.10
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.10.0
  dmi.board.name: Alienware 15 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 15 R3
  dmi.product.sku: 0774
  dmi.product.version: 1.10.0
  dmi.sys.vendor: Alienware

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


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

[Kernel-packages] [Bug 1990945] Update Released

2022-10-24 Thread Łukasz Zemczak

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

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

Title:
  i915: Add GuC v70.1.1 for all platforms

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]  
 

 
  Intel Quake N i915 for kernel 5.19+ will need v70.1.1 firmware files. 
 

 
  [Fix] 
 

 
  Upstream commit ab0d8c137d42 ("i915: Add GuC v70.1.1 for all platforms"). 
 

 
  [Test Case]   
 

 
  With v69 firmware, kernel prints: 
 

 
kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin  
 
is recommended, but only i915/adlp_guc_69.0.3.bin was found

 
  New firmware would silence this line. 
 

 
  [Where problems could occur]  
 

 
  Firmware update, little knowledge to what was actually fixed, and the 
 
  actual revision being used is guarded by kernel.   

 
  [Other Info]  
 

 
  This update already exists in Kinetic, so only Jammy is nominated.

  == original bug report ==

  Quake N i915 for kernel 5.19+ will need the firmware files listed in the 
following mail post:
  https://www.spinics.net/lists/intel-gfx/msg295995.html

  We are targeting Quake N to release with 6.0-oem kernel.

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


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

[Kernel-packages] [Bug 1990945] Re: i915: Add GuC v70.1.1 for all platforms

2022-10-24 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.6

---
linux-firmware (20220329.git681281e4-0ubuntu3.6) jammy; urgency=medium

  * i915: Add GuC v70.1.1 for all platforms (LP: #1990945)
- i915: Add GuC v70.1.1 for all platforms

 -- Juerg Haefliger   Mon, 03 Oct 2022
13:08:31 +0200

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  i915: Add GuC v70.1.1 for all platforms

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]  
 

 
  Intel Quake N i915 for kernel 5.19+ will need v70.1.1 firmware files. 
 

 
  [Fix] 
 

 
  Upstream commit ab0d8c137d42 ("i915: Add GuC v70.1.1 for all platforms"). 
 

 
  [Test Case]   
 

 
  With v69 firmware, kernel prints: 
 

 
kernel: i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin  
 
is recommended, but only i915/adlp_guc_69.0.3.bin was found

 
  New firmware would silence this line. 
 

 
  [Where problems could occur]  
 

 
  Firmware update, little knowledge to what was actually fixed, and the 
 
  actual revision being used is guarded by kernel.   

 
  [Other Info]  
 

 
  This update already exists in Kinetic, so only Jammy is nominated.

  == original bug report ==

  Quake N i915 for kernel 5.19+ will need the firmware files listed in the 
following mail post:
  https://www.spinics.net/lists/intel-gfx/msg295995.html

  We are targeting Quake N to release with 6.0-oem kernel.

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


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

[Kernel-packages] [Bug 1994070] [NEW] Kinetic update: v5.19.11 upstream stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.11 upstream stable release
   from git://git.kernel.org/

of: fdt: fix off-by-one error in unflatten_dt_nodes()
pinctrl: qcom: sc8180x: Fix gpio_wakeirq_map
pinctrl: qcom: sc8180x: Fix wrong pin numbers
pinctrl: rockchip: Enhance support for IRQ_TYPE_EDGE_BOTH
pinctrl: sunxi: Fix name for A100 R_PIO
SUNRPC: Fix call completion races with call_decode()
NFSv4: Turn off open-by-filehandle and NFS re-export for NFSv4.0
gpio: mpc8xxx: Fix support for IRQ_TYPE_LEVEL_LOW flow_type in mpc85xx
NFSv4.2: Update mode bits after ALLOCATE and DEALLOCATE
Revert "SUNRPC: Remove unreachable error condition"
drm/panel-edp: Fix delays for Innolux N116BCA-EA1
drm/meson: Correct OSD1 global alpha value
drm/meson: Fix OSD1 RGB to YCbCr coefficient
drm/rockchip: vop2: Fix eDP/HDMI sync polarities
drm/i915/vdsc: Set VDSC PIC_HEIGHT before using for DP DSC
drm/i915/guc: Don't update engine busyness stats too frequently
drm/i915/guc: Cancel GuC engine busyness worker synchronously
block: blk_queue_enter() / __bio_queue_enter() must return -EAGAIN for nowait
parisc: ccio-dma: Add missing iounmap in error path in ccio_probe()
of/device: Fix up of_dma_configure_id() stub
io_uring/msg_ring: check file type before putting
cifs: revalidate mapping when doing direct writes
cifs: don't send down the destination address to sendmsg for a SOCK_STREAM
cifs: always initialize struct msghdr smb_msg completely
blk-lib: fix blkdev_issue_secure_erase
parisc: Allow CONFIG_64BIT with ARCH=parisc
tools/include/uapi: Fix  for parisc and xtensa
drm/i915/gt: Fix perf limit reasons bit positions
drm/i915: Set correct domains values at _i915_vma_move_to_active
drm/amdgpu: make sure to init common IP before gmc
drm/amdgpu: Don't enable LTR if not supported
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
net: Find dst with sk's xfrm policy not ctl_sk
dt-bindings: apple,aic: Fix required item "apple,fiq-index" in affinity 
description
cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()
ALSA: hda/sigmatel: Keep power up while beep is enabled
ALSA: hda/sigmatel: Fix unused variable warning for beep power change
Linux 5.19.11
UBUNTU: Upstream stable to v5.19.11

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Kinetic)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Changed in: linux (Ubuntu Kinetic)
   Status: Confirmed => In Progress

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.19.11 upstream stable release
+    from git://git.kernel.org/
  
-v5.19.11 upstream stable release
-from git://git.kernel.org/
+ of: fdt: fix off-by-one error in unflatten_dt_nodes()
+ pinctrl: qcom: sc8180x: Fix gpio_wakeirq_map
+ pinctrl: qcom: sc8180x: Fix wrong pin numbers
+ pinctrl: rockchip: Enhance support for IRQ_TYPE_EDGE_BOTH
+ pinctrl: sunxi: Fix name for A100 R_PIO
+ SUNRPC: Fix call completion races with call_decode()
+ NFSv4: Turn off open-by-filehandle and NFS re-export for NFSv4.0
+ gpio: mpc8xxx: Fix support for

[Kernel-packages] [Bug 1994069] [NEW] Kinetic update: v5.19.10 upstream stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.10 upstream stable release
   from git://git.kernel.org/

iommu/vt-d: Fix kdump kernels boot failure with scalable mode
net/mlx5: Introduce ifc bits for using software vhca id
net/mlx5: Use software VHCA id when it's supported
RDMA/mlx5: Rely on RoCE fw cap instead of devlink when setting profile
RDMA/mlx5: Add a umr recovery flow
RDMA/mlx5: Fix UMR cleanup on error flow of driver init
ACPI: resource: skip IRQ override on AMD Zen platforms
Input: goodix - add support for GT1158
platform/surface: aggregator_registry: Add support for Surface Laptop Go 2
drm/msm/rd: Fix FIFO-full deadlock
peci: cpu: Fix use-after-free in adev_release()
kvm: x86: mmu: Always flush TLBs when enabling dirty logging
dt-bindings: iio: gyroscope: bosch,bmg160: correct number of pins
HID: ishtp-hid-clientHID: ishtp-hid-client: Fix comment typo
hid: intel-ish-hid: ishtp: Fix ishtp client sending disordered message
Bluetooth: MGMT: Fix Get Device Flags
tg3: Disable tg3 device on system reboot to avoid triggering AER
r8152: add PID for the Lenovo OneLink+ Dock
gpio: mockup: remove gpio debugfs when remove device
ieee802154: cc2520: add rc code in cc2520_tx()
Input: iforce - add support for Boeder Force Feedback Wheel
drm/amdgpu: disable FRU access on special SIENNA CICHLID card
drm/amd/pm: use vbios carried pptable for all SMU13.0.7 SKUs
nvme-pci: add NVME_QUIRK_BOGUS_NID for Lexar NM610
nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()
drm/amd/amdgpu: skip ucode loading if ucode_size == 0
net: dsa: hellcreek: Print warning only once
perf/arm_pmu_platform: fix tests for platform_get_irq() failure
platform/x86: acer-wmi: Acer Aspire One AOD270/Packard Bell Dot keymap fixes
usb: storage: Add ASUS <0x0b05:0x1932> to IGNORE_UAS
platform/x86: asus-wmi: Increase FAN_CURVE_BUF_LEN to 32
LoongArch: Fix section mismatch due to acpi_os_ioremap()
LoongArch: Fix arch_remove_memory() undefined build error
gpio: 104-dio-48e: Make irq_chip immutable
gpio: 104-idio-16: Make irq_chip immutable
RDMA/irdma: Use s/g array in post send only when its valid
Input: goodix - add compatible string for GT1158
Linux 5.19.10
UBUNTU: Upstream stable to v5.19.10

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Kinetic)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Changed in: linux (Ubuntu Kinetic)
   Status: Confirmed => In Progress

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.19.10 upstream stable release
+    from git://git.kernel.org/
  
-v5.19.10 upstream stable release
-from git://git.kernel.org/
+ iommu/vt-d: Fix kdump kernels boot failure with scalable mode
+ net/mlx5: Introduce ifc bits for using software vhca id
+ net/mlx5: Use software VHCA id when it's supported
+ RDMA/mlx5: Rely on RoCE fw cap instead of devlink when setting profile
+ RDMA/mlx5: Add a umr recovery flow
+ RDMA/mlx5: Fix UMR cleanup on error flow of driver init
+ ACPI: resource: skip IRQ override on AMD Zen platforms
+ Input: goodix - add support for GT1158
+ platform/surface: aggregator_registry: Add support

[Kernel-packages] [Bug 1994068] Re: Kinetic update: v5.19.10 upstream stable release

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.19.9 upstream stable release
+    from git://git.kernel.org/
  
-v5.19.10 upstream stable release
-from git://git.kernel.org/
+ drm/msm/dp: make eDP panel as the first connected connector
+ drm/msm/dsi: fix the inconsistent indenting
+ drm/msm/dpu: populate wb or intf before reset_intf_cfg
+ drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4
+ drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
+ drm/msm/dsi: Fix number of regulators for SDM660
+ platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
+ platform/x86: x86-android-tablets: Fix broken touchscreen on Chuwi Hi8 with 
Windows BIOS
+ xsk: Fix corrupted packets for XDP_SHARED_UMEM
+ drm/msm/gpu: Drop qos request if devm_devfreq_add_device() fails
+ peci: aspeed: fix error check return value of platform_get_irq()
+ iio: adc: mcp3911: make use of the sign bit
+ skmsg: Fix wrong last sg check in sk_msg_recvmsg()
+ bpf: Restrict bpf_sys_bpf to CAP_PERFMON
+ ip_tunnel: Respect tunnel key's "flow_flags" in IP tunnels
+ bpf, cgroup: Fix kernel BUG in purge_effective_progs
+ drm/i915/gvt: Fix Comet Lake
+ ieee802154/adf7242: defer destroy_workqueue call
+ bpf: Fix a data-race around bpf_jit_limit.
+ drm/i915/ttm: fix CCS handling
+ drm/i915/display: avoid warnings when registering dual panel backlight
+ ALSA: hda: intel-nhlt: Correct the handling of fmt_config flexible array
+ wifi: cfg80211: debugfs: fix return type in ht40allow_map_read()
+ xhci: Fix null pointer dereference in remove if xHC has only one roothub
+ Revert "xhci: turn off port power in shutdown"
+ bpf: Allow helpers to accept pointers with a fixed size
+ bpf: Tidy up verifier check_func_arg()
+ bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO
+ Bluetooth: hci_event: Fix vendor (unknown) opcode status handling
+ Bluetooth: hci_sync: Fix suspend performance regression
+ Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt
+ Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn
+ net: sparx5: fix handling uneven length packets in manual extraction
+ net: smsc911x: Stop and start PHY during suspend and resume
+ openvswitch: fix memory leak at failed datapath creation
+ nfp: flower: fix ingress police using matchall filter
+ net: dsa: xrs700x: Use irqsave variant for u64 stats update
+ net: sched: tbf: don't call qdisc_put() while holding tree lock
+ net/sched: fix netdevice reference leaks in attach_default_qdiscs()
+ net: phy: micrel: Make the GPIO to be non-exclusive
+ net: lan966x: improve error handle in lan966x_fdma_rx_get_frame()
+ ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler
+ cachefiles: fix error return code in cachefiles_ondemand_copen()
+ cachefiles: make on-demand request distribution fairer
+ mlxbf_gige: compute MDIO period based on i1clk
+ kcm: fix strp_init() order and cleanup
+ sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb
+ tcp: annotate data-race around challenge_timestamp
+ Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb"
+ net/smc: Remove redundant refcount increase
+ soundwire: qcom: fix device status array range
+ mm/slab_common: Deleting kobject in kmem_cache_destroy() without holding 
slab_mutex/cpu_hotplug_lock
+ platform/mellanox: mlxreg-lc: Fix coverity warning
+ platform/mellanox: mlxreg-lc: Fix locking issue
+ serial: fsl_lpuart: RS485 RTS polariy is inverse
+ tty: serial: atmel: Preserve previous USART mode if RS485 disabled
+ staging: rtl8712: fix use after free bugs
+ staging: r8188eu: Add Rosewill USB-N150 Nano to device tables
+ staging: r8188eu: add firmware dependency
+ Revert "powerpc: Remove unused FW_FEATURE_NATIVE references"
+ powerpc: align syscall table for ppc32
+ powerpc/rtas: Fix RTAS MSR[HV] handling for Cell
+ vt: Clear selection before changing the font
+ musb: fix USB_MUSB_TUSB6010 dependency
+ tty: serial: lpuart: disable flow control while waiting for the transmit 
engine to complete
+ Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
+ iio: light:

[Kernel-packages] [Bug 1994068] [NEW] Kinetic update: v5.19.10 upstream stable release

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.10 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Kinetic update: v5.19.10 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

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

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


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

[Kernel-packages] [Bug 1994061] Re: Kinetic update: v5.19.8 upstream stable release

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.19.8 upstream stable release
+    from git://git.kernel.org/
  
-v5.19.8 upstream stable release
-from git://git.kernel.org/
+ drm/msm/dp: make eDP panel as the first connected connector
+ drm/msm/dsi: fix the inconsistent indenting
+ drm/msm/dpu: populate wb or intf before reset_intf_cfg
+ drm/msm/dp: delete DP_RECOVERED_CLOCK_OUT_EN to fix tps4
+ drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg
+ drm/msm/dsi: Fix number of regulators for SDM660
+ platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask
+ platform/x86: x86-android-tablets: Fix broken touchscreen on Chuwi Hi8 with 
Windows BIOS
+ xsk: Fix corrupted packets for XDP_SHARED_UMEM
+ drm/msm/gpu: Drop qos request if devm_devfreq_add_device() fails
+ peci: aspeed: fix error check return value of platform_get_irq()
+ iio: adc: mcp3911: make use of the sign bit
+ skmsg: Fix wrong last sg check in sk_msg_recvmsg()
+ bpf: Restrict bpf_sys_bpf to CAP_PERFMON
+ ip_tunnel: Respect tunnel key's "flow_flags" in IP tunnels
+ bpf, cgroup: Fix kernel BUG in purge_effective_progs
+ drm/i915/gvt: Fix Comet Lake
+ ieee802154/adf7242: defer destroy_workqueue call
+ bpf: Fix a data-race around bpf_jit_limit.
+ drm/i915/ttm: fix CCS handling
+ drm/i915/display: avoid warnings when registering dual panel backlight
+ ALSA: hda: intel-nhlt: Correct the handling of fmt_config flexible array
+ wifi: cfg80211: debugfs: fix return type in ht40allow_map_read()
+ xhci: Fix null pointer dereference in remove if xHC has only one roothub
+ Revert "xhci: turn off port power in shutdown"
+ bpf: Allow helpers to accept pointers with a fixed size
+ bpf: Tidy up verifier check_func_arg()
+ bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO
+ Bluetooth: hci_event: Fix vendor (unknown) opcode status handling
+ Bluetooth: hci_sync: Fix suspend performance regression
+ Bluetooth: hci_event: Fix checking conn for le_conn_complete_evt
+ Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn
+ net: sparx5: fix handling uneven length packets in manual extraction
+ net: smsc911x: Stop and start PHY during suspend and resume
+ openvswitch: fix memory leak at failed datapath creation
+ nfp: flower: fix ingress police using matchall filter
+ net: dsa: xrs700x: Use irqsave variant for u64 stats update
+ net: sched: tbf: don't call qdisc_put() while holding tree lock
+ net/sched: fix netdevice reference leaks in attach_default_qdiscs()
+ net: phy: micrel: Make the GPIO to be non-exclusive
+ net: lan966x: improve error handle in lan966x_fdma_rx_get_frame()
+ ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler
+ cachefiles: fix error return code in cachefiles_ondemand_copen()
+ cachefiles: make on-demand request distribution fairer
+ mlxbf_gige: compute MDIO period based on i1clk
+ kcm: fix strp_init() order and cleanup
+ sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb
+ tcp: annotate data-race around challenge_timestamp
+ Revert "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb"
+ net/smc: Remove redundant refcount increase
+ soundwire: qcom: fix device status array range
+ mm/slab_common: Deleting kobject in kmem_cache_destroy() without holding 
slab_mutex/cpu_hotplug_lock
+ platform/mellanox: mlxreg-lc: Fix coverity warning
+ platform/mellanox: mlxreg-lc: Fix locking issue
+ serial: fsl_lpuart: RS485 RTS polariy is inverse
+ tty: serial: atmel: Preserve previous USART mode if RS485 disabled
+ staging: rtl8712: fix use after free bugs
+ staging: r8188eu: Add Rosewill USB-N150 Nano to device tables
+ staging: r8188eu: add firmware dependency
+ Revert "powerpc: Remove unused FW_FEATURE_NATIVE references"
+ powerpc: align syscall table for ppc32
+ powerpc/rtas: Fix RTAS MSR[HV] handling for Cell
+ vt: Clear selection before changing the font
+ musb: fix USB_MUSB_TUSB6010 dependency
+ tty: serial: lpuart: disable flow control while waiting for the transmit 
engine to complete
+ Input: iforce - wake up after clearing IFORCE_XMIT_RUNNING flag
+ iio: light:

[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

2022-10-24 Thread Andrea Righi

Thanks for testing and good to know that the kernel doesn't seem to
crash (so far). All the i915 fixes that I applied will be available in
the next official Kinetic kernel, so we should be good. Let me know if
the problem happens again.

About the color distortions I'll investigate a bit. I may ask you to
test another kernel if I find something interesting. :)

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

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant kernel: [  281.052899]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Oct 21 20:41:38 tyrant kernel: [  281.052902]  ? __x64_sys_kcmp+0x1f/0x30
  Oct 21 20:41:38 tyrant kernel: [  281.052905]  ? do_syscall_64+0x67/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052908]  ? 
sysvec_apic_timer_interrupt+0x4b/0xd0
  Oct 21 20:41:38 tyrant

[Kernel-packages] [Bug 1994061] [NEW] Kinetic update: v5.19.8 upstream stable release

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.19.8 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Kinetic update: v5.19.8 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

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

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


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

[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)

2022-10-24 Thread Lorenzo J. Lucchini

Just a FYI: I reported this bug as well, concerning a closely related
Fibocom modem on an Asus Expertbook laptop to Fedora at
https://bugzilla.redhat.com/show_bug.cgi?id=2131366

I have not as yet been able to try the patch because I've never built a
kernel on Fedora and currently I'm stuck. In other words I'm an idiot.
I'll let you know if I figure it out, but meanwhile I thought it just
might be useful to know there is another bug report on this.

** Bug watch added: Red Hat Bugzilla #2131366
   https://bugzilla.redhat.com/show_bug.cgi?id=2131366

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

Title:
   Fibocom WWAN FM350-GL suspend error (notebook not suspend)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module 
mtk_t7xx . Power management for this modem is bad. When the notebook goes to 
sleep/suspend, kernel module mtk_t7xx return an error:

  mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 
  mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110 
  mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110 
  mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 

  So power management failed to suspend:
  PM: Some devices failed to suspend, or early wake event detected 

  And the notebook not suspend and wake up again.
  It must be this module, because if I remove the module first (modprobe -r), 
the laptop goes to sleep and wakes up normally.
  However, after reinserting the module, the modem no longer appears in the 
system.

  Expected state: sleep occurs when the device is put to sleep -
  including the modem. When you wake up, you will wake up, including
  activating the modem and logging into the operator's network.

  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  lspci -v:
  58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
  Subsystem: Device 1cf8:3500
  Flags: bus master, fast devsel, latency 0, IRQ 17
  Memory at 601e80 (64-bit, prefetchable) [size=32K]
  Memory at 5e80 (64-bit, non-prefetchable) [size=8M]
  Memory at 601e00 (64-bit, prefetchable) [size=8M]
  Capabilities: [80] Express Endpoint, MSI 00
  Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
  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
  Capabilities: [300] Secondary PCI Express
  Kernel driver in use: mtk_t7xx
  Kernel modules: mtk_t7xx

  lshw:
  *-generic
  description: Wireless controller
  product: MEDIATEK Corp.
  vendor: MEDIATEK Corp.
  physical id: 0
  bus info: pci@:58:00.0
  version: 01
  width: 64 bits
  clock: 33MHz
  capabilities: pciexpress msix msi pm bus_master cap_list
  configuration: driver=mtk_t7xx latency=0
  resources: iomemory:600-5ff iomemory:600-5ff irq:17 
memory:601e80-601e807fff memory:5e80-5eff 
memory:601e00-601e7f

  modinfo:
  modinfo mtk_t7xx
  filename:   
/lib/modules/5.19.10-051910-generic/kernel/drivers/net/wwan/t7xx/mtk_t7xx.ko
  license:GPL
  description:MediaTek PCIe 5G WWAN modem T7xx driver
  author: MediaTek Inc
  srcversion: 5FA53465EA0167231B632D4
  alias:  pci:v14C3d4D75sv*sd*bc*sc*i*
  depends:
  retpoline:  Y
  intree: Y
  name:   mtk_t7xx
  vermagic:   5.19.10-051910-generic SMP preempt mod_unload modversions 
  sig_id: PKCS#7
  signer: Build time autogenerated kernel key
  sig_key:7E:38:36:48:BB:F2:74:0E:30:57:1B:6E:64:90:57:55:30:C5:AF:45
  sig_hashalgo:   sha512
  signature:  78:1B:C9:7F:DE:D2:BE:87:EA:17:94:14:C2:51:3E:2C:75:03:76:0F:
  36:96:92:9B:88:48:B0:C8:73:E6:88:E4:A2:61:25:E9:16:E8:87:40:
  45:99:CC:50:FD:21:B0:BB:11:0E:B5:8F:CC:5F:47:7A:5E:00:BF:7D:
  77:50:A1:F5:00:24:DC:EF:E6:3E:A0:3B:0A:D7:2E:84:EC:FC:6B:4D:
  9E:42:CD:A2:07:C3:D9:F8:6E:7B:76:12:7F:B9:9B:70:6A:22:3D:09:
  4D:04:98:59:35:2A:95:D1:9A:B3:53:77:BE:E5:3E:50:51:18:D0:CE:
  9A:DB:3B:0E:DA:4D:05:5D:D1:5F:4F:6B:DB:98:47:F3:32:25:D8:AD:
  4E:CE:5F:3E:46:76:D9:F4:FA:28:F2:49:B3:3D:D1:5F:74:CF:69:39:

[Kernel-packages] [Bug 1994060] Re: dkms drivers not built or installed

2022-10-24 Thread mike Bernson

try doing dkms autoinstall:
Error! Your kernel headers for kernel 5.17.0-1020-oem cannot be found.
Please install the linux-headers-5.17.0-1020-oem package or use the 
--kernelsourcedir option to tell DKMS where it's located.
Error! Your kernel headers for kernel 5.17.0-1020-oem cannot be found.
Please install the linux-headers-5.17.0-1020-oem package or use the 
--kernelsourcedir option to tell DKMS where it's located.
Error! Your kernel headers for kernel 5.17.0-1020-oem cannot be found.
Please install the linux-headers-5.17.0-1020-oem package or use the 
--kernelsourcedir option to tell DKMS where it's located.


The kernel header have alls been install upto now (Missing depend for)


doing  apt-get install linux-headers-5.17.0-1020-oem cause the dkms to build 
and install.

sound like a missing depend 5.17 stuff version 5.15.

The 5.15 installed the header for every upgraded kernel version but when the 
apt installed the
5.17 kernel it did not install the kernel headers.



** Attachment added: "dpkg -l after installing kernel header file myself"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.17/+bug/1994060/+attachment/5626473/+files/installed

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

Title:
  dkms drivers not built or installed

Status in linux-signed-oem-5.17 package in Ubuntu:
  New

Bug description:
  The system updated kernels to 5.17.0-1020-oem from 5.15.0-52-generic
  The dkms driver did not install on the new kernel.

  I Have 3 dkms drivers installed. They all build on 5.15.0.52 kernel.

  I have look and the lib/modules/kenerl-version/update does not exists

  The 3 dkms moudles:

  nvidia/520.56.06
  virtualbox/6.1.38
  zfs/2.1.6, 5.15.0-52-generic

  mike@mike-think:/lib/modules$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  Codename: jammy

  mike@mike-think:/lib/modules$ uname -a
  Linux mike-think 5.17.0-1020-oem #21-Ubuntu SMP PREEMPT Fri Oct 14 09:33:24 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux


  mike@mike-think:/lib/modules/5.17.0-1020-oem$ ls
  initrd/  modules.builtin.bin  modules.softdep
  kernel/  modules.builtin.modinfo  modules.symbols
  modules.aliasmodules.dep  modules.symbols.bin
  modules.alias.binmodules.dep.bin  vdso/
  modules.builtin  modules.devname
  modules.builtin.alias.bin  modules.order

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21
  ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
  Uname: Linux 5.17.0-1020-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Oct 24 14:07:31 2022
  InstallationDate: Installed on 2020-03-30 (937 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-5.17
  UpgradeStatus: Upgraded to jammy on 2022-10-07 (16 days ago)

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


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

[Kernel-packages] [Bug 1994059] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  NVME down errors after kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the latest kernel update (from 5.15.0-50-generic to
  5.15.0-52-generic) some NVME errors show up in dmesg like

  nvme nvme0: controller is down; will reset: CSTS=0x PCI_STATUS=0x10
  nvme :01:00.0: enabling device ( -> 0002)
  nvme nvme0: Removing after probe failure status: -19
  nvme0n1: detected capacity change from 1000215216 to 0

  (Typed from a picture, could not send actual dmesg since the machine
  freezes shortly after losing the root filesystem and no new program
  can be loaded.)

  Tried some tricks like kernel parameters
  nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off, suggested in
  the Internet to solve similar problems. It only seems to delay the
  freeze average time from 20-30 min to 120-180 min but does not solve
  the issue.

  Going back to kernel 5.15.0-50 seems to have stabilized the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  epx1175 F pipewire-media-
epx1176 F pulseaudio
   /dev/snd/seq:epx1174 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 14:57:35 2022
  InstallationDate: Installed on 2022-10-17 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XDA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash mitigations=off 
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P17CFB.044.220223.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550XDA-KH3BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLB187A0D-C01-G001-S0001+10.0.22000
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP17CFB.044.220223.HQ:bd02/23/2022:br5.19:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XDA:pvrP17CFB:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XDA-KH3BR:rvrSGLB187A0D-C01-G001-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-TGL3-PCFB:
  dmi.product.family: Notebook Plus2
  dmi.product.name: 550XDA
  dmi.product.sku: SCAI-A5A5-A5A5-TGL3-PCFB
  dmi.product.version: P17CFB
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Kernel-packages] [Bug 1994060] [NEW] dkms drivers not built or installed

2022-10-24 Thread mike Bernson

Public bug reported:

The system updated kernels to 5.17.0-1020-oem from 5.15.0-52-generic
The dkms driver did not install on the new kernel.

I Have 3 dkms drivers installed. They all build on 5.15.0.52 kernel.

I have look and the lib/modules/kenerl-version/update does not exists

The 3 dkms moudles:

nvidia/520.56.06
virtualbox/6.1.38
zfs/2.1.6, 5.15.0-52-generic

mike@mike-think:/lib/modules$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy

mike@mike-think:/lib/modules$ uname -a
Linux mike-think 5.17.0-1020-oem #21-Ubuntu SMP PREEMPT Fri Oct 14 09:33:24 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux


mike@mike-think:/lib/modules/5.17.0-1020-oem$ ls
initrd/modules.builtin.bin  modules.softdep
kernel/modules.builtin.modinfo  modules.symbols
modules.alias  modules.dep  modules.symbols.bin
modules.alias.bin  modules.dep.bin  vdso/
modules.builtinmodules.devname
modules.builtin.alias.bin  modules.order

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21
ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
Uname: Linux 5.17.0-1020-oem x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Oct 24 14:07:31 2022
InstallationDate: Installed on 2020-03-30 (937 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-oem-5.17
UpgradeStatus: Upgraded to jammy on 2022-10-07 (16 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  dkms drivers not built or installed

Status in linux-signed-oem-5.17 package in Ubuntu:
  New

Bug description:
  The system updated kernels to 5.17.0-1020-oem from 5.15.0-52-generic
  The dkms driver did not install on the new kernel.

  I Have 3 dkms drivers installed. They all build on 5.15.0.52 kernel.

  I have look and the lib/modules/kenerl-version/update does not exists

  The 3 dkms moudles:

  nvidia/520.56.06
  virtualbox/6.1.38
  zfs/2.1.6, 5.15.0-52-generic

  mike@mike-think:/lib/modules$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  Codename: jammy

  mike@mike-think:/lib/modules$ uname -a
  Linux mike-think 5.17.0-1020-oem #21-Ubuntu SMP PREEMPT Fri Oct 14 09:33:24 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux


  mike@mike-think:/lib/modules/5.17.0-1020-oem$ ls
  initrd/  modules.builtin.bin  modules.softdep
  kernel/  modules.builtin.modinfo  modules.symbols
  modules.aliasmodules.dep  modules.symbols.bin
  modules.alias.binmodules.dep.bin  vdso/
  modules.builtin  modules.devname
  modules.builtin.alias.bin  modules.order

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.17.0-1020-oem 5.17.0-1020.21
  ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
  Uname: Linux 5.17.0-1020-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Oct 24 14:07:31 2022
  InstallationDate: Installed on 2020-03-30 (937 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-5.17
  UpgradeStatus: Upgraded to jammy on 2022-10-07 (16 days ago)

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


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

[Kernel-packages] [Bug 1994059] Re: NVME down errors after kernel update

2022-10-24 Thread EPx

Picture of dmesg errors

** Attachment added: "PXL_20221023_041635766.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994059/+attachment/5626470/+files/PXL_20221023_041635766.jpg

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

Title:
  NVME down errors after kernel update

Status in linux package in Ubuntu:
  New

Bug description:
  After the latest kernel update (from 5.15.0-50-generic to
  5.15.0-52-generic) some NVME errors show up in dmesg like

  nvme nvme0: controller is down; will reset: CSTS=0x PCI_STATUS=0x10
  nvme :01:00.0: enabling device ( -> 0002)
  nvme nvme0: Removing after probe failure status: -19
  nvme0n1: detected capacity change from 1000215216 to 0

  (Typed from a picture, could not send actual dmesg since the machine
  freezes shortly after losing the root filesystem and no new program
  can be loaded.)

  Tried some tricks like kernel parameters
  nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off, suggested in
  the Internet to solve similar problems. It only seems to delay the
  freeze average time from 20-30 min to 120-180 min but does not solve
  the issue.

  Going back to kernel 5.15.0-50 seems to have stabilized the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  epx1175 F pipewire-media-
epx1176 F pulseaudio
   /dev/snd/seq:epx1174 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 14:57:35 2022
  InstallationDate: Installed on 2022-10-17 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XDA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash mitigations=off 
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P17CFB.044.220223.HQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP550XDA-KH3BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLB187A0D-C01-G001-S0001+10.0.22000
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP17CFB.044.220223.HQ:bd02/23/2022:br5.19:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XDA:pvrP17CFB:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XDA-KH3BR:rvrSGLB187A0D-C01-G001-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-TGL3-PCFB:
  dmi.product.family: Notebook Plus2
  dmi.product.name: 550XDA
  dmi.product.sku: SCAI-A5A5-A5A5-TGL3-PCFB
  dmi.product.version: P17CFB
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Kernel-packages] [Bug 1994059] [NEW] NVME down errors after kernel update

2022-10-24 Thread EPx

Public bug reported:

After the latest kernel update (from 5.15.0-50-generic to
5.15.0-52-generic) some NVME errors show up in dmesg like

nvme nvme0: controller is down; will reset: CSTS=0x PCI_STATUS=0x10
nvme :01:00.0: enabling device ( -> 0002)
nvme nvme0: Removing after probe failure status: -19
nvme0n1: detected capacity change from 1000215216 to 0

(Typed from a picture, could not send actual dmesg since the machine
freezes shortly after losing the root filesystem and no new program can
be loaded.)

Tried some tricks like kernel parameters
nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off, suggested in
the Internet to solve similar problems. It only seems to delay the
freeze average time from 20-30 min to 120-180 min but does not solve the
issue.

Going back to kernel 5.15.0-50 seems to have stabilized the machine.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-52-generic 5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  epx1175 F pipewire-media-
  epx1176 F pulseaudio
 /dev/snd/seq:epx1174 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 24 14:57:35 2022
InstallationDate: Installed on 2022-10-17 (6 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XDA
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash mitigations=off 
nvme_core.default_ps_max_latency_us=0 pcie_aspm=off vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-50-generic N/A
 linux-backports-modules-5.15.0-50-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P17CFB.044.220223.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP550XDA-KH3BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLB187A0D-C01-G001-S0001+10.0.22000
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP17CFB.044.220223.HQ:bd02/23/2022:br5.19:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XDA:pvrP17CFB:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XDA-KH3BR:rvrSGLB187A0D-C01-G001-S0001+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-TGL3-PCFB:
dmi.product.family: Notebook Plus2
dmi.product.name: 550XDA
dmi.product.sku: SCAI-A5A5-A5A5-TGL3-PCFB
dmi.product.version: P17CFB
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug jammy

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

Title:
  NVME down errors after kernel update

Status in linux package in Ubuntu:
  New

Bug description:
  After the latest kernel update (from 5.15.0-50-generic to
  5.15.0-52-generic) some NVME errors show up in dmesg like

  nvme nvme0: controller is down; will reset: CSTS=0x PCI_STATUS=0x10
  nvme :01:00.0: enabling device ( -> 0002)
  nvme nvme0: Removing after probe failure status: -19
  nvme0n1: detected capacity change from 1000215216 to 0

  (Typed from a picture, could not send actual dmesg since the machine
  freezes shortly after losing the root filesystem and no new program
  can be loaded.)

  Tried some tricks like kernel parameters
  nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off, suggested in
  the Internet to solve similar problems. It only seems to delay the
  freeze average time from 20-30 min to 120-180 min but does not solve
  the issue.

  Going back to kernel 5.15.0-50 seems to have stabilized the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-52-generic 5.15.0-52.58
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  epx1175 F pipewire-media-
epx1176 F pulseaudio
   /dev/snd/seq:epx1174 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 14:57:35 2022
  InstallationDate: Installed on 2022-10-17 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release

[Kernel-packages] [Bug 1905261] Re: Openssl ignores order from /etc/nsswitch.conf

2022-10-24 Thread Dan Bungert

While my strace output looks similar, it may be still working as
intended.  I added a hosts entry for ubuntu.com pointing to a different
server, and received output indicating that I connected to the other
server.  Perhaps that has been fixed since the bug was filed?
Alternately, would you update with more steps to reproduce?

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

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

Title:
  Openssl ignores order from /etc/nsswitch.conf

Status in linux-meta package in Ubuntu:
  Incomplete
Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  
  I'm issuing command like below:
  openssl s_client -connect subdomain.domain.example.com

  I have following nsswitch.confg defined:
  '''
  $ cat /etc/nsswitch.conf 
  # /etc/nsswitch.conf
  #
  # Example configuration of GNU Name Service Switch functionality.
  # If you have the `glibc-doc-reference' and `info' packages installed, try:
  # `info libc "Name Service Switch"' for information about this file.

  passwd: compat systemd
  group:  compat systemd
  shadow: compat

  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns myhostname
  networks:   files

  protocols:  db files
  services:   db files
  ethers: db files
  rpc:db files

  netgroup:   nis
  '''

  
  For host resolution /etc/hosts file should take precedence. But it doesn't 
work that way and when I have some unresolvable name it tries to connect to DNS 
ignoring local hosts file. The order can be clearly visible in strace:

  
  '''openat(AT_FDCWD, "/usr/lib/ssl/ct_log_list.cnf", O_RDONLY) = -1 ENOENT (No 
such file or directory)
  openat(AT_FDCWD, "/usr/lib/ssl/cert.pem", O_RDONLY) = -1 ENOENT (No such file 
or directory)
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  openat(AT_FDCWD, "/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=560, ...}) = 0
  read(5, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 560
  read(5, "", 4096)   = 0
  close(5)= 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  openat(AT_FDCWD, "/etc/host.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=93, ...}) = 0
  read(5, "# The \"order\" line is only used "..., 4096) = 93
  read(5, "", 4096)   = 0
  close(5)= 0
  futex(0x7f3d2d2b5ba4, FUTEX_WAKE_PRIVATE, 2147483647) = 0
  openat(AT_FDCWD, "/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  read(5, "# Generated by NetworkManager\nse"..., 4096) = 64
  read(5, "", 4096)   = 0
  close(5)= 0
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=335124, ...}) = 0
  mmap(NULL, 335124, PROT_READ, MAP_PRIVATE, 5, 0) = 0x7f3d2de05000
  close(5)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", 
O_RDONLY|O_CLOEXEC) = 5
  read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P#\0\0\0\0\0\0"..., 
832) = 832
  fstat(5, {st_mode=S_IFREG|0644, st_size=47568, ...}) = 0
  mmap(NULL, 2168632, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f3d2cab
  mprotect(0x7f3d2cabb000, 2093056, PROT_NONE) = 0
  mmap(0x7f3d2ccba000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0xa000) = 0x7f3d2ccba000
  mmap(0x7f3d2ccbc000, 22328, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3d2ccbc000
  close(5)= 0
  mprotect(0x7f3d2ccba000, 4096, PROT_READ) = 0
  munmap(0x7f3d2de05000, 335124)  = 0
  openat(AT_FDCWD, "/etc/hosts", O_RDONLY|O_CLOEXEC) = 5
  '''

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
  Uname: Linux 4.15.0-124-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  Date: Mon Nov 23 10:49:41 2020
  InstallationDate: Installed on 2015-05-08 (2026 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)

[Kernel-packages] [Bug 1905261] Re: Openssl ignores order from /etc/nsswitch.conf

2022-10-24 Thread Dan Bungert

Looks like the linux-meta task was added recently, was that intended?
I'm not certain that this would be a kernel bug.   Marking that part
incomplete - additional info would help.

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

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

Title:
  Openssl ignores order from /etc/nsswitch.conf

Status in linux-meta package in Ubuntu:
  Incomplete
Status in openssl package in Ubuntu:
  New

Bug description:
  
  I'm issuing command like below:
  openssl s_client -connect subdomain.domain.example.com

  I have following nsswitch.confg defined:
  '''
  $ cat /etc/nsswitch.conf 
  # /etc/nsswitch.conf
  #
  # Example configuration of GNU Name Service Switch functionality.
  # If you have the `glibc-doc-reference' and `info' packages installed, try:
  # `info libc "Name Service Switch"' for information about this file.

  passwd: compat systemd
  group:  compat systemd
  shadow: compat

  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns myhostname
  networks:   files

  protocols:  db files
  services:   db files
  ethers: db files
  rpc:db files

  netgroup:   nis
  '''

  
  For host resolution /etc/hosts file should take precedence. But it doesn't 
work that way and when I have some unresolvable name it tries to connect to DNS 
ignoring local hosts file. The order can be clearly visible in strace:

  
  '''openat(AT_FDCWD, "/usr/lib/ssl/ct_log_list.cnf", O_RDONLY) = -1 ENOENT (No 
such file or directory)
  openat(AT_FDCWD, "/usr/lib/ssl/cert.pem", O_RDONLY) = -1 ENOENT (No such file 
or directory)
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(5)= 0
  openat(AT_FDCWD, "/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=560, ...}) = 0
  read(5, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 560
  read(5, "", 4096)   = 0
  close(5)= 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  openat(AT_FDCWD, "/etc/host.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=93, ...}) = 0
  read(5, "# The \"order\" line is only used "..., 4096) = 93
  read(5, "", 4096)   = 0
  close(5)= 0
  futex(0x7f3d2d2b5ba4, FUTEX_WAKE_PRIVATE, 2147483647) = 0
  openat(AT_FDCWD, "/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
  read(5, "# Generated by NetworkManager\nse"..., 4096) = 64
  read(5, "", 4096)   = 0
  close(5)= 0
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=335124, ...}) = 0
  mmap(NULL, 335124, PROT_READ, MAP_PRIVATE, 5, 0) = 0x7f3d2de05000
  close(5)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libnss_files.so.2", 
O_RDONLY|O_CLOEXEC) = 5
  read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P#\0\0\0\0\0\0"..., 
832) = 832
  fstat(5, {st_mode=S_IFREG|0644, st_size=47568, ...}) = 0
  mmap(NULL, 2168632, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f3d2cab
  mprotect(0x7f3d2cabb000, 2093056, PROT_NONE) = 0
  mmap(0x7f3d2ccba000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0xa000) = 0x7f3d2ccba000
  mmap(0x7f3d2ccbc000, 22328, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3d2ccbc000
  close(5)= 0
  mprotect(0x7f3d2ccba000, 4096, PROT_READ) = 0
  munmap(0x7f3d2de05000, 335124)  = 0
  openat(AT_FDCWD, "/etc/hosts", O_RDONLY|O_CLOEXEC) = 5
  '''

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
  Uname: Linux 4.15.0-124-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  Date: Mon Nov 23 10:49:41 2020
  InstallationDate: Installed on 2015-05-08 (2026 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (819 days ago)

To manage

[Kernel-packages] [Bug 1993205] Re: EXT4-fs errors on black screen after resume from sleep

2022-10-24 Thread Anton Keks

The failing stack already has a patch:
https://bugzilla.kernel.org/show_bug.cgi?id=216266


** Bug watch added: Linux Kernel Bug Tracker #216266
   https://bugzilla.kernel.org/show_bug.cgi?id=216266

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

Title:
  EXT4-fs errors on black screen after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some time after updating to Ubuntu 22.04 and Kernel 5.15, Intel Tiger
  Lake laptop started getting black screen and EXT4-fs errors 10-20
  seconds after resume from sleep. This is reproducible approximately
  every other time, i.e. sometimes the resume works normally.

  Usually, after resume I can enter GDM password, unlock the desktop and
  see running apps, but soon when they start writing to the disk (NVME),
  the screen goes blank with a bunch of errors regarding read-only
  filesystem, unable to unmount partitions, etc.

  Upgrading to Ubuntu 22.10 / Kernel 5.19 does not fix the issue. The
  same laptop worked flawlessly before Ubuntu 22.04.

  After hard reset and boot, the system works normally.

  The logs are not written anywhere besides the screen.

  OCR from an photo using Google Lens:

  [19449.602615) systemd[9792) home.mount: Failed at step EXEC spawning 
/bin/umount: Input/output error
  [19449.609995) systemd[1]: Failed unmounting /home.
  [19449.932421] systemd[9794): docker.service: Failed at step EXEC spawning 
/usr/bin/dockerd: Input/output error
  [19449.959791) systemd[1]: Failed to start Docker Application Container 
Engine.
  [19452.164163) systemd[9795): docker.service: Failed at step EXEC spawning 
/usr/bin/dockerd: Input/output error
  [19452.165445] systemd[1]: Failed to start Docker Application Container 
Engine.
  [19454.397310] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#655370: comm systemd: reading directory Iblock o
  [19454.397999) EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#2: comm systemd: reading directory 1block o
  [19454.997891] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#655370: comm systemd: reading directory 1block 0
  [19454.397949] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#2: comm systemd: reading directory Iblock o
  [19454.420294] systemd[9797]: docker.service: Failed at step EXEC spawning 
/usr/bin/dockerd: Input/output error
  119454.421508] systemd[1]: Failed to start Docker Application Container 
Engine.
  [19456.207832 EXT4-fs error (device nvmeon1p5): __ext4_find_entry: 1658: 
inode #922214: comm gmain: reading directory Iblock 0
  [19456.264664 EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode 
#1187760: comm gmain: reading directory Iblock o
  [13456.264765] EXT4-fs error (device Avme0n1p5): ext4_find_entry: 1658: inode 
#1187760: comm gmain: reading directory Iblock o
  [19456.264816] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode 
#1187760: comm gmain: reading directory Iblock 0
  [13456.467816] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode 
#1179649: comm thermald: reading directory Iblock 0
  [13456.468150] EXT4-fs error (device nvmeon1p5): __ext4_find_entry: 1658: 
inode #1179649: comm thermald: reading directory lblock 0
  113456.648475] systemd[1]: Failed to start Docker Application Container 
Engine.
  113459.330449] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode 
#48896417: comm Daemon periodic: reading directory Iblock
  [13459.330594] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode 
#48896417: comm Daemon periodic: reading directory Iblock
  [13459.330680] EXT4-fs error (device nvmeon1p6): ext4_find_entry: 1658: inode 
#48896417: comm Daemon periodic: reading directory lblock
  113459.420371] systemd [9799]: gpu-manager.service: Failed at step EXEC 
spawning /usr/bin/gpu-manager: Input/output error
  113459.421974] systemd[1]: Failed to start Detect the available GPUS and deal 
with any system changes
  113459.424728] systemd [9800]: gdm.service: Failed at step EXEC spawning 
/usr/share/gdm/generate-config: Input/output error
  [13459.426019] systemd[1]: Failed to start GNOME Display Manager.
  113459.647301] EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode 
#1315384: comm systemd-logind: reading directory Iblock 0
  113459.649171] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode 
#45744136: comm systemd: reading directory lblock 0
  113459.649295] EXT4-fs error (device nvme0n1p6): ext4_find_entry: 1658: inode 
#45744134: comm systemd: reading directory lblock 0
  113459.649318] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#1315384: comm systemd-logind: reading directory lblock 0
  113459.649359] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#922214: comm systemd: reading directory lblock 0
  113459.649472] EXT4-fs error

[Kernel-packages] [Bug 1993205] Re: EXT4-fs errors on black screen after resume from sleep

2022-10-24 Thread Anton Keks

I tried mainline kernels in Ubuntu 22.10:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.0.3/ - resume now
works, but both resume and suspend are really slow (20+ seconds)

https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.1-rc1/ - works as
well, without the long delay

Probably something was finally fixed in the kernel.

Note: mainline 6.x kernels also log the following error:

[   49.449840] Freezing user space processes ... (elapsed 0.002 seconds) done.
[   49.452576] OOM killer disabled.
[   49.452578] Freezing remaining freezable tasks ... (elapsed 2.760 seconds) 
done.
[   52.216297] printk: Suspending console(s) (use no_console_suspend to debug)
[   52.594630] ACPI: EC: interrupt blocked
[   52.637203] 

[   52.637205] UBSAN: array-index-out-of-bounds in 
/home/kernel/COD/linux/drivers/acpi/acpica/dswexec.c:401:12
[   52.637208] index -1 is out of range for type 'acpi_operand_object *[9]'
[   52.637210] CPU: 0 PID: 240 Comm: kworker/u16:4 Tainted: G U OE  
6.1.0-060100rc1-generic #202210162332
[   52.637214] Hardware name: ASUSTeK COMPUTER INC. ZenBook 
UX393EA_UX393EA/UX393EA, BIOS UX393EA.312 04/22/2022
[   52.637216] Workqueue: events_unbound async_run_entry_fn
[   52.637224] Call Trace:
[   52.637226]  
[   52.637229]  show_stack+0x4e/0x61
[   52.637234]  dump_stack_lvl+0x4a/0x6f
[   52.637241]  dump_stack+0x10/0x18
[   52.637245]  ubsan_epilogue+0x9/0x43
[   52.637249]  __ubsan_handle_out_of_bounds.cold+0x42/0x47
[   52.637253]  acpi_ds_exec_end_op+0x1ca/0x828
[   52.637259]  acpi_ps_parse_loop+0x58d/0x678
[   52.637263]  acpi_ps_parse_aml+0x2e6/0x59e
[   52.637265]  acpi_ps_execute_method+0x241/0x315
[   52.637269]  acpi_ns_evaluate+0x34c/0x515
[   52.637273]  acpi_evaluate_object+0x212/0x3a5
[   52.637275]  __acpi_power_off+0x26/0x70
[   52.637279]  acpi_power_off_unlocked+0x54/0x90
[   52.637283]  acpi_power_off_list.isra.0+0x43/0xa0
[   52.637287]  acpi_power_transition+0xab/0x100
[   52.637291]  acpi_device_set_power+0x319/0x470
[   52.637295]  ? _raw_spin_lock_irqsave+0xe/0x20
[   52.637298]  acpi_pci_set_power_state+0x98/0x150
[   52.637303]  pci_set_power_state+0x9f/0x220
[   52.637306]  ? acpi_pci_choose_state+0x26/0x50
[   52.637309]  pci_prepare_to_sleep+0x7e/0xd0
[   52.637312]  pci_pm_suspend_noirq+0x1f7/0x2c0
[   52.637316]  ? pci_pm_suspend_late+0x50/0x50
[   52.637319]  dpm_run_callback+0x63/0x160
[   52.637322]  __device_suspend_noirq+0x8f/0x290
[   52.637325]  async_suspend_noirq+0x23/0x70
[   52.637327]  async_run_entry_fn+0x30/0x130
[   52.637331]  process_one_work+0x222/0x400
[   52.637334]  worker_thread+0x50/0x3e0
[   52.637337]  ? process_one_work+0x400/0x400
[   52.637339]  kthread+0xe6/0x110
[   52.637342]  ? kthread_complete_and_exit+0x20/0x20
[   52.637344]  ret_from_fork+0x1f/0x30
[   52.637350]  
[   52.637351] 

[   60.734902] ACPI: EC: interrupt unblocked
[   61.575520] pcieport 1:e0:1d.0: can't derive routing for PCI INT A
[   61.575528] nvme 1:e1:00.0: PCI INT A: no GSI
[   61.576151] i915 :00:02.0: [drm] GuC firmware i915/tgl_guc_70.1.1.bin 
version 70.1.1
[   61.576157] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin 
version 7.9.3
[   61.580528] i915 :00:02.0: [drm] HuC authenticated
[   61.580535] i915 :00:02.0: [drm] GuC submission disabled
[   61.580537] i915 :00:02.0: [drm] GuC SLPC disabled
[   61.580970] nvme nvme0: 8/0/0 default/read/poll queues
[   61.905786] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_component_ops [i915])
[   61.906125] OOM killer enabled.
[   61.906128] Restarting tasks ... 
[   61.906449] mei_pxp :00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 
:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[   61.922392] done.
[   61.922431] random: crng reseeded on system resumption
[   61.935746] thermal thermal_zone6: failed to read out thermal zone (-61)
[   61.949978] PM: suspend exit

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

Title:
  EXT4-fs errors on black screen after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some time after updating to Ubuntu 22.04 and Kernel 5.15, Intel Tiger
  Lake laptop started getting black screen and EXT4-fs errors 10-20
  seconds after resume from sleep. This is reproducible approximately
  every other time, i.e. sometimes the resume works normally.

  Usually, after resume I can enter GDM password, unlock the desktop and
  see running apps, but soon when they start writing to the disk (NVME),
  the screen goes blank with a bunch of errors regarding read-only
  filesystem, unable to unmount partitions, etc.

  Upgrading to Ubuntu 22.10 / Kernel 5.19 does not fix the issue.

[Kernel-packages] [Bug 1992667] Re: Application windows invisible (on DG2 graphics)

yes, mesa 22.2.x is a part of the hwe stack

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

Title:
  Application windows invisible (on DG2 graphics)

Status in linux-oem-6.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New

Bug description:
  When using GNOME Shell with Wayland, all application windows become
  invisible from time to time. This usually happens right after starting
  GNOME Shell for the first time or after having a VRAM intensive
  application open, such as a game.

  I have installed the latest linux-oem-6.0 kernel and manually enabled
  support for DG2 graphics by passing the i915.force_probe parameter
  with the PCIe ID of the graphics card.

  I have attached a screenshot of the described behavior below.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 17:23:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1993936] Re: Laptop battery stays 100% while discharging

2022-10-24 Thread soumyajyoti

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

** Summary changed:

- Laptop battery stays 100% while discharging
+ Laptop battery stays 100%(or whatever percentage of battery it started with) 
while discharging

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

Title:
  Laptop battery stays 100%(or whatever percentage of battery it started
  with) while discharging

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  I have recently upgraded from 22.04 to 22.10.
  The battery remains at 100% or whatever percentage of battery it started with 
. The system do not identify the plugging in of the ac adapter and neither 
removing of it.
  My system is Asus TUF A15 FA506II-FA566II.
  The battery is correctly detected in Windows 11 and worked like a charm in 
the 22.04 version.
  ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  soumyajyoti   2539 F wireplumber
   /dev/snd/controlC0:  soumyajyoti   2539 F wireplumber
   /dev/snd/controlC1:  soumyajyoti   2539 F wireplumber
   /dev/snd/seq:soumyajyoti   2536 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-11-22 (699 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506II_FA566II
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/12/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506II.316
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506II
  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.ec.firmware.release: 3.12
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506II.316:bd03/12/2021:br5.16:efr3.12:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming A15
  dmi.product.name: ASUS TUF Gaming A15 FA506II_FA566II
  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/upower/+bug/1993936/+subscriptions


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

debian has 2.2.2, so LL should just sync it once it's opened

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

** Changed in: linux-oem-6.0 (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1971712

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  Fix resume on AMD platforms when TBT monitor is plugged

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  When TBT monitor is connected to AMD platform, system resume will hit
  stack corruption or BUG_ON() macro.

  [Fix]
  Revert the offending commit and handle MST properly.

  [Test]
  The system can resume normally and no more kernel splat.
   
  [Where problems could occur]
  The new logic is restriced to MST hub, so normal DP/HDMI usage should be
  unaffected.

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


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

[Kernel-packages] [Bug 1980621] Re: Fix blank screen on Thinkpad ADL 4K+ panel

** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  Fix blank screen on Thinkpad ADL 4K+ panel

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Won't Fix
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  It's a upstream kernel regression.
  And reverted by upstream.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  Low risk, it reverts a regression and may break i915 driver.

  On 5.14-oem and Jammy kernel, This commit was claimed to backport
  commit 73867c8709b5 ("drm/i915/display: Remove check for low voltage sku for 
max dp source rate")
  But it's not kind of it.
  So revert it instead.

  On 5.17 kernel, revert it by upstream commit.

  Unstable kernel already got it.

  
  V2:
  [Impact]
  Set screen off on ThinkPad P1G5 with 4k+ panel.
  The screen will never be back.

  [Fix]
  Reload link rate as WA to fix the issue.

  [Test]
  Verified on hardware, screen on/off 20 times OK.

  [Where problems could occur]
  It may break DP output on Intel platform.

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


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

[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

2022-10-24 Thread Dan Meyers

Hi Andrea, I was seeing the problem quite frequently (maybe every 5-10
minutes), although I haven't seen it in the past 30 minutes, since I've
updated to your kernel.

And since this is related to i915, I'm also going to mention that I see
some visual distortions on the screen when I move my mouse across a
specific area of the screen. The distortions are multi-colored
horizontal lines that stretch all the way across the display. This issue
also existed prior to installing your test kernel. Anyhow, just thought
I'd mention it in case it could be somehow related to something that
went missing along the way (22.04 works beautifully for me).

Thanks for the quick fix on the stability issues!

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

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant

[Kernel-packages] [Bug 1989041] Re: Add iommu passthrough quirk for Intel IPU6 on RaptorLake

** Changed in: linux-oem-6.0 (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/1989041

Title:
  Add iommu passthrough quirk for Intel IPU6 on RaptorLake

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Intel iommu was turned on by default in mainline build v5.15.5 or jammy
  -generic kernel 5.15.0-12.12. This would breaks IPU6.

  For TGL and ADL platforms, it has been fixed in bug 1958004 for oem-5.14 and
  above. This patch adds a new ID for RPL.

  [Fix]

  Use IOMMU passthrough mode for IPU6 as it has its own iommu hardware.

  [Test Case]

  Apply the fix and kernel should print a new info line:

Passthrough IOMMU for integrated Intel IPU

  and IPU6 camera should continue to work without intel_iommu=off
  work-around.

  [Where problems could occur]

  No. That's what it should have been done.

  [Other Info]

  Nominates only oem-6.0 and unstable for we have RPL IPU6 enabled on oem-6.0
  and newer.

  == original bug report ==

  Per
  
https://github.com/intel/ipu6-drivers/commit/89c6b99e4bec00a04b53f37cd8c3c01ce824a4ab,
  an additional quirk is necessary for Intel IPU6 on Raptor Lake as
  previous TGL/ADL do.

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


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

[Kernel-packages] [Bug 1993936] Re: Laptop battery stays 100% while discharging

2022-10-24 Thread soumyajyoti

** Description changed:

  I have recently upgraded from 22.04 to 22.10.
- The battery remains at 100% . The system do not identify the plugging in of 
the ac adapter and neither removing of it.
+ The battery remains at 100% or whatever percentage of battery it started with 
. The system do not identify the plugging in of the ac adapter and neither 
removing of it.
  My system is Asus TUF A15 FA506II-FA566II.
  The battery is correctly detected in Windows 11 and worked like a charm in 
the 22.04 version.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  soumyajyoti   2539 F wireplumber
-  /dev/snd/controlC0:  soumyajyoti   2539 F wireplumber
-  /dev/snd/controlC1:  soumyajyoti   2539 F wireplumber
-  /dev/snd/seq:soumyajyoti   2536 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  soumyajyoti   2539 F wireplumber
+  /dev/snd/controlC0:  soumyajyoti   2539 F wireplumber
+  /dev/snd/controlC1:  soumyajyoti   2539 F wireplumber
+  /dev/snd/seq:soumyajyoti   2536 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-11-22 (699 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506II_FA566II
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.19.0-23-generic N/A
-  linux-backports-modules-5.19.0-23-generic  N/A
-  linux-firmware 20220923.gitf09bebf3-0ubuntu1
+  linux-restricted-modules-5.19.0-23-generic N/A
+  linux-backports-modules-5.19.0-23-generic  N/A
+  linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/12/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506II.316
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506II
  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.ec.firmware.release: 3.12
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506II.316:bd03/12/2021:br5.16:efr3.12:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA506II_FA566II:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506II:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming A15
  dmi.product.name: ASUS TUF Gaming A15 FA506II_FA566II
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  Laptop battery stays 100% while discharging

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have recently upgraded from 22.04 to 22.10.
  The battery remains at 100% or whatever percentage of battery it started with 
. The system do not identify the plugging in of the ac adapter and neither 
removing of it.
  My system is Asus TUF A15 FA506II-FA566II.
  The battery is correctly detected in Windows 11 and worked like a charm in 
the 22.04 version.
  ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  soumyajyoti   2539 F wireplumber
   /dev/snd/controlC0:  soumyajyoti   2539 F wireplumber
   /dev/snd/controlC1:  soumyajyoti   2539 F wireplumber
   /dev/snd/seq:soumyajyoti   2536 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-11-22 (699 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA506II_FA566II
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=80cc1579-96aa-4743-aef2-d67dbff067cb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session

[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169

not fixed in kinetic and up

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

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

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

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

Title:
  Can only reach PC3 when ethernet is plugged r8169

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-5.13 source package in Kinetic:
  Invalid
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  System only can reach PC3, and it affects power consumption alot.

  [Fix]
  Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state 
issue, but also fixes network speed issue.
  V7:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/
  V6:
  
https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/

  
  [Test]
  Verified on 2 different systems which has PC state issue and has network 
speed issue, these patches fix both issues.

  [Where problems could occur]
  It toggles ASPM on and off depends on the network traffic during runtime, I 
don't think it'll lead to any regressions. Some potential issues have been 
addressed during the patch submitting. It's v6 now and accepted by upstream.

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


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

[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode

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

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

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: New => Invalid

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

Title:
  RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror
  mode

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  The Screen is shaking connected monitor to Onboard HDMI port.

  [Fix]
  The interlaced mode is not supported for Intel Gen 12 onwards.
  Disable interlaced mode for DP on Display >= 12.

  Due to schedule, SRU for OEM kernels first.
  After these patches are merged to mainline/drmtip kernel, will SRU for 
generic kernels.

  [Test Case]
  1.Connected two external Monitor to the onboard HDMI/DP port .
  2.Boot OS.
  2.set mirror mode. (onboard HDMI / onboard DP)
  3.check if screen shakes.

  [Where problems could occur]
  Low, Remove interlace support for Display >= 12 so it wouldn't cause a 
regression.

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

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

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1994038] [NEW] Jammy update: v6.0.3 upstream stable release

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

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

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Jammy update: v6.0.3 upstream stable release

Status in linux-oem-6.0 package in Ubuntu:
  Confirmed
Status in linux-oem-6.0 source package in Jammy:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

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

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


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

[Kernel-packages] [Bug 1992572] Re: Samba crashes in gnutls at logon

2022-10-24 Thread Peter Metzler

Here are a comparisions of the cpu flags beetween 5.15.71-051571-generic
(works) and 5.15.0-52-generic (works not)

5.15.71-051571-generic: 
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush 
mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon 
nopl xtopology tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq 
ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes 
xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault 
invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 avx2 
smep bmi2 invpcid avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd 
avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves arat pku ospke avx512_vnni 
md_clear flush_l1d arch_capabilities

5.15.0-52-generic:  
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush 
mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon 
nopl xtopology tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq 
ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes
   f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single 
ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 smep bmi2 invpcid 
rdseed adx smap clflushopt clwb arat md_clear flush_l1d arch_capabilities

The 5.15.71-051571-generic image has more flags:
fma xsave avx avx2 avx512f avx512dq avx512cd avx512bw avx512vl xsaveopt xsavec 
xgetbv1 xsaves pku ospke avx512_vnni

This could make the difference.

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

Title:
  Samba crashes in gnutls at logon

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows a lot of:

  [ 8665.587829] traps: smbd[4612] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.617605] traps: smbd[4614] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.649484] traps: smbd[4616] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.676820] traps: smbd[4618] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.701019] traps: smbd[4620] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.726626] traps: smbd[4622] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.747612] traps: smbd[4624] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.768710] traps: smbd[4626] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.790433] traps: smbd[4628] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.821738] traps: smbd[4630] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]

  entries and logon from an windows 10 workstation failes.

  Mainline Kernel version 5.15.71 works!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Okt 12 09:35 seq
   crw-rw+ 1 root audio 116, 33 Okt 12 09:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 09:41:59 2022
  HibernationDevice: RESUME=UUID=3d1cb136-8319-4996-b9f7-44a9c63cad8c
  InstallationDate: Installed on 2015-07-06 (2654 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc.

[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

2022-10-24 Thread Andrea Righi

I noticed that we're missing some i915 fixes from stable updates, so
I've applied a bunch of patches from stable and produced this test
kernel:

https://kernel.ubuntu.com/~arighi/lp-1993818/

It'd be great if someone affected by this bug could give it a try and
verify if the problem is still happening. Thanks in advance!

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

Title:
  Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Been experiencing random hangs since upgraded to 22.10.

  Looking at /var/log/kern.log after crash I'm seeing general protection
  fault from /var/log/kern.log.

  Oct 21 20:41:38 tyrant kernel: [  281.051619] general protection fault, 
probably for non-canonical address 0x258d1b207028:  [#1] PREEMPT SMP 
NOPTI
  Oct 21 20:41:38 tyrant kernel: [  281.051629] CPU: 13 PID: 2445 Comm: 
gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu
  Oct 21 20:41:38 tyrant kernel: [  281.051633] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
  Oct 21 20:41:38 tyrant kernel: [  281.051636] RIP: 0010:rm_hole+0x1a7/0x340 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051676] Code: 8b 78 08 eb 1c 48 89 50 
28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 
8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 
4f 28 48 39
  Oct 21 20:41:38 tyrant kernel: [  281.051679] RSP: 0018:ac26834ab9c0 
EFLAGS: 00010206
  Oct 21 20:41:38 tyrant kernel: [  281.051683] RAX: 90258161d1b0 RBX: 
902580fd7800 RCX: 258d1b207000
  Oct 21 20:41:38 tyrant kernel: [  281.051686] RDX: 0003ccf0 RSI: 
9025a4351528 RDI: 0090
  Oct 21 20:41:38 tyrant kernel: [  281.051688] RBP: ac26834ab9e0 R08: 
 R09: 
  Oct 21 20:41:38 tyrant kernel: [  281.051690] R10: 902580fd7870 R11: 
902581747740 R12: 902580fd7858
  Oct 21 20:41:38 tyrant kernel: [  281.051692] R13: 9025a4351528 R14: 
9025a43515f8 R15: 0011
  Oct 21 20:41:38 tyrant kernel: [  281.051694] FS:  7f553c5d45c0() 
GS:902cbf74() knlGS:
  Oct 21 20:41:38 tyrant kernel: [  281.051697] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 21 20:41:38 tyrant kernel: [  281.051700] CR2: 7f35e73685c0 CR3: 
00013119a001 CR4: 00770ee0
  Oct 21 20:41:38 tyrant kernel: [  281.051702] PKRU: 5554
  Oct 21 20:41:38 tyrant kernel: [  281.051704] Call Trace:
  Oct 21 20:41:38 tyrant kernel: [  281.051707]  
  Oct 21 20:41:38 tyrant kernel: [  281.051711]  
drm_mm_insert_node_in_range+0x26a/0x500 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.051745]  
_i915_gem_object_stolen_init+0x28c/0x2e0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051871]  
__i915_gem_object_create_region+0xb2/0x170 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.051977]  
i915_gem_object_create_region+0x1e/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052080]  
i915_gem_object_create_stolen+0x19/0x30 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052184]  intel_dpt_create+0x20b/0x2c0 
[i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052299]  
intel_framebuffer_init+0x749/0x960 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052408]  ? 
kmem_cache_alloc_trace+0x189/0x310
  Oct 21 20:41:38 tyrant kernel: [  281.052414]  
intel_framebuffer_create+0x40/0x90 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052521]  
intel_user_framebuffer_create+0xf8/0x1d0 [i915]
  Oct 21 20:41:38 tyrant kernel: [  281.052626]  
drm_internal_framebuffer_create+0xb3/0x150 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052667]  drm_mode_addfb2+0x44/0xd0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052705]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052743]  drm_mode_addfb2_ioctl+0xe/0x20 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052780]  drm_ioctl_kernel+0xd3/0x180 
[drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052811]  drm_ioctl+0x29d/0x4d0 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052840]  ? 
drm_mode_addfb_ioctl+0x20/0x20 [drm]
  Oct 21 20:41:38 tyrant kernel: [  281.052879]  __x64_sys_ioctl+0x9d/0xe0
  Oct 21 20:41:38 tyrant kernel: [  281.052884]  do_syscall_64+0x58/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052888]  ? __do_sys_kcmp+0x208/0x550
  Oct 21 20:41:38 tyrant kernel: [  281.052894]  ? 
exit_to_user_mode_prepare+0x30/0xb0
  Oct 21 20:41:38 tyrant kernel: [  281.052899]  ? 
syscall_exit_to_user_mode+0x26/0x50
  Oct 21 20:41:38 tyrant kernel: [  281.052902]  ? __x64_sys_kcmp+0x1f/0x30
  Oct 21 20:41:38 tyrant kernel: [  281.052905]  ? do_syscall_64+0x67/0x90
  Oct 21 20:41:38 tyrant kernel: [  281.052908]  ? 
sysvec_apic_timer_interrupt+0x4b/0xd0
  Oct 21 20:41:38 tyrant kernel: [  281.052911]

[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade

2022-10-24 Thread Hans Deragon

I just noticed that when I simply move the mouse, gnome-shell CPU jumps
up 30% CPU.  For those of you suffering from this problem, this is the
issue to follow:  https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4130

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4130
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4130

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

Title:
  massive performance issues since 22.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  After upgrading to 22.04 i had to fight with massive performance issues.

  Browsers appeared to hang every other minute, youtube videos being
  laggy and hang in between, applications in a virtualbox VM where slow
  and also hanging every other minute to a level of not being useable.
  On a pretty recent and powerful system just 2 years old.

  I noticed CPU jumps in top, but also somehow thought it could be a graphics 
issue so invested some time installing nvidia drivers properly.
  Also I wondered if it might be the lowlatency kernel I normally use because I 
do audio stuff, and switched to generic. But nothing helped.

  ThenI had the idea it could be a kernel/scheduler issue because the
  system wasn't always slow, but it appeared certain things kept hanging
  when other processed had a lot of cpu for a few seconds.

  So I got a recent mainline kernel, configured it with my last running
  config from 21.10 before the update, made the debs and installed them,
  and now can tell that a mainline kernel 5.17.7 with all the dkms
  modules that i had before which got compiled automatically at
  installation brings back a "normal" performance.

  I can browse the web, run multiple youtube vids at once, even in
  another browser, have thunderbird running, and a virtualbox machine
  open with another browser for some web app testing and everything runs
  fine and smooth, no lagging.

  Not sure yet what the real reason is - either the kernel version, or a
  patch in the ubuntu version, or the 22.04 kernel config so far, or
  some configuration made in 21.10 that isn't good with 22.04 and it's
  kernel anymore.

  I will go ahead tomorrow and see if I can build a vanilla kernel with
  the config from the ubuntu 22.04 kernel and "make oldconfig", then I
  will be able to tell if only the config is making the difference.

  Please let me know of there is anything I should test to further
  analyze this issue, or any ideas I can try to solve it without having
  to run a mainline manually installed kernel.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.30.33
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  henning6198 F pulseaudio
   /dev/snd/controlC1:  henning6198 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 23:02:38 2022
  InstallationDate: Installed on 2020-04-12 (761 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=/dev/mapper/vgubuntu-root ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00CEGE
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1924298] Re: accept returns duplicate endpoints under load

2022-10-24 Thread Marcel Guzmán de Rojas

I have the same bug on AWS Ubuntu fully patched. The error was reported
once by a Java EE application under load, ~250 requests/min.

java -version
openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment (build 17.0.4+8-Ubuntu-120.04)
OpenJDK 64-Bit Server VM (build 17.0.4+8-Ubuntu-120.04, mixed mode, sharing)

uname -a
Linux g2 5.15.0-1022-aws #26~20.04.1-Ubuntu SMP Sat Oct 15 03:23:19 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux

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

Title:
  accept returns duplicate endpoints under load

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When accepting client connections under load, duplicate endpoints may
  be returned. These endpoints will have different (usually sequential)
  file descriptors but will refer to the same connection (same server
  IP, same server port, same client IP, same client port). Both copies
  of the endpoint appear to be functional.

  Reproduction requires:
  - compilation of the attached server.c program
  - wrk (https://github.com/wg/wrk) to generate load

  The steps to reproduce are:
  - run 'server' application in one console window
  - run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency 
--timeout 1s http://localhost:/post; done' in a second console window
  - run the same command in a third window to generate concurrent load

  You may need to run additional instance of the wrk command in multiple
  windows to trigger the issue.

  When the problem occurs the server executable will exit and print some 
debugging info. e.g.:
  accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient 
= 232

  This indicates that the sockets with file descriptors 233 and 232 are
  duplicates.

  The issue has been reproduced on fully patched versions of Ubuntu
  20.04 and 18.04. Other versions have not been tested.

  This issue was originally observed in Java and was reported against the 
Spring Framework:
  https://github.com/spring-projects/spring-framework/issues/26434

  Investigation from the Spring team and the Apache Tomcat team identified that 
it appeared to be a JDK issue:
  https://bugs.openjdk.java.net/browse/JDK-8263243

  Further research from the JDK team determined that the issue was at
  the OS level. Hence this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 15 12:52:53 2021
  HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
  InstallationDate: Installed on 2017-02-02 (1532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   lono wireless extensions.
   
   docker0   no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-71-generic N/A
   linux-backports-modules-5.4.0-71-generic  N/A
   linux-firmware1.187.10
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1953575] Re: Update gvnic driver code

2022-10-24 Thread Thadeu Lima de Souza Cascardo

** Changed in: linux-gcp (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Update gvnic driver code

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-gcp source package in Impish:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Committed

Bug description:
  The GCE internal team responsible for gVNIC would like to have driver
  updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS.


  [Impact]
  Missing functionality from the Google gvnic driver

  
  [Test Plan]
  Confirm that gvnic module still loads and operates the gvnic driver. More 
extensive testing done by the gvnic developers at GCE

  
  [Regression potential]
  Possible regression in gvnic behaviour or functionality. Changes are confined 
to the gvnic driver code so regression potential is limited to gvnic only.


  
  List of changes:

  3712db620c613 gve: DQO: Configure interrupts on device up
  a9fd7559a367a gve: Check TX QPL was actually assigned
  c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check
  f48adc2842b17 gve: DQO: Remove incorrect prefetch
  98fd04939ae7e gve: Simplify code and axe the use of a deprecated API
  56c0904d8491d gve: Propagate error codes to caller
  86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo()
  ea364622fb118 gve: Fix warnings reported for DQO patchset
  8890e8783c6e6 gve: DQO: Add RX path
  abfc55f80d423 gve: DQO: Add TX path
  ef63867982913 gve: DQO: Add ring allocation and initialization
  dc3e0aef11bf0 gve: DQO: Add core netdev features
  873fd9825efd7 gve: Update adminq commands to support DQO queues
  543dc0e670472 gve: Add DQO fields for core data structures
  b580730931348 gve: Add dqo descriptors
  74e123d3c62b2 gve: Add support for DQO RX PTYPE map
  a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic
  3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format`
  a6b09c93c1735 gve: Introduce a new model for device options
  34d6b75678979 gve: Add support for raw addressing in the tx path
  30b6221596699 Revert "gve: Check TX QPL was actually assigned"
  98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset
  ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument
  5fc5c482008b5 gve: Move some static functions to a common file
  ed1e0daeee1ac gve: Rx Buffer Recycling
  da57760d6370d gve: Add support for raw addressing to the rx path
  b512608f33d8e gve: Add support for raw addressing device option
  e85394c77cdce gve: Enable Link Speed Reporting in the driver.
  8961791d8ba16 gve: Batch AQ commands for creating and destroying queues.
  50bafd6d5a041 gve: NIC stats for report-stats and for ethtool
  feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags.
  08578185ab296 gve: Use dev_info/err instead of netif_info/err.
  613ed2d16246f gve: Add stats for gve.
  250d220740d21 gve: Get and set Rx copybreak via ethtool

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


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

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

I've also tried the solution suggested in bug 1406208 (i.e. sudo apt
purge backport-iwlwifi-dkms) but that didn't work either.

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

I've even tried turning Bluetooth on & off, rebooting after each change.
But that didn't help. It just shows my level of desperation!

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

I've tried downloading from
https://wireless.wiki.kernel.org/_media/en/users/drivers/iwlwifi-7265-ucode-25.30.14.0.tgz,
and after extracting the resultant 7265files copying them to similarly
named 3165 files and then copying the 4 resultant files to
/lib/firmware, rebooting and trying again to 'start' wifi. No joy.

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165

On Ubuntu Forums it wasted that I try the solutions at
https://bugzilla.kernel.org/show_bug.cgi?id=207409. Those solutions are
above my pay grade to implement!

** Bug watch added: Linux Kernel Bug Tracker #207409
   https://bugzilla.kernel.org/show_bug.cgi?id=207409

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

Title:
  Jammy does not work on wifi for Intel 3165

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network
  Manager sees the router but never manages to connect to it. I've tried
  the purge of the backport iwlwifi module but that didn't help. I
  followed the instructions on another post to give diagnostics. They
  are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/

  Some more info:

  admin@Server:~$ lspci -nnk | grep 3165 
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 
[8086:4010] 
  admin@Server:~$ rfkill list all
  0: hci0: Bluetooth Soft blocked: yes Hard blocked: no
  1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 
  2: phy0: Wireless LAN Soft blocked: no Hard blocked: no –

  I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and
  that worked Ok. I rebooted, disconnected Ethernet & turned wifi on.
  But still get 'SSID connecting' which never finishes and no wifi.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.52.52
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  admin  1506 F pulseaudio
   /dev/snd/controlC0:  admin  1506 F pulseaudio
   /dev/snd/controlC1:  admin  1506 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 14:36:50 2022
  InstallationDate: Installed on 2022-08-15 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   wlp2s0no wireless extensions.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-52-generic N/A
   linux-backports-modules-5.15.0-52-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-404
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku:

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


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

2022-10-24 Thread Ubuntu SRU Bot

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

nvidia-graphics-drivers-515/515.76+really.515.65.01-0ubuntu0.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-oem-6.0

[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 packing 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 1993205] Re: EXT4-fs errors on black screen after resume from sleep

2022-10-24 Thread Anton Keks

It seems that some logs are written on resume before the freeze:
/var/log/kern.log

Oct 23 20:42:29 aziber kernel: [ 1478.088305] Filesystems sync: 0.010 seconds
Oct 24 11:55:24 aziber kernel: [ 1478.355281] Freezing user space processes ... 
(elapsed 0.002 seconds) done.
Oct 24 11:55:24 aziber kernel: [ 1478.358121] OOM killer disabled.
Oct 24 11:55:24 aziber kernel: [ 1478.358124] Freezing remaining freezable 
tasks ... (elapsed 6.366 seconds) done.
Oct 24 11:55:24 aziber kernel: [ 1484.724770] printk: Suspending console(s) 
(use no_console_suspend to debug)
Oct 24 11:55:24 aziber kernel: [ 1485.095679] ACPI: EC: interrupt blocked
Oct 24 11:55:24 aziber kernel: [56249.613366] typec port0-partner: PM: parent 
port0 should not be sleeping
Oct 24 11:55:24 aziber kernel: [56249.799810] asus_wmi: Unknown key code 0xcf
Oct 24 11:55:24 aziber kernel: [56253.854934] ACPI: EC: interrupt unblocked
Oct 24 11:55:24 aziber kernel: [56254.819343] i915 :00:02.0: [drm] GuC 
firmware i915/tgl_guc_70.1.1.bin version 70.1
Oct 24 11:55:24 aziber kernel: [56254.819348] i915 :00:02.0: [drm] HuC 
firmware i915/tgl_huc_7.9.3.bin version 7.9
Oct 24 11:55:24 aziber kernel: [56254.822876] i915 :00:02.0: [drm] HuC 
authenticated
Oct 24 11:55:24 aziber kernel: [56254.822890] i915 :00:02.0: [drm] GuC 
submission disabled
Oct 24 11:55:24 aziber kernel: [56254.822891] i915 :00:02.0: [drm] GuC SLPC 
disabled
Oct 24 11:55:24 aziber kernel: [56255.040555] OOM killer enabled.
Oct 24 11:55:24 aziber kernel: [56255.040559] Restarting tasks ... 
Oct 24 11:55:24 aziber kernel: [56255.044577] mei_hdcp 
:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops 
i915_hdcp_component_ops [i915])
Oct 24 11:55:24 aziber kernel: [56255.047165] mei_pxp 
:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound :00:02.0 (ops 
i915_pxp_tee_component_ops [i915])
Oct 24 11:55:24 aziber kernel: [56255.051527] done.
Oct 24 11:55:24 aziber kernel: [56255.059513] thermal thermal_zone7: failed to 
read out thermal zone (-61)
Oct 24 11:55:24 aziber kernel: [56255.070581] PM: suspend exit
Oct 24 11:55:24 aziber kernel: [56255.168618] audit: type=1400 
audit(101724.319:107): apparmor="DENIED" operation="capable" class="cap" 
profile="/usr/sbin/cupsd" pid=25817 comm="cupsd" capability=12  
capname="net_admin"

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

Title:
  EXT4-fs errors on black screen after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some time after updating to Ubuntu 22.04 and Kernel 5.15, Intel Tiger
  Lake laptop started getting black screen and EXT4-fs errors 10-20
  seconds after resume from sleep. This is reproducible approximately
  every other time, i.e. sometimes the resume works normally.

  Usually, after resume I can enter GDM password, unlock the desktop and
  see running apps, but soon when they start writing to the disk (NVME),
  the screen goes blank with a bunch of errors regarding read-only
  filesystem, unable to unmount partitions, etc.

  Upgrading to Ubuntu 22.10 / Kernel 5.19 does not fix the issue. The
  same laptop worked flawlessly before Ubuntu 22.04.

  After hard reset and boot, the system works normally.

  The logs are not written anywhere besides the screen.

  OCR from an photo using Google Lens:

  [19449.602615) systemd[9792) home.mount: Failed at step EXEC spawning 
/bin/umount: Input/output error
  [19449.609995) systemd[1]: Failed unmounting /home.
  [19449.932421] systemd[9794): docker.service: Failed at step EXEC spawning 
/usr/bin/dockerd: Input/output error
  [19449.959791) systemd[1]: Failed to start Docker Application Container 
Engine.
  [19452.164163) systemd[9795): docker.service: Failed at step EXEC spawning 
/usr/bin/dockerd: Input/output error
  [19452.165445] systemd[1]: Failed to start Docker Application Container 
Engine.
  [19454.397310] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#655370: comm systemd: reading directory Iblock o
  [19454.397999) EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#2: comm systemd: reading directory 1block o
  [19454.997891] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#655370: comm systemd: reading directory 1block 0
  [19454.397949] EXT4-fs error (device nvmeon1p5): ext4_find_entry: 1658: inode 
#2: comm systemd: reading directory Iblock o
  [19454.420294] systemd[9797]: docker.service: Failed at step EXEC spawning 
/usr/bin/dockerd: Input/output error
  119454.421508] systemd[1]: Failed to start Docker Application Container 
Engine.
  [19456.207832 EXT4-fs error (device nvmeon1p5): __ext4_find_entry: 1658: 
inode #922214: comm gmain: reading directory Iblock 0
  [19456.264664 EXT4-fs error (device nvme0n1p5): ext4_find_entry: 1658: inode 
#1187760: comm gmain: reading directory Iblock o
  [13456.264765] EXT4-fs

[Kernel-packages] [Bug 1994025] [NEW] Suspend or hibernate fails when using Arc Alchemist (DG2) graphics

2022-10-24 Thread Sebastian Heiden

Public bug reported:

The computer is unable to suspend or hibernate, when a DG2 graphics card
is installed and in-use in the system.

When attempting to suspend or hibernate the system will turn off its
screens for a few seconds after which they will light up again.

I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages
from the canonical-x/x-staging ppa.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-oem-22.04b 6.0.0.1005.5
ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
Uname: Linux 6.0.0-1005-oem x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 24 12:07:27 2022
InstallationDate: Installed on 2022-02-23 (242 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-oem-6.0
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

** Package changed: linux-meta-oem-6.0 (Ubuntu) => linux-oem-6.0
(Ubuntu)

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

Title:
  Suspend or hibernate fails when using Arc Alchemist (DG2) graphics

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

Bug description:
  The computer is unable to suspend or hibernate, when a DG2 graphics
  card is installed and in-use in the system.

  When attempting to suspend or hibernate the system will turn off its
  screens for a few seconds after which they will light up again.

  I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages
  from the canonical-x/x-staging ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04b 6.0.0.1005.5
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 12:07:27 2022
  InstallationDate: Installed on 2022-02-23 (242 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-oem-6.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode

2022-10-24 Thread Andy Chi

** Tags added: originate-from-1981168 somerville

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Opinion

Bug description:
  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #22 0x7fcae0743293 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #23 0x7fcadf8d0849 in meta_context_run_main_loop () from 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #24 0x55773f1a4f12 in ?? ()
  #25 0x7fcadf429d90 in __libc_start_call_main 
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1, 
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
  #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, 
argc=1, argv=0x7fffc54053e8, init=, fini=, 
rtld_fini=, stack_end=0x7fffc54053d8)
  at ../csu/libc-start.c:392
  #27 0x55773f1a51b5 in ?? ()
  ```

  Other discussion thread:
  https://gitlab.freedesktop.org/drm/intel/-/issues/6851
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2431

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  Uname: Linux 5.18.0-rc2+ x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5json:
   {
     "result": "skip"
   }
  Date: Mon Sep 19 10:39:59 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see

[Kernel-packages] [Bug 1990916] Re: Add AMDI0009 support to amd-pmc

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

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

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

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

Title:
  Add AMDI0009 support to amd-pmc

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  New

Bug description:
  For AMD Pink Sardine a change is being made in newer BIOSes that will
  use a different _HID than is currently supported in amd-pmc as of
  kernel 6.0. This new ID changes a interface to the BIOS and is not
  just adding the ID.

  To support s0i3 in OEM 6.0 kernel we will need to support this new
  ID/interface.

  AMD will submit the code to target to kernel 6.1, but it will be
  needed in OEM-6.0 kernel.

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


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

[Kernel-packages] [Bug 1990922] Re: Fix USB4 PCIe hotplug on AMD Pink Sardine

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

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

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

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

Title:
Fix USB4 PCIe hotplug on AMD Pink Sardine

Status in HWE Next:
New
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Fix Committed

Bug description:
[SRU Justification]

[Impact]

For some reason that PCIe device hotplug is disabled once another OS
stack launches prior to Linux CM, which makes some registers not go
properly, so correct those registers to meet the default value of the
USB4 spec.

[Fix]

Two commits targeting v6.1 to restore the default values.

[Test Case]

To be verified from ODM side.

[Where problems could occur]

These two commits restores the default values as expected from USB4 spec
at being initialized, so it should be the right behaviour anyway.

[Other Info]

While this is for AMD Pink Sardine platforms, only oem-6.0 and newer
are nominated for fix.

== original bug description ==

https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=fixes=31f87f705b3c1635345d8e8a493697099b43e508

https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=5d2569cb4a65c373896ec0217febdf88739ed295

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

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

[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

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

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

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

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

Title:
  Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  turbostat doesn't show the correct fields for RPL-S.
  This's a wrong column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI

  [Fix]
  Add RPL-S support in turbostat

  [Test Case]
  1. run "turbostat --list"
  2. check the output, this is a correct column.
  
usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_%

  [Where problems could occur]
  Low, just add a devcie id to support RPL-S.

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


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

[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

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

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

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

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

Title:
  Fix Thunderbolt device hotplug fail when connect via thunderbolt dock

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

Bug description:
  [SRU Justification]

  [Impact]
  Some Dell laptops where booting with Thunderbolt/USB4 devices connected the 
BIOS leaves some of
  the PCIe devices unconfigured. The kernel message shows "No bus number 
available for hot-added bridge". The connected devices can't be found.

  [Fix]
  Current linux PCI distribute the "spare" resources between hotplug ports on 
hot-add but have not done that upon the initial scan. The patches make the 
initial root bus scan path to do the same. The additional patches are just a 
small cleanups that can be applied separately too.

  [Test]
  1. Power on the machine with Thunderbolt/USB4 devices connected.
  2. Check the kernel message to see if "No bus number available for hot-added 
bridge" shows up or not.
  3. Check if the Thunderbolt/USB4 devices works or not.

  [Where problems could occur]
  The patches only apply the same procedures on initial root bus scan which was 
not done. If the BIOS configures the PCI correctly, everything is OK. It only 
takes effect for the BIOS w/ unconfigured PCIe devices.

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

2022-10-24 Thread AceLan Kao

We also need this in kinetic, so there is the merge proposal for kinetic
https://code.launchpad.net/~acelankao/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/432078

** Also affects: firmware-sof (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux-oem-6.0 (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

** Changed in: firmware-sof (Ubuntu Kinetic)
   Status: Confirmed => In Progress

** Changed in: firmware-sof (Ubuntu Kinetic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in firmware-sof source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

2022-10-24 Thread Launchpad Bug Tracker

** Merge proposal linked:
   
https://code.launchpad.net/~acelankao/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/432078

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in firmware-sof source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

you need an upload for kinetic/LL too, assuming that support for RPL
only came in via 2.2.2 while kinetic has 2.1.1

** Changed in: firmware-sof (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Confirmed
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

2022-10-24 Thread AceLan Kao

Submitted a merge proposal here
https://code.launchpad.net/~acelankao/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/432073

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support

2022-10-24 Thread Launchpad Bug Tracker

** Merge proposal linked:
   
https://code.launchpad.net/~acelankao/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/432073

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1992714] Re: SoF for RPL platform support

2022-10-24 Thread Hui Wang

Subscribed Sponsor team.

Hi Sponsor-team,

when you have time, please help review the SRU request and upload it.

thx.


** Summary changed:

- SoF for RPL platform support
+ [SRU] SoF for RPL platform support

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

Title:
  [SRU] SoF for RPL platform support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  RPL platforms require new sof struct and firmware to enable its audio

  [Fix]
  Below 2 commits are from v6.1-rc1
  63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions
  5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake

  Firmware are from here
  https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2

  [Test]
  Verified Dell machine which comes with rpl sdw audio.

  [Where problems could occur]
  Adding new struct, new ID, and new firmware, it won't affect old systems.

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


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

[Kernel-packages] [Bug 1993935] Status changed to Confirmed