Support for Intel Discrete Gale Peak2/BE200

Bug #2028065 reported by You-Sheng Yang
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
New
Undecided
Unassigned
OEM Priority Project
New
Undecided
Unassigned
linux (Ubuntu)
Fix Released
High
You-Sheng Yang
Jammy
Invalid
Undecided
Unassigned
Mantic
Fix Released
High
You-Sheng Yang
linux-firmware (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Incomplete
High
You-Sheng Yang
Mantic
Incomplete
High
You-Sheng Yang
linux-oem-6.5 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
High
You-Sheng Yang
Mantic
Invalid
Undecided
Unassigned

Bug Description

[SRU Justification]

========== linux-firmware ==========

[Impact]

Missing firmware for Intel BE200 on Intel Meteor Lake platform.

[Fix]

2 upstream commits needed, and the iwlwifi firmware one is in the pull request
for bug 2037390 (Add firmware for Intel CNVi AX211 on Intel Meteor Lake
platform). Rebased the second one onto PR for bug 2037390.

[Test Case]

Boot with firmware blobs installed, and iwlwifi and btintel should probe
successfully without error.

[Where problems could occur]

While this introduces support for new hardware on new platforms, expect every
possible problem.

[Other Info]

We're to support oem-6.5/jammy, and mantic for best effort. While there is no
Noble branch yet, Noble is not nominated.

While this is rebased onto PR for bug 2037390, it makes that PR a prerequisite
to this one.

========== kernel ==========

[Impact]

Missing Intel Gale Peak WiFi/Bluetooth support.

[Fix]

WIFI:
a. kernel driver :
   - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix
     crash") [v6.5-rc2]
b. firmware (to be released):
   - ES
     - iwlwifi-gl-b0-fm-b0-83.ucode
     - iwlwifi-gl-b0-fm-b0.pnvm
   - QS
     - iwlwifi-gl-c0-fm-c0-83.ucode
     - iwlwifi-gl-c0-fm-c0.pnvm

Bluetooth:
a. kernel driver:
   - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
   - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
   - ES
     - intel/ibt-0191-0191.sfi
     - intel/ibt-0191-0191.ddc
   - QS
     - intel/ibt-0291-0291.sfi
     - intel/ibt-0291-0291.ddc

[Test Case]

To boot with patched kernel and prereleased firmware blob and check basic
WiFi/Bluetooth functions.

[Where problems could occur]

New device. Expect incomplete functions and bugs.

[Other Info]

Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.

========= original bug report ==========

WIFI:
a. kernel driver :
   - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix crash") [v6.5-rc2]
b. firmware (to be released):
   - iwlwifi-gl-b0-fm-b0-83.ucode
   - iwlwifi-gl-b0-fm-b0.pnvm

Bluetooth:
a. kernel driver:
   - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak")
   - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)")
b. firmware (to be released):
   - intel/ibt-0191-0191.sfi
   - intel/ibt-0191-0191.ddc

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Kernel patches are in linux-next, but not in v6.5-rcX.

Changed in linux (Ubuntu Jammy):
status: New → Invalid
tags: added: oem-priority originate-from-2012807 somerville
Revision history for this message
You-Sheng Yang (vicamo) wrote :

Added to:
* https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/experimental-unstable
  - linux-unstable/mantic version 6.5.0-9001.1+exp.2
* https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/linux-firmware-staging
  - linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.15+exp.74
  - linux-firmware/mantic version 20230629.gitee91452d-0ubuntu1+exp.4

Juerg Haefliger (juergh)
tags: added: kern-7468
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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

apport-collect 2028065

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

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

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

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: originate-from-2032161
You-Sheng Yang (vicamo)
description: updated
Changed in linux-firmware (Ubuntu Jammy):
status: New → Incomplete
Changed in linux-firmware (Ubuntu Mantic):
status: New → Incomplete
Changed in linux-oem-6.5 (Ubuntu Mantic):
status: New → Invalid
Changed in linux-oem-6.5 (Ubuntu Jammy):
assignee: nobody → You-Sheng Yang (vicamo)
importance: Undecided → High
status: New → In Progress
Changed in linux (Ubuntu Mantic):
assignee: nobody → You-Sheng Yang (vicamo)
importance: Undecided → High
status: Incomplete → In Progress
You-Sheng Yang (vicamo)
description: updated
Revision history for this message
You-Sheng Yang (vicamo) wrote :
description: updated
Timo Aaltonen (tjaalton)
Changed in linux-oem-6.5 (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (62.8 KiB)

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1004.4

---------------
linux-oem-6.5 (6.5.0-1004.4) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1004.4 -proposed tracker (LP: #2036238)

  * Infiniate systemd loop when power off the machine with multiple MD RAIDs
    (LP: #2036184)
    - SAUCE: md: do not _put wrong device in md_seq_next

  * dell-uart-backlight fails to communicate with the scalar IC somtimes.
    (LP: #2035299)
    - SAUCE: platform/x86: dell-uart-backlight: add small delay after write
      command

  [ Ubuntu: 6.5.0-6.6 ]

  * mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595)
  * Mantic update: v6.5.3 upstream stable release (LP: #2035588)
    - drm/amd/display: ensure async flips are only accepted for fast updates
    - cpufreq: intel_pstate: set stale CPU frequency to minimum
    - tpm: Enable hwrng only for Pluton on AMD CPUs
    - Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
    - Revert "fuse: in fuse_flush only wait if someone wants the return code"
    - Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
    - Revert "PCI: tegra194: Enable support for 256 Byte payload"
    - Revert "net: macsec: preserve ingress frame ordering"
    - reiserfs: Check the return value from __getblk()
    - splice: always fsnotify_access(in), fsnotify_modify(out) on success
    - splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice
    - splice: fsnotify_access(in), fsnotify_modify(out) on success in tee
    - eventfd: prevent underflow for eventfd semaphores
    - fs: Fix error checking for d_hash_and_lookup()
    - iomap: Remove large folio handling in iomap_invalidate_folio()
    - tmpfs: verify {g,u}id mount options correctly
    - selftests/harness: Actually report SKIP for signal tests
    - vfs, security: Fix automount superblock LSM init problem, preventing NFS sb
      sharing
    - ARM: ptrace: Restore syscall restart tracing
    - ARM: ptrace: Restore syscall skipping for tracers
    - btrfs: zoned: skip splitting and logical rewriting on pre-alloc write
    - erofs: release ztailpacking pclusters properly
    - locking/arch: Avoid variable shadowing in local_try_cmpxchg()
    - refscale: Fix uninitalized use of wait_queue_head_t
    - clocksource: Handle negative skews in "skew is too large" messages
    - powercap: arm_scmi: Remove recursion while parsing zones
    - OPP: Fix potential null ptr dereference in dev_pm_opp_get_required_pstate()
    - OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
    - selftests/resctrl: Add resctrl.h into build deps
    - selftests/resctrl: Don't leak buffer in fill_cache()
    - selftests/resctrl: Unmount resctrl FS if child fails to run benchmark
    - selftests/resctrl: Close perf value read fd on errors
    - sched/fair: remove util_est boosting
    - arm64/ptrace: Clean up error handling path in sve_set_common()
    - sched/psi: Select KERNFS as needed
    - cpuidle: teo: Update idle duration estimate when choosing shallower state
    - x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
    - arm64/fpsimd: Only provide the length to cpufeature for xCR registers
    - sched/rt: Fix sysctl_sched_rr_timeslice in...

Changed in linux-oem-6.5 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.5.0-7.7

---------------
linux (6.5.0-7.7) mantic; urgency=medium

  * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611)

  * kexec enable to load/kdump zstd compressed zimg (LP: #2037398)
    - [Packaging] Revert arm64 image format to Image.gz

  * Mantic minimized/minimal cloud images do not receive IP address during
    provisioning (LP: #2036968)
    - [Config] Enable virtio-net as built-in to avoid race

  * Miscellaneous Ubuntu changes
    - SAUCE: Add mdev_set_iommu_device() kABI
    - [Config] update gcc version in annotations

 -- Andrea Righi <email address hidden> Thu, 28 Sep 2023 10:19:24 +0200

Changed in linux (Ubuntu Mantic):
status: In Progress → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-done-jammy-linux-azure-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-failed-jammy-linux-azure-6.5'.

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

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

tags: added: kernel-spammed-jammy-linux-azure-6.5-v2 verification-needed-jammy-linux-azure-6.5
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'.

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

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

tags: added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5
You-Sheng Yang (vicamo)
description: updated
You-Sheng Yang (vicamo)
Changed in linux-firmware (Ubuntu Jammy):
assignee: nobody → You-Sheng Yang (vicamo)
importance: Undecided → High
status: Incomplete → In Progress
Changed in linux-firmware (Ubuntu Mantic):
assignee: nobody → You-Sheng Yang (vicamo)
importance: Undecided → High
status: Incomplete → In Progress
Changed in linux-firmware (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
You-Sheng Yang (vicamo) wrote :
description: updated
Revision history for this message
You-Sheng Yang (vicamo) wrote (last edit ):

Regression found. To be sorted out.

[ 6.415486] Bluetooth: hci0: Device revision is 0
[ 6.415491] Bluetooth: hci0: Secure boot is enabled
[ 6.415492] Bluetooth: hci0: OTP lock is disabled
[ 6.415493] Bluetooth: hci0: API lock is enabled
[ 6.415494] Bluetooth: hci0: Debug lock is disabled
[ 6.415495] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 6.415497] Bluetooth: hci0: Bootloader timestamp 2022.18 buildtype 1 build 16362
[ 6.425852] Bluetooth: hci0: Found device firmware: intel/ibt-0291-0291.sfi
[ 6.425896] Bluetooth: hci0: Boot Address: 0x100800
[ 6.425897] Bluetooth: hci0: Firmware Version: 113-23.23
[ 6.444273] loop8: detected capacity change from 0 to 8
[ 6.446749] iwlwifi 0000:55:00.0 wlp85s0f0: renamed from wlan0
[ 6.623877] iwlwifi 0000:55:00.0: WRT: Invalid buffer destination
[ 6.624514] r8152 4-1:1.0 enx00e04c69105f: carrier on
[ 7.004818] iwlwifi 0000:55:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
[ 7.253833] rfkill: input handler disabled
[ 8.234350] Bluetooth: hci0: Failed to send firmware data (-38)
[ 8.234393] Bluetooth: hci0: Intel reset sent to retry FW download
[ 8.239077] usb 3-10: USB disconnect, device number 4
[ 8.392720] Bluetooth: hci0: sending frame failed (-19)
[ 8.392732] Bluetooth: hci0: Reading supported features failed (-19)
[ 8.392739] Bluetooth: hci0: Error reading debug features
[ 8.392748] Bluetooth: hci0: sending frame failed (-19)
[ 8.392754] Bluetooth: hci0: Failed to read MSFT supported features (-19)

Changed in linux-firmware (Ubuntu Jammy):
status: In Progress → Incomplete
Changed in linux-firmware (Ubuntu Mantic):
status: In Progress → Incomplete
Andy Chi (andch)
tags: added: originate-from-2042551
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.