[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BI-02-C bluetooth certification failure

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Fix L2CAP/LE/CPU/BI-02-C bluetooth certification failure

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Jusitification for Kernel

  [Impact]

  Noble failed the L2CAP/LE/CPU/BI-02-C test in the Porfile Tuning Suite
  (PTS), which Jammy previously could pass.

  This is due to new behavior introduced in
  e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce
  validation on max value of connection interval). The kernel only
  accept Connection Parameter Update Requests whose incoming
  conn_max_interval are lower than the current conn_max_interval, and
  adjust the newer conn_max_interval to that received max value.

  However, this behavior means that conn_max_interval can only decrease,
  but never increase. This could potentially make the conditions for
  connection parameters narrower over time, causing subsequent
  connections failed on some devices. See the issue 847 in bluez
  upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4
  (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the
  linux-next fixed this by accepting connection parameter
  unconditionally. The relavent test procedure is also on the mailing
  list[2].

  [1] https://github.com/bluez/bluez/issues/847
  [2] 
https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326

  [Fix]
  Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: 
L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the 
linux-next.

  [1]
  
https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/

  [Test Case]
  1. Install the kernel with the backported patch
  2. Run the following test case in the PTS:
   L2CAP/LE/CPU/BI-02-C
   GAP/CONN/CPUP/BV-05-C

  [Where problems could occur]
  This essentially revert the behavior of accepting L2CAP connection parameters 
back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 
(Bluetooth: Enforce validation on max value of connection interval).

  Note that implementing restriction to the conenction parameters may
  take greater effort than just adding a few checks in the kernel. The
  user space, notably the bluetoothd may also need adjustments[1]. So in
  this case, removing the half-done boundary checks in kernel may still
  do greater good if there's no plan to make those additional changes.

  [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058

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


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

[Kernel-packages] [Bug 2072643] Re: Embedded camera using camera sensors ov02e10 and ov08a10 doesn't work: missing kernel driver

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Embedded camera using camera sensors ov02e10 and ov08a10 doesn't work:
  missing kernel driver

Status in OEM Priority Project:
  New
Status in ipu6-drivers package in Ubuntu:
  Fix Released
Status in linux-signed-oem-6.5 package in Ubuntu:
  Invalid
Status in ipu6-drivers source package in Jammy:
  Won't Fix
Status in linux-signed-oem-6.5 source package in Jammy:
  New
Status in ipu6-drivers source package in Noble:
  Fix Released
Status in linux-signed-oem-6.5 source package in Noble:
  Invalid
Status in ipu6-drivers source package in Oracular:
  Fix Released
Status in linux-signed-oem-6.5 source package in Oracular:
  Invalid

Bug description:
  [SRU Justfication]

  [Impact]

  Device camera won't work.

  [Fix]

  The current version in -proposed pocket may skip installation of built
  kernel module ov02e10 and ov08a10. The fix is to use fixed index
  numbers in dkms.conf.

  [Test Case]

  Install the dkms and check if ov02e10.ko and ov08a10.ko have been
  installed to /lib/modules//updates/dkms.

  [Where problems could occur]

  Minimal, as this is restoring driver modules that were previously
  installed prior to the regression.

  [Other Info]

  While this happens to ipu6-drivers/{oracualr,noble} only, proposed
  fixes are therefore nominated accordingly.

  == original bug report =

  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04
  linux-oem-22.04d 6.5.0.1026.28

  com.canonical.certification::camera/camera-quality_video0 test fails:

  [ WARN:0] global ./modules/videoio/src/cap_gstreamer.cpp (1100) open OpenCV | 
GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
  /bin/sh: 1: kill: Illegal number: -
  Traceback (most recent call last):
    File 
"/tmp/nest-oh_l6kjy.e6eacba27b81ed7929f808c3af9ceaf803facf6256ab97b917f65943c394f09d/camera_quality_test.py",
 line 178, in 
  sys.exit(main(sys.argv[1:]))
    File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py", 
line 93, in _f
  return run_with_timeout(f, timeout_s, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/checkbox_support/helpers/timeout.py", 
line 78, in run_with_timeout
  raise TimeoutError("Task unable to finish in {}s".format(timeout_s))
  TimeoutError: Task unable to finish in 120s

  It passed on 6.5.1024.25 on the same device.

  It fails on all Dell Oasis MTL machines
  202312-33186 (usbio, ov02e10)
  202312-33187 (usbio, ov02e10)
  202312-33214 (usbio, hi556, checkbox test pass)
  202312-33215 (usbio, hi556, checkbox test pass)
  202312-32371 (usbio, hi556, checkbox test pass)
  202312-32372 (usbio, ov02e10)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-1026-oem 6.5.0-1026.27
  ProcVersionSignature: Ubuntu 6.5.0-1026.27-oem 6.5.13
  Uname: Linux 6.5.0-1026-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jul 10 06:38:38 2024
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-oddish13+X120
  InstallationDate: Installed on 2024-02-27 (134 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  SourcePackage: linux-signed-oem-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2068567] Re: Irregular frame rate in fullscreen glxgears on Intel Meteor Lake

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Irregular frame rate in fullscreen glxgears on Intel Meteor Lake

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Frame drops when running glxgears in fullscreen mode.
  The issue only appears in Wayland.
  Add CLUTTER_PAINT=disable-dynamic-max-render-time fixes it

  [Reproduce steps]
1. run glxgears in fullscreen mode
2. observe the fps

  [glxgears output]
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  295 frames in 5.0 seconds = 58.949 FPS
  183 frames in 5.0 seconds = 36.584 FPS
  212 frames in 5.0 seconds = 42.231 FPS
  176 frames in 5.0 seconds = 35.022 FPS
  166 frames in 5.0 seconds = 33.048 FPS
  159 frames in 5.0 seconds = 31.775 FPS
  222 frames in 5.0 seconds = 44.363 FPS
  197 frames in 5.0 seconds = 39.379 FPS
  164 frames in 5.0 seconds = 32.784 FPS

  [Related information]
  Ubuntu 24.04
  Mutter: 46.0-1ubuntu9
  GPU model: Intel Corporation Meteor Lake-P [Intel Arc Graphics]
  Graphics driver in use: i915

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 46.0-0ubuntu5.1
  ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
  Uname: Linux 6.8.0-35-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckMismatches: ./.disk/casper-uuid-generic ./casper/initrd 
./casper/minimal.standard.live.hotfix.squashfs 
./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs 
./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Jun  6 14:56:43 2024
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-noble-hwe-20240528-99
  InstallationDate: Installed on 2024-06-06 (0 days ago)
  InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 
(20240528)
  RelatedPackageVersions: mutter-common 46.0-1ubuntu9
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

[Rex Tsai]

@bogdan

Unfortunately, we didn't see the log you reported with ubuntu-bug. Could
you try reproducing the issue and then upload the log here? Please run
the following command and upload the lp2062280 file to this bug:

ubuntu-bug --save=lp2062280 bluez

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 6.5 the external Bluetooth USB dongle based on
  Realtek stop working.

  This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
  version is > 6.5. On a lower kernel version it works as we were using
  it for almost 2 years without issues.

  Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
  USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

  ```
  $ uname -a
  Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth
  Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
  ```

  Journalctl logs after the OS is starting
  ```
  journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  ```

  I have installed BlueZ package https://www.bluez.org/ and trying to
  discover the device which worked but i am always getting errors when
  trying to connect to the device via BT (after pairing)

  ```
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Changed settings: 0x0008
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Pending settings: 0x0

[Kernel-packages] [Bug 2060914] Re: kernel NULL pointer dereference in ipu6 driver

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  kernel NULL pointer dereference in ipu6 driver

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  pr 11 14:43:43 OCBYM2-DVT1-C3 kernel: BUG: kernel NULL pointer dereference, 
address: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: supervisor read access in kernel 
mode
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: error_code(0x) - not-present 
page
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PGD 0 P4D 0 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Oops:  [#1] PREEMPT SMP NOPTI
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CPU: 16 PID: 568 Comm: (udev-worker) 
Tainted: G   O   6.8.0-22-generic #22-Ubuntu
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Hardware name: Dell Inc. Precision 
5490/, BIOS 1.1.0 02/07/2024
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RIP: 0010:__wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Code: 55 48 89 e5 41 57 41 56 41 55 41 
54 53 48 89 fb 48 83 c3 08 48 83 ec 08 48 8b 47 08 89 75 d4 89 55 d0 48 39 c3 
74 51 4d 89 c7 <4c> 8b 00 41 89 ce 48 8d 78 e8 4d 8d 68 e8 eb 25 74 0c 41 83 e4 
01
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RSP: 0018:b5ebc3063768 EFLAGS: 
00010086
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RAX:  RBX: 
8fb79e181d50 RCX: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RDX:  RSI: 
0003 RDI: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RBP: b5ebc3063798 R08: 
 R09: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R10:  R11: 
 R12: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R13: 0003 R14: 
0246 R15: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: FS:  77cceb6148c0() 
GS:8fc6cf60() knlGS:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CR2:  CR3: 
0001068ae003 CR4: 00f70ef0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR0:  DR1: 
 DR2: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR3:  DR6: 
07f0 DR7: 0400
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PKRU: 5554
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Call Trace:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? show_regs+0x6d/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __die+0x24/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? page_fault_oops+0x99/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? do_user_addr_fault+0x2ee/0x6b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? exc_page_fault+0x83/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? asm_exc_page_fault+0x27/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __wake_up+0x37/0x70
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __vb2_queue_cancel+0xcd/0x300 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_core_queue_release+0x23/0x70 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_queue_release+0xe/0x20 
[videobuf2_v4l2]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_queue_cleanup+0x12/0x20 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_video_cleanup+0x2e/0x40 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
ipu_isys_csi2_be_soc_cleanup+0x37/0x50 [intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_unregister_subdevices+0x40/0xa0 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_probe+0x5c5/0xb80 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? kernfs_create_link+0x66/0xe0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_probe+0x72/0x130 [intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  really_probe+0x1c4/0x410
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_probe_device+0x8c/0x180
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_probe_device+0x24/0xd0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_attach+0x10b/0x210
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx___driver_attach+0x10/0x10
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_for_each_dev+0x8a/0xf0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_attach+0x1e/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_add_driver+0x156/0x260
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_register+0x5e/0x130
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx_isys_driver_init+0x10/0x10 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_register_driver+0x16/0x20 
[intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_driver_init+0x15/0xff0 
[intel_ipu6_isys]
  Apr 11 14:43:43 O

[Kernel-packages] [Bug 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

[Rex Tsai]

Please describe how to reproduce the issue. The bug report was based on
a self-built bluez, and did not explain what was the profile were
tested, which the built in UI or via an application talk to bluetoothd


When you are able to reproduce the issue, please run the following command, and 
upload the lp2062280 to this bug.
 
ubuntu-bug --save=lp2062280 bluez

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 6.5 the external Bluetooth USB dongle based on
  Realtek stop working.

  This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
  version is > 6.5. On a lower kernel version it works as we were using
  it for almost 2 years without issues.

  Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
  USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

  ```
  $ uname -a
  Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth
  Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
  ```

  Journalctl logs after the OS is starting
  ```
  journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  ```

  I have installed BlueZ package https://www.bluez.org/ and trying to
  discover the device which worked but i am always getting errors when
  trying to connect to the device via BT (after pairing)

  ```
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
  Apr 18 09:22:37 bomi-edge bluetoothd[24

[Kernel-packages] [Bug 2051720] Re: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

[Rex Tsai]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 2051720

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

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

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

Bug description:
  ```
  kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  ```

  This issue started with kernel 6.5. Bluetooth has been broken ever
  since. The issue was not present in earlier versions of the kernel.

  ```
  $ uname -a

  Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth

  Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  ```

  ```
  $ journalctl -b | egrep -i bluetooth

  Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
  Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
  Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
  Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed 
(-110)
  ```

  ```
  linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all 
[installed,automatic]
  ```

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


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

[Kernel-packages] [Bug 2029031] Re: Tap event stop working after suspend/resuem with Synaptics TM3512-010 on Thinkpad P1Gen1

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Tap event stop working after suspend/resuem with Synaptics TM3512-010
  on Thinkpad P1Gen1

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:

  The tap event of the touchpad stops working after resuming/suspend,
  the failure rate is 20% (one time failure every 5 times).

  
  Linux ThinkPad-P1 6.3.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun  8 
16:02:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  The system firmware is 0.1.43.
  ├─System Firmware:
  │ │   Device ID:  a45df35ac0e948ee180fe216a5f703f32dda163f
  │ │   Summary:UEFI ESRT device
  │ │   Current version:0.1.43
  │ │   Minimum Version:0.1.34
  │ │   Vendor: Lenovo (DMI:LENOVO)
  │ │   Update State:   Success
  │ │   Problems:   • System power is too low to perform the update
  │ │   GUIDs:  a95d69e7-2fa0-4849-9159-75645bc6e153
  │ │   230c8b18-8d9b-53ec-838b-6cfc0383493a ← 
main-system-firmware
  │ │   Device Flags:   • Internal device
  │ │   • System requires external power source
  │ │   • Supported on remote server
  │ │   • Needs a reboot after installation
  │ │   • Cryptographic hash verification is available
  │ │   • Device is usable for the duration of the update
  │ │   • Updatable

  
  The touchpad module is Synaptics TM3512-010
  /dev/input/event13
 bustype : BUS_RMI
 vendor  : 0x6cb
 product : 0x0
 version : 0
 name: "Synaptics TM3512-010"
 phys: "rmi4-00/input0"
 bits ev : (null) (null) (null)

  (can not tell the firmware version of the touchpad from the OS)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.3.0-7-generic 6.3.0-7.7
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fenris 3590 F wireplumber
   /dev/snd/controlC1:  fenris 3590 F wireplumber
   /dev/snd/seq:fenris 3584 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 30 14:59:07 2023
  InstallationDate: Installed on 2023-07-08 (22 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.3.0-7-generic N/A
   linux-backports-modules-6.3.0-7-generic  N/A
   linux-firmware   20230629.gitee91452d-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2022
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET61W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MES15C00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 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.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET61W(1.43):bd12/20/2022:br1.43:efr1.15:svnLENOVO:pn20MES15C00:pvrThinkPadP1:rvnLENOVO:rn20MES15C00:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20ME_BU_Think_FM_ThinkPadP1:
  dmi.product.family: ThinkPad P1
  dmi.product.name: 20MES15C00
  dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1
  dmi.product.version: ThinkPad P1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2044377] Re: ThinkPad PrivacyScreen handle /proc/acpi/ibm/lcdshadow does not toggle hardware

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  ThinkPad PrivacyScreen handle /proc/acpi/ibm/lcdshadow does not toggle
  hardware

Status in linux package in Ubuntu:
  New

Bug description:
  My laptop is equipped with PrivacyGuard, however the hardware feature
  does not work since one upgrade in Ubuntu 23.04. I just upgraded to
  23.10 and this issue is still not fixed. It used to work when I was
  using 22.04.

  I have tested writing to the procfs interface directly: `echo 0 >
  /proc/acpi/ibm/lcdshadow` This command have no effect, even though the
  status `cat /proc/acpi/ibm/lcdshadow` is changed.

  I also tried rebooting into the UEFI setup, then pressing Ctrl+D (the
  PrivacyGuard hotkey). This works as expected. (Toggles the
  PrivacyGuard.)

  Currently, under 23.10, the PrivacyGuard seemed to be stuck on the
  "on" state.

  Ubuntu release: 23.10
  Kernel version: 6.5.0-13-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-13-generic 6.5.0-13.13
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Nov 23 21:11:40 2023
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-12-17 (706 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vt52bg@/vmlinuz-6.5.0-13-generic 
root=ZFS=rpool/ROOT/ubuntu_vt52bg ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-13-generic N/A
   linux-backports-modules-6.5.0-13-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (23 days ago)
  dmi.bios.date: 06/27/2022
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1NET51W (1.21)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1NET51W(1.21):bd06/27/2022:br1.21:efr1.21:svnLENOVO:pn20XHCTO1WW:pvrThinkPadX13Gen2a:rvnLENOVO:rn20XHCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XH_BU_Think_FM_ThinkPadX13Gen2a:
  dmi.product.family: ThinkPad X13 Gen 2a
  dmi.product.name: 20XHCTO1WW
  dmi.product.sku: LENOVO_MT_20XH_BU_Think_FM_ThinkPad X13 Gen 2a
  dmi.product.version: ThinkPad X13 Gen 2a
  dmi.sys.vendor: LENOVO

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


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

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

[Rex Tsai]

dynamic boost control is landed in upstream kernel 6.6, noble will have
such feature by default.

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

Title:
  Enable dynamic boost control in ccp kernel driver

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

Bug description:
  [Impact]

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

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

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

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

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

  [Test case]

  WIP

  [Regression potential]

  WIP

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


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

[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[Rex Tsai]

- Dell Precision 5570[1] has the CNVi wireless module on an Alder Lake-S 
platform. The wireless module needs the correct firmware[2] for bluetooth to 
work. Based on Dilyn's comment #18[3], it's unclear if the firmware has been 
loaded on Core. Please check dmesg and see if it loads the 
intel/ibt-0040-0041.* firmwares.

- Plase include the following information in the following tests, which will 
help the team identify the root cause quicker
$ sudo grep '' /sys/class/dmi/id/product_* /sys/class/dmi/id/*_serial
$ sudo cat /etc/cpuinfo
$ snap info bluez && snap connections bluez # version of bluez (even
it's not been updated for a while, but we may not remember what it is
after a while)
$ snap info pc-kernel
$ sudo lspci -nn -vvv -k
$ sudo lsusb -vvv

[1] Dell Precision 5570 (RTX A2000 ) certified on Ubuntu 20.04 LTS -
https://ubuntu.com/certified/202112-29758/20.04%20LTS
[2] [Bug #1933938 “Missing CNVi firmware for Intel
AX211/AX201/9560/9...” : Bugs : linux-firmware package : Ubuntu -
https://bugs.launchpad.net/bugs/1933938
[3] https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/comments/18

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

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

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


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

[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[Rex Tsai]

The title of the bug seems incorrect, the Bluetooth AdvertisementMonitor
does not work with bluetoohd from bluez 22/stable: 5.64-2 2022-05-03
with Ubuntu Core22 on Dell Precision 5570.

I would assume the rest of bluetooth functions and profile are still working, eg
% bluetoothctl show

If order to isolate the root cause is between kernel hci driver or bluetoothd. 
Could you please run the following commands on core to see if the hci driver 
works as expected? 
% sudo btmgmt version
% sudo btmgmt revision
% sudo btmgmt monitor.features
% sudo btmon --mgmt

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

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

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


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

[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs

[Rex Tsai]

The support plan for RPL-S is

Focal - will not support RPL-S.
Jammy - will support with the patch thermald 2.5.2 in this SRU and linux-oem 
6.1+

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

Title:
  Add support for Raptor Lake S CPUs

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * Support thermald on Raptor Lake S CPU.

  [Test Plan]

   * Use a machine with a Raptor Lake S cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Raptor Lake S in thermald, which
  won't impact other hardware.

  [Other Info]

  
https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

[Rex Tsai]

** Tags added: regression-update

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

[Rex Tsai]

** Tags added: ubuntu-certified

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2002757] Re: Dell precision 5560 screen can't back after suspend

[Rex Tsai]

** Tags added: certified

** Tags removed: certified
** Tags added: ubuntu-certified

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

Title:
  Dell precision 5560 screen can't back after suspend

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

Bug description:
  The screen can't back on after suspend.

  Here is the kernel log error:

  [84090.414190] Asynchronous wait on fence 
:00:02.0:gnome-shell[2816]:1c469c timed out (hin  
t:intel_atomic_commit_ready [i915])
  [84090.414462] Asynchronous wait on fence 
:00:02.0:gnome-shell[2816]:1c469c timed out (hin  
t:intel_atomic_commit_ready [i915])
  [84094.705130] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, in 
chrome [106889]
  [84094.705150] i915 :00:02.0: [drm] Resetting rcs0 for stopped heartbeat 
on rcs0
  [84094.705205] i915 :00:02.0: [drm] chrome[106889] context reset due to 
GPU hang
  [90008.508158] input: T8-L (AVRCP) as /devices/virtual/input/input50
  [90008.609265] input: T8-R (AVRCP) as /devices/virtual/input/input51

  There is a upstream bug reported the similar error.

  https://gitlab.freedesktop.org/drm/intel/-/issues/6757#note_1707377

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


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

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Rex Tsai]

Hi, There are a few OEM platforms that also requires these memory
patches in grub2 on jammy, could we also port 2.06-2ubuntu16 back to
jammy?

** Tags added: originate-from-1998995

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:

  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 0002 000F
  BS_Data2B633000-2B63CFFF 000A 000F
  Available  2B63D000-2B649FFF 000D 000F
  BS_Data2B64A000-2B64EFFF 0005 000F
  Available  2B64F000-2B666FFF 0018 000F
  BS_Data2B667000-2D8D5FFF 226F 000F
  LoaderCode 2D8D6000-2D8E9FFF 0014 000F
  BS_Data2D8EA000-2D925FFF 003C 000F
  LoaderCode 2D926000-2D932FFF 000D 000F
  BS_Data2D933000-2D969FFF 0037 000F
  BS_Code2D96A000-2D973FFF 000A 000F
  BS_Data2D974000-2E377FFF 0A04 000F
  Available  2E378000-2E37AFFF 0003 000F
  ...
  Reserved   3C08B000-4192 58A5 000F
  ACPI_NVS   4193-41B2 0200 000F
  ACPI_Recl  41B3-41BFEFFF 00CF 000F
  BS_Data41BFF000-41BF 0001 000F
  Available  0001-0002AB7F 001AB800 000F
  Reserved   000A-000F 0060 
  Reserved   41C0-43FF 0

[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

[Rex Tsai]

@seb

Sorry, I did not see the modemmanager (1.20.0-1ubuntu1) in jammy-proposed, 
would you please confirm the process? 
 
% rmadison modemmanager
 modemmanager | 1.0.0-2ubuntu1| trusty   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.0.0-2ubuntu1.1  | trusty-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.4.12-1ubuntu1   | xenial   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.4-1ubuntu0.16.04.1| xenial-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.8-2ubuntu1| bionic   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.10.0-1~ubuntu18.04.2| bionic-updates   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.12.8-1  | focal| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1~ubuntu20.04.1| focal-updates| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1  | jammy| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.19~git20220905-0ubuntu2 | kinetic  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1~ubuntu22.10.1| kinetic-proposed | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1ubuntu1   | lunar| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x


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

** Changed in: oem-priority
 Assignee: (unassigned) => Yao Wei (medicalwei)

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board

[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel

[Rex Tsai]

Removed oem-priority, confirmed this is not a certified device, and it's not in 
the support scope. 
However, this is a regression that breaks previous supported hardware in mm and 
kernel.

** No longer affects: oem-priority

** Tags removed: oem-priority

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

Title:
  Please add support for Qualcomm IPC Router in 5.4 focal kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The modemmanager debian package in focal was recently upgraded to 1.18
  (the jammy version was backported - see LP: #1965901). This version
  has broken some Qualcomm modems as it start to require the Qualcomm
  IPC Router for them, which drivers are not enabled in Ubuntu kernel
  5.4. To fix this we need these options enabled in the focal kernel:

  CONFIG_QRTR=m
  CONFIG_QRTR_SMD=m
  CONFIG_QRTR_TUN=m
  CONFIG_QRTR_MHI=m

  The options are already enabled in more modern Ubuntu kernel, i.e.
  5.17.

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


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

[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1

[Rex Tsai]

** Changed in: thermald (Ubuntu)
   Status: Fix Released => New

** Summary changed:

- Upgrade thermald to 2.5.1
+ Upgrade thermald to 2.5.1 for Jammy (22.04)

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

Title:
  Upgrade thermald to 2.5.1 for Jammy (22.04)

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New
Status in thermald source package in Jammy:
  Incomplete

Bug description:
  [Justification]
  The purpose of this bug is that prevent the regression in the future.
  The automatic test scripts are better for the future SRU and is still on the 
planning.

  [Test case]
  For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be 
run on machines in the CI lab:

  1. Run stress-ng, and observe the temperature/frequency/power with s-tui
    - Temperatures should stay just below trip values
    - Power/performance profiles should stay roughly the same between old 
thermald and new thermald (unless specifically expected eg: to fix 
premature/insufficient throttling)
  2. check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
    - this depends on if acpi_thermal_rel exist.
    - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
   could be landed in etc/thermald/.
    - if not, the user-defined xml could be created, then jump to (3).
    - run thermald with --loglevel=debug, and compare the log with xml.auto 
file. check if the configuration could be parsed correctly.
  3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
    - run thermald with --loglevel=debug, and compare the log with xml files.
    - if parsed correctly, the configurations from XML files would appear in 
the log.

  4. Run unit tests, the scripts are under test folder, using emul_temp to 
simulate the High temperatue and check thermald would throttle CPU through the 
related cooling device.
    - rapl.sh
    - intel_pstate.sh
    - powerclamp.sh
    - processor.sh
  5. check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
  6. check if system would be throttled even the temperature is under the 
trip-points.

  [ Where problems could occur ]
  since the PL1 min/max is introduced, there may have some cases that don't 
check the minimum of PL1 then make PL1 to smaller and smaller and throttle the 
CPU. 
  this may cause machines run like the old behavior that doesn't have PL1 
min/max.

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


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

[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Tags added: hwe-thermal

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

Title:
  Upgrade thermald to 2.5.1 for Jammy (22.04)

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New
Status in thermald source package in Jammy:
  Incomplete

Bug description:
  [Justification]
  The purpose of this bug is that prevent the regression in the future.
  The automatic test scripts are better for the future SRU and is still on the 
planning.

  [Test case]
  For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be 
run on machines in the CI lab:

  1. Run stress-ng, and observe the temperature/frequency/power with s-tui
    - Temperatures should stay just below trip values
    - Power/performance profiles should stay roughly the same between old 
thermald and new thermald (unless specifically expected eg: to fix 
premature/insufficient throttling)
  2. check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
    - this depends on if acpi_thermal_rel exist.
    - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
   could be landed in etc/thermald/.
    - if not, the user-defined xml could be created, then jump to (3).
    - run thermald with --loglevel=debug, and compare the log with xml.auto 
file. check if the configuration could be parsed correctly.
  3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
    - run thermald with --loglevel=debug, and compare the log with xml files.
    - if parsed correctly, the configurations from XML files would appear in 
the log.

  4. Run unit tests, the scripts are under test folder, using emul_temp to 
simulate the High temperatue and check thermald would throttle CPU through the 
related cooling device.
    - rapl.sh
    - intel_pstate.sh
    - powerclamp.sh
    - processor.sh
  5. check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
  6. check if system would be throttled even the temperature is under the 
trip-points.

  [ Where problems could occur ]
  since the PL1 min/max is introduced, there may have some cases that don't 
check the minimum of PL1 then make PL1 to smaller and smaller and throttle the 
CPU. 
  this may cause machines run like the old behavior that doesn't have PL1 
min/max.

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


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

[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive

[Rex Tsai]

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

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

Title:
  dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under
  universe archive

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  New

Bug description:
  [Description]

  The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in
  universe archive.

  https://packages.ubuntu.com/search?keywords=gcc-12
  gcc-12 is under main for kinect, and the patches are cherry-picked from 
kinect/stable, I suppose it is a mistake for jammy in universe.

  [debian/changelog]

  dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium

  Cherry-pick patches from kinetic/stable to address building dkms
  modules correctly for HWE kernels (LP: #1991664):

  Fix dkms-autopkgtest when a given dkms package is built into the
  kernel already of the same version. (i.e. zfs-linux on Ubuntu).

  Use exact compiler for dkms as used to build the kernel, when
  possible.

  Depend on gcc-12 to build modules for HWE kernels correctly.

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


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

[Kernel-packages] [Bug 1998194] Re: Please add support for Qualcomm IPC Router in 5.4 focal kernel

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

Title:
  Please add support for Qualcomm IPC Router in 5.4 focal kernel

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The modemmanager debian package in focal was recently upgraded to 1.18
  (the jammy version was backported - see LP: #1965901). This version
  has broken some Qualcomm modems as it start to require the Qualcomm
  IPC Router for them, which drivers are not enabled in Ubuntu kernel
  5.4. To fix this we need these options enabled in the focal kernel:

  CONFIG_QRTR=m
  CONFIG_QRTR_SMD=m
  CONFIG_QRTR_TUN=m
  CONFIG_QRTR_MHI=m

  The options are already enabled in more modern Ubuntu kernel, i.e.
  5.17.

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


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

[Kernel-packages] [Bug 1966061] Re: thinkpad_acpi: Support privacy-screen

[Rex Tsai]

** Changed in: oem-priority
   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/1966061

Title:
  thinkpad_acpi: Support privacy-screen

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 5.15.0-23-generic, the lcdshadow is not synced.

  $ cat /proc/acpi/ibm/lcdshadow
  status: 0
  commands: 0, 1

  And after press the Fn + D, the screen display angle changed, but the
  content of /proc/acpi/ibm/lcdshadow d0 not change.

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


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

[Kernel-packages] [Bug 1967726] Re: Disabled S3 ACPI standby state on DELL Precision M3560

[Rex Tsai]

Hi,

S3 is no longer required in UEFI for certification, the machine can
enter suspend with Suspend-to-idle S0ix.

[1] http://certification-
static.canonical.com/docs/coverage_by_release/20.04/UbuntuDesktopCoverage2004.pdf


** Changed in: linux-signed-oem-5.14 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Disabled S3 ACPI standby state on DELL Precision M3560

Status in linux-signed-oem-5.14 package in Ubuntu:
  Won't Fix

Bug description:
  Device information for https://answers.launchpad.net/ubuntu-
  certification/+question/701164

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
  ProcVersionSignature: Ubuntu 5.14.0-1031.34-oem 5.14.21
  Uname: Linux 5.14.0-1031-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  4 09:58:28 2022
  InstallationDate: Installed on 2021-12-06 (118 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apport: [deleted]

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


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

[Kernel-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Kernel-packages] [Bug 1956232] Re: ipu6: ov01a1s: failed to init camera

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  ipu6: ov01a1s: failed to init camera

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With proposed oem-5.14 kernel from bug 1955383 and latest middleware
  installed, cheese no longer gives video streaming.

  Installed middleware are:
  * linux-firmware:   1.187.24+staging.39
  * libipu6:  0~git202112020845.a14b40c-1~ubuntu20.04.1
  * libcamhal-common: 0~git202112130639.4585612~ubuntu20.04.1
  * libcamhal0:   0~git202112130639.4585612~ubuntu20.04.1
  * libgsticamerainterface-1.0-1: 0~git202112230614.eb13eb1~ubuntu20.04.1
  * gstreamer1.0-icamera: 0~git202112230614.eb13eb1~ubuntu20.04.1

  But when switched back to following ones, same oem-5.14 kernel works
  just fine:

  * libipu6:  0~git202104021802.45905c6-1~ubuntu20.04.1
  * libcamhal-common: 0~git202105200731.43dcb4c~ubuntu20.04.1
  * libcamhal0:   0~git202105200731.43dcb4c~ubuntu20.04.1
  * libgsticamerainterface-1.0-1: 0~git202104021904.aeed9b9~ubuntu20.04.1
  * gstreamer1.0-icamera: 0~git202104021904.aeed9b9~ubuntu20.04.1

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2171 F pulseaudio
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-mewtwo+X103
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-17 (17 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 9420
  Package: linux-firmware 1.187.24+staging.39 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f010c12a-7bf3-4d44-8e9e-6236b24bdb57 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  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.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.24+staging.39
  Tags: focal third-party-packages
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/25/2021
  dmi.bios.release: 89.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 89.5.23
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr89.5.23:bd01/25/2021:br89.5:svnDellInc.:pnLatitude9420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0A32:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
   Importance: Low => Wishlist

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

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Kernel-packages] [Bug 1918253] Re: WWAN I XMM 7360 LTE-Advanced (Cat 9) doesn't work [8086:7360]

[Rex Tsai]

The modem based on Intel XMM7360 can support both PCI and USB mode, the
HP's UEFI does not support switching the model to USB mode.

The WWAN suspend D state is D2 instead of D3, under windows. The WWAN
under PCI will block suspend-to-idle on Linux.

Canonical CE team planned not to fix this issue. A workaround has been
proposed  https://lkml.org/lkml/2021/3/24/489

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

** Changed in: oem-priority
   Importance: Low => Wishlist

** Description changed:

  There is no driver for it [8086:7360] when using 5.10 kernel.
  
  $ lspci -nnv -s 55:00.0
  55:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced 
Modem [8086:7360] (rev 01)
-   Subsystem: Hewlett-Packard Company XMM7360 LTE Advanced Modem 
[103c:8337]
-   Flags: fast devsel, IRQ 255
-   Memory at 6e40 (64-bit, non-prefetchable) [disabled] [size=4K]
-   Memory at 6e401000 (64-bit, non-prefetchable) [disabled] [size=1K]
-   Capabilities: 
+  Subsystem: Hewlett-Packard Company XMM7360 LTE Advanced Modem [103c:8337]
+  Flags: fast devsel, IRQ 255
+  Memory at 6e40 (64-bit, non-prefetchable) [disabled] [size=4K]
+  Memory at 6e401000 (64-bit, non-prefetchable) [disabled] [size=1K]
+  Capabilities: 

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

Title:
  WWAN I XMM 7360 LTE-Advanced (Cat 9) doesn't work [8086:7360]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is no driver for it [8086:7360] when using 5.10 kernel.

  $ lspci -nnv -s 55:00.0
  55:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced 
Modem [8086:7360] (rev 01)
   Subsystem: Hewlett-Packard Company XMM7360 LTE Advanced Modem [103c:8337]
   Flags: fast devsel, IRQ 255
   Memory at 6e40 (64-bit, non-prefetchable) [disabled] [size=4K]
   Memory at 6e401000 (64-bit, non-prefetchable) [disabled] [size=1K]
   Capabilities: 

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


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

[Kernel-packages] [Bug 1940665] Re: Lenovo Carbon X1 9th gen no longer powers off

[Rex Tsai]

It would be only useful if we have the boot log of the failure session.
Please reproduce the issue and run the following command to capture the
log.

% journalctl -b -1

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

Title:
  Lenovo Carbon X1 9th gen no longer powers off

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04.3 LTS

  linux-oem-5.10: 5.10.0-1044.46

  Power off system, either through GUI or by shutdown -P now

  Expected result:
  System powers completely off

  What happens:
  System seems to be powering completely off. Screen goes black, but computer 
is still running, getting hot and using battery. Have to press power button for 
4 seconds to power completely off. 

  Solution so far:
  Use linux-generic-something

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


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

[Kernel-packages] [Bug 1940665] Re: Lenovo Carbon X1 9th gen no longer powers off

[Rex Tsai]

Please report the issue with apport-collect 1940665, so we can learn
more about the BIOS and hw configs.

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

Title:
  Lenovo Carbon X1 9th gen no longer powers off

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04.3 LTS

  linux-oem-5.10: 5.10.0-1044.46

  Power off system, either through GUI or by shutdown -P now

  Expected result:
  System powers completely off

  What happens:
  System seems to be powering completely off. Screen goes black, but computer 
is still running, getting hot and using battery. Have to press power button for 
4 seconds to power completely off. 

  Solution so far:
  Use linux-generic-something

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


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

[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware

[Rex Tsai]

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

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

Title:
  [SRU] Revert amdgpu/renoir firmware

Status in OEM Priority Project:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released

Bug description:
  [Impact]
  The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA 
Dongle after the system resumed from S3.

  [Fix]
  Revert below change, this issue is gone.

  commit a543b9c1bfd12e60d962acd48108234481a8581f
  Author: Alex Deucher 
  Date:   Thu Jul 1 12:23:11 2021 +0800

  amdgpu: update renoir firmware from 21.20

  BugLink: https://bugs.launchpad.net/bugs/1934014

  From internal git commit:
  8b05e03570818d047d7ea0a7388c89c4192fd20b

  Signed-off-by: Alex Deucher 
  Signed-off-by: Josh Boyer 
  (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0)
  [khfeng: Squashed multiple updates into one commit]
  Signed-off-by: Kai-Heng Feng 
  Signed-off-by: Timo Aaltonen 

  [Test]
  Verify S3 on renoir's platforms.

  [Where problems could occur]
  Renoir based systems can't resume from s2idle.

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


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

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

Hi,

WW38.2'21: Confirmed Intel LAN issue; promoted to LAN engineering. Please see 
further details below.
Please verify the issue again with FIA wa.7z, which should be final solution 
candidate.

Root cause:

The power management flow on TGL shut down a clock that is required for
exiting from K1 (K1 Is the equivalent of L1 for the proprietary PCIe
like interface between the MAC and the PHY).

Due to missing configuration, the clock request was not asserted
properly which caused a long K1 exit latency which is the reason for the
performance issue.

Solution:

Update the HW MAC initialization flow. Do not gate DMA clock from the
modPHY block. Keeping this clock will prevent drop packets sent in burst
mode on the Kumaran interface.

** Attachment added: "FIA wa.7z"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925/+attachment/5526765/+files/FIA%20wa.7z

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros1673 F pulseaudio
   /dev/snd/controlC1:  ros1673 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20W0004MGE
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31
  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.10.0-102

[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in Nouveau Xorg driver:
  Unknown
Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Hirsute:
  In Progress
Status in xorg-server source package in Impish:
  Fix Released

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

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


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

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

Hi Shengyao,
According to Lenovo, the issue can be reproduced on a failed system in Windows 
environment. Would you please try? If you can see the same result, let's do 
debug in Windows environment.

Please provide your system information for me to understand if it is vPro or 
non-vPro system.
--
SoC Model:
BIOS version:
Windows version:
Windows LAN driver version:
ME FW version:
--

If you can reproduce the issue in Windows, please follow steps below to collect 
logs. 
1.) Boot to system to S0
2.) Unzip the folder
3.) Open Windows PowerShell as administrator in the folder of debug tool
4.) Run start_trace.bat e1d 0x
5.) Start to reproduce the issue
6. Run stop_trace.bat e1d 0x

Rex

** Attachment added: "Intel-LAN-Trace-Tool.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925/+attachment/5523584/+files/Intel-LAN-Trace-Tool.zip

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros1673 F pulseaudio
   /dev/snd/controlC1:  ros1673 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20W0004MGE
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31
  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.10.0-1026-o

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

Hi Shengyao,
Thanks; I thought the option is to disable GbE. I will find correct option for 
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/1927925

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros1673 F pulseaudio
   /dev/snd/controlC1:  ros1673 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20W0004MGE
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31
  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.10.0-1026-oem N/A
   linux-backports-modules-5.10.0-1026-oem  N/A
   linux-firmware   1.187.12
  Tags:  focal
  Uname: Linux 5.10.0-1026-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkP

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

@Shengyao Xue, 
1.) Intel suspected that this Lenovo issue might be related to this issue: 
https://bugs.launchpad.net/somerville/+bug/1933807 on Intel vPro system. Lenovo 
did mention that vPro systems have the same issue.

2.) Intel SW debug engineer is adding some debug prints to the I219
runtime power managements callbacks to see if they are getting called,
even though they shouldn’t. I will share patches once it is available.

3.) Can you please try below and see whether you can reproduce the
issue? Please also pay attention if the system cannot enter Suspend to
Idle after applying this.

echo on > /sys/bus/pci/devices/\:00\:16.0/power/control
Explanation, taken from 
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-power:

What:  /sys/devices/.../power/control
Date:  January 2009

Contact:   Rafael J. Wysocki r...@rjwysocki.net

Description:

   The /sys/devices/.../power/control attribute allows the
user

   space to control the run-time power management of the
device.


   All devices have one of the following two values for the

   power/control file:


   + "auto\n" to allow the device to be power managed at run
time;

   + "on\n" to prevent the device from being power managed;


   The default for all devices is "auto", which means that
they may

   be subject to automatic power management, depending on
their

   drivers.  Changing this attribute to "on" prevents the
driver

   from power managing the device at run time.  Doing that
while

   the device is suspended causes it to be woken up.

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevi

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

Hi Andreas,
Can you please share whether your system is a Intel vPro system?

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros1673 F pulseaudio
   /dev/snd/controlC1:  ros1673 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20W0004MGE
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31
  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.10.0-1026-oem N/A
   linux-backports-modules-5.10.0-1026-oem  N/A
   linux-firmware   1.187.12
  Tags:  focal
  Uname: Linux 5.10.0-1026-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:

[Kernel-packages] [Bug 1936009] Re: The internal mic of Dell Precision 5750 can't record sound

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

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

Title:
  The internal mic of Dell Precision 5750 can't record sound

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade the linux kernel, the mixer names of rt715 is changed, the 
current alsa-ucm-conf will fail to initialize that codec, then users can't 
record sound from internal mic since the internal mic is routed to the codec 
rt715.

  [Fix]
  Backport 3 upstream commits, after applying these 3 commits, the ucm conf 
file dosn't initialize the codec with hardcoded mixer names anymore, it will 
check the existence of the mixer name first, then conditionally initialize the 
codec.

  [Test]
  run 'alsactl init 1' on the precision 5750 with old and new kernel, there is 
no error logs, use the internal mic to record sound, it could record 
successfully.

  [Where problems will occur]
  The change only affects the rt715 codec, so far, that codec only connects to 
the internal mic on Dell soundwire audio machines, so it could introduce 
regression on the internal mic like users can't record sound via internal mic 
anymore on the Dell soundwire audio machines. But this possibility is very low 
since we already tested these 3 commits on different Dell soundwire audio 
machines (latitude and precision). We tested it with old kernel and new kernel, 
all worked well.

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


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

[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
  wireless [8086:a0f0]

Status in Linux Firmware:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Whenever I am using a wireless connection, the image freezes roughly
  every two minutes. Sometimes, email cannot be retrieved / computer
  complains the connection was momentarily lost.

  - If I am on a wire, this problem does NOT occur.
  - This problems occurs on wireless independent of the platform used (behavior 
seen in both Google Hangout and Zoom)
  - This problem does NOT occur on Windows. I did a meeting where both my Linux 
and Windows machines were connected to the same meeting and using the same wifi 
router, and while the performance on Windows was flawless, unfortunately it was 
not so on the Ubuntu box. So I don't think my wifi router or network is to 
blame.
  - As far as I can recall, the problem used not to be there 2 weeks ago. So it 
may have been introduced by a recent update.
  - As communicated before, I am on a certified machine from Dell, recently 
purchased with Ubuntu already on board from factory (I assume the logs there 
were sent to you would contain the information).
  - I tried to generate a log on the wireless, but the process did not let me 
do this very easily. I am more than happy to send you additional information - 
but please let me know which package you want me to spy upon exactly, as I am 
not sure what would be helpful in this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
  Uname: Linux 5.10.0-1029-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 18 09:47:58 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0991]
  InstallationDate: Installed on 2021-04-24 (54 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem 
root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 2.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.1
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1928694] Re: [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those landing upstream

[Rex Tsai]

** Tags added: cezanne renoire

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

Title:
  [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those
  landing upstream

Status in amd:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  New

Bug description:
  The following patches are accepted into upstream for 5.14 and should
  displace the existing patches carried in OEM tree.

  *  "ACPI: processor idle: Fix up C-state latency if not ordered" replaces the 
hack to hardcode latency values for HP's RN systems.
  * "ACPI: PM: s2idle: Add missing LPS0 functions for AMD" has been accepted

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

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

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros1673 F pulseaudio
   /dev/snd/controlC1:  ros1673 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20W0004MGE
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31
  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.10.0-1026-oem N/A
   linux-backports-modules-5.10.0-1026-oem  N/A
   linux-firmware   1.187.12
  Tags:  focal
  Uname: Linux 5.10.0-1026-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrN

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
 Assignee: Bin Li (binli) => Shengyao Xue (xueshengyao)

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1924970] Re: Add soundwire sdca codec support

[Rex Tsai]

** Changed in: oem-priority
   Status: New => Fix Released

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

Title:
  Add soundwire sdca codec support

Status in OEM Priority Project:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * The output device in sound settings will non-functional.
     Sound input device will be empty.
     An upstream commit add supports for SDW sdca codec support.

  [Test Plan]

   * Open settings and select Sound column.
     Testing speaker won't have any sound output.
   * Try to update files mentioned here
     
https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/a7f348bb37d2b3254801702299ab2c76833a3c16
     
https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/651c2c851bf17a1d76e0a046eb33eccbcf98845f
   * alsactl init

   * Open settings and select Sound column and test output device again.
     Sound devices work properly.

  [Where problems could occur]

   * This change adds new hardware support.

   * The change only adds new hardware support,
     it will not affect other codec device.

  [Other Info]

   * The change has been verified on Dell machine with sdca codec.

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

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

[Kernel-packages] [Bug 1836215] Re: [DELL][BIONICS] Redpine driver got crashed during shutdown/reboot

[Rex Tsai]

** Tags added: redpine

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

Title:
  [DELL][BIONICS] Redpine driver got crashed during shutdown/reboot

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  SRU Justification:
  --

  Impact:
  ---
    Kernel crash upon shutdown or rebooting the device.

  Test case:
  --
    1) Power up the device, Redpine modules are loaded by default.
    2) Reboot or shutdown the device.
    3) Observe the behavior.

  Result:
  ---
     Redpine driver crashes the entire kernel and below is the crash log.
     ... skipping ...
     [ 47.002030] BUG: unable to handle kernel NULL pointer dereference
  at 0038
     [ 47.010828] IP: rsi_shutdown+0x2c/0x100 [rsi_sdio]
     [ 47.016180] PGD 0 P4D 0
     [ 47.019025] Oops:  1 SMP PTI
     [ 47.136275] CPU: 1 PID: 1 Comm: systemd-shutdow Not tainted
  4.15.0-1035-oem #40-Ubuntu
     [ 47.145131] Hardware name: Dell Inc. Edge Gateway 3001/0YMHCG,
  BIOS 01.00.08 10/23/2018
     [ 47.154096] RIP: 0010:rsi_shutdown+0x2c/0x100 [rsi_sdio]
     [ 47.160039] RSP: 0018:b08dbd78 EFLAGS: 00010246
     [ 47.165887] RAX:  RBX: a08b77f1d000 RCX: 

     [ 47.173869] RDX: 0002 RSI: c07aa77f RDI: 
0001
     [ 47.181851] RBP: b08dbd90 R08:  R09: 
b08dbc50
     [ 47.189834] R10:  R11: 023a R12: 
a08b6d94
     [ 47.197816] R13: a08b3cbfb408 R14: 8f556137 R15: 
a08b3cbfb468
     [ 47.205801] FS: 7f85cd093940() GS:a08b70b0()
  knlGS:
     [ 47.214854] CS: 0010 DS:  ES:  CR0: 80050033
     [ 47.221281] CR2: 0038 CR3: 6a93 CR4: 
001006e0
     [ 47.229262] Call Trace:
     [ 47.232017] device_shutdown+0x14e/0x200
     [ 47.236416] kernel_power_off+0x35/0x70
     [ 47.240711] SYSC_reboot+0x132/0x210
     [ 47.244721] ? SYSC_rt_sigtimedwait+0x88/0xe0
     [ 47.249604] ? do_writev+0x61/0xf0
     [ 47.253411] ? do_writev+0x61/0xf0
     [ 47.257219] ? sigprocmask+0x6f/0xa0
     [ 47.261225] SyS_reboot+0xe/0x10
     [ 47.264841] do_syscall_64+0x73/0x130
     [ 47.268945] entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  Root cause analysis:
  
     Device operating mode 8(bluetooth alone), our driver supports multiple 
modes like 13(WiFi + Bluetooth), WiFi related structures are not been 
initialized in Bluetooth alone mode(8), dereferencing them in rsi_shutdown 
function causes crash. In Redpine driver, this NULL check is missed. Hence, 
Added the fix for the same.

  Fix:
  
     Added proper NULL check in rsi_shutdown function.

  Regression Potential:
  -
  This is a very direct issue, since the driver is getting crashed 
while reboot. We rebooted multiples times, checked the driver stability. Every 
thing ran smooth.

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

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

[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04

[Rex Tsai]

Dell Precision 5750 is a hardware platform using Intel Soundwire
technology. The current official support scope on this certified
platform is only targeting 20.04, with 5.10 oem kernel.

The platform is supported by "oem-somerville-bronn-meta" meta packages,
it's only available in 20.04.

% rmadison oem-somerville-bronn-meta  
 oem-somerville-bronn-meta | 20.04~ubuntu1 | focal-updates | source, all


** Changed in: oem-priority
   Status: New => Won't Fix

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

Title:
  No sound output/input available after installing 21.04

Status in OEM Priority Project:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Image: Hirsute 21.04 (20210415 daily build)

  Device: Dell Precision 5750

  After installing 21.04, the sound card is unavailable. In Sound
  Settings, there is only one choice: "Dummy Output" .

  The only way to hear sound is to connect a Bluetooth speaker.

  Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:

  https://certification.ubuntu.com/hardware/202002-27726

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-generic 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1561 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 15:10:05 2021
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: Dell Inc. Precision 5750
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-generic N/A
   linux-backports-modules-5.11.0-14-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

Title:
  No sound output/input available after installing 21.04

Status in OEM Priority Project:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Image: Hirsute 21.04 (20210415 daily build)

  Device: Dell Precision 5750

  After installing 21.04, the sound card is unavailable. In Sound
  Settings, there is only one choice: "Dummy Output" .

  The only way to hear sound is to connect a Bluetooth speaker.

  Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:

  https://certification.ubuntu.com/hardware/202002-27726

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-generic 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1561 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 15:10:05 2021
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: Dell Inc. Precision 5750
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-generic N/A
   linux-backports-modules-5.11.0-14-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6

[Rex Tsai]

** Tags added: ipu6

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

Title:
  Support MIPI camera through Intel IPU6

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-firmware source package in Hirsute:
  Invalid
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  There are new platforms with MIPI camera based on Intel IPU6(Imaging
  Processing Unit version 6) currently unsupported in Ubuntu.

  [Fix]

  Intel IPU6 can be enabled by integration of following kernel driver,
  firmware, userspace HAL libraries as well as a GStreamer source element:

* https://github.com/intel/ipu6-drivers
* https://github.com/intel/ipu6-camera-bins
* https://github.com/intel/ipu6-camera-hal
* https://github.com/intel/icamerasrc

  This patchset took kernel patches from intel/ipu6-drivers.

  [Test Case]

  With kernel/firmware properly installed, the hardware should be ready for
  further development:

$ dmesg | grep ipu
intel-ipu6 intel-ipu: enabling device ( -> 0002)
intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1)
intel-ipu6 intel-ipu: physical base address 0x605400
intel-ipu6 intel-ipu: mapped as: 0x97793328
intel-ipu6 intel-ipu: IPU in secure mode
intel-ipu6 intel-ipu: IPC reset done
intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin
intel-ipu6 intel-ipu: FW version: 20201222
intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE
intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE
intel-ipu6 intel-ipu: CSE authenticate_run done
intel-ipu6 intel-ipu: IPU driver version 1.0
intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8
intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0
intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1
  port is 1
intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed.
intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036

  There should be nearly 24 video4linux devices created under /dev.

  [Where problems could occur]

  MIPI camera through Intel IPU6 takes also firmware blobs loaded in
  runtime from user space, addtional softwares are also required to
  fully enable it for oridinary use. The exposed video devices are hidden
  from general users and a relay daemon+v4l2loopback is used to enable
  use from existing applications.

  >From kernel's point of view, there is still a known issue that it takes
  root priviledge to access these devices.

  [Other Info]

  So far Intel has no plan to commit this driver to upstream yet, so it's
  only nominated for oem-5.10. It will only be nominated to generic
  kernels when the plan/requirements have changed.

  The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's
  reverted to avoid unnecessary changes to existing users.

  == original bug description ==

  The Intel imaging processing unit version 6, found in Intel SoCs and
  used for capturing images and video from a camera sensor is enabled by
  integration of following kernel driver, firmware, userspace HAL
  libraries as well as a GStreamer source element:

    * https://github.com/intel/ipu6-drivers
    * https://github.com/intel/ipu6-camera-bins
    * https://github.com/intel/ipu6-camera-hal
    * https://github.com/intel/icamerasrc

  With all components properly installed, the hardware should be ready
  for further development:

    intel-ipu6 intel-ipu: enabling device ( -> 0002)
    intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1)
    intel-ipu6 intel-ipu: physical base address 0x605400
    intel-ipu6 intel-ipu: mapped as: 0x97793328
    intel-ipu6 intel-ipu: IPU in secure mode
    intel-ipu6 intel-ipu: IPC reset done
    intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin
    intel-ipu6 intel-ipu: FW version: 20201222
    intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE
    intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE
    intel-ipu6 intel-ipu: CSE authenticate_run done
    intel-ipu6 intel-ipu: IPU driver version 1.0
    intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8
    intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0
    intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1
    intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed.
    intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036

  This one equips an OV01A1S sensor, and HM11B1 is also supported.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u 

[Kernel-packages] [Bug 1897110] Re: [Nvidia] sometimes cannot control brightness on some high-end Lenovo ThinkPads

[Rex Tsai]

The issue is addressed in 450.76 driver.

** Changed in: oem-priority
   Status: In Progress => Won't Fix

** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
   Status: New => Won't Fix

** Changed in: oem-priority/focal
   Status: New => Won't Fix

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

Title:
  [Nvidia] sometimes cannot control brightness on some high-end Lenovo
  ThinkPads

Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project focal series:
  Won't Fix
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]
  On some high-end Lenovo ThinkPads with dual GPUs(Intel+Nvidia), there is a 
setting in BIOS to choose Hybrid Mode(means enable both Intel and Nvidia GPUs) 
and Discrete Mode(means only enable Nvidia GPU)

  We found that with the latest nvidia-graphics-drivers-450 (450.66), if
  the laptop's BIOS change to Discrete Mode, then Ubuntu 20.04 sometimes
  cannot control the monitor brightness, the fail rate is about 50%.

  [Fix]
  We get a new version of nvidia driver from Nvidia, 450.76, which can fix this 
issue in our testing.

  [Regression Risk]
  Low, upstream driver.

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

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

[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device

[Rex Tsai]

The upstream alia-lib has not yet accepted the patch[1].

Shengyao, Hui, please clarify all "Cmedia Audio" chip does not support
"Digital Output(S/PDIF)" as iec958 device.


[1] conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device by 
jason77-wang · Pull Request #122 · alsa-project/alsa-lib - 
https://github.com/alsa-project/alsa-lib/pull/122/commits/879d57d979b59be8632ba788d5f567f2b6ec0c19

Regards
-Rex

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

Title:
  [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-
  Audio.pcm.iec958_device

Status in OEM Priority Project:
  In Progress
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Where problems will occur]
  This fix limits to the Cmedia Audio only, other devices are unaffected.

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

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

[Kernel-packages] [Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [SRU] No sound from internal card chtmax98090 (missing UCM2 files in
  alsa-ucm-conf)

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Groovy:
  In Progress

Bug description:
  [Impact]
  There is no ucm for ASUS C300 in the 20.04 and 20.10, as a result,
  the audio doesn't work on this machine after installing the 20.04 or
  20.10.

  [Fix]
  The ucm files for this machine are in the alsa-ucm-conf 1.2.3,
  cherry-pick them to ubuntu 20.04 and 20.10

  [Test Case]
  After booting up, use speaker to play some sound, it works well,
  plug a headset, play sound to headphone, it basically works but has
  some crankling noise, it is a kernel issue for this noise.

  [Regression Risk]
  This SRU adds new ucm files, If the machine uses the audio driver
  of chtmax98090, it will apply this new added ucm files, there will
  be speaker/headphone in the UI. So the possible regression is with
  this SRU, users could see the audio devices in the UI but the audio
  doesn't work (without this SRU, users couldn't see the audio devices
  in the UI at all and the audio doesn't work). This possibility is
  low since we tested it on the ASUS C300.


  Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script)  - 
Kubuntu Focal minimal fresh installation.
  The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in 
alsamixer and it's not muted.
  I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case 
config files: no success.
  I tried and unmute speakers left and right in alsamixer: no success.

  I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the
  same issue.

  I'm running on the same rig Debian Bullseye, kernel 5.4: sound card
  output and input are both working perfectly - I noticed that in
  Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH
  (the HDMI card), while in Debian I find Pulseaudio.

  I attach the alsa-info.sh output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.17
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Apr  7 08:55:46 2020
  InstallationDate: Installed on 2020-04-04 (2 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gabriel3937 F pulseaudio
   /dev/snd/controlC0:  gabriel3937 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-04 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp.
   Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Quawks
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-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: 03/17/2020
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.11.2
  dmi.board.name: Quawks
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr:
  dmi.product.name: Quawks
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-package

[Kernel-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress
Status in nvidia-prime source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  In Progress
Status in nvidia-prime source package in Groovy:
  In Progress
Status in nvidia-settings source package in Groovy:
  In Progress

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions

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

[Kernel-packages] [Bug 1842106] Re: [EHL][OSE] HS-UART implementation

[Rex Tsai]

** Tags added: ehl

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

Title:
  [EHL][OSE] HS-UART implementation

Status in intel:
  In Progress
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:
  Elkhart Lake has Offload Services Engine (OSE) that will be BIOS configurable 
either to have some RTOS take control of its IO blocks or hand them off to 
running OS. IoTG has asked to support UART. This should be based on Synopsys 
v4.00a specification.

  Target Release: 20.10
  Target Kernel: TBD

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

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

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[Rex Tsai]

** Changed in: oem-priority
   Status: Incomplete => Won't Fix

** Changed in: oem-priority
 Assignee: Rex Tsai (chihchun) => (unassigned)

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

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in OEM Priority Project:
  Won't Fix
Status in backport-iwlwifi-dkms package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

  [   59.582667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.582669] Call Trace:
  [   59.582678]  ? __switch_to_asm+0x41/0x70
  [   59.582703]  ieee80211_scan_work+0xf4/0x4b0 [mac80211]
  [   59.582710]  process_one_work+0x1de/0x420
  [   59.582715]

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

[Rex Tsai]

It seems the V3 patch[1] is merged[2]. Is that patch enough to address
the problem we have?


[1] [v3] PCI: vmd: Offset Client VMD MSI-X vectors - Patchwork - 
https://patchwork.kernel.org/project/linux-pci/patch/20200914190128.5114-1-jonathan.derr...@intel.com/
[2] PCI: vmd: Offset Client VMD MSI-X vectors · torvalds/linux@f6b7bb8 - 
https://github.com/torvalds/linux/commit/f6b7bb847ca821a8aaa1b6da10ee65311e6f15bf

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Confirmed
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

[Kernel-packages] [Bug 1905591] Re: no brightness control after update from 450 to 455

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  no brightness control after update from 450 to 455

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Triaged

Bug description:
  On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
  GTX 1050 Ti Mobile]

  Updating to nvidia-driver-455 results in loss of brightness control.
  On boot, the laptop display brightness is somewhat less than fully
  bright and cannot be changed.   The brightness up/down keys do pop up
  the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/*
  values do change, but the actual display's brightness does not.

  Problem occurs with either version of nvidia-driver-455 (the archive
  or the ~graphics-drivers/PPA). Normal functionality returns if I
  downgrade to any version of nvidia-driver-450.

  Note also that manually applying this to 
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
  
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04
  Codename: bionic

  kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
  2020 x86_64 x86_64 x86_64 GNU/Linux

  nvidia-driver-455: 455.38-0ubuntu0.18.04.1

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

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

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[Rex Tsai]

** Changed in: oem-priority
 Assignee: Alex Tu (alextu) => Rex Tsai (chihchun)

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

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in OEM Priority Project:
  Incomplete
Status in backport-iwlwifi-dkms package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

  [   59.582667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.582669] Call Trace:
  [   59.582678]  ? __switch_to_asm+0x41/0x70
  [   59.582703]  ieee80211_scan_work+0xf4/0x4b0 [mac80211]
  [   59.582710]  process_one_work+0x1de/0x420
  [   59.582715]  worker_thread+0x32/0x410
  [   59.582719]  kthread+0x121/0x140
  

[Kernel-packages] [Bug 1900883] Re: Add new iwlwifi firmware to solve AX201 hang

[Rex Tsai]

The change is proposed on - [PATCH 0/1] Add new iwlwifi firmware to
solve AX201 hang - https://lists.ubuntu.com/archives/kernel-
team/2020-October/114185.html

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

Title:
  Add new iwlwifi firmware to solve AX201 hang

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Confirmed

Bug description:
  [Impact]
  Intel AX201 firmware crashes or hardware RX ring buffer hangs after S3.

  [Fix]
  Use new firmware from linux-firmware.git can solve the issue.

  [Test]
  WiFi works for each cycle of 1000 S3 cycles.

  [Regression Potential]
  Both Focal 5.4 and OEM 5.6 kernel use this firmware, so it might regress
  current 5.4 users. I did a smoke test with this firmware on Focal 5.4,
  and I didn't see any regression. 

  Instead of cherry-pick the commit, only add the firmware needed for
  AX201 to minimize the regression risk.

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

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

[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Dell XPS 13 (7390) Display Flickering - 19.10

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  Hi there,
  I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to 
replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, 
there is one issue which occurs frequently whereby the display flickers and 
becomes unusable. The best way to describe the appearance is that the image 
becomes heavily distorted. 

  Sometimes it only happens for a split second, other times it is
  permanently distorted. When this happens, simply closing the laptop
  lip and re-opening seems to put the display back into it's correct
  state.

  I didn't experience this issue on 18.04 LTS which is why I believe
  it's a Software Bug within 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 11:11:43 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-10-25 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[Rex Tsai]

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

** Changed in: backport-iwlwifi-dkms (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in OEM Priority Project:
  Incomplete
Status in backport-iwlwifi-dkms package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

  [   59.582667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.582669] Call Trace:
  [   59.582678]  ? __switch_to_asm+0x41/0x70
  [   59.582703]  ieee80211_scan_work+0xf4/0x4b0 [mac80211]
  [   59.582710]  process_one_work+0x1de/0x420
  [   59.582715]  worker_thread+0x32

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[Rex Tsai]

Hi, Peter

The backport-iwlwifi-dkms is the offical supported version, that we
recommended you to use.

Somehow, you receive an OLD image with a non-supported version of dkms.
We would like to find out what was the version of the image you are
using, could you run `ubuntu-report show`? or bto.xml in the recovery
partition or provide the Serial Number of your machine (sudo dmidecode)?

Thanks

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

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in OEM Priority Project:
  Incomplete
Status in backport-iwlwifi-dkms package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

  [   59.582667] DR3:  DR6: fffe0ff0

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Rex Tsai]

** Tags added: oem-priority originate-from-1896145 sutton

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

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

Title:
  initramfs unpacking failed

Status in OEM Priority Project:
  New
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

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

[Kernel-packages] [Bug 1883065] Re: Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without plugged in power cable

[Rex Tsai]

** Tags added: oem-priority

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

Title:
  Dell Latitude/Precision, sig=0x806ec/20090609: Linux hangs without
  plugged in power cable

Status in OEM Priority Project:
  New
Status in intel-microcode package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Already present reported in project *dell-sputnik*. (Note, it happened
  here also without suspend/resume.):

  1.  https://bugs.launchpad.net/dell-sputnik/+bug/1661741
  2.  Quote from 
https://bugs.launchpad.net/dell-sputnik/+bug/1661741/comments/26:

  > A similar bug affects several Dell laptop models:
  > - Dell 5480/5488 :
  >  https://bugs.launchpad.net/dell-sputnik/+bug/1866343
  > - Dell E5470 :
  > https://bugs.launchpad.net/dell-sputnik/+bug/1661741
  > (Note that the bug https://bugs.launchpad.net/dell-sputnik/+bug/1661741 
is not fixed; it has been changed, by error, to fixed. Please, it will be nice 
if somebody can change the status to "confirmed")
  > - Dell 7740 :
  > https://bugs.launchpad.net/dell-sputnik/+bug/1871491
  >
  > I suppose that the bug can also affect Dell precision 7730

  After experiencing this already on the Dell Latitude 5480/5488
  (https://bugs.launchpad.net/dell-sputnik/+bug/1866343), we have seen
  this now too with the Dell Precision 3540 (with dedicated AMD graphics
  card).

  Without the power cord plugged in, the system started fine, then
  updating packages, including the Linux kernel, turning the system off,
  and right back on, it went to GRUB, and GRUB was able to load Linux
  and initrd, and starting Linux it hung.

  Num lock key didn’t respond (but also didn’t blink – no idea if this
  should work), and Ctrl + Alt + Del didn’t work either. So, the system
  had to be powered off by pressing the power button for some (ten(?))
  seconds.

  Subsequent tries didn’t help, until we remembered the issues with the
  other device, and plugging in the power cord fixed it.

  With the power cable unplugged, it didn’t boot.

  The state of the connected power cable only mattered, when starting
  the Linux kernel. That means, plugging it in, when GRUB was active,
  the system booted. Removing the cable, when GRUB was running, Linux
  hung.

  I tried to get Linux messages, but `debug nomodeset earlyprintk=efi`
  didn’t get Linux to output any messages.

  ### Workarounds ###

  I was able to get Linux booting by adding either one of the following
  Linux kernel parameters.

  1.  `maxcpus=1` (once it started with `maxcpus=2`)
  2.  `nosmp`
  2.  `acpi=off`
  3.  `nolapic`

  In this state, there was only one CPU online. Trying to bring one more
  online, the system always froze instantly.

  echo 1 | sudo tee /sys/devices/system/cpu/cpu1/online

  (Nothing in pstore either.) (Where maxcpus=2` worked, we were able to
  bring a third CPU online, but the system froze when trying the
  fourth.)

  ### Reproducibilty ###

  Letting the system sit over night, and trying again in the morning,
  unfortunately, we did *not* test without a power cable plugged in, as
  we had an idea to test the non-USB-Type-C power cable. With that the
  system started.

  Powering the system off, and unplugging the cable, the system booted
  without issues. So something changed.

  We weren’t able to get it into a state, where it doesn’t boot in the
  last hour, but we would like this investigated, as we are giving these
  systems to our users.

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

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

[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series

[Rex Tsai]

** Tags added: originate-from-1879213 sutton

** Tags added: originate-from-1879232

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

Title:
  Introduce the new NVIDIA 450-server and the 450 UDA series

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

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

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

[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio

[Rex Tsai]

** Tags added: oem-priority timbuktu

** Tags added: originate-from-1889531

** No longer affects: oem-priority

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

Title:
  alsa/hdmi: support nvidia mst hdmi/dp audio

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed

Bug description:
  This is the justification for focal:

  This patchset will introduce a big change on hda_jack and hda_hdmi,
  So I sent the patcheset to oem-b 4 months ago. After 4 months of running
  oem-b kernel, there is no any regression reported on this patchset,
  now I am backporting the patchset to our focal kernel since our oem
  project is waiting for the patchset to be landed to ubuntu 5.4 kernel
  ASAP.

  This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc,
  so there is no need to send the patchset to oem-5.6 or groovy kernel.

  [Impact]
  On some LENOVO I+N machines, when setting the graphic mode to discrete,
  The dp/hdmi audio on the Docking Gen2 can't work with this machine +
  LENOVO Docking Gen2, users can't find the hdmi audio entry in the
  gnome-sound-setting.

  [Fix]
  Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1,
  those patches could fix this issue.

  [Test Case]
  set the machien to discrete, plug the dock gen2 to it, then boot, after
  booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works.

  test other machines without Nvidia graphic or without gen2, their hdmi/dp
  audio still work, and check other output/input devices like headphone,
  microphone, they all worked as well as before.

  [Regression Risk]
  one regression possibility is the audio jacks (including analogue and hdmi)
  can't work anymore, that means after users plug a headphone, headset, hdmi
  monitor or microphone to the audio jacks or hdmi connectors, the audio
  driver can't detect the plugging event.

  But regression's possibility is very low:
   - this patchset was already applied to oem-b kernel for 4 months, and
     oem projects didn't report any regression on the patchset
   - I tested the testing focal kernel with this patchset on many machines,
     includes a dell hda audio machine, a dell dmic  machine, a Lenovo I+N
     hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio
     machine, a lenovo amd hda audio machine. The audio on them all worked
     as well as before.

  This is the justification for oem-b

  Drop the B, so far only need to merge this patchset to OEM-B first,
  After the patchset is widely verified with oem-b kernel, I send the
  patchset to B and F then.

  This patchset will add support of mst audio for nvidia hdmi/dp, this
  patchset changes lots of common code on hda_jack and hdmi codec, so it
  is not easy to say it is 100% safe for other machines, but our oem
  project needs this patchset to be backported to ubuntu kernel, because
  the tight sechdule of oem project, we backport this patchset to B and
  OEM-B first, if the hdmi audio works well for a period of time after
  this patchset is merged, I will backport this patchset to focal, maybe
  eoan as well.

  [Impact]
  On some LENOVO I+N machines, when setting the graphic mode to discrete,
  The dp/hdmi audio on the Docking Gen2 can't work with this machine +
  LENOVO Docking Gen2

  [Fix]
  Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1,
  those patches could fix this issue.

  [Test Case]
  set the machien to discrete, plug the dock gen2 to it, then boot, after
  booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works.

  test other machines without Nvidia graphic or without gen2, their hdmi/dp
  audio still work.

  [Regression Risk]
  Low, those patches come from mainline kernel, I have tested those patches
  on the machiens with or without nvidia hdmi, and on the machines with or 
without
  docks, all worked well as before.

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

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

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rex Tsai]

Upstream found a regression[1] with the new patch in #128, Jeremy will
review and re-test the solution in focal before asking for sponsorship.

[1] Multiple regressions in multi-user environments since 3.36.2 (#602)
· Issues · GNOME / gdm · GitLab -
https://gitlab.gnome.org/GNOME/gdm/-/issues/602


** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #602
   https://gitlab.gnome.org/GNOME/gdm/-/issues/602

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  Triaged
Status in gdm3 package in Ubuntu:
  In Progress
Status in gnome-session package in Ubuntu:
  Confirmed
Status in grub2 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards (with nvidia-driver-440), enable 
auto-login (either during installation or after installation) will fail (either 
stuck in gdm login screen and not able to login even typing correct password).

  [ Test Case ]
  Here are two scenario of auto login with groovy (20.10) daily build[1]:

  1) Checked "Install third-party software" (e.g. nvidia-driver) with
  enabling "Login automatically" during installation.

  2) Install groovy daily build with default options, after installation 
completed:
  2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive.
  2.2) Enable "Login automatically" from system settings.

  Then reboot.

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) 
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] 
and it works good. It passed the 30 times reboot stress test by using 
stress/reboot_30 from checkbox.

  [1] sha256sum: 
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
  [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4
  [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801

  ---

  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  Upgrad

[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Introduce the new NVIDIA 450-server and the 450 UDA series

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

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

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

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Alex Tu (alextu)

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

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in OEM Priority Project:
  New
Status in backport-iwlwifi-dkms package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

  [   59.582667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.582669] Call Trace:
  [   59.582678]  ? __switch_to_asm+0x41/0x70
  [   59.582703]  ieee80211_scan_work+0xf4/0x4b0 [mac80211]
  [   59.582710]  process_one_work+0x1de/0x420
  [   59.582715]  worker_thread+0x32/0x410
  

[Kernel-packages] [Bug 1850089] Re: iwlwifi fails with linux-image-4.15.0-1059-oem

[Rex Tsai]

** Tags removed: somerville
** Tags added: oem-priority

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

Title:
  iwlwifi fails with linux-image-4.15.0-1059-oem

Status in OEM Priority Project:
  New
Status in backport-iwlwifi-dkms package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With the linux-image-4.15.0-1059-oem kernel, wifi does not work at all
  on my Precision 7540 laptop (Intel ax200 wifi)

  This is a regression from 4.15.0-1057 to -1059.

  dmesg shows repeated crashes:

  [   59.582277] [ cut here ]
  [   59.582368] WARNING: CPU: 13 PID: 189 at 
/var/lib/dkms/oem-wifi-intel-iwlwifi-lp1810708-4.15-stack-dev-e33ba6d-core43-10/1.0/build/net/mac80211/scan.c:376
 __ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582369] Modules linked in: rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc vmnet(OE) 
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs snd_hda_codec_hdmi 
overlay snd_hda_codec_realtek snd_hda_codec_generic joydev hid_multitouch cmac 
dell_rbtn bnep binfmt_misc nls_iso8859_1 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core btusb btrtl videodev btbcm btintel media bluetooth ecdh_generic 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp dell_wmi dell_laptop dell_smbios dcdbas 
wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt mxm_wmi xt_addrtype 
dell_smm_hwmon
  [   59.582436]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
arc4 kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw 
idma64 virt_dma iwlmvm(OE) mac80211(OE) iwlwifi(OE) cfg80211(OE) compat(OE) 
rtsx_pci_ms memstick snd_hda_intel nf_conntrack_ipv4 nf_defrag_ipv4 
snd_hda_codec xt_conntrack snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq mei_me mei snd_seq_device snd_timer snd 
intel_lpss_pci soundcore ucsi_acpi intel_lpss processor_thermal_device 
typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal 
int340x_thermal_zone dell_smo8800 wmi int3400_thermal mac_hid intel_hid 
acpi_pad acpi_thermal_rel sparse_keymap nvidia_uvm(OE) sch_fq_codel 
ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp
  [   59.582501]  nf_nat nf_conntrack_ftp nf_conntrack ib_iser rdma_cm iw_cm 
ib_cm ib_core iptable_filter iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) i915
  [   59.582550] ieee80211 phy0: Hardware restart was requested
  [   59.582552]  crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nvidia(POE) 
rtsx_pci_sdmmc pcbc i2c_algo_bit aesni_intel e1000e drm_kms_helper aes_x86_64 
crypto_simd glue_helper syscopyarea ptp sysfillrect cryptd sysimgblt pps_core 
rtsx_pci thunderbolt fb_sys_fops ahci ipmi_devintf drm libahci ipmi_msghandler 
i2c_hid hid video
  [   59.582588] CPU: 13 PID: 189 Comm: kworker/u32:2 Tainted: PW  OE   
 4.15.0-1059-oem #68-Ubuntu
  [   59.582590] Hardware name: Dell Inc. Precision 7540/0CYJDT, BIOS 1.1.3 
06/21/2019
  [   59.582618] Workqueue: phy0 ieee80211_scan_work [mac80211]
  [   59.582644] RIP: 0010:__ieee80211_scan_completed+0x19f/0x3d0 [mac80211]
  [   59.582647] RSP: 0018:b2f5c3bd7de8 EFLAGS: 00010282
  [   59.582650] RAX: 0024 RBX: c2390c30 RCX: 

  [   59.582652] RDX:  RSI: 92043bd56498 RDI: 
92043bd56498
  [   59.582654] RBP: b2f5c3bd7e18 R08: 052c R09: 
0004
  [   59.582655] R10:  R11: 0001 R12: 
92042a0a0f80
  [   59.582657] R13: 0001 R14:  R15: 

  [   59.582660] FS:  () GS:92043bd4() 
knlGS:
  [   59.582662] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.582664] CR2: 5558ff22b668 CR3: 00037ae0a004 CR4: 
003606e0
  [   59.582666] DR0:  DR1:  DR2: 

  [   59.582667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.582669] Call Trace:
  [   59.582678]  ? __switch_to_asm+0x41/0x70
  [   59.582703]  ieee80211_scan_work+0xf4/0x4b0 [mac80211]
  [   59.582710]  process_one_work+0x1de/0x420
  [   59.582715]  worker_thread+0x32/0x410
  [   59.582719]  kthread+0x121/0x140
  [   59.582722]  ? process_one_work+0x420/0x420
  [   59.5

[Kernel-packages] [Bug 1859538] Re: Harrison Peak wifi / BT support

[Rex Tsai]

** No longer affects: oem-priority

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

Title:
  Harrison Peak  wifi / BT support

Status in HWE Next:
  New
Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  HrP2 will be supported in CML/TGL platform.

  Target Release: 20.04
  Target Kernel: 5.4

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

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

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rex Tsai]

** Tags added: originate-from-1892498

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in OEM Priority Project:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in grub2 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards, auto-login will fail due to the 
old vt-handoff patch in grub2.

  [ Test Case ]
  1. Boot ubuntu into desktop environment.
  2. Enabled auto login in System->Users
  3. Reboot the system

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Low, the patch just removes vt.handoff part in grub2 package, and I can't 
find any regression in several runs of stress tests.

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801

  ---

  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver

[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04

[Rex Tsai]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => koba (kobako)

** Tags added: stella

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

Title:
  Comet Lake PCH-H RAID not support on Ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
  { PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */

  If Thinkstation P340 configured as RAID mode, It can not find any RAID volume 
disk.
  please update such support. Thanks.

  Regards,
  Jiqi.

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

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

[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04

[Rex Tsai]

Intel has proposed the patch in upstream[1], a testing build of linux-
oem 5.6 is availbile on ppa[2].

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5e125d13371b3049d238a4bf5f2108bfbfe8a900
[2] https://launchpad.net/~kobako/+archive/ubuntu/ppa-lp1888311

** Tags added: oem-priority

** Tags added: sutton

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

Title:
  Comet Lake PCH-H RAID not support on Ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
  { PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */

  If Thinkstation P340 configured as RAID mode, It can not find any RAID volume 
disk.
  please update such support. Thanks.

  Regards,
  Jiqi.

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

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

[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04

[Rex Tsai]

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

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

Title:
  Comet Lake PCH-H RAID not support on Ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
  { PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */

  If Thinkstation P340 configured as RAID mode, It can not find any RAID volume 
disk.
  please update such support. Thanks.

  Regards,
  Jiqi.

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

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

[Kernel-packages] [Bug 1884251] Re: Support Audio Mute LED for two new HP laptops

[Rex Tsai]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  Support Audio Mute LED for two new HP laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Mute LED doesn't work on two new HP laptops.

  [Fix]
  Add IDs to apply quirks to enable mute LED.

  [Test]
  After applying the patch the audio mute LED will light up when speaker is 
muted.

  [Regression Potential]
  Low. The fix limits to two specific systems.

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

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

[Kernel-packages] [Bug 1866156] Re: Wireless LAN RF is hardware blocked forever after r8153 ethernet connected.

[Rex Tsai]

The isse has been address in BIOS version 1.0.0 for  -
https://bugs.launchpad.net/bugs/1803384

** Changed in: oem-priority
 Assignee: Che Cheng (cktenn) => (unassigned)

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

** Changed in: hwe-next
   Status: New => Invalid

** Changed in: oem-priority
   Status: Triaged => Invalid

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

Title:
  Wireless LAN RF is hardware blocked forever after r8153 ethernet
  connected.

Status in HWE Next:
  Invalid
Status in OEM Priority Project:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Dell laptops have an option for power management in the BIOS setting
  to control WLAN radio. If enabled, it will sense the connection of the
  system to a wired network and subsequently disable the selected
  wireless radios (WLAN and/or WWAN). Upon disconnection from the wired
  network, the selected wireless radios will be re-enabled.

  When Dell docking station (the ethernet is Realtek r8153 USB controller), 
with runtime PM enabled, is the wired network, WLAN radio won't be re-enabled 
after unplugging ethernet cable. By checking rfkill, the radio is hard blocked. 
Disable runtime PM of the r8153 USB device can work around this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2160 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-highsparrow+X32
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-10 (54 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 9510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 
root=UUID=d12aa9db-fdec-46cc-aefd-77a0c7e61db2 ro thunderbolt.dyndbg=+p quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-1040-oem-osp1 N/A
   linux-backports-modules-5.0.0-1040-oem-osp1  N/A
   linux-firmware   1.173.14
  Tags:  bionic
  Uname: Linux 5.0.0-1040-oem-osp1 x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/24/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.6
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.6:bd12/24/2019:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct31:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1831587] Re: brightness control not work with OLED panel

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  brightness control not work with OLED panel

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  image: disco 19.04
  kernel: 5.0.0-15-generic
  also verified failed on linux-image-unsigned-5.2.0-050200rc2-generic

  also refer to :
   - 
https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness
   - https://bugs.freedesktop.org/show_bug.cgi?id=97883

  Linux can not control the brightness on the OLED panel in the traditional way 
[1].
  Although there's a workaround from the community [2] that to execute script 
while brightness hotkey event is triggered. But if we want to upstream it, it's 
still a problem to recognize the OLED panel so that the system knows when to go 
workaround.
   - EDID of my laptop which has OLED: https://paste.ubuntu.com/p/w7rVqJTYDy/
   - EDID of the same model without OLED: https://paste.ubuntu.com/p/P3ChhX9yBJ/

  there's a kernel patch related OLED for reference:
   - https://patchwork.kernel.org/patch/6133471/

  [1] https://wiki.ubuntu.com/Kernel/Debugging/Backlight
  [2] 
https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness

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

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

[Kernel-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1813877] Re: Can't adjust brightness on DELL UHD dGPU AIO

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Can't adjust brightness on DELL UHD dGPU AIO

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The dell-uart-backlight driver has been loaded, but the backlight is 
controller by graphics driver instead of scalar IC. The old way to determinate 
weather the driver should be loaded is not working anymore, since the behavior 
of scalar command, show firmware version, is not the same as old platforms.

  [Fix]
  Using more a reliable command, get_scalar_status, to check if scalar is in 
charge of the AIO backlight.
  For the old platforms which don't have the new command, I add a list to list 
them all and use the old way to determinate the scalar IC. 

  [Test]
  Verified on old and new Dell AIO platforms.

  [Regression Potential]
  Low. The quirk lists all old platforms which use the old way to check if 
scalar IC is in use. So, it won't change the behavior on old platforms, and 
apply the new method on new platforms.

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

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

[Kernel-packages] [Bug 1859387] Re: intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and cnl

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  intel/sof: update the intel sof firmware to v1.3-0f73628 for cml and
  cnl

Status in OEM Priority Project:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  Intel released a new version sof firmware to Canonical, they suggested
  that we should integrate the version v1.3-0f73628 and we should only
  pick the cml and cnl firmwares since other firmwares are not fully
  tested. Since we have a couple of Lenovo and Dell cnl and cml machines
  which need to enable sof driver, we integrate the firmwares to
  ubuntu.

  [Fix]
   - fix the hang issue in the firmware for the cml and cnl
   - introduce the ldc file which helps to do the firmware debug
   - divide the firmware to cml and cnl specific ones

  
  [Test Case]
  These firmwares are already widely used in oem project, the audio
  functions worked very well under both Lenovo and Dell dmic machines.

  [Regression Risk]
  Low, Intel released these firmware to us, and we already did large
  numbers audio test in the oem project.

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

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

[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  alsa/sof: load different firmware on different platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware)
  on all platforms, but mainline kernel already supported the multi
  firmwares on differnt platforms, and OEM project needs us to
  support the mutli-firmware names in the ubuntu kernel

  [Fix]
  cherry-pick 3 upstream patches, then on cnl platforms, it will
  load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl
  platforms, it will load sof-cfl.ri

  
  [Test Case]
  Prepare the firmware from https://github.com/thesofproject/linux-firmware
  master branch, then boot the kernel with these patches.

  [Regression Risk]
  Low, just let different platforms load differnt firmware, and these
  patches are in the upstream kernel.

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

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

[Kernel-packages] [Bug 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  linux-oem 4.15 can not suspend to idle XPS-13-9380

Status in OEM Priority Project:
  New
Status in linux-signed-oem package in Ubuntu:
  New

Bug description:
  it somehow s2i failed, from message , it seems the s2i process be
  blocked by thunderbolt device.

  dmesg:
  [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response 
from device
  [193141.012736] PM: noirq suspend of devices failed
  [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809
  [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118
  [193141.872317] thunderbolt :05:00.0: control channel starting...

  Not sure is it relative that I hot plug out WD19 docking before
  suspend.

  reproduce rate:
  random

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50
  ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18
  Uname: Linux 4.15.0-1045-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 00:02:08 2019
  InstallationDate: Installed on 2019-08-11 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed-oem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

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

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

[Kernel-packages] [Bug 1800413] Re: It can not use nvidia-settings to switch from the power saving mode to the performance mode

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  It can not use nvidia-settings to switch from the power saving mode to
  the performance mode

Status in NVIDIA Drivers Ubuntu:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I try to use nvidia-settings 410.73-0ubuntu0~gpu18.04.1 in 
ppa:graphics-drivers/ppa to switch from the power saving mode to the 
performance mode on Ubuntu 18.04.
  But it failed.

  
  $ nvidia-settings

  ERROR: NVIDIA driver is not loaded

  ERROR: Unable to load info from any available system
  

  However `prime-select nvidia` still works fine and there is no such
  issue by nvidia-settings 390.77-0ubuntu0.18.04.1 in bionic-updates.

  Private Bug: https://bugs.launchpad.net/bugs/1800081

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800413/+subscriptions

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

[Kernel-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  Updated Description to match SRU requirements for bionic

  [Impact]
  linux-firmware doesn't install any package hooks for apport, so it will only 
carry some default items leaving hardware list, kernel messages unattached. 
Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to 
source_linux.py as other linux image debs do in bug 1847967.

  [Test Case]
  1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'.
  2) Choose 'View report'
  3) Observe that 'ProcFB' is not collected

  With the version of apport from -proposed 'ProcFB' will be in the
  report.

  
  [Regression Potential]
  Very limited, as we are just adding a symlink from linux-firmware to the 
linux source package hook. this change has been available in Focal and Groovy 
without problem


  Original Description
  
  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:

  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: allSourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:

  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work

[Rex Tsai]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  OBSOLETE_BY in DKMS.CONF does not work

Status in DKMS:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released
Status in dkms source package in Disco:
  Fix Released

Bug description:
  [Impact]
  OBSOLETE_BY in DKMS.CONF not work
  Which also be reported on upstream:
  https://github.com/dell/dkms/issues/81

  [Test case]
  1. add OBSOLETE_BY in DKMS.CONF
  e.g. OBSOLETE_BY="4.15.0-1033"
  2. the kernel module should not be built with kernel greater than the version 
specified by OBSOLETE_BY
  e.g.
   - user install kernel 4.15.0-1030 and 4.15.0-10360
   - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which 
has OBSOLETE_BY="4.15.0-1033"
   - the kernel module from dkms [1] should only built for 4.15.0-1030, but not 
for 4.15.0-10360

  [Regression potential]
  None as it used to work, but somehow regression there.

  [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm-
  ath10k-lp1803647-4.15-dkms-daily

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

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

[Kernel-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

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

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

[Kernel-packages] [Bug 1839124] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT
  advertising packet wakes up the system from S3 and suspend-to-idle

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A generic issue which happens on Intel BT(8087:0aaa) and Atheros 
BT(0cf3:e005)(0cf3:e007).
  Once the system has paired with BT4 devices(disconnected), the system will be 
waken up randomly from S3/s2idle while receiving advertising packet from any 
random BT4 devices in the environment which are even not paired/connected.

  By removing all previously paired BT4 devices(disconnected) from BT
  menu can fix this issue.

  The advertising packet could be none connectable undirected or
  connectable undirected.

  And the BT4 devices we found can reproduce this issue are
  1. Microsoft Surface 1678
  2. Logitech K375s
  3. Microsoft Designer Mouse
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1539 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0FN010
  dmi.board.vendor: Dell Inc.
  dmi.board.version: D02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1844798] Re: [SRU][OEM-B]UBUNTU: SAUCE: enable adjusting brightness on some samsung OLED panels

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [SRU][OEM-B]UBUNTU: SAUCE: enable adjusting brightness on some samsung
  OLED panels

Status in OEM Priority Project:
  New
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  SRU justification:

  [Impact]
  OLED backlight is not supported by the current kernel.
  brightness can't be adjusted.

  [Fix]
  Fix max brightness value;
  Follow samsung panel's spec to enable dpcd and
  support adjusting brightness on OLED.

  [Test]
  Verified on several laptops, backlight on and brightness is adjusted.

  [Regression Potential]
  Medium, change is limited to specific hardware feature.
  Verified on no dpcd support laptops, no regression found yet.

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

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

[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting

[Rex Tsai]

** Changed in: oem-priority
   Status: New => Won't Fix

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

Title:
  Kernel wrong temperature reporting

Status in OEM Priority Project:
  Won't Fix
Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board

[Kernel-packages] [Bug 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  amdgpu kernel module should be used instead of radeon on amd graphic

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  there're some graphic be supported both on amdgpu and radeon.
  But somehow kernel might pick radeon instead of amdgpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem 4.15.0.1057.61
  ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18
  Uname: Linux 4.15.0-1057-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Oct  8 03:33:43 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97
  InstallationDate: Installed on 2019-10-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: linux-meta-oem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [Focal] No HDMI output through thunderbolt docking station

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I can find monitor in display list, but no output from it.
  Also, I can't switch to extend mode, it failed to apply the setting and 
switched back to mirror mode.

  [Steps]
  1. Connect a thunderbolt docking station to thunderbolt port.
  2. Connect HDMI monitor to HDMI port on the docking station.
  3. Switch mode in display setting

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 16:44:40 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2020-04-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=98c0c28f-278e-442b-8fc9-6d663bacd68d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd01/08/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  usb-audio: the mic can't record any sound after resume on Dell Dock
  WD19

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  There is a heaset jack on the dock, after resume, the mic on that jack
  can't record sound anymore, need to close the recording app then reopen
  that app to workaround this issue.

  [Fix]
  set the interface and EP, then the mic can record sound again.

  
  [Test Case]
  test the kernel with this patch, the mic can record sound after resume.

  [Regression Risk]
  Low, this quirk is specific to WD19 (usb vednor and device id).

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

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

[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-AC [1a56:143a]: Disabling wifi causes kernel warning in __sta_info_destroy_part2

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-
  AC [1a56:143a]: Disabling wifi causes kernel warning in
  __sta_info_destroy_part2

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have multiple issues with wifi on my Dell XPS 9380.
  This error was triggered when I tried to disable my wifi.

  [ 3634.322471] [ cut here ]
  [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 
__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep 
binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi 
dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio 
ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep 
snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi 
usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo 
videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev 
snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth 
mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc 
wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 
soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device 
ucsi_acpi typec_ucsi mei_me intel_rapl_common
  [ 3634.322564]  intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf 
intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal 
mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt 
usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 
ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper 
drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 
fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid 
virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel
  [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G   OE  
   5.4.0-21-generic #25-Ubuntu
  [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 
12/11/2019
  [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211]
  [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 
00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 
2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
  [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282
  [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: 

  [ 3634.322640] RDX: 90061ba3c740 RSI:  RDI: 
900613a62f48
  [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 
0004
  [ 3634.322642] R10:  R11:  R12: 
900613f28000
  [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 
900613a60d68
  [ 3634.322644] FS:  7f596b396240() GS:90061e4c() 
knlGS:
  [ 3634.322645] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 
003606e0
  [ 3634.322647] Call Trace:
  [ 3634.322670]  __sta_info_flush+0x128/0x180 [mac80211]
  [ 3634.322696]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
  [ 3634.322719]  ieee80211_mgd_deauth+0x104/0x490 [mac80211]
  [ 3634.322743]  ieee80211_deauth+0x18/0x20 [mac80211]
  [ 3634.322782]  cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211]
  [ 3634.322804]  cfg80211_mlme_down+0x66/0x80 [cfg80211]
  [ 3634.322823]  cfg80211_disconnect+0x127/0x1e0 [cfg80211]
  [ 3634.322827]  ? _raw_spin_unlock_bh+0x1e/0x20
  [ 3634.322845]  __cfg80211_leave+0x133/0x1b0 [cfg80211]
  [ 3634.322862]  cfg80211_leave+0x2c/0x40 [cfg80211]
  [ 3634.322879]  cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211]
  [ 3634.322902]  ? ath10k_warn.cold+0x1a/0x1f [ath10k_core]
  [ 3634.322911]  ? ath10k_config_ps+0x52/0x70 [ath10k_core]
  [ 3634.322913]  ? rtnl_is_locked+0x15/0x20
  [ 3634.322917]  ? inetdev_event+0x47/0x560
  [ 3634.322919]  ? skb_dequeue+0x5a/0x70
  [ 3634.322923]  notifier_call_chain+0x55/0x80
  [ 3634.322925]  raw_notifier_call_chain+0x16/0x20
  [ 3634.322927]  call_netdevice_notifiers_info+0x2e/0x60
  [ 3634.322929]  __dev_close_many+0x63/0x120
  [ 3634.322931]  dev_close_many+0x91/0x150
  [ 3634.322933]  dev_close.part.0+0x4a/0x70
  [ 3634.322936]  dev_close+0x18/0x20
  [ 3634.322955]  cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211]
  [ 3634.

[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Fix I219 doesn't get woken up after plugging ethernet cable

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Plugging ethernet cable doesn't work on new I219 after it runtime
  suspends to D3.

  [Fix] 
  Intel confirms that it only supports D0, so disable runtime power
  management to prevent it from entering D3.

  [Test]
  Once the patch applied, the device always stays at D0, which doesn't
  have this problem.

  [Regression Potential]
  Low. This doesn't introduce any functional change.

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

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

[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  ath10k_pci crashing

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  The below happens on a regular basis on my DELL XPS 13 9380:

  [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 
[ath10k_core]
  [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 
85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 
db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 
  [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246
  [77451.338533] RAX:  RBX: 9d97b7c12290 RCX: 
9d96cbfd5528
  [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 
9d9944c51de0
  [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: 

  [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 
9d9944c51520
  [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 
9d996e503e28
  [77451.338540] FS:  () GS:9d996e50() 
knlGS:
  [77451.338541] CS:  0010 DS:  ES:  CR0: 80050033
  [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 
003606e0
  [77451.338543] Call Trace:
  [77451.338545]  
  [77451.338557]  ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core]
  [77451.338561]  ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci]
  [77451.338563]  ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci]
  [77451.338567]  ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci]
  [77451.338571]  net_rx_action+0x140/0x3a0
  [77451.338575]  __do_softirq+0xe4/0x2d4
  [77451.338580]  irq_exit+0xc5/0xd0
  [77451.338582]  do_IRQ+0x8a/0xe0
  [77451.338585]  common_interrupt+0xf/0xf
  [77451.338586]  
  [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0
  [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 
31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d 
d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 
  [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: 
ffde
  [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 
001f
  [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: 

  [77451.338625] RBP: af4601993e90 R08: 0002 R09: 
000224c0
  [77451.338626] R10: af4601993e20 R11: 00d9 R12: 
0004
  [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: 

  [77451.338630]  cpuidle_enter+0x17/0x20
  [77451.338632]  call_cpuidle+0x23/0x40
  [77451.338634]  do_idle+0x204/0x280
  [77451.338636]  cpu_startup_entry+0x73/0x80
  [77451.338639]  start_secondary+0x1ab/0x200
  [77451.338642]  secondary_startup_64+0xa5/0xb0
  [77451.338643] ---[ end trace 22914e3b3a848f81 ]---
  [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2

  $ uname -a
  Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  $ modinfo ath10k_pci
  filename:   
/lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
  firmware:   ath10k/QCA9377/hw1.0/board.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA9377/hw1.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/board-2.bin
  firmware:   ath10k/QCA6174/hw3.0/board.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-6.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-5.bin
  firmware:   ath10k/QCA6174/hw3.0/firmware-4.bin
  firmware:   ath10k/QCA6174/hw2.1/board-2.bin
  firmware:   ath10k/QCA6174/hw2.1/board.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-5.bin
  firmware:   ath10k/QCA6174/hw2.1/firmware-4.bin
  firmware:   ath10k/QCA9887/hw1.0/board-2.bin
  firmware:   ath10k/QCA9887/hw1.0/board.bin
  firmware:   ath10k/QCA9887/hw1.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/board-2.bin
  firmware:   ath10k/QCA988X/hw2.0/board.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-5.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-4.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-3.bin
  firmware:   ath10k/QCA988X/hw2.0/firmware-2.bin
  license:Dual BSD/GPL
  description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB 
devices
  author: Qualcomm Atheros
  srcversion: D49EBAB0107B6CE28383BB8
  alias:  pci:v168Cd0050sv*sd*bc*sc*i*
  alias:  pci:v168Cd0042sv*sd*bc*sc*i*
  alias:  pci:v168Cd0046sv*sd*bc*sc*i*
  alias:  pci:v168Cd0056sv*sd*bc*sc*i*
  alias:  pci:v168Cd0040sv*sd*bc*sc*i*
  alias:  pci:v168C

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 
12133 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12140]: Reached target Sockets

[Kernel-packages] [Bug 1741166] Re: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]
  QCA6174A XR can scan but can't pair with bt 4.0 device.

  [Fix]
  [0cf3:e010] is one of the QCA ROME family and should be listed in btusb 
driver.

  [Test Case]
  Applied the patch and can pair with bt 4.0 keyboard without any issue.

  [Regression Potential]
  Adding the device to the list won't have any regression potential.

  impacted tickets:
  LP: #1736330
  LP: #1742849

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

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

[Kernel-packages] [Bug 1876066] Re: Support Intel TGL CPU on Focal

[Rex Tsai]

** Tags added: oem-priority

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  Support Intel TGL CPU on Focal

Status in OEM Priority Project:
  Fix Released
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Focal:
  Fix Released
Status in thermald source package in Groovy:
  Fix Released

Bug description:
  [impact]

  thermald doesn't support Tiger Lake cpus

  [test case]

  run thermald on Tiger Lake cpu

  It can be checked by following command, and the patch works if it return 
"passed".
  $ systemctl is-active --quiet thermald && echo passed

  [regression potential]

  because TGL is not supported by current thermald, so thermald always inactive 
on TGL platform. This patch is to activate it.
  So, there's not potential regression.

  [scope]

  needed for F/G

  [original description]

  need the patch to support Intel TGL CPU on Focal

  https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666

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

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