This bug was fixed in the package linux - 5.11.0-11.12
---------------
linux (5.11.0-11.12) hirsute; urgency=medium
* hirsute/linux: 5.11.0-11.12 -proposed tracker (LP: #1917335)
* Packaging resync (LP: #1786013)
- update dkms package versions
- [Packaging] update variants
* Support no udeb profile (LP: #1916095)
- [Packaging] replace custom filter script with dctrl-tools
- [Packaging] correctly implement noudeb build profiles.
* Miscellaneous Ubuntu changes
- [Packaging] dkms-versions -- remove nvidia-graphics-drivers-440-server
- [Debian] run ubuntu-regression-suite for linux-unstable
- [Packaging] remove Provides: aufs-dkms
- [Packaging] Change source package name to linux
- [Config] update gcc version in config due to toolchain update
* Miscellaneous upstream changes
- Revert "UBUNTU: [Config] disable nvidia and nvidia_server builds"
- Xen/x86: don't bail early from clear_foreign_p2m_mapping()
- Xen/x86: also check kernel mapping in set_foreign_p2m_mapping()
- Xen/gntdev: correct dev_bus_addr handling in gntdev_map_grant_pages()
- Xen/gntdev: correct error checking in gntdev_map_grant_pages()
- xen/arm: don't ignore return errors from set_phys_to_machine
- xen-blkback: don't "handle" error by BUG()
- xen-netback: don't "handle" error by BUG()
- xen-scsiback: don't "handle" error by BUG()
- xen-blkback: fix error handling in xen_blkbk_map()
- tty: protect tty_write from odd low-level tty disciplines
- Bluetooth: btusb: Always fallback to alt 1 for WBS
- media: pwc: Use correct device for DMA
- bpf: Fix truncation handling for mod32 dst reg wrt zero
- HID: make arrays usage and value to be the same
- USB: quirks: sort quirk entries
- usb: quirks: add quirk to start video capture on ELMO L-12F document
camera
reliable
- ntfs: check for valid standard information attribute
- Bluetooth: btusb: Some Qualcomm Bluetooth adapters stop working
- arm64: tegra: Add power-domain for Tegra210 HDA
- hwmon: (dell-smm) Add XPS 15 L502X to fan control blacklist
- KVM: x86: Zap the oldest MMU pages, not the newest
- KVM: do not assume PTE is writable after follow_pfn
- mm: provide a saner PTE walking API for modules
- KVM: Use kvm_pfn_t for local PFN variable in hva_to_pfn_remapped()
-- Andrea Righi <[email protected]> Mon, 01 Mar 2021 18:17:45
+0100
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1914543
Title:
Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid
driver
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
Device sensors attached to Intel Integrated Sensor Hub (ISH) on TGL-H
platforms are not detected due to the lack of corresponding PCI ID in
intel-ish-hid driver.
[Fix]
Add PCI ID 8086:43FC the intel-ish-hid driver. Fix also proposed to
linux-input mailing list as
https://patchwork.kernel.org/project/linux-input/patch/[email protected]/
[Test Case]
On the affected platforms, sensors should be probed with this patch
applied:
$ dmesg | grep ish
ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]:
enum_devices_done OK, num_hid_devices=3
hid-generic 001F:8087:0AC2.0003: hidraw2: <UNKNOWN> HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0004: hidraw3: <UNKNOWN> HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0005: hidraw4: <UNKNOWN> HID v2.00 Device
[hid-ishtp 8087:0AC2] on
$ ls -1 /sys/bus/iio/devices/
iio:device0
iio:device1
trigger0
trigger1
[Where problems could occur]
While this would bring up sensor hub and sensors attached to this
platform, it might affect system power consumption, and might introduce
unexpected behavior if an unsupported/misbehaved sensor is up.
========== Original Bug Description ==========
Following PCI device not recognized by intel-ish-hid driver:
00:12.0 Serial controller [0700]: Intel Corporation Device [8086:43fc]
(prog-if 00 [8250])
Subsystem: Dell Device [1028:0a66]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at 6073170000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] Vendor Specific Information: Len=14 <?>
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-oem (not installed)
ProcVersionSignature: Ubuntu 5.10.0-1010.11-oem 5.10.6
Uname: Linux 5.10.0-1010-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: u 1900 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 4 14:34:09 2021
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-pidgeot-14+X81
InstallationDate: Installed on 2021-01-22 (13 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: Dell Inc. Latitude 5421
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1010-oem
root=UUID=75317576-b181-4bb4-bdd6-b2911ff95aa2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1010-oem N/A
linux-backports-modules-5.10.0-1010-oem N/A
linux-firmware 1.187.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2020
dmi.bios.release: 99.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 99.2.3
dmi.board.name: 020BN6
dmi.board.vendor: Dell Inc.
dmi.board.version: X01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr99.2.3:bd12/02/2020:br99.2:svnDellInc.:pnLatitude5421:pvr:rvnDellInc.:rn020BN6:rvrX01:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5421
dmi.product.sku: 0A66
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1914543/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
